You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Attendees

Amy Lana - University of Missouri

Jim Ottaviani - University of Michigan

Maureen Walsh - The Ohio State University

Valorie Hollister - DuraSpace

 

Time

  • 11:00am Eastern/16:00 UTC

Dial-in

  • (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 have been having lots of connectivity issues with the "freeconferencecallhd.2096471600" Skype dial-in lately. Generally you can get on, but Skype seems to boot you off at regular intervals. 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. We are looking for other solutions to the problem -- and also for your suggestions if you know of other solutions.

Discussion Topics

 

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 

 

 


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

    • Amy: need to chat with cmtrs about limitations
    • Maureen: need more clarity of what direction we should go before taking w/cmtrs
    • Proposed process
      • 1) draft a proposal on updating DC from DC sub-team (Sarah P., Amy, Maureen, Maura)  - 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 
          • identify what specifically DSpace DC should be updated to - QDC vs DCTerms 
        • User Modifications: identify what if any 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 
      • 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) JIRA workflow improvements

  • useful improvements that should make it easier to understand what needs to be done on JIRA issues
  • more tweaks coming before implementing - more feedback welcomed (email Tim) - will discuss in detail at a later point

5) Topic for developer overlap mtg

  • too early for DC discussion 
  • priority for developers on 3.0 release, forgo overlap for Oct and possibly Nov unless something comes up

6) Topic for Thurs/Fri discussion

  • nothing identified
  • Val to contact each DCAT discussion leader to identify status on their issues on the DCAT Discussion Schedule

 

 

 

Actions Items from this meeting

Action Item

Assignee

Deadline

test new features / improvements and provide feedbackALLOct 19

draft a proposal on updating DC from DC sub-team

Sarah P., Amy, Maureen, Maura  

Dec 1

poll DCAT to see if everyone is available on Dec 18

Val

Oct 12

contact each DCAT discussion leader to identify status on their issues on the DCAT Discussion Schedule

Val

Oct 19

 

 

 

 

 

 

  • No labels