Date & Time
- Main Call Tuesday, September 09, 15:00 UTC/GMT - 11:00 ET
- Satellite call Wednesday September 10, 20:00 UTC/GMT - 16:00 ET
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
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.
September Meeting Agenda: Administrative use cases
During the September meeting we will be discussing use cases that affect users who use DSpace:
- as collection or community administrators through the XML or JSP UI
- as full DSpace administrator through the XML or JSP UI
- as a system administrator through direct server access
For each of the needs that emerge, we will try to qualify those needs as:
- Supported: the use case is being addressed and that the bulk of configuration associated with it (if any) can happen through the UI.
- Partially supported: there is room for improvement in the support for the use case. It also covers the cases where specific server configuration or small customizations to the code are required in order to properly support the use case.
- Unsupported: if at all possible with DSpace, addressing the use case requires substantial modifications to the DSpace sourcecode.
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 a explanation and discussion about the actual use case. This means we hope to cover at least 10 use cases during the call.
Read more about certain use cases that were already identified: Use Cases
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 administrative use cases for you or your institution, especially if they fall in the category unsupported.
- Sign up for an account on this wiki and log in.
- Put your use cases in the comment section of this page.
- Join either the main call or satellite call and tell us about your use cases
Discussed use cases
- Workflow use cases - Bram Luyten
- Undo a bulk import from the User Interface - Terry Brady & Kate Dohe - Sarah Potvin
- Trigger the re-index of a collection - Terry Brady & Kate Dohe - Sarah Potvin
- Move a collection and trigger a re-index - Terry Brady & Kate Dohe
- Move a community - Terry Brady & Kate Dohe
- Allow collection administrators to perform bulk metadata import - Terry Brady & Kate Dohe
- Rebuild the discovery index - Terry Brady & Kate Dohe
- Rebuild the OAI index - Terry Brady & Kate Dohe - Sarah Potvin
- Clear the OAI Cache - Terry Brady & Kate Dohe
- Quality Control Reports - Terry Brady & Kate Dohe - Sarah Potvin
- Collection Admin can construct a Quality Control report - Terry Brady & Kate Dohe
- More robust and configurable statistics reports - Terry Brady & Kate Dohe - Sarah Potvin
- Configure and manage custom facets - Terry Brady & Kate Dohe
- Collection Admin can select fields to include in metadata export - Terry Brady & Kate Dohe
- Admin can cleanup an normalize language attribute for metadata fields - Terry Brady & Kate Dohe
- Configuration overlay solution - Terry Brady & Kate Dohe
- Re-read configuration files without restart - Terry Brady & Kate Dohe
- Re-read xslt files without restart - Terry Brady & Kate Dohe
- Managing controlled vocabularies - Sarah Potvin
- Managing input forms - Sarah Potvin
- Managing home page - Sarah Potvin - Peter Dietz
- Managing themes - Sarah Potvin
- Managing browse indexes - Sarah Potvin
- Changing/editing OAI crosswalks - Sarah Potvin
- Configure and Manage changes during an update - Peter Dietz
- Alter messages easier - Peter Dietz
- Configure the Admin UI - Peter Dietz
- Apply an existing theme to a collection or community through the GUI - Peter Dietz
- Apply an input-form to the collection through the GUI - Peter Dietz
- Ability to specify the emphasis of a collection through GUI - Peter Dietz
- Repo Admin documentation - Peter Dietz
- End to end solution for users who wish to batch deposit - Peter Dietz
- Customise which metadata fields to facet upon, search upon - Peter Dietz - Sarah Potvin
- Permissions of a new user in an eperson group - Peter Dietz
Call Attendees (main+satellite)
- Bram Luyten (@mire) - @mire
- Maureen Walsh - Ohio State University
Sabine Grinsven - @mire
Terry Brady - Georgetown
Kathleen Schweitzberger - University of Missouri-Kansas City
Monica Rivera - Rice University
Scott Carlson - Rice University
Iryna Kuchma - eIFL.net
Sarah Potvin - Texas A&M
Peter Dietz - Longsight
Kate Dohe - Georgetown
Valorie Hollister - DuraSpace
- Jim Ottaviani - University of Michigan
- Mark Diggory - @mire
9 Comments
Bram Luyten (Atmire)
Workflow use cases
Terrence W Brady
From Georgetown University: Terrence W Brady and Kate Dohe
In addition to the Admin Use Cases that already exist on the Use Cases page, we recommend the following. In particular, bulk import and media filter are critical functions to make available to the admin interface.
Daryl Grenz
Options for better reporting on and management of embargoes and bitstream authorizations in the admin UI would be nice. For example, ability to list all items with unexpired embargos.
Sarah Potvin
+1 to:
all should be within the reach of DSpace administrators.
I would add:
Sarah Potvin
also +1 to managing browse indexes.
Peter Dietz
Here's our Longsight DSpace Wishlist:
Upgrades don't "stick" unless you really know what you are doing.
i.e. instead of giant i18n/messages that you have to alter. Have a base messages.xml (with all 10,000 keys) and then a messages-custom.xml (with 200 keys that overrides). Also, it would be great that to change the site name from "DSpace" to "Scholar Archive", you didn't have to alter 200 keys.
It would be great if you could set most configs / i18n values through the UI. i.e. It would be great if you never needed to "contact IT" to do anything for the site. So, itemize everything that only "IT" can do: alter configs, i18n, theme, batch import, alter item submission form, add sidebar discovery facets, edit the default system license... Ability to map the input-form to the collection, via GUI. Ability to map the theme/skin to the collection via GUI. Ability to specify if a collection should be thesis emphasis, file emphasis, or gallery emphasis from gui.
I wish there was solid "repo admin" documentation. Most documentation that I've found is aimed at your fellow DSpace developer who is going to alter a spring xml file to alter which beans are dependency injected at runtime. Ok, good for developers, how about repo admin docs (i.e. how to add epersons to a group, how to use batch metadata edit).
End to end solution for people who wish to batch deposit. i.e. Scan a directory of 1000 files on their local computer, (i.e. SimpleArchiveFormat package creation). Then maybe help push that to DSpace using BatchImportUI. It should also validate the input. i.e. are dc.date fields in ISO8601 (if not, here's our recommendation). Validate that the metadata fields in the spreadsheet exist in dspace metadata registry.
Allow for one to customize which metadata fields to facet upon, search upon. i.e. The learning object collection would like to facet upon lo.gradelevel = {REMEDIARY, FRESHMAN, SECOND, THIRD, SENIOR, GRADUATE, POSTDOC, ...}
Add person to an eperson group, and apply the permissions recursively/retroactively. I.e. DSpace doesn't work well here, you get added to the group, but permissions have "cached" that you don't get added to all sub-collections, sub-items, sub-bitstreams.
Ability to edit homepage text, homepage top downloads, homepage featured collections from a GUI.
Terrence W Brady
Charlene Barina
Agree with Sarah Potvin. In particular XMLUI sidebar modifications are daunting; admins who don't have extensive XSLT/XML experience (but some web development experience) should be able to reorder items in sidebars/navbars.
Daryl Grenz
+1 for the following: