Contents

Action Plan

-distill list from DGOC and Ambassadors - eliminate/group dups, etc.

-identify quick wins - and JIRA issue #s for those already in JIRA

-Tim to review distilled list w/developers and committers

-Val to start new review process w/DGOC on JIRA new feature requests - review items, try to get more info and define feature, promote/discuss with community and encourage JIRA voting

Possible quick wins

These are features where either some work is already done, there is an issue in JIRA (preferrably with code), or it might be relatively easy to do. There's no promise that they could all be implemented by the next version of DSpace (1.7) – but, hopefully a few could be targeted.

  1. Admin or depositor tool for re-ordering the bitstreams in an existing item - fields displayed on the simple item record and ability to globally change the location of the parts of an item record - move the bitstream links from bottom to top of record
  2. Embargo out-of-the-box configuration (Leonie Hayes/Univ of Auckland, Jim Ottaviani/Univ of Michigan, Alvin Hutchinson/Smithsonian)
    • have it turned on by default
    • possibly implement a full embargo where item is submitted and assigned a persistent URL, but no metadata or bitstream is visiable or searchable
    • have an embargo that allows temporary access to a bitstreem via a URL emailed to the requestor
  3. Type-based submission - different submission processes for Theses versus papers versus presentations, etc (Ronee Francis/Vanderbilt)
  4. Ability to isolate a single bitstream entry from admin interface --where the file is located in the asset store (Ronee Francis/Vanderbilt Univ)
    • This issue is not yet in JIRA, but it should be relatively simple to add this information to the Admin Interface.
    • Is this of broad appeal?
  5. Admin GUI interface for configuration Import functionality to harvest content from PubMed Central (Julie Speer/Georgia Tech)
  6. Tombstone functionality upon item withdrawal that includes a pull down for specifying reason for withdrawal, showing relevant metadata to confirm item's identity, (Jim Ottaviani/Univ of Michigan)
  7. Format checking at time of bitstream deposit to verify that a file is in a specific format
    • Some Curation functionality is being prepared for DSpace 1.7: https://wiki.duraspace.org/display/DSPACE/CurationTaskProposal
    • It has yet to be determined exactly which Curation features will be ready for 1.7, and which will need to wait for future versions of DSpace (so, the 'format checking' feature may or may not be available in 1.7).
  8. Batch sub-community and collection creation - it would be nice to batch-create the sub-communities and collections from a csv file – similar to the batch metadata import (Richard Jizba/Creighton Univ)
    • ?LEONIE CAN YOU DO THIS WITH BATCH METADATA EDITING?
  9. Stats package from Univ of Minho incorporated as a stats option, Eloy expressed interest in providing as an option
    • NOTE: Minho developers would need to work with the DSpace Committers/Developers to ensure their stats package is compatible with current versions of DSpace.
  10. @mire stats package improvements - are they planning on contributing any improvements to the 1.6 stats package? Are there any other improvements from the community for the 1.6 stats package?

Likely longer term development required

1) Bulk editing of authorizations/resource policies for one or more items, IN JIRA-http://jira.dspace.org/jira/browse/DS-520, MED/HIGH EFFORT, CURRENTLY NOT SCHEDULED FOR 1.7

  • Ability to edit in bulk the resource policies for a group of items - admin could edit multiple items and apply a resource policy such as bitstream read anonymous or bitstream read administrator, etc.

2) Admin GUI interface for generating reports on specific metadata, elements, file types, dates, collections, etc, MED EFFORT, NEED MORE DEFINITION OF FEATURE

3) Admin GUI interface for configuration, HIGH EFFORT - WHEN YOU START DSPACE AFTER DOWNLOADING DSPACE IT WOULD START CONFIGURATION UTILITY (INSTEAD OF CFG FILE - WHICH IS MORE MACHINE READABLE),  FOR 1.8 -- FREQUENT PAIN POINT AND SOURCE OF QUESTIONS/PROBLEMS FOR CMTRS/DEV

4) Ability to edit templates via the admin interface and delegate - at the moment we use templates to control the different types of files we receive. This would be nice for repository managers who only work through the UI (Ronee Francis/Vanderbilt Univ) NOT SURE ABOUT THIS - ITEM TEMPLATES OR MANAKIN TEMPLATES?

5) Simplify install/upgrade processes - (http://jira.dspace.org/jira/browse/DS-456 AND http://jira.dspace.org/jira/browse/DS-439), MED TO HIGH EFFORT

6) An admin tool to handle licenses - ability for admin to send link to end users, end users login to archive, sign contract and log off, DISCONNECT FROM SUBMISSION PROCESS? HAVE AS A PART OF  DSPACE OR SOME OTHER LOCAL WORKFLOW SOLUTION? OR DURING SUBMISSION PROCESS ABILITY TO ACCEPT ON BEHALF OF -- NOTE THAT OR SEND EMAIL TO END USER

7) Inherit or ignore collection policies when moving items to a new collection, ENHANCEMENT TO MOVING ITEMS

Possibly not enough broad community interest

1) Batch load admin GUI interface for metadata and files - DON'T WE HAVE 1/2 OF THIS  WITH BATCH METADATA EDITING?

2) Output a citation to an item in DSpace in a standard (e.g. Endnote or BibTex) format, BUTTON TO DOWNLOAD TO ENDNOTE OR DOWNLOAD TEXT FILE IN ENDNOTE FORMAT? BROAD INTEREST?, MED EFFORT - DEPENDING ON HOW MANY FORMATS, STUART LEWIS HAS BUILT EXPORT FOR ENDNOTE (Leonie Hayes/Univ of Auckland)

3) Integrate “Request a Copy” plugin into code base, BROAD INTEREST? FIND PLUGIN AND PUT INTO JIRA

4) An easy license contract for users to accept, NEED MORE INFO, MORE OPTIONS? ALLOW USERS TO ACCEPT IT 1X? BROAD AGREEMENT ON HOW TO EXECUTE?

5) Zotero integration – Zotero translator needs fixed to be able to define the item type from dc.type (Leonie Hayes/Univ of Auckland and Elin Stangeland/Univ of Cambridge) ZOTERO PROBLEM, NOT DSPACE

6) Crowdsource metadata enhancement where user can submit updated, corrected or enhanced metadata, HIGH DIFFICULTY, BROAD INTEREST?

7) SFX – full open url compliance – configurable field mapping and look up of the DOI registry along with WorldCat registry lookup mysql port, NEED MORE DETAIL/DISCUSSION, PUT IN JIRA

8) A watch script for monitoring system status that would let us know, for example, that there is a problem with the handler and it is not functioning correctly, NEED CLARIFICATION - HANDLE SYSTEM? OR IS THIS TO MONITOR IF SYSTEM IS UP OR DOWN -- THERE IS SOFTWARE (ONE THAT WE USE FOR DURASPACE SERVERS: For monitoring if a server is up/down: http://mon.itor.us/, SENDS AN EMAIL)THAT DOES THAT BETTER THAN CAN BE BUILT INTO DSPACE

9) Greater ability to customize the themes in Manakin, particularly in manipulating the search, browse, and sort options - picking the default search (simple / advanced) for a theme; suppressing the "browse All of Bluebrary" option when in some collections or sub-communities; implementing custom sort options within sub-communities and collections, NEED TO UNDERSTAND ISSUE BETTER -- SHOULD BE ABLE TO DO THIS ALREADY USING CSS OR CREATING THEME IN MANAKIN, SHOULD ALL BE POSSIBLE IN THEMES AND ASPECTS IN MANAKIN

10) MySQL port (Ronee Francis/Vanderbilt Univ), REPLACEMENT FOR POSTGRES OR ORACLE, FEW INSTITUTIONS USE MYSQL, COULD POLL THOSE INSTITUTIONS WHO ARE USING MYSQL SO THEY CAN DO IT AND MTN IT GOING FORWARD, PUT IN JIRA AND SOLICIT THOSE INSTITUTIONS

11) how the Java code handles memory to better manage the six different webapps (Julie Speer/Georgia Tech), SHOULD SEND MSG TO DEV LIST SO THEY CAN FIGURE OUT HOW TO HELP

  • No labels

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