Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add fields for information about metadata maintenance #146

Open
mbjones opened this issue Mar 12, 2017 · 1 comment
Open

add fields for information about metadata maintenance #146

mbjones opened this issue Mar 12, 2017 · 1 comment
Labels
bug
Milestone

Comments

@mbjones
Copy link
Contributor

@mbjones mbjones commented Mar 12, 2017


Author Name: Matt Jones (Matt Jones)
Original Redmine Issue: 1991, https://projects.ecoinformatics.org/ecoinfo/issues/1991
Original Date: 2005-02-28
Original Assignee: Matt Jones


This is a request for additional fields regarding metadata maintenance that I am
filing for Xiaoping Wang.

----- Original request from Xiaoping Wang -----------
Dear eml-dev:

As mentioned in my email to Matt and Peter (see below), providing necessary
timestamp inforamtion for the EML metadata document is important not only to
metadata generators but also to metadata users. Both
/eml/dataset/maintenance/description and
/eml/dataset/maintenance/maintenanceUpdateFrequency in EML schemas are used for
description of dataset, not for the metadata document itself. Although we can
use /eml/additionalMetadata to say something about the metadata document, I
believe that the timestamp information about the EML metadata document is so
important that it needs to be highlighted. The following is my recommendataion
about the way you can provide more information about the metadata itself.

In the /eml/dataset/res:ResourceGroup, instead of using metadataProvider as one
of the elements, use metadataInformation as suggested below:

A sequency of
required (comment: inforamtion
about metadata providers is listed here)
required (comment: the date when
the metadata document is originally created)
Optional (comment: this element is
used when the metadata document needs to be updated in the future)
A sequency of
required (comment: the date of last
metadata update)
required (comment: for example, the
endDate for rangeOfDates, numberOfRecords for an entity (table), size of entity
(table)........ These values will be changed after new data are loaded into the
dataset)
required (comment: by comapring
updateFrequency and lastUpdateDate, metadata developers know when they need to
update their metadata document, and metadata users know if the metadata document
describes the most current information about the dataset)

These are the necessary elements that I think they should be provided in EML
metadata document. Hope my recommendation helps.

Thank you very much for your support.

Xiaoping Wang
PMEL /NOAA

---------- End request ----------
The full email thread regarding this request can be seen in the EML-dev email
archive here:
http://www.ecoinformatics.org/pipermail/eml-dev/2005-February/001076.html

@mbjones

This comment has been minimized.

Copy link
Contributor Author

@mbjones mbjones commented Mar 12, 2017


Original Redmine Comment
Author Name: Redmine Admin (Redmine Admin)
Original Date: 2013-03-27T21:18:48Z


Original Bugzilla ID was 1991

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
1 participant
You can’t perform that action at this time.