Hi Grant, The provision to make items 'private' (non-searchable) is already available in later versions of DSpace; we're currently on v3.2 on our dev environment and that has this capability. There is also an option to embargo both metadata and/or files separately, which might work depending on what your requirement is.
Are you thinking about this as part of the HEFCE requirements for post-2014 REF? If so, I have this high on my agenda now, and would love to have a chat about it in the new year (and any other UK DSpace users)? We're also looking to go to v4.x at some point in 2015. We've made some workflow enhancements and display changes, all of which I'm really pleased with, I can send you a list of the enhancements and some screenshots if this would be helpful (it's not on a public server yet). Hope that helps Sarah Research Support Manager Library & Archives Queen Mary University of London -----Original Message----- From: Denkinson, Grant W. [mailto:[email protected]] Sent: 08 December 2014 16:49 To: 'General List ([email protected])' Subject: [Dspace-general] Updating user experience and workflows with DSpace 4 We're upgrading soon from DSpace 1.x to 4.x and I'm looking forward to it. When we update I'd like improve our user experience. I'd like to be inspired by some good examples. Are there DSpace instances I could see that you'd recommend for inspiration in terms of look and feel, design and features? We'd also like to update our workflows so we can triage and navigate incoming items as well as put records in a holding place to be updated before being made visible: e.g. User sends through a manuscript at acceptance with minimal metadata, we process this at the time and keep it somewhere private. Then perhaps months later, when the item is published, we update the metadata, possibly the manuscript (e.g. to a CC-BY Gold copy) and make it visible (perhaps with an embargo on the full text). We don't currently do much of this 2-phase sort of work. What would work best in DSpace 4? Can we put processed items in a separate pool or mark them as done and filter them in/out? Should we instead put them in a hidden collection if such as thing is possible? Can they be processed but embargoed (both data and metadata) and then gone back to later from a list? I'm more than happy to be pointed at tutorials, specific documentation, examples etc. for further reading or be directed to a more suitable forum. Grant -- Grant Denkinson, Manager of Leicester Research Archive (LRA) University of Leicester Library, University of Leicester PO Box 248, University Road, Leicester, ENGLAND LE1 7RH Telephone: +44 116 252 2310, Fax.: +44 116 252 5075 Email: [email protected] ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
