On Tuesday, February 27, 2018 at 11:42:38 AM UTC-5, Hughes ll, Rex wrote: > > Hello all, > > > I wanted to reach out to the community and ask for your recommendations > regarding the DC Date element. Our common usage of DC Date include: > > > > - dc.date.issued (publication of the object) > - dc.date.accessioned (resource accessioned into the system; > auto-assigned) > - dc.date.available (date available to public; auto-assigned) > - dc.date.copyright (copyright date of the object) > > > We also have qualifiers in our schema for dc.date.created, > dc.date.submitted, and dc.date.updated that have not been used consistently > in the past. > > > We recently discussed using a qualifier of dc.date.original to > differentiate between the original creation of the content and the > publication date (dc.date.issued); however, I thought many institutions > used dc.date.created in these instances. We did discuss how the term > "created" might be confusing to some users regarding the kind of creation > that occurs (creation of the document or creation of the repository object). > > >
QDC doesn't define date.original. http://dublincore.org/documents/2000/07/11/dcmes-qualifiers/ If I were wanting a new meaning, I would, first, look around to see if someone has already defined it, and add that namespace if so; otherwise, create a local namespace and put it there. Difficulties arise if you expose your metadata to harvesters and the like, because then it matters what other sites think your fields mean. (I'm not a metadata expert, but I do have strong views on interoperability of networked systems.) > A second dilemma we came across was the correct qualifier to use for > revised objects. There was an idea to use dc.date.issued.revised, but I am > wondering if we should simply use dc.date.updated. > > > DSpace's operable metadata support only has two levels: schema.element.qualifier. There's no way to create a sub-qualifier like that. You might consider QDC's date.modified. If you find it unsuitable, then you might also look in DCTERMS http://dublincore.org/documents/dcmi-terms/ which supersedes QDC. Recent DSpace versions come with a DCTERMS namespace. There are other element.qualifier namespaces defined by various organizations, and DSpace makes it fairly easy to add such namespaces. > Thank you for your recommendations, and examples from your systems would > be greatly appreciated. I am fairly new to our current system and would > like to establish more consistent metadata practices than there have been > in the past. > > > *applause* -- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
