...
| Topic | Discussion leader |
---|---|---|
1 | News / announcements / etc.
| Val |
2 | Metadata improvements project:
| Metadata Sub-Team: Sarah P., Amy, Maura Valentio, Maureen |
4 | Annual discussion Proposed tweaks on how DCAT works together - what do we want to continue doing, what seems to work well/not so well
|
|
...
1) News/Announcements
Other
Sue: exploring learning object repos - does anyone know of any learning repos using
- Bram: Jorum (also mentioned by Ciaran). Other DSpaces that include OER's (open education resources):
- Ciaran: In relation to using DSpace as a repository of learning objects, the NDLR site in Ireland is at http://www.ndlr.ie, with the repository element available at https://dspace.ndlr.ie. We’ve also been working with MIMAS in the UK on upgrading Jorum which will be re-launching shortly, but the current version of the repository is available at http://resources.jorum.ac.uk/xmlui . Finally we’ve also been working with NCEL in Saudi Arabia to implement a repository based on the NDLR site in English and Arabic which will be launching shortly and which will also be hosting learning objects (https://maknaz.elc.edu.sa, repository at https://dspace.elc.edu.sa).
2) ALA meet up Fri 1/28 eve: Sarah P., Amy - Sarah P. to send msg to see if anyone else is interested
3) Update DC
Sarah P: clarify the the level of lock down
- make additions (qualifiers to elements in the schema) but not allow deleting or modifying fields unless you go through 2 step process - set up in configuration file
- Current default behaviour:
- fields can be added, changed or deleted from any schema
- Proposed default behaviour
- qualifiers can still be added
- entirely new fields can still be added
- existing fields from a standardized schema can not be deleted
- existing fields from a standardized schema can not be altered/abused for something non standard
- Proposed "override" behaviour
- Repository managers can override the new default behaviour by flipping a safety switch in the dspace.cfg
- After flipping the safety switch, they can do changes and deletions to any field in the interface just like before.
- Current default behaviour:
- need for robust upgrade/migration tools
- Sarah to make refinements on proposal
Bram: How does DCAT proposal intergrate with other projects
- "Metadata for All" - fully included in the proposal for metadata enhancement. So no need to ask about both of them in the DCAT proposal
- "Proposal for Metadata Enhancements" - technical description of changes, but seems consistent/aligned w/DCAT proposal
- all DCAT members should review wiki page, make sure it is consistent with DCAT proposals, post questions in comment section at the bottom of the page
- Amy to create wiki page for proposal: Proposal to Update QDC Registry and Add DCTERMS Registry
- Gather JIRA tickets that might be affected by DCAT proposals - put on wiki page w/the proposal - metadata team and Bram
Metadata project 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 key areas to address for the update
- identify proposed direction forward along with the benefits/drawbacks/outstanding questions for cmtrs (and community)
- identify what specifically DSpace DC should be updated to - QDC and flat DCTerms
- identify what if any user modifications will be allowed
- identify any areas/processes that will be affected (forms, imports/exports, etc.) 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
4) DCAT working together
- Iryna: establish discret DCAT/cmtr mtgs - maybe 4x a year
- JIRA vs projects
- new JIRA workflow will help identify places we can help "needs more detail" status category - we can help ask requestor for info
- Val to find out where cmtrs are in the migration process
- Everyone has to somehow fit DCAT work into their real jobs - limited time
- Val to get mtg dates posted
- February 12, 2013
- March 12, 2013
- April 9, 2013
- May 14, 1013
- June 11, 2013
...
| Val/Tim |
Discussion Notes/References
Actions Items from the last meeting
Action Item | Assignee | Deadline |
---|---|---|
Review Proposal for Metadata enhancement wiki page, make sure it is consistent with DCAT proposals, post questions in comment section at the bottom of the page | All DCAT members | Jan 18DONE |
Wiki page for updating DC proposal: Proposal to Update QDC Registry and Add DCTERMS Registry, update per today's discussion | Sarah P. | DONE |
Gather JIRA tickets that might be affected by DCAT proposals - put on wiki page w/the proposal | Metadata sub-team, Bram | Jan 18DONE |
Set mtg with cmtrs to review DC proposal, find out where cmtrs are in the new JIRA workflow migration process | Val | Jan 11DONE |