[dspace-tech] Re: Bug in ORCID v2 implementation?

['Qin Zhao' via DSpace Technical Support]

I got the same problem. 
orcid seemed not been saved in item authority, just only in solr index.
After re-indexing (called via command "dspace index-authority") all orcid 
informaiton were overwritten from item authority with null, and authority 
types changed from "orcid" to "person".
I think that the method setValue(SolrDocument document) in class 
Orcidv2AuthorityValue should be extended for orcid fields etc.

I add code like following in my project class, the lookup function works as 
well.
(Some linies copied from 
https://github.com/Cineca/DSpace/blob/dspace-5_x_x-cris/dspace-api/src/main/java/org/dspace/authority/orcid/OrcidAuthorityValue.java)

 @Override
public void setValues(SolrDocument document) {
super.setValues(document);

this.setOrcid_id(ObjectUtils.toString(document.getFieldValue("orcid_id")));
for (String fieldName : document.getFieldNames()) {
String labelPrefix = "label_";
if (fieldName.startsWith(labelPrefix)) {
String label = fieldName.substring(labelPrefix.length());
Collection fieldValues = document.getFieldValues(fieldName);
for (Object o : fieldValues) {
addOtherMetadata(label,String.valueOf(o));
}
}
}
}

Kind regards,
Qin Zhao


On Wednesday, August 22, 2018 at 7:56:45 PM UTC+2, Darryl Friesen wrote:
>
>
> I was happy to see the return of ORCID in 6.3, however I'm experiencing 
> some odd behavior which I think may be a bug.
>
> Using the Lookup button, the initial interaction with the OCRID v2 API 
> seems to work great
>
> [image: orcid_bug_01.png]
>
>
>
> A match is found, I can see the ORCID and I can add that person as an 
> author. An entry is written in the Solr autority database.
>
>
> [image: orcid_bug_02.png]
>
> However, if the Lookup button is used again with that same author's name, 
> not only is the current entry from authority control returned, but an 
> additional hit from OCRID appears (shown in yellow in the image below).  To 
> add to the confusion, the current hit from authority control does *not* show 
> the ORCID, even though is it recorded in the Solr database.
>
>
> [image: orcid_bug_03.png]
>
>
> This differs from the previous behavior with DSpace and the ORCID v1 API.  
> I'm sure matches from the local authority control database *would* display 
> the ORCID, and if a hit from the ORCID API matched an existing entry in 
> authority control, it would not be displayed in italics as a new author.
>
>
> If I go ahead and select the new italicized author in the above scenario, 
> DSpace will create a duplicate entry in the authority control database.  
> The records will have different record IDs, but the data, including the 
> ORCID ID, is the same.
>
>
> [image: orcid_bug_04.png]
>
>
>
> This process can repeat; each time you lookup an author, an additional new 
> entry from ORCID will appear as new, and if selected, and additional 
> authority control record will be created.
>
> I'm seeing this behavior on my test server (running DSpace 6.4-SNAPSHOT 
> checked out of GitHub lat week) but I also see the same behavior on the 
> DSpace 6.3 demo site, so I don't believe it's an issue with my 
> configuration.
>
> Does this sound like a bug?  Is anyone else using ORCID v2 integration 
> experiencing this behavior?
>
> - Darryl
>
>
> --
>
> Darryl Friesen, B.Sc., Programmer/Analystdarryl@usask.ca 
> 
>
> Library Systems & Information Technology,http://library.usask.ca/
>
> University of Saskatchewan Library
>
> --
>
> "Go not to the Elves for counsel, for they will say both no and yes"
>
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech]

[Birol Tilki]

Hello All,
I am installing DSpace 6.3 on ubuntu 18. I have PostgreSQL 'pgcrypto'
extension installed and created this extension for dspace database. But
when run ant fresh_instal command I got following error.
What can be solutions?
Thanks,
Birol.

root@bel-test:/opt/dspace-6.3-release/dspace/target/dspace-installer# ant
fresh_install
Buildfile: /opt/dspace-6.3-release/dspace/target/dspace-installer/build.xml

init_installation:

prepare_configs:
[mkdir] Created dir:
/opt/dspace-6.3-release/dspace/target/dspace-installer/config-temp
 [copy] Copying 159 files to
/opt/dspace-6.3-release/dspace/target/dspace-installer/config-temp
 [copy] Copying 1 file to
/opt/dspace-6.3-release/dspace/target/dspace-installer/config-temp
 [copy] Copying 16 files to
/opt/dspace-6.3-release/dspace/target/dspace-installer/config-temp

init_configs:
 [copy] Copying 1 file to /dspace/config
   [delete] Deleting directory
/opt/dspace-6.3-release/dspace/target/dspace-installer/config-temp

test_database:
 [java] 2018-08-23 09:25:21,437 WARN
org.dspace.services.email.EmailServiceImpl @ Couldn't get an email session
from environment:  Need to specify class name in environment or system
property, or as an applet parameter, or in an application resource file:
java.naming.factory.initial
 [java]
 [java] Attempting to connect to database
 [java] Connected successfully!
 [java]
 [java] Database Type: postgres
 [java] Database URL: jdbc:postgresql://localhost:5432/dspace
 [java] Database Schema: public
 [java] Database Username: dspace
 [java] Database Software: PostgreSQL version 10.4 (Debian
10.4-2.pgdg90+1)
 [java] Database Driver: PostgreSQL JDBC Driver version 42.2.1
 [java] PostgreSQL 'pgcrypto' extension installed/up-to-date? false
(not installed)
 [java]
 [java] WARNING: Required PostgreSQL 'pgcrypto' extension is NOT
INSTALLED on this database.
 [java]
 [java] ** DSpace REQUIRES PostgreSQL >= 9.4 AND pgcrypto extension >=
1.1 **
 [java]
 [java] To install it, please connect to your DSpace database as a
'superuser' and manually run the following command:
 [java]
 [java]   CREATE EXTENSION pgcrypto;
 [java]
 [java] 2018-08-23 09:25:22,128 WARN
org.dspace.services.sessions.SessionRequestServiceImpl @ Request
interceptor
(org.dspace.services.events.SystemEventService$EventRequestInterceptor@7e9a7df9)
failed to execute on end (request-458-1535009121853): null

BUILD FAILED
/opt/dspace-6.3-release/dspace/target/dspace-installer/build.xml:789: Java
returned: 1

Total time: 6 seconds

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] mirage2 error after dbuilding

[Ze Victor Harry]

hello again am trying to install mirage2 for xmlui and after bulding
succefully by the command mvn package -Dmirage2.on=true after installing
git.and it succefully installed and done the configurations as the dspace
guide but when i try to open the page i am getting this error
"java.lang.IllegalArgumentException: Could not resolve placeholder 'item'
in string value "${item}""

Cocoon stacktrace [show]

Java stacktrace [show]

Java full stacktrace [show]
can please some one help me what is wrong

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech]

[Shaun donovan]

Hi Birol.

Did you enable the pgcrypto extension on the dspace database, as in:

|# Login to the database as a superuser, and enable the pgcrypto 
extension on ||this| |database|

|psql --username=postgres dspace -c ||"CREATE EXTENSION pgcrypto;"

|

|Kind Regards.|

|Shaun|

||


On 23/08/2018 12:14, Birol Tilki wrote:

Hello All,
I am installing DSpace 6.3 on ubuntu 18. I have PostgreSQL 'pgcrypto' 
extension installed and created this extension for dspace database. 
But when run ant fresh_instal command I got following error.

What can be solutions?
Thanks,
Birol.

root@bel-test:/opt/dspace-6.3-release/dspace/target/dspace-installer# 
ant fresh_install
Buildfile: 
/opt/dspace-6.3-release/dspace/target/dspace-installer/build.xml


init_installation:

prepare_configs:
    [mkdir] Created dir: 
/opt/dspace-6.3-release/dspace/target/dspace-installer/config-temp
 [copy] Copying 159 files to 
/opt/dspace-6.3-release/dspace/target/dspace-installer/config-temp
 [copy] Copying 1 file to 
/opt/dspace-6.3-release/dspace/target/dspace-installer/config-temp
 [copy] Copying 16 files to 
/opt/dspace-6.3-release/dspace/target/dspace-installer/config-temp


init_configs:
 [copy] Copying 1 file to /dspace/config
   [delete] Deleting directory 
/opt/dspace-6.3-release/dspace/target/dspace-installer/config-temp


test_database:
 [java] 2018-08-23 09:25:21,437 WARN 
org.dspace.services.email.EmailServiceImpl @ Couldn't get an email 
session from environment:  Need to specify class name in environment 
or system property, or as an applet parameter, or in an application 
resource file:  java.naming.factory.initial

 [java]
 [java] Attempting to connect to database
 [java] Connected successfully!
 [java]
 [java] Database Type: postgres
 [java] Database URL: jdbc:postgresql://localhost:5432/dspace
 [java] Database Schema: public
 [java] Database Username: dspace
 [java] Database Software: PostgreSQL version 10.4 (Debian 
10.4-2.pgdg90+1)

 [java] Database Driver: PostgreSQL JDBC Driver version 42.2.1
 [java] PostgreSQL 'pgcrypto' extension installed/up-to-date? 
false (not installed)

 [java]
 [java] WARNING: Required PostgreSQL 'pgcrypto' extension is NOT 
INSTALLED on this database.

 [java]
 [java] ** DSpace REQUIRES PostgreSQL >= 9.4 AND pgcrypto 
extension >= 1.1 **

 [java]
 [java] To install it, please connect to your DSpace database as a 
'superuser' and manually run the following command:

 [java]
 [java]   CREATE EXTENSION pgcrypto;
 [java]
 [java] 2018-08-23 09:25:22,128 WARN 
org.dspace.services.sessions.SessionRequestServiceImpl @ Request 
interceptor 
(org.dspace.services.events.SystemEventService$EventRequestInterceptor@7e9a7df9) 
failed to execute on end (request-458-1535009121853): null


BUILD FAILED
/opt/dspace-6.3-release/dspace/target/dspace-installer/build.xml:789: 
Java returned: 1


Total time: 6 seconds

--
All messages to this mailing list should adhere to the DuraSpace Code 
of Conduct: https://duraspace.org/about/policies/code-of-conduct/

---
You received this message because you are subscribed to the Google 
Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to dspace-tech+unsubscr...@googlegroups.com 
.
To post to this group, send email to dspace-tech@googlegroups.com 
.

Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Cascading Dropdowns in submission

[Mark H. Wood]

On Wednesday, August 22, 2018 at 10:36:56 AM UTC-4, Tim Donohue wrote:
>
> Unfortunately, DSpace doesn't support cascading dropdowns out-of-the-box.  
> You'd likely need to look for a third-party library (perhaps a Javascript 
> library) to help you achieve this sort of customization.
>
>

I haven't done it, but Googling for "jquery ui cascading dropdown" turns up 
a lot of hits, and DSpace already incorporates jQuery and jQuery UI.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Problem about jsp and component

[hy zhang]

Thanks a lot !

在 2018年7月16日星期一 UTC+8下午1:34:10，Paul Münch写道：
>
> Hi, 
>
> we don't use the JSPUI, but I think this is a language localisation issue: 
>
>
> https://wiki.duraspace.org/display/DSDOC5x/Localization+L10n#LocalizationL10n-JSPUIspecificlocalization
>  
>
> Kind regards, 
>
> Paul Münch 
>
> Quoting hy zhang <3090...@qq.com >: 
>
> > Hi, 
> > 
> > I'm using dspace-cris 5.8, 
> > 
> > 
> > I add a component and a relationpreference cause I want to list relation 
> > project on the entity Awards defined by myself, 
> > 
> > When I try it, the project already list, but the box title can't display 
> > well , it shows "relation awards 
> > 
> ???jsp.layout.dspace.detail.fieldset-legend.component.boxtitle.projects???" 
> > 
> > What's the problem? Maybe some advice? 
> > 
> > Thanks a lot 
> > 
> > Huaiyuan Zhang 
> > 
> > -- 
> > You received this message because you are subscribed to the Google   
> > Groups "DSpace Technical Support" group. 
> > To unsubscribe from this group and stop receiving emails from it,   
> > send an email to dspace-tech...@googlegroups.com . 
> > To post to this group, send email to dspac...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/dspace-tech. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>
>
> -- 
> Philipps-Universität Marburg | UB 
> Digitale Dienste | Deutschhausstraße 9 | D018 
> Tel. +49 06421 28-24624 
> -- 
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] How to list dynamic object info

[hy zhang]

Hi ,

I'm using Dspace-cris 5.8 , and I want to list dynamic object information 
on the basic objects' profile page,

for example , I create an entity "award" , and I want to list all awards 
won by a researcher on his or her profile 

page, and the list information should be awardname, awarddate, just like 
list person's name and e-mail on 

affiliated  organization's profile page, so which configuration file should 
I modify? I found a "sortby"  in 

component.xml is likely to implement it , but I don't know how to use it or 
if it is right , could someone give me 

some advice ?  Thanks a lot !

Huaiyuan Zhang

 

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] SWORDv2 configuration error- Help!

[tuf04742]

Andrea- 

Thank you so much for this tip!  Uncommenting and standardizing the 
servicedocument.url property, plus one other minor change, fixed the 
problem.  

Keep up the good work!  

-GG


On Wednesday, August 22, 2018 at 5:41:26 PM UTC-4, Andrea Schweer wrote:
>
> And further to that (having tripped over this myself about five minutes 
> ago) - the url property in that file doesn't carry over to the 
> collection.url and servicedocument.url properties, so if you use a non 
> standard "url" value then (as stated in the comments of the file) you'll 
> have to adjust those two properties as well.
>
> cheers,
> Andrea
>
> On Thu, 23 Aug 2018 at 09:23, Andrea Schweer  > wrote:
>
>> Hi,
>>
>> check what you have configured as the service document URL - probably in 
>> [dspace]/config/modules/swordv2-server.cfg. It's the first property in that 
>> file "url". The default is {dspace.url}/swordv2 and the base URL you use in 
>> your sword deposit must match that exactly.
>>
>> cheers,
>> Andrea
>>
>> On Thu, 23 Aug 2018 at 09:21, > wrote:
>>
>>>
>>>
>>> We're attempting to enable the SWORDv2 endpoint in our DSpace instance 
>>> for use in a DSpace-Symplectic Elements Repository Tools 2 integration.  
>>> The service document gives this error: "Unable to recognise URL as a 
>>> valid service document:..." 
>>>
>>> Does anyone have any insight into what could be causing this error?  
>>>
>>> Here's the full message: 
>>>
>>> http://purl.org/net/sword/terms/"; href="
>>> http://www.dspace.org/ns/sword/2.0/errors/BadUrl";>
>>> http://www.w3.org/2005/Atom";>ERROR
>>> http://www.w3.org/2005/Atom";>
>>> 2018-08-22T17:05:38Z
>>> http://www.w3.org/2005/Atom"; uri="
>>> http://www.dspace.org/ns/sword/2.0/"; version="2.0">[EmailRedacted]
>>> 
>>> Processing failed
>>> http://www.w3.org/2005/Atom";>
>>> Unable to recognise URL as a valid service document: 
>>> http://155.247.166.104:8080/swordv2/servicedocument
>>> 
>>> 
>>> org.swordapp.server.SwordError: Unable to recognise URL as a valid 
>>> service document: http://155.247.166.104:8080/swordv2/servicedocument 
>>> at 
>>> org.dspace.sword2.SwordUrlManager.extractDSpaceObject(SwordUrlManager.java:323)
>>>  
>>> at 
>>> org.dspace.sword2.ServiceDocumentManagerDSpace.getServiceDocument(ServiceDocumentManagerDSpace.java:169)
>>>  
>>> at 
>>> org.dspace.sword2.ServiceDocumentManagerDSpace.getServiceDocument(ServiceDocumentManagerDSpace.java:74)
>>>  
>>> at org.swordapp.server.ServiceDocumentAPI.get(ServiceDocumentAPI.java:56) 
>>> at 
>>> org.swordapp.server.servlets.ServiceDocumentServletDefault.doGet(ServiceDocumentServletDefault.java:32)
>>>  
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:624) at 
>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at 
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>>>  
>>> at 
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>>  
>>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) 
>>> at 
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>>>  
>>> at 
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>>  
>>> at 
>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218)
>>>  
>>> at 
>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
>>>  
>>> at 
>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506)
>>>  
>>> at 
>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
>>>  
>>> at 
>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
>>>  
>>> at 
>>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:962) 
>>> at 
>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
>>>  
>>> at 
>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:445) 
>>> at 
>>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1087)
>>>  
>>> at 
>>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
>>>  
>>> at 
>>> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318)
>>>  
>>> at 
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>>  
>>> at 
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>>  
>>> at 
>>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>>>  
>>> at java.lang.Thread.run(Thread.java:748)
>>> 
>>> http://www.w3.org/2005/Atom"; rel="alternate" type
>>> ="text/html" href="http://localhost:8080/contact"/>
>>> 
>>>
>>> Thanks for any help you can give us!  
>>>
>>> -GG
>>>
>>> -- 
>>> All messages to this mailing list should adhere to the DuraSpace Code o

Re: [dspace-tech] handles, isreplacedby, and withdrawn items

[Tim Donohue]

Thanks for reporting back on your findings, Deborah.

It sounds like the act of pointing to handles at one item "works"...but,
removing the handle from the withdrawn item is the core issue.  I'm not
surprised that DSpace cannot fully manage Items without handles -- as
handles are still very "built into" DSpace.

I've logged this issue as a bug: https://jira.duraspace.org/browse/DS-3993

In the meantime, one option to possibly work around this issue would be to
define a "fake/dummy" handle for the withdrawn item.  For example, give it
a handle of "withdrawn/[old-id]" or something.  This isn't exactly ideal,
but if the only issue is that the Handle cannot be null, this might be a
possible workaround.

Nonetheless, honestly, Claudia's fix seems very reasonable and it seems to
involve much less "messing around in the database".  So, I wouldn't fault
you for looking towards simply using that.

- Tim

On Wed, Aug 22, 2018 at 8:56 PM Fitchett, Deborah <
deborah.fitch...@lincoln.ac.nz> wrote:

> Hi all,
>
>
>
> I finally got around to trying this out on our dev server: updated the
> “handle” table to point two different handles to the one resource_id (and
> none to the withdrawn resource_id). It seemed in the first instance to work
> – following the links did what I expected.
>
>
>
> Then I tried running the index-discovery -b job. That kept stopping
> mysteriously in the middle of it – no obvious errors in the solr or dspace
> logs, just stopped. (I don’t know, maybe our dev server’s just slow and ran
> out of memory or got distracted or something.) But running index-discovery
> with no options picked up where it left off, and after a couple of
> repetitions of this it finally indexed the item in question and all my
> search/browse tests worked as expected too.
>
>
>
> So I was on the verge of declaring victory – and then I ran an oai import
> -c -v job. To my tremendous disappointment that failed partway through with:
>
>
>
> Item with handle null indexed
>
> org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:
> Document is missing mandatory uniqueKey field: item.handle
>
> at
> org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:552)
>
> at
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
>
> at
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
>
> at
> org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:124)
>
> at org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:116)
>
> at org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:102)
>
> at org.dspace.xoai.app.XOAI.index(XOAI.java:213)
>
> at org.dspace.xoai.app.XOAI.indexAll(XOAI.java:200)
>
> at org.dspace.xoai.app.XOAI.index(XOAI.java:131)
>
> at org.dspace.xoai.app.XOAI.main(XOAI.java:495)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:606)
>
> at
> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:226)
>
> at
> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78)
>
>
>
> This makes sense in retrospect: the OAI feed includes withdrawn items (in
> order to publish a “record status: deleted” record) but identifies them by
> their handles (so obviously requires a handle).
>
>
>
> This is highly disappointing, but at least now we know. It looks like it
> would work for a repository which didn’t publish an OAI feed, but sadly
> that’s vital for us.
>
>
>
> Our fall-back will be to follow Claudia’s suggestion of adjusting the Item
> Withdrawn page and using the metadata to point to the new item.
>
>
>
> Deborah
>
>
>
>
>
> *From:* Tim Donohue 
> *Sent:* Friday, 15 June 2018 2:42 AM
> *To:* Fitchett, Deborah 
> *Cc:* dspace-tech@googlegroups.com
>
>
> *Subject:* Re: [dspace-tech] handles, isreplacedby, and withdrawn items
>
>
>
> Hi Deborah,
>
>
>
> I'll admit, I've never tried this myself, but your suggestion to simply
> update the old "handle" table entries to point at the new "resource_id"
> seems like it *should work*.  The "handle" table in DSpace is really just
> used to resolve/assign Handles to Objects.  So, at least conceptually, it
> should support pointing two handles at the same object (Item).
>
>
>
> That said, I'd recommend first trying this out on a test or development
> server.  I think it should work, but it'd be worth testing more thoroughly
> how DSpace behaves when one Item object has multiple Handles (and for
> example, whether both handles appear on the Item splash page, etc).  I'd
> recommend testing basic functionality like browse/search/reindex. I susp

[dspace-tech] Re: Problem with Uploading files in Dspace 6.3

[Franklin Rodríguez Vargas]

This is the form where I'm submitting the file, when I click next shows an 
"Internal Server" error page and the dump is copied in the log of the 
application server.  

In the past, we had an installation of Dspace 5.x and never had this 
problem before.

Any help would be appreciated.





El martes, 21 de agosto de 2018, 16:16:38 (UTC-6), Franklin Rodríguez 
Vargas escribió:
>
> Have anybody have problems uploading files in Dspace 6.3 using JSPUI?
>
> I'm in trouble uploading files either with simple or HTML5 interface, this 
> is the stacktrace:
>
> 2018-08-21 15:14:52,186 WARN  org.dspace.app.webui.servlet.DSpaceServlet @ 
> em...@domain.com:session_id=e54362ea5fb6906f54e0cd34798c:ip_addr=10.202.46.20:general_jspui_error:javax.servlet.ServletException\colon;
>  
> java.lang.IllegalArgumentException\colon; setAttribute\colon; 
> Non-serializable attribute with name file-upload-listner
> javax.servlet.ServletException: java.lang.IllegalArgumentException: 
> setAttribute: Non-serializable attribute with name file-upload-listner
> at 
> org.dspace.app.webui.servlet.SubmissionController.wrapMultipartRequest(SubmissionController.java:1513)
> at 
> org.dspace.app.webui.servlet.SubmissionController.doDSPost(SubmissionController.java:265)
> at 
> org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:122)
> at 
> org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:80)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at 
> org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:344)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
> at 
> org.dspace.app.webui.filter.RegisteredOnlyFilter.doFilter(RegisteredOnlyFilter.java:66)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
> at 
> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:316)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160)
> at 
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734)
> at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673)
> at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174)
> at 
> org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:415)
> at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:282)
> at 
> com.sun.enterprise.v3.services.impl.ContainerMapper$HttpHandlerCallable.call(ContainerMapper.java:459)
> at 
> com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:167)
> at 
> org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:201)
> at 
> org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:175)
> at 
> org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:235)
> at 
> org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119)
> at 
> org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:284)
> at 
> org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:201)
> at 
> org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:133)
> at 
> org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:112)
> at 
> org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77)
> at 
> org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:561)
> at 
> org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:112)
> at 
> org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:117)
> at 
> org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:56)
> at 
> org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run

[dspace-tech] Call for Participants: DSpace 7 Entities Working Group

[Tim Donohue]

All,

Per the DSpace Steering Group's June statement on the DSpace 7 Data Model
[1] and the DSpace 7 Update talk at OR2018 [2], we are now establishing a
DSpace 7 Entities Working Group whose role will be to:

   - Define an implementation roadmap for DSpace 7 Configurable Entities
   (based on the assessment of an early prototype)
   - Draft a post-DSpace 7 roadmap for Configurable Entities (to be
   reviewed by Steering and Leadership)
   - Implement Configurable Entities, per defined roadmap (by creating a
   Pull Request, to be reviewed by DSpace 7 team and Committers)

*This group will be a Technical Working Group. Core participants will be
expected to be able to review/analyze code, implement new code, etc. While
less-technical participants are welcome to join meetings and provide
feedback, you should expect discussions to often be highly technical in
nature.*

More information can be found on this group's wiki page at:
https://wiki.duraspace.org/display/DSPACE/DSpace+7+Entities+Working+Group

*Anyone is welcome to join this working group (at any time). To register
your interest in joining this team, please fill out the below Doodle poll
by Weds, August 29.*

Doodle Poll for first meeting (early September):
https://doodle.com/poll/nvaykbdevwnfc5fd

As with all our working groups, all meetings will be publicly announced (on
Slack  and on the group's
wiki page). All meeting notes/recordings will also be publicly available on
the wiki.

If you have any questions, please let me know.

Tim Donohue

[1] Steering group statement:
https://duraspace.org/statement-from-dspace-steering-group-on-the-dspace-7-data-model/
[2] DSpace 7 Update talk: http://tinyurl.com/or2018-dspace7
-- 
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Bitstream order and display of thumbnails

[Fitchett, Deborah]

Kia ora koutou,

This seems to be my week for getting so close and yet so far….

We’re running v5.8 and Mirage2 and have got thumbnails beautifully displaying 
for most items, both in the web interface and the OAI feed.

The exception is where items have:

· More than one ORIGINAL bitstream generating a thumbnail; and

· One bitstream doesn’t have ANON READ permissions (eg permissions 
files which are admin-only); and

· That bitstream is earlier in the bitstream order than a bitstream 
which does have ANON READ permissions
Essentially, the interfaces display whichever thumbnail comes first in the 
bitstream order, without regard for whether or not the user can view it.

I can think of two potential approaches to fix this:


1)  Change our XSL (in both item-view.xsl/item-list.xsl, and in oai_dc.xsl) 
to choose the thumbnail from the set of bitstreams with ANON READ permissions, 
rather than the full set of bitstreams. I have managed to do this in 
item-view.xsl/item-list.xsl based on the url’s isAllowed=y parameter which is 
calculated for the current user, which is great (and am happy to share the xsl 
if anyone else wants it!). But once I took a look at the OAI it became obvious 
the thumbnail urls don’t include that parameter there (I’d be hoping they would 
be based on the Anonymous user) or any other form of bitstream permissions 
data. Maybe this would be codable in the java?



2)  Change the bitstream order. Doing this manually through the web 
interface on an item-by-item basis is  p  a  i  n  f  u  l  l  y  
sloow – does anyone know a way to somehow do it in batch? (This may be 
wishful thinking: I’ve looked at the underlying database structure and I don’t 
even know the logic of what I want: somehow to have bitstreams with ANON READ 
permissions to be reassigned lower bitstream order numbers than other 
bitstreams.)

Honestly both sound like even if a solution is possible it would be painfully 
complex, but thought it worth a try!

Ngā mihi,

Deborah
––
Deborah Fitchett
Head of Department: Digital Services

––
Library, Teaching and Learning – Te Wharepūrākau
PO Box 85064, Lincoln University
Lincoln 7647, Christchurch, New Zealand
+64 3 423 0358
deborah.fitch...@lincoln.ac.nz
ltl.lincoln.ac.nz

––
Lincoln University
Te Whare Wānaka o Aoraki
––




"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."

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.