Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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!

 

 

Multivote
idmultivote_dshum_1452263847442
sorttrue
resultHeaderNameVotes
ID CMR FeatureDescription
1Fat JSONBuild a JSON response which has all fields in the response
2UMM-P Implement UMM-Parameters in the CMR 
3CSW APIAdd a CSW compliant API 
4Tagging ImprovementsUpdated Tagging Design 
5 REST Based Ordering Be able to order and check order status via REST
6 ComponentsAdd re-usable components to UMM-C for Organizations and Contacts  
7Quality RubricsBe able to assess the quality of an individual metadata record based on adherence to various recommendations such as CSW
8Holdings AnalyticsBe able to run analytics across a provider's holdings to look for areas of inconsistencies or missing fields
10Bulk Update Update a specific field(s) across multiple records with one command 
11HTML Rsp Format Retrieve collections in a well designed / EUI compliant .html format for easy display or hosting
12Facet Improvements  Updated facet response
13Relevancy Improved relevancy based on the work done in the ESDSWG Relevancy Working Group 
14Templated Virtual Product Creation Automate the ability to setup virtual products and make it easily accessible to all providers
15 Fat Granule CSVIncrease 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.
17Allow Ingest with URS TokensCMR is currently only recognizing ECHO tokens for ingest, can it be allowed to use URS tokens for ingest as well?