search

PASTAplus / DataPortal

EDI Data Portal
3 stars 3 forks source link

consider how we display pubDate #12

Open mobb opened 4 years ago

mobb commented 4 years ago

paraphrased from slack: the new data citation service (https://github.com/PASTAplus/cite) will use the upload year for the citation publication date instead of the internal pubDate (eml/dataset/pubDate). The upload date is when we (EDI) the publisher, published it on EDI.

background: there are not enough date fields in EML to describe every milestone. Some LTER sites use pubDate to hold something more like "dateFirstAvailable". But when people put that into pubDate and then create a new revision of the package, its confusing because you see coverage/endDate that is later than the pubDate

So this means that the citation publication date will often not match the internal pubDate (eml/dataset/pubDate). Therefore, EDI might want to rethink how we display that (eml/dataset/pubDate) with XSL. Because it will probably not match the citation's pubdate and that will be confusing.

mobb commented 4 years ago

If all we change is the field's label, maybe "Local release date" and then it's clearer that it's up to contributors how to define that -- EDI won't use it.

mobb commented 4 years ago

It may be beneficial to include the upload date on the Detailed Metadata page explicitly (as it's not in the EML, it would have to be passed into the stylesheet from pasta).

mobb commented 4 years ago

example of a dataset with mismatched "publication date": https://portal.edirepository.org/nis/mapbrowse?scope=knb-lter-hfr&identifier=243 9:18 https://portal.edirepository.org/nis/metadataviewer?packageid=knb-lter-hfr.243.4

servilla commented 4 years ago

Would it be acceptable for EDI to overwrite any content with the local upload date as this date would represent the true date that the data package was published in the EDI repository. Is there an alternative way to capture and/or disambiguate these dates?