Re: [Dspace-tech] How to find item with strange metadata value of |||
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 and now my facets are clean again. ;) Thanks a bunch, Alan On Sun, Aug 2, 2015 at 5:24 AM Kim Shepherd kim.sheph...@gmail.com wrote: Hi Alan, that's close, but not quite what I was suggesting: the ||| will not be stored in the database, that's added in when indexing the values to Solr, so I think a SQL query like: select item_id from metadatavalue where metadata_field_id=86 and (text_value='' OR text_value IS NULL); Will be closer to what you're after. If you want to try and find items that might match in solr, you could try something like curl http://localhost:8080/solr/search/select?query=*:*fq=FIELDNAME_filter :||| Where FIELDNAME is the name of the field as configured in the discovery spring configuration (eg. 'subject', 'type', 'author', and so on) Cheers! Kim M: k...@shepherd.nz T: @kimshepherd P: +6421883635 0CCB D957 0C35 F5C1 497E CDCF FC4B ABA3 2A1A FAEC https://keybase.io/kshepherd On 1 August 2015 at 01:28, Alan Orth alan.o...@gmail.com wrote: So I found the metadata_field_id for this metadata item using a known valid value: dspace=# select * from metadatavalue where text_value='DRYLAND CEREALS'; ... and then I tried to find text values containing several variations of |||, like '\|\|\|', '%|%', '%\|%' etc... dspace=# select item_id from metadatavalue where metadata_field_id=86 and text_value='|||'; But I am not getting any hits. I also figured that, since we figured CSV export by nature wouldn't expose this anomaly, that I could simple export and re-import, but DSpace said no changes were detected upon re-import. Hmmm. Anyone know how I could query Solr directly for this information? Alan On Fri, Jul 31, 2015 at 9:35 AM Alan Orth alan.o...@gmail.com wrote: Thanks for the interesting suggesting, Kim! This is happening in DSpace 4.3. I will try to poke around in the database, as you're probably right that this anomaly probably wouldn't make it through a CSV export... Alan On Thu, Jul 30, 2015 at 1:44 PM Kim Shepherd kim.sheph...@gmail.com wrote: Hi Alan, Discovery filters use ||| as a separator between lowercase value and a display/stored value, eg. something|||SomeThing I'm sort of surprised it displays in the sidebar, because acting as the separator, it should be pulled out, but I think the first thing I'd look for is empty or null metadata values in your database (probably easier than CSV because of how metadata export works), for the field in question. What version is this happening in? M: k...@shepherd.nz T: @kimshepherd P: +6421883635 0CCB D957 0C35 F5C1 497E CDCF FC4B ABA3 2A1A FAEC https://keybase.io/kshepherd On 30 July 2015 at 20:45, Alan Orth alan.o...@gmail.com wrote: Hi, I've got an strange metadata value shown in one of our XMLUI Discovery sidebar facets, and I'm not sure how to find the offending item to fix it. The value is displaying as |||, and I've narrowed down the collection the item belongs to by navigating through my communities and looking at the facet in question. I've exported the metadata as CSV and attempted to find the item using LibreOffice and OpenRefine but nothing strange sticks out... Does anyone have any suggestions? Thanks, Alan -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] retrospectively assigning DOIs to live items
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. You can only send information about changes in your local DSpace database to the registration agency. Does this mean I'd have to figure out how to change the state of the already live items to whatever the starting point of doi-organiser is (presumably to be reserved)? cheers, Andrea [1] https://wiki.duraspace.org/display/DSDOC5x/DOI+Digital+Object+Identifier#DOIDigitalObjectIdentifier-CommandLineInterface -- Dr Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] retrospectively assigning DOIs to live items
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:
INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
SELECT nextval('doi_seq'),
concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2, item_id, 7
FROM item
WHERE in_archive=true and item_id not in (select resource_id from doi where
resource_type_id=2);
Then the cron job for the usual doi-organiser commands will pick up the job.
I've just been investigating the use of doi's for us. There are a couple of
issues with it, especially the datacite connector crosswalk and data provider,
see the latest JIRA issues.
At the moment with datacite the update of metadata does not work among other
things.
Hope this helps
Claudia
Am 02.08.2015 um 23:27 schrieb 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. You can only send information about changes in your local
DSpace database to the registration agency.
Does this mean I'd have to figure out how to change the state of the
already live items to whatever the starting point of doi-organiser is
(presumably to be reserved)?
cheers,
Andrea
[1]
https://wiki.duraspace.org/display/DSDOC5x/DOI+Digital+Object+Identifier#DOIDigitalObjectIdentifier-CommandLineInterface
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] retrospectively assigning DOIs to live items
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 the status of newly items in archive:
INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
SELECT nextval('doi_seq'),
concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2, item_id,
7 FROM item
WHERE in_archive=true and item_id not in (select resource_id from doi where
resource_type_id=2);
Then the cron job for the usual doi-organiser commands will pick up the job.
Perfect, thanks a lot for that!
I've just been investigating the use of doi's for us. There are a couple of
issues with it, especially the datacite connector crosswalk and data
provider, see the latest JIRA issues.
At the moment with datacite the update of metadata does not work among other
things.
Good to know; I had seen some DOI-related Jira issues come through but
I'll make sure to review them in more detail. Yes, we'll be using
DataCite; luckily with this particular repository, we're not really
expecting metadata changes once the submission is completed.
cheers,
Andrea
--
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Three user questions
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/ / -- Our workflow.cfg has: workflow.framework=originalworkflow reviewer.file-edit=true And when reviewers go to Edit Metadata Upload they get the “Upload Files” option as desired. [cid:image001.png@01D0CDF5.5B3A3F90] If this is a bug, I hope it doesn’t get fixed. :-) Deborah From: bluy...@gmail.com [mailto:bluy...@gmail.com] On Behalf Of Bram Luyten Sent: Thursday, 30 July 2015 2:04 a.m. To: RENTON Scott Cc: Fitchett, Deborah; dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Three user questions Note that this is only for XMLUI and only if you have switched to the optional Configurable Workflow framework https://wiki.duraspace.org/display/DSDOC5x/Configurable+Workflow A bit of an old video on what this alternative workflow enables: https://www.youtube.com/watch?v=_Z52gne55so The information should still be fairly accurate today however. -- [Image removed by sender. logo] Bram Luyten 2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010 Esperantolaan 4, Heverlee 3001, Belgium www.atmire.comhttp://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml On 29 July 2015 at 10:43, RENTON Scott scott.ren...@ed.ac.ukmailto:scott.ren...@ed.ac.uk wrote: Hi Deborah That looks EXACTLY what they're looking for. I've put it in, and assume that they're all happy if nobody hears anything else about this! Thanks very much again! Scott From: Fitchett, Deborah deborah.fitch...@lincoln.ac.nzmailto:deborah.fitch...@lincoln.ac.nz Sent: 29 July 2015 00:53 To: RENTON Scott; dspace-tech@lists.sourceforge.netmailto:dspace-tech@lists.sourceforge.net Subject: RE: Three user questions Stumbling around looking for something else, have found the answer to #1: In dspace/config/modules/workflow.cfg there’s a line reviewer.file-edit=false --Change this to true and reviewers can add/edit/remove files from the submission. Deborah From: Fitchett, Deborah [mailto:deborah.fitch...@lincoln.ac.nzmailto:deborah.fitch...@lincoln.ac.nz] Sent: Tuesday, 14 July 2015 11:30 a.m. To: RENTON Scott; dspace-tech@lists.sourceforge.netmailto:dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Three user questions Hi Scott et al, We’re on v.3.1, just switched to XMLUI, and are also wondering about the first two questions: 1) We definitely were able to add files when editing metadata under v.3.1 JSPUI, and for our workflows it’s really useful to be able to do this. 2) Likewise would love to be able to display the number of items in a collection again. Does anyone know about either of these? For the third question, I went with what I knew and created a javascript bookmarklet that hides “Archived submissions”, makes all the remaining tables sortable, and automatically sorts by oldest tasks first: https://github.com/LincolnUniLTL/dspace/tree/master/workflowhelper It’s a bit of a hack but might be useful as a workaround. Deborah From: RENTON Scott [mailto:scott.ren...@ed.ac.uk] Sent: Friday, 10 July 2015 9:40 p.m. To: dspace-tech@lists.sourceforge.netmailto:dspace-tech@lists.sourceforge.net Subject: [Dspace-tech] Three user questions Hi folks Sorry to package different things up in one e-mail. I have a user who we’re upgrading from 1.8 to 4.2 who has asked for some things which seem a little bit off-road”! 1. Workflow Tasks- when the approver takes task and goes to edit metadata, they’ve noticed there’s no option to add a file- there’s a feeling here that this is a conscious decision, it’s perfectly reasonable for the approver NOT to be able to add a file at this point. It looks like it was possible in the v1.8 JSPUI, so just wanted to check that this is by design and not a bug. 2. The old JSPUI displayed (or could be configured to display) the number of items in a collection in brackets on collections lists. Is this configurable for them in 4.2? I could not find a way to do this, and haven’t seen any other sites which have. 3. They have requested Workflow Tasks come above Archived Submission on the Submission page layout. It appears to me that this cannot be done in any XSLT files, so wondered if such a change would need to be performed in Submissions.java in the XMLUI. I have only changed the XSLs in mirage for layout thus far, so don’t want to alter the java files unless absolutely necessary. Thanks in advance Scott Scott Renton Digital Developer Lower Ground Floor East Main Library, George Square tel: 515219 P Please consider the environment before you print this email. The contents of this e-mail (including any
Re: [Dspace-tech] 'admin use only' fields in input-forms.xml
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 it would be perfect for a field where users can submit an embargo request and we can’t accidentally delete it and destroy our accountability trail (ahem). Deborah From: Andrea Schweer [mailto:schw...@waikato.ac.nz] Sent: Thursday, 30 July 2015 11:14 a.m. To: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] 'admin use only' fields in input-forms.xml On 29/07/15 18:30, Claudia Jürgen wrote: this configurable for each field in the input forms see https://wiki.duraspace.org/display/DSDOC3x/Submission+User+Interface You can add an element visibility to each field which is either set to submit - visible only during submission workflow - visible only during workflow Huh I had no idea -- thanks Claudia! I see you can even set the field to read-only in the other scope: visibility otherwise=readonlyworkflow/visibility cheers, Andrea -- Dr Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand +64-7-837 9120 P Please consider the environment before you print this email. The contents of this e-mail (including any attachments) may be confidential and/or subject to copyright. Any unauthorised use, distribution, or copying of the contents is expressly prohibited. If you have received this e-mail in error, please advise the sender by return e-mail or telephone and then delete this e-mail together with all attachments from your system. -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
