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

Compare with Current View Page History

« Previous Version 6 Current »

Date & Time

  • Main call Dec 09th 16:00 UTC/GMT - 11:00 ET 
  • Satellite call Dec 10th 08:00 UTC/GMT - 03:00 ET CANCELLED

What is the difference between the "main call" and satellite call? 

Dial-in

We will use the international conference call dial-in. Please follow directions below.

  • U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
  • International toll free: http://www.readytalk.com/intl
    • Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial in #
    • Once on the call, enter participant code 2257295

DSpace project governance changes

In conjunction with the new DuraSpace membership program there is a new governance model for the project providing a larger role for the community.
Currently assembling the DSpace Leadership Group: includes representative from member institutions who have contributed >$10K to the project as well as elected representatives from those who've contributed at either the $5K or $2.5K level.
The Leadership Group will work with the DSpace Steering Group (which is more of the management group for the project) and has a role in approving the annual DSpace budget (how to spend membership $s), the project roadmap as well as helping to establish the community direction.
Leadership Group members will be formally announced in January.
For more information on DSpace governance visit http://www.dspace.org/governanc

2014 Meeting objectives

From August until December 2014, the monthly DCAT meetings are centered around defining, refining and prioritizing DSpace use cases.

These use cases are expected to have an important impact on the medium and long term roadmap of DSpace, starting with DSpace 6 in 2015.

December Meeting Agenda: Structure use cases

During the December meeting we will be discussing structure use cases. Structure use cases are all needs that relate to DSpace's currently hierarchical data model of Communities / Collections / Items / Bitstreams, with associated configuration, metadata and authorizations. Are there things that you or your faculty wishes to do with DSpace that's currently not possible due to the structure of the system? Let us know!

We rather want to cover more use cases than to stick to a limited number, allowing to dig deeper in detail. This is why we will be asking the participants in the call for their institutions or personal priority after devoting ~5 minutes to an explanation and discussion about the actual use case. This means we hope to cover at least 10 use cases during the call. 

Structure use cases that were already identified and logged in the Use Case space:

TitleCreatorModified
Admin UI - Simplify Collection Creation Based on TemplateMonika MevenkampJun 22, 2015
Structure - Check Bitstream names against allowed file name patternMonika MevenkampJun 12, 2015
Structure - Format checking of data entry in input formsMonika MevenkampJun 12, 2015
End User - Image file display (pan, zoom, size options)Maureen WalshMay 12, 2015
Structure - Generated provenance for all added bitstreamsMaureen WalshMay 11, 2015
Structure - Apply licenses to bitstreamsMaureen WalshMay 11, 2015
Structure - Generate technical metadata per bitstreamMaureen WalshMay 11, 2015
Structure - Simple AssetStore for Human TraversalTim DonohueApr 28, 2015
Structure - purpose of bundle layerIgnace DeroostApr 09, 2015
Structure - Create the ability to place "dynamic collections" (pre-faceted view of a collection) within the community hierarchy.Terrence W BradyApr 06, 2015
Structure - Drag and drop opportunities for changing collections structureIgnace DeroostDec 10, 2014
Structure - Manual Creation of "New Editions" of an ItemMark DiggoryApr 28, 2014
Structure - Automated Retention of All changes to ItemsMark DiggoryApr 28, 2014
Structure - Create / manage files and metadata (as an Item)Mark DiggoryApr 26, 2014
Structure - Relationships between objectsMark DiggoryApr 26, 2014
Structure - Support for hierarchical metadata formats (e.g. METS / MODS)Mark DiggoryApr 26, 2014
Structure - Community and Collection hierarchy (or generic containers)Mark DiggoryApr 26, 2014
Structure - Metadata for all levels of object hierarchyMark DiggoryApr 26, 2014
Structure - Manage Lists, Controlled Vocabularies and Authority ControlMark DiggoryApr 26, 2014
Structure - Describe Individual Bitstream within an ItemMark DiggoryApr 26, 2014
Structure - Associate Separate Properties with Each DSpace CommunityMark DiggoryApr 26, 2014
Structure - Support for derivative objectsMark DiggoryApr 26, 2014
Structure - Management of Deposits / SubmissionsMark DiggoryApr 26, 2014
Structure - Automated Update of Existing ItemsMark DiggoryApr 26, 2014
Structure - Manual Edit of Existing ItemsMark DiggoryApr 26, 2014
Structure - Automated Deposit of New ItemsMark DiggoryApr 26, 2014
Structure - Manual Submission of New ItemsMark DiggoryApr 26, 2014

The best way to participate and contribute

If you have some time to spare to prepare for this meeting, it would be great if you could briefly list the most important structure use cases for you or your institution, especially if they are currently unsupported by DSpace.

  1. Sign up for an account on this wiki and log in.
  2. Put your use cases in the comment section of this page. 
  3. Join either the main call or satellite call and tell us about your use cases 

Discussed use cases

  • ...

 

Call Attendees (main+satellite)

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.