Versions Compared

Old Version 3

changes.mady.by.user user-b9cd4

Saved on

compared with

New Version Current

changes.mady.by.user user-b9cd4

Saved on

Key

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

...

Section
bordertrue
Column
width50%

Description of Problem

The way that Resource Citation appears in UMM, MMT, and CMR needs to be improved.

Definition of 'Resource Citation':  the text that someone using the collection data in research should use to cite the collection in professional scientific literature. 

DAACs are using Citations according to different formats, and these are at the discretion of the DAAC manager. ESDIS provides guidance for Citations, and the MMT form needs to have some logic to enable these Citations to be formatted correctly. The addition of a Preview button could be added to the MMT form, which shows how the Citation would look, or the card for Citation needs to be revised. Title and Name are not required in the MMT form since these relate to the Collection by default, and logic needs to be introduced to make DOI and RelatedURL either-or.

See https://earthdata.nasa.gov/earth-observation-data/data-citations-acknowledgements for individual DAAC citation rules.

The UMM needs to be revised to ensure that any unnecessary fields have been removed. For each collection, the EDSC needs to display the citation, per NASA guidelines, and using the formats provided by each DAAC.

 

 Issues:

1.Citation block in UMM-C currently contains individual fields which are used to construct the full citation string;  some of these fields are redundant with other collection metadata fields (e.g. dataset title, dataset version, dataset DOI, dataset publisher)

2.DAACs may construct citation strings using individual DAAC choice of order, as long as NASA-required information is present

3.Client (like EDSC) needs an algorithm to construct the citation string from the building blocks; algorithm varies by DAAC

4. Configuration Management:  DAACs are required to list citation text on the landing page for the collection; if the citation text is also maintained in the CMR, we need to decide which is the authoritative source, and we need a process to keep the values in synch.

Column

JIRA Linkage

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyECSE-87

<Ctrl+Shift+J allows you to link to your ECSE JIRA ticket easily.  Replace the ticket above with your ticket>

 

The sections below detail the proposed changes based on the analysis done by the ECSE team:

 

Affected issues include: Issues which require the Citation relation to be better defined:

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyMMT-543

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-392

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-433

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyMMT-438

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-344

Issues which related to Citation format on a DAAC-by-DAAC basis

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-153

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-193

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-153

Issues pertaining to DOI or RelatedURL fields to be used

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyECSE-76

 

Issues pertaining to UMM Citation improvements

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-142

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-145

Recommendation 1: Modify MMT per the recommended changes below. Provide a recommended format example for each DAAC, and invite the DAACs which have not yet particpated in the Beta testing for the MMT form to provide an example ResourceCitation format. Collect these in this wiki page to provide a defined format. Review these against the NASA guidelines included in this page. Update the MMT form to show a preview of the format following saved changes, either in a text string format showing the actual formatted citation, prior to publication of the record. Remove any fields which pertain to PublicationReference (subject to separate JIRA ticket).

Changes to UMM-C fields

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-344

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyECSE-76

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyECSE-65
 

ResourceCitation

Currently:                                                           Change to:

ResourceCitation 
ResourceCitation 
ResourceCitation/CreatorsResourceCitation/Creators
ResourceCitation/Editors 
ResourceCitation/TitleResourceCitation/Title
ResourceCitation/SeriesNameResourceCitation/SeriesName
ResourceCitation/ReleaseDateResourceCitation/ReleaseDate
ResourceCitation/ReleasePlaceResourceCitation/ReleasePlace
ResourceCitation/Publisher 
ResourceCitation/VersionResourceCitation/Version
ResourceCitation/IssueIdentification 
ResourceCitation/DataPresentation 
ResourceCitation/OtherCitationDetails 
ResourceCitation/DOIResourceCitation/DOI
ResourceCitation/DOI/AuthorityResourceCitation/DOI/Authority
ResourceCitation/DOI/DOIResourceCitation/DOI/DOI
ResourceCitation/RelatedURL 
 ResourceCitation/RelatedURL/URLContentType
 ResourceCitation/RelatedURL/Type
 ResourceCitation/RelatedURL/Subtype
ResourceCitation/RelatedURL/Protocol 
ResourceCitation/RelatedURL/Title 
ResourceCitation/RelatedURL/DescriptionResourceCitation/RelatedURL/Description
ResourceCitation/RelatedURL/Caption 
ResourceCitation/RelatedURL/URLResourceCitation/RelatedURL/URL
ResourceCitation/RelatedURL/MimeType 
ResourceCitation/RelatedURL/FileSize 
ResourceCitation/RelatedURL/Size 
ResourceCitation/RelatedURL/Unit 

 

Changes to UMM-Common fields

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyECSE-135

Mappings to DIF, ECHO, ISO

See mapping between DIF9, DIF10, ECHO10 and UMM-C (suggested) below:

 

Current UMM-C Mappings to DIF, ECHO, ISO

See mapping between DIF9, DIF10, ECHO10 and UMM-C (suggested) below:

 

DIF9  DIF10  UMM-C  ECHO10  
ElementsReqCElementsReqCElementsReqCElementsReqC
Data_Set_CitationN0..*Dataset_CitationN0..*Resource Citation N0..*   
Data_Set_Citation/Dataset_CreatorN0..1Dataset_Citation/Dataset_CreatorN0..1ResourceCitation/CreatorsN0..1   
Data_Set_Citation/Dataset_EditorN0..1Dataset_Citation/Dataset_EditorN0..1ResourceCitation/EditorsN0..1   
Data_Set_Citation/Dataset_TitleN0..1Dataset_Citation/Dataset_TitleN0..1ResourceCitation/TitleN0..1   
Data_Set_Citation/Dataset_Series_NameN0..1Dataset_Citation/Dataset_Series_NameN0..1ResourceCitation/SeriesNameN0..1   
Data_Set_Citation/Dataset_Release_DateN0..1Dataset_Citation/Dataset_Release_DateN0..1ResourceCitation/ReleaseDateN0..1   
Data_Set_Citation/Dataset_Release_PlaceN0..1Dataset_Citation/Dataset_Release_PlaceN0..1ResourceCitation/ReleasePlaceN0..1   
Data_Set_Citation/Dataset_PublisherN0..1Dataset_Citation/Dataset_PublisherN0..1ResourceCitation/PublisherN0..1   
Data_Set_Citation/VersionN0..1Dataset_Citation/VersionN0..1ResourceCitation/VersionN0..1   
Data_Set_Citation/Issue_IdentificationN0..1Dataset_Citation/Issue_IdentificationN0..1ResourceCitation/IssueIdentificationN0..1   
Data_Set_Citation/Data_Presentation_FormN0..1Dataset_Citation/Data_Presentation_FormN0..1ResourceCitation/DataPresentationFormN0..1   
Data_Set_Citation/Other_Citation_DetailsN0..1Dataset_Citation/Other_Citation_DetailsN0..1ResourceCitation/OtherCitationDetailsN0..1CitationForExternalPublicationN0..1
Data_Set_Citation/Dataset_DOIN0..1Dataset_Citation/Persistent_IdentifierN0..1ResourceCitation/DOIN0..1   
   Dataset_Citation/Persistent_Identifier/Type (DOI or ARK)Y1DOI onlyN/AN/A   
      ResourceCitation/DOI/AuthorityN0..1   
   Dataset_Citation/Persistent_Identifier/IdentifierY1ResourceCitation/DOI/DOIY1   
      ResourceCitation/RelatedUrlN0..1   
      ResourceCitation/RelatedUrl/ContentType
ResourceCitation/RelatedUrl/Relation		N0..1   
      ResourceCitation/RelatedUrl/ContentType/TypeY1   
      ResourceCitation/RelatedUrl/ContentType/SubtypeN0..1   
      ResourceCitation/RelatedUrl/ProtocolN0..1   
      ResourceCitation/RelatedUrl/TitleN0..1   
      ResourceCitation/RelatedUrl/DescriptionN0..1   
      ResourceCitation/RelatedUrl/Caption 
DIF9  DIF10  UMM-C  ECHO10  
ElementsReqCElementsReqCElementsReqCElementsReqC
Data_Set_CitationN0..*Dataset_CitationN0..*Resource Citation N0..*   
Data_Set_Citation/Dataset_CreatorN0..1Dataset_Citation/Dataset_CreatorN0..1ResourceCitation/CreatorsN0..1   
Data_Set_Citation/DatasetOnline_EditorResourceN0..1Dataset_Citation/DatasetOnline_EditorResourceN0..1ResourceCitation/RelatedUrl/EditorsURLNY01..1*   Data_Set_Citation/Dataset_TitleN0..1Dataset_Citation/Dataset_TitleN0..1ResourceCitation/Title
      ResourceCitation/RelatedUrl/MimeType N0..1   Data_Set_Citation/Dataset_Series_Name
      ResourceCitation/RelatedUrl/FileSize N0..1Dataset_Citation/Dataset_Series_NameN0..1ResourceCitation/SeriesNameN0..1   Data_Set_Citation/Dataset_Release_DateN0..1Dataset_Citation/Dataset_Release_DateN0..1ResourceCitation/ReleaseDateN
      ResourceCitation/RelatedUrl/FileSize/Size 0..1   Data_Set_Citation/Dataset_Release_PlaceN0..1Dataset_Citation/Dataset_Release_PlaceN0..1ResourceCitation/ReleasePlace
      ResourceCitation/RelatedUrl/FileSize/Unit 1  N0..1 

 

 

...

Affected issues include:   Issues which require the Citation relation to be better defined:

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyMMT-543

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-392

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-433

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyMMT-438

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-344

Issues which related to Citation format on a DAAC-by-DAAC basis

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-153

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-193

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-153

Issues pertaining to DOI or RelatedURL fields to be used

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyECSE-76

 

Issues pertaining to UMM Citation improvements

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-142

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-145

 

Possible Solutions:

 Option 1: Keep Citation Block as individual fields, but remove redundant fields

  a. Remove DOI from Citation block

  b. Remove Title and Version (redundant with Entry Title and Version)

  c.  Remove Publisher (redundant with Data Center Long Name, for Role = Distributor)

Changes to UMM-C fields

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyUMMC-344

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyECSE-76

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyECSE-65
 

ResourceCitation

Currently:                                                           Change to:

ResourceCitation 
ResourceCitation 
ResourceCitation/CreatorsResourceCitation/Creators
ResourceCitation/Editors 
ResourceCitation/TitleResourceCitation/Title
ResourceCitation/SeriesNameResourceCitation/SeriesName
ResourceCitation/ReleaseDateResourceCitation/ReleaseDate
ResourceCitation/ReleasePlaceResourceCitation/ReleasePlace
ResourceCitation/Publisher 
ResourceCitation/VersionResourceCitation/Version
ResourceCitation/IssueIdentification 
ResourceCitation/DataPresentation 
ResourceCitation/OtherCitationDetails 
ResourceCitation/DOIResourceCitation/DOI
ResourceCitation/DOI/AuthorityResourceCitation/DOI/Authority
ResourceCitation/DOI/DOIResourceCitation/DOI/DOI
ResourceCitation/RelatedURL 
 ResourceCitation/RelatedURL/URLContentType
 ResourceCitation/RelatedURL/Type
 ResourceCitation/RelatedURL/Subtype
ResourceCitation/RelatedURL/Protocol 
ResourceCitation/RelatedURL/Title 
ResourceCitation/RelatedURL/DescriptionResourceCitation/RelatedURL/Description
ResourceCitation/RelatedURL/Caption 
ResourceCitation/RelatedURL/URLResourceCitation/RelatedURL/URL
ResourceCitation/RelatedURL/MimeType 
ResourceCitation/RelatedURL/FileSize 
ResourceCitation/RelatedURL/Size 
ResourceCitation/RelatedURL/Unit 

 

Changes to UMM-Common fields

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyECSE-135

Option 2. Remove Citation block altogether from UMM-C (and just keep citation on the dataset landing page)

Option 3.  List full citation text in single field, like ECHO, and keep in synch with landing page citation text

...

 

Interoperability Considerations

...

Note that there are specific differences between the fields in the examples and the ISO CI_Citation class fields. For example, edition, editionDate, identifier, citedResponsibePartycitedResponsibleParty, presentationForm, series, otherCitationDetails ISBN, ISSN, and graphic are not in the NASA recommended format. Other fields are present in the NASA recommended format, but not in the ISO CI_Citation class: doi or RelatedURL, and note CI_OnlineResource is not needed as a class, RelatedURL can suffice.

...

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyCMR-2414

What should the MMT forms look like

Recommendation: 

...

keyCMR-2414

What should the MMT forms look like

 

 

...

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyMMT-543

...

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyMMT-437
 

ResourceCitation

>Remove the Title

>Remove the Name

>Move DOI to the Collection Information section of the MMT

>Make DOI and RelatedURL either/or 

 

How should the values in these fields be presented to the user on the EDSC

<Describe changes to EDSC in terms of facet changes, data display changes or functionality changes> 

 

Jira
serverEarthdata Ticketing System
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keyEDSC-441

...

Reconciliation of Existing Metadata values with new rules

tbd

 

Impact of Changes on Ingest of Granule Metadata 

None