search

ioos / glider-dac

The IOOS Glider DAC site/scripts/tools
http://gliders.ioos.us/providers/
10 stars 13 forks source link

Redesign of existing deployment registration pages #225

Open kerfoot opened 1 year ago

kerfoot commented 1 year ago

Re-design of the DAC deployment registration pages allowing for data set searches by glider, operator, provider, wmo id, etc. This should extend to the API as well.

benjwadams commented 1 year ago

Deployment IDs form a unique key, so by default these should be used. We can still keep the old hash URLs, but it's much easier to reference a URL using the deployment ID.

kerfoot commented 1 year ago

I strongly disagree with this. From a UI usability perspective, urls are much more helpful, understandable and easy to construct for end users if they refer to the name of the item of interest. Regardless of how the internal search is performed, the url should be built using the registered data sets name, i.e:

https://gliders.ioos.us/providers/users/rutgers/deployment/ru30-20230525T1918

https://gliders.ioos.us/providers/users/rutgers/deployment/6470075f8fe48f000c1faf94

This is particularly important given the current DAC registration app as it is very difficult to find a data set of interest if it was created/registered by another user. Currently, in order to find a deployment not registered by me (rutgers), I have to figure out which data provider registered it, find it from the unordered list of data providers on the right side of the page, click on that data provider and then ^F to search the page for the deployment of interest. All of this can be replaced if I know the name of the data set and can type in:

https://gliders.ioos.us/providers/users/rutgers/deployment/ru30-20230525T1918

benjwadams commented 1 year ago

I strongly disagree with this. From a UI usability perspective, urls are much more helpful, understandable and easy to construct for end users if they refer to the name of the item of interest. Regardless of how the internal search is performed, the url should be built using the registered data sets name, i.e:

https://gliders.ioos.us/providers/users/rutgers/deployment/ru30-20230525T1918

This is actually what I meant, sorry it this wasn't clear.

benjwadams commented 11 months ago

307 implements this, please review that PR.

sarinamann-noaa commented 1 month ago

Implemented as part of https://github.com/ioos/glider-dac/pull/346 will take place when PR is merged after hurricane season