So many great things to work on next, help us understand where you'd like us to start by voting below. You can also edit the page and add a row to the table if we're missing your top need. We plan on opening up voting approx. once every 3 months to feed into our planning cycles. Voting will only be limited for a short period of time, so please vote now!
ID | CMR Feature | Description |
---|
1 | Fat JSON | Build a JSON response which has all fields in the response | 2 | UMM-P | Implement UMM-Parameters in the CMR | 3 | CSW API | Add a CSW compliant API | 4 | Tagging Improvements | Updated Tagging Design | 5 | REST Based Ordering | Be able to order and check order status via REST | 6 | Components | Add re-usable components to UMM-C for Organizations and Contacts | 7 | Quality Rubrics | Be able to assess the quality of an individual metadata record based on adherence to various recommendations such as CSW | 8 | Holdings Analytics | Be able to run analytics across a provider's holdings to look for areas of inconsistencies or missing fields | 10 | Bulk Update | Update a specific field(s) across multiple records with one command | 11 | HTML Rsp Format | Retrieve collections in a well designed / EUI compliant .html format for easy display or hosting | 12 | Facet Improvements | Updated facet response | 13 | Relevancy | Improved relevancy based on the work done in the ESDSWG Relevancy Working Group | 14 | Templated Virtual Product Creation | Automate the ability to setup virtual products and make it easily accessible to all providers | 15 | Fat Granule CSV | Increase the fields supplied in the CSV download to include all granule metadata fields | 16 | DOI Search | Improve CMR's ability to search by DOI. This would involve ensuring DOIs are specified correctly in the metadata also. | 17 | Allow Ingest with URS Tokens | CMR is currently only recognizing ECHO tokens for ingest, can it be allowed to use URS tokens for ingest as well? |
|