[
https://jira.duraspace.org/browse/DS-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20974#action_20974
]
Tim Donohue commented on DS-805:
--------------------------------
Discussion from Devel Mtg on May 18:
[20:19] <tdonohue> Moving on to next one: DS-805
[20:19] <kompewter> [ https://jira.duraspace.org/browse/DS-805 ] - [#DS-805]
QDC schema registry needs to be brought into conformity with the current DCMI
standards - DuraSpace JIRA
[20:20] <robint> Couldn't disagree but its not a 5 minute job
[20:20] <tdonohue> this is a larger issue, obviously. Metadata schemas is in
our "Topics in Waiting" list for Special Topics meeting
[20:21] <tdonohue> It could also be something we could bring up for some
discussion at our OR11 Dev Mtg, if others are interested
[20:21] <tdonohue> (as the topic of Metadata support may also be of great
interest to folks from DCAT, some of whom will be at the OR11 Dev Mtg)
[20:21] <mhwood> harking back to CC license + embargo: license means it *will
be* freely usable once the embargo is lifted. Embargo is a temporary overlay on
rights.
[20:22] <robint> tdonohue +1
[20:22] <mdiggory> tdonohue: I agree.. Of strong interest to me was well
[20:23] <mdiggory> looking forward to any dialog
[20:23] <tdonohue> Ok. we'll stop there. Seems like agreement that Ds-805 (and
idea of ongoing Metadata support) be "tabled" for some initial discussions at
OR11 Dev Mtg along with DCAT and others. May also warrant a future Special
Topic Mtg after OR11, we'll see
> QDC schema registry needs to be brought into conformity with the current DCMI
> standards
> ---------------------------------------------------------------------------------------
>
> Key: DS-805
> URL: https://jira.duraspace.org/browse/DS-805
> Project: DSpace
> Issue Type: Improvement
> Affects Versions: 1.7.1, 1.8.0
> Reporter: Jeffrey Trimble
> Assignee: Jeffrey Trimble
> Priority: Major
>
> The Qualified Dublin Core registry currently used by DSpace is approximately
> 8 years without changes to the field names/usage. Between the time that
> DSpace 1.1 was distributed and the current time, Dublin Core standards were
> spun off from OCLC as the parent/guardian of the standard to it's own
> Identity, known as DCMI (Dublin Core Metadata Initiative).
> I am suggesting that in a future release, perhaps as early as 1.8 that the
> DSpace Metadata Schema Registry be revised to reflect the newest standards
> for coding metadata using QDC. Additionally, there may be the need to
> convert currently used fields in the registry to the new standard fields for
> existing installations of DSpace. Also, the Lucene and browse indexes would
> be affected by this change.
> There will be a caveat that institutions that have added their own DC fields,
> may need to perform some manual maintenance to adjust their registry tables
> to this new standard.
> I would be happy to put together a spreadsheet with the new standards and
> their counterpart currently used in DSpace.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
