Attendees
Bram Luyten - @mire
Amy Lana - University of Missouri
...
Maureen Walsh - The Ohio State University
Sarah Molloy - Queen Mary, University of London
Sarah Potvin - Texas A&M University
Valorie Hollister - DuraSpace
Time
- 11:00am Eastern/16:00 UTC
...
| Topic | Discussion leader |
|---|---|---|
1 | DC registry changes: Re: Updating the Qualified Dublin Core registry in DSpace | Metadata Sub-Team: Sarah P., Amy, Maura Valentio, Maureen |
...
Discussion Notes
Key points during the discussion:
Amy
Sarah Potvin
Sarah Malloy
Bram
Maureen
Jim
Bram: Update to DCTerms and DCMI compliance ultimate goal – linked data compliance
Jim: agree – concrete goal to have positive effect on user experience. There are a lot of stds to chose from – need to pick what is useful to end users of DSpace – more likely to influence how people use DSpace in the end – goal of having DSpace work better with linked data – need goals to broaden a bit – look at end result rather than just chosing a std
Maureen
: if goal is better user experience – DCTERMS – how do we do that w/DSpace - incremental step DCTERMS namespace as interium step (due to limitations of data model – has to be 2 steps) cannot assign ranges to values
: want to be moving in a future dir – not QDC – clean up QDC (admin fields, customized fields) and add DCTERMS namespace and eventually move to
Amy
: ; ship DSpace with local registry and admin registry (more actionable, intergral to operation to DSpace)
...
Maureen : add DCTerms namespaceShips , DSpace would ship with 4 metadata schemas: QDC, existing, /local and DCTerms, ETC
Jim: need to provide tools to migrate
Maureen
: more admin help on how to add metadata schema (how to do batch loading, cross walk – need cookbook for other (local) schemas)
...
--ex: item view page – dc.authors or dc.title – defined on item view page – need to discover where dc is hard coded – need to root it out
Maureen: need an update tool to update (oeverlay old) registry to new QDC, DCTerms
Bram
: need cookbooks for 2 main user case: both new users and updating users
...
Jim: funding sources are requiring more of the use and re-use of data – linked metadata is important evolotion
Insert – after dis with develpers, before final proposal to community
Sarah
: would Need Would like someone with DCTerm DCTerms familiarity review the proposal ? - Maureen offered
: - go through mapping
-comfirming : confirming functionality and reqmts around DCTerms
this is what we are prposing for
...
Summary of DCAT proposal:
1) update/upgrade current QDC registry (current is DC
...
/“DCMI Terms”
...
2) add DCTerms namespace – new
...
parellel registry
...
3) Lockdown registries: offer migratory tool
...
to pull out all local
...
customizations, push into new local schema and lock everything else down; make it possible, but not easy
...
to change QDC and DCTerms
Val to set mtg time w/developers
1) Good discussion last month in DCAT mtg, but not much of an asynchronous follow up discussion - how can we best move this forward?Minutes
...
Review of next steps:
1) finalize
...
draft a proposal on updating DC
...
following DCAT feedback (DCAT sub-team
...
: Sarah P., Amy, Maureen, Maura)
- identify main goal (why is it important/why should it be done) and - identify key areas to address for the update
- , identify proposed direction forward along with the benefits/drawbacks/outstanding questions for cmtrs and DCAT, should include:
Goal of update:
identify goal for the update - why is it important/why should it be done (and community) - identify what specifically DSpace DC should be updated to - QDC vs and flat DCTerms
- User Modifications: identify what if any user modifications will be allowed
- Migration / Implementation: identify any areas/processes that will be affected (forms, imports/exports, etc.)
- Other areas?
- 2) hold targeted DCAT discussion - for December DCAT mtg have targeted discussion about the proposal - validating / revising DC sub-team's proposal - Val to poll DCAT to see if everyone is available on Dec 18 or if we need to re-schedule 3) revise proposal based on DCAT discussion and path for migration / implementation
4) discuss proposal with developers/cmtrs to understand limitations/pain points
5) revise proposal based on developer/cmtrs feedback
6) hold discussion / allow for feedback on proposal by DSpace community - and maybe the broader repository community
Val to set mtg time w/developers
Actions Items from this meeting
Action Item | Assignee | Deadline |
|---|---|---|
| Set meeting day/time with Tim / committers to review proposal | Val | Jan ?8 |
Refine draft a proposal | Sarah P., Amy, Maureen, Maura | Jan ?8 |
|
|
|
|
|
|