DCAT Meeting Agenda January 8, 2013

Potential Attendees

(209) 647-1600, participant code 373133, host code: 560833 (can be done via Skype - for directions: https://wiki.duraspace.org/display/cmtygp/DCAT+Conference+Call+Dial-in).
Please note that we continue to have connectivity issues with the "freeconferencecallhd.2096471600" Skype dial-in. To avoid the frustration we recommend dialing in via a Skype phone call -- simply use the Skype dial pad and dial the USA # 209-647-1600 and then the conference code # as prompted. You will need to have a Skype account with money in it in order to place this kind of call -- and it will likely be about 3 cents a minute, depending on where you are calling from.

	Topic	Discussion leader
1	News / announcements / etc.	Val
2	Midwinter ALA DCAT meet up? (Seattle, January 25-28) - who is going? please use DCAT list to arrange time/place	Val
3	Metadata improvements project: Review summary for committers "Recommendations towards Updating the Qualified Dublin Core registry in DSpace to the latest standards of the DCMI" Proposal for DSpace metadata registry update cmtrs (1 4 2013).docxrecap of next steps	Metadata Sub-Team: Sarah P., Amy, Maura Valentio, Maureen
4
4	Annual discussion on how DCAT works together - what do we want to continue doing, what seems to work well/not so well	Val

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