Re: [Dspace-tech] How to find item with strange metadata value of |||

2015-08-02 Thread Alan Orth
Bingo, I found the item, and then got its handle using the item_id: dspace=# SELECT * FROM item, handle WHERE handle.resource_id = item.item_id AND item.item_id = '66841'; The item did indeed have empty contents for that field. I deleted it from the Edit this item function in the web interface

[Dspace-tech] retrospectively assigning DOIs to live items

2015-08-02 Thread Andrea Schweer
Hi all, I'm looking into switching on DOIs for an existing DSpace repository with ~1,000 live items. We'd like to retrospectively generate DOIs for the live items. How do I do that? The documentation about the doi-organiser tool [1] says Currently you cannot generate new DOIs with this tool.

Re: [Dspace-tech] retrospectively assigning DOIs to live items

2015-08-02 Thread Claudia Jürgen
Hello Andrea, yes this is right. If you enable the identifier service this will only cover new items. Assuming you are using the DataCite Connector, the easiest way would be to manipulate the database (usual warnings about that) to give the old items the status of newly items in archive:

Re: [Dspace-tech] retrospectively assigning DOIs to live items

2015-08-02 Thread Andrea Schweer
Hi Claudia, On 03/08/15 11:16, Claudia Jürgen wrote: yes this is right. If you enable the identifier service this will only cover new items. Assuming you are using the DataCite Connector, the easiest way would be to manipulate the database (usual warnings about that) to give the old items

Re: [Dspace-tech] Three user questions

2015-08-02 Thread Fitchett, Deborah
Oddly, perhaps, it seems to work for us (yes, XMLUI, DSpace 3.1) even though we haven’t switched to Configurable Workflow! Our xmlui.xconf has: aspect name=Original Workflow path=resource://aspects/Workflow/ / !-- aspect name=XMLWorkflow path=resource://aspects/XMLWorkflow/ / --

Re: [Dspace-tech] 'admin use only' fields in input-forms.xml

2015-08-02 Thread Fitchett, Deborah
Thank you both! visibilityworkflow/visibility gives us a “for administrative use only” field which is just what we wanted. Unfortunately I’m having trouble getting visibility otherwise=readonlyworkflow/visibility to do anything different from visibilityworkflow/visibility which is a shame, as