Most (possibly all) uses of the word 'Search' are actually where we want to display fewer items in an existing listing.

Replace the use of 'Search' with 'Filter' wherever this is the case.

tilde can mean 'about' or 'approximately'... just want to define a clean range.

The resources section of the ZMT should have two 'tabs' presenting the same information, but in different ways.

• TableView - existing, with editing and filters available
• HierarchicalView - showing the resource hierarchies (trees) with their parent/child relationships
  • should have drag and drop
  • should have 'folding' or collapsible branches (in case of many resources, too many to see at once, etc)
  • should accumulate 'edits', provide a 'confirm' dialog/page, and then update/refresh
  • should possibly provide an 'undo' stack?

Server context provider can make full use of the new rest api to boost its performance. Implement concurrent operations in server context provider, and handle all fetch requests for user, group and resource page.

I think it will be a better user experience if the filters are case-insensitive instead.

• users
• resources
• groups

similar to #8, these should be lazy loaded and cached on first load of the app.

and live updated on-screen when they change

• Users
• Groups
• Resources

I start the service but can not login to it
Is there something I missed?
I tried with the user and password that I used with REST API and RPC
Thank you

in the configuration for the application...

• iRODS REST API URL (protocol://hostname:port/path)
• allow for specifying an image to serve as a branding logo
  • relative path into a container? absolute URL? not sure here...
  • to be used on login page
  • to be used in title bar
• allow for specifying the colors used in the application
  • main background (default white)
  • titlebar (default iRODS green)
  • active navigation tab (default iRODS green)

It could be an issue when it comes to large scale. Searching by user/group/resc name will help. Some pagination is also in needed.

Refactor environment context provider to store the full rest api url, including subdirectory path '/irods-rest/1.0.0'. Domain part will still load from .env file.

when editing a resource (for example)... it would be nice to hit enter... and the value I typed to be 'saved'.

I think it should also just 'close' the text area and repaint just that resource's details..., not necessarily refresh the entire page... the refresh takes the user away from their search and the resource they were editing... maybe they wanted to edit a second field... this can be a new issue if requires more changes (aka no modal 'success' dialog, etc.)

Currently, you need to click on the hidden arrow beside/under the column name that you want to sort.

Please make the entire title clickable, not just the arrow.

certainly in naming... but also perhaps in color...

possibly another color to be defined for #7

instead of saying
Users
the sidebar should show
Users (13)

And that 13 should be live updated whenever a change is made in the application.

It should be lazy loaded and cached on first load of the app.

so we see http://localhost:9000/groups in the URL instead of /group

• 'resource' -> 'resources'
• 'group' -> 'groups'
• 'user' -> 'users'
• 'server' -> 'servers'

when creating a new resource, the dropdown should be populated with the list of available resource plugin types. This information... is in the zone_report, I believe.

let's see what it looks like with just the lowercase names, too.

new user and new group are currently modal pop-ups.

they should create a new row in the existing table view and await 'save'/'cancel'.

this should work similarly to the 'new resource' behavior.

I accidentally found this bug: when filtering results, the input value will re-render and stay empty all the time which could be confusing. I think it relates to the new loading indicator.. Results are correct, but the input element should display the current value. In other words, all other components should not re-render when typing, only the linear progress indicator should render conditionally.

Auth header in the new rest api has changed. The ZMT controller needs to be updated. Token will be stored in localstorage and old auth context provider will be removed.

During testing, I found that under certain circumstances, the filtering on group page might display all groups after showing initial filtered results. This relates to the request order react context provider sends out.

this should include version number as well as git SHA

could be in the title bar... or an about box... or perhaps in a footer? We don't have a footer for anything else yet.

perhaps with the username in the top right

Have a dialog when clicking the 'remove' button. Let user double-check if that is the one to remove. Should work similar as user/resource page.

• display groupname
• be able to display error message during remove operation

Servers

just like

Users
Groups
Resources

The current list view is not very consist. Having a sort function for each column might be a good idea. Also need to merge edit/remove button into each row of data, having the entire row clickable into editor mode.

from left to right...

• Zone Status
• Servers
• Resources
• Users
• Groups

The current ZMT won't have any redirecting issues when user first login and then forward to home page. But it might have redirecting issues when an authenticated user go back to the login page. In that case, redirected url is pointed to '/home', but not rendering home react component.

Current edit page does not support filtering, which means there is no way for user to find out a group or user among hundreds or thousands. Implementing dynamic filtering function in both edit-user and edit-group page will help. The filter function would also detect whether a user is in this group or not (or a group has this user), and display the functionality accordingly.

Some weird extra space between footer and main component when scrolled down to the bottom and up to the top again:

The footer should stay at the bottom all the time, and main component can be infinite scolling. We could also adding a 'Back to top' button?

• HTML
  • clean up comments
  • have 404 and 5xx error page #47
  • any anchor tag with target="_blank" should have a rel="noopener" attribute to prevent tab nabbing
  • lint check #53
• CSS
  • responsive design, mobile friendly, check at different resolution width<= 768px, 1024px, etc..
  • css validator, and stylelint
  • test on different kernel browsers (Safari, Firefox, Chrome, Internet Explorer, EDGE...)
  • test on mobile browsers
• Image
  • images are optimized to be rendered in the browser
  • width and height are set to limit the rendering
  • have alternative text when image is not available
• Functionality
  • Test with the latest irods client rest api
  • Authentication
  • User/Group Page Scenario
    • Listing + Sorting
    • Add new user/group (various name case) + key event
    • Delete user/group
    • Edit user group
  • Resource Page Scenario
    • Listing + Sorting
    • Add new resource, handle error messages if not created successfully + key event
    • Edit resource attribute, hostname, vault path, context string, comment
    • Remove resource, show error message
    • Treeview Drag and drop
  • Zone report Scenario
    • display all zone data appropriately
• Update README

When filtering users/groups/resources, counts in current sidebar will change over time, showing the filtered results. It should always display the total results.

Like other columns, 'users' column on group page should be numerical sortable.

ZMT should have a 404 error page, so when users hit a url that is not served, it will notify users and provide links back to homepage.

All these resources will be defined for this Zone - no need to list it.

the entered value appears to have been urlencoded before getting into the database.

value "good ideas" became "good+ideas":

Let ZMT use iRODS genquery ordering syntax. ZMT Server context providers should take care of all the logic and query string, and page views (user,group,resoruce) only needs to pass in props (which order and order by which column).

Resource 'demoResc' disappeared after I change items per page from 10 to 25. I suspect it is related to the offset, since demoResc is the first resource in the initial response.

when creating a new resource... i was able to add some spaces or a tab character and they made it into the database... which, due to them being a hostname... made iRODS timeout in talking to all its resources during new connections.

these fields should be trimmed for all whitespace (front and back) before sending to the server.

seen in the screenshot and then in the database... ip-172-31-13-194%20%20

also note the incorrect dialog box...

• "Vault Path" -> "Hostname"
• "Zone" should be dropped from this dialog
• "Vault Path" should be added, with correct value

a booleon OR should be used...

so if the query matches either name OR hostname, it should appear in the result list.

please hide it from the list of resources

it's not really a thing that can/should be edited and it does not interact (parent/child) with any other resources.

on the resource/ page, clicking the sort for 'Vault Path' does not put the vault paths in order... but it's close...

test IP address and port currently hardcoded throughout the code

https://github.com/irods/irods_client_zone_management_tool/search?q=http://

Current ZMT has several eslint warnings and errors, some of which might have a negative impact on performance and security issue. These should be resolved, and web console should be clean for the initial release.

I think... add "Version" between "Role" and "Hostname"

That information is in the details tab already, just need to pull it out front.

Have a green(OK)/red(Error) status bar will help user determine if REST Api deployment or the its url in .env is correct.

Click on the status bar will pop up a new window showing each endpoint status(currently /auth, /zone_report, /admin, /query), along with a retry button for each.

either the navigation should show a different color for the 'page' you're on, or we introduce consistent breadcrumbs near the top of any page to show where the user is in the app.

if we don't have two-levels of navigation (which we do not at the moment)... then an active color in the sidebar is sufficient, and saves space.