Re: [dspace-tech] Wrong handle/url generated when running dspace update-handle-prefix

[euler]

Hi Tom,

Even if I batch edit the metadata fields to start with 
http://hdl.handle.net/, and re-run the script, although it will update the 
prefix, the problem is that the generated new URL will not match the 
dc.identifier.uri value. It is always off by 1. I also tried merging my 
local branch to the latest upstream 6_x branch (Since the pull request you 
mentioned was already merged). Same results. Any advice on how to fix this?

Thanks in advance,
euler

On Wednesday, June 28, 2017 at 9:52:14 PM UTC+8, Tom Desair (Atmire) wrote:
>
> I've corrected this in the following pull-request 
> https://github.com/DSpace/DSpace/pull/1727
>
> In DSpace 6.0 the update-handle-prefix script only updates metadata fields 
> if they start with "http://hdl.handle.net/";. That is why your metadata 
> values are not updated.
>
> You can port the changes to the UpdateHandlePrefix.java file (
> https://github.com/DSpace/DSpace/pull/1727/files#diff-5c44dc1a4d6071cdcfdf65b29e108d6d)
>  
> and then re-run the script.
>
> Best regards,
> Tom
>  
> [image: logo] Tom Desair
> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
> Gaston Geenslaan 14, Leuven 3001, Belgium
> www.atmire.com 
> 
>
> 2017-06-28 15:11 GMT+02:00 Claudia Jürgen  >:
>
>> Hello euler,
>>
>> did you backup your db prior to updating the handle sequence?
>> Actually the handle_id is taken to build the new handle rather than the
>> existing handle.
>> You may take a look at the handle table in the backup and the new one.
>>
>> I'll file a ticket in JIRA this may have sideeffects on AIP and other
>> things.
>>
>> Hope this helps
>>
>> Claudia Jürgen
>>
>> Am 28.06.2017 um 08:37 schrieb euler:
>>
>>> Dear All,
>>>
>>> The repository I'm working on is running with the latest dspace-6_x 
>>> branch.
>>> Based on this link: Updating Existing Handle Prefixes
>>> <
>>> https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-UpdatingExistingHandlePrefixes
>>> >,
>>> I run the following command [dspace]/bin/dspace update-handle-prefix
>>> 123456789 20.500.12066 after we received the handle prefix from CNRI and
>>> updating the config.dct file. Below is the output of the command:
>>>
>>> Getting information about handles from database...
>>> In your repository will be updated 391 handles to new prefix 20.500.12066
>>> from original 123456789!
>>>
>>> Servlet container (e.g. Apache Tomcat, Jetty, Caucho Resin) must be 
>>> running.
>>> If it is necessary, please make a backup of the database.
>>> Are you ready to continue? [y/n]: y
>>>
>>> Updating handle table... 391 items updated
>>> Updating metadatavalues table... 2 metadata values updated
>>> Handles successfully updated in database.
>>>
>>> Re-creating browse and search indexes...
>>> Browse and search indexes are ready now.
>>>
>>> All done successfully. Please check the DSpace logs!
>>>
>>> Now, below is a screenshot of an item *before* I ran the update handle
>>> command.
>>>
>>> <
>>> https://lh3.googleusercontent.com/-OlfqlTpuXno/WVNJdV_8kuI/BfA/RSuaHmeHQ28UpXXqt_ug3ru2zjH61WO4QCLcBGAs/s1600/b4-update-prefix.PNG
>>> >
>>>
>>> Below is the same item *after* the update prefix command:
>>>
>>>
>>> <
>>> https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/BfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG
>>> >Notice
>>> that the updated handle is now 20.500.12066/391 which is clearly wrong
>>> because it should be 20.500.12066/390 since the original URI was
>>> 123456789/390. The handle 20.500.12066/390 is now assigned to the owning
>>> collection of the item. Is this a bug? I hope someone from the list can
>>> reproduce this. Please help on how to resolve this issue. This could 
>>> really
>>> be a problem if you have thousands of records from your demo system that
>>> you would like to migrate to a production server.
>>> <
>>> https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/BfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG
>>> >Thanks
>>> in advance and hoping for your favorable response,
>>> <
>>> https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/BfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG
>>> >
>>> <
>>> https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/BfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG
>>> >
>>> euler
>>> <
>>> https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/BfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG
>>> >
>>>
>>>
>> --
>> Claudia Juergen
>> Eldorado
>>
>> Technische Universität Dortmund
>> Universitätsbibliothek
>> Vogelpothsweg 76
>> 44227 Dortmund
>>
>> Tel.: +49 231-755 40 43
>> Fax: +49 231-755 40 32
>> claudia...@tu-dortmund.de 
>> www.ub.tu-dortmund.de
>>
>> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Si

Re: [dspace-tech] Wrong handle/url generated when running dspace update-handle-prefix

[euler]

Hi Claudia,

On Thursday, June 29, 2017 at 8:48:27 PM UTC+8, Claudia Jürgen wrote:
>
> Hello euler, 
>
> 5 is the site see: 
>
> https://github.com/DSpace/DSpace/blob/dspace-6.0/dspace-api/src/main/java/org/dspace/core/Constants.java
>  
>
> It tested the update handle prefix and this line was the only one 
> changed see 
> https://jira.duraspace.org/browse/DS-3632 
>
> In your old db did any other lines exist where the handle_id did not 
> match the number in handle? 
>

All the lines or rows in my old db did not match with the handle_id and the 
the handle number, it is always handle_id = handle + 1.

*handle_id |handle   | resource_type_id |*
1 | 123456789/0 |5 |
2 | 123456789/1 |4 |
   
So when I run the update handle script, the handle_id would be equals the 
handle number (123456789/0 will be replaced by [handle]/1). The problem is 
that the updated handle prefix is not matching with the prefix found in 
dc.identifier.uri.

Thanks,
euler


> Claudia 
>
>
>
> Am 29.06.2017 um 08:43 schrieb euler: 
> > Hi Claudia, 
> > 
> >  From your suggestion to compare the handle table from the backup to the 
> new 
> > one, I found out that the original handle table contains 123456789/0 
> handle 
> > entry with a value of a 5 in the resource_type_id. When I run the update 
> > handle script, this handle becomes 20.500.12066/1. I'm pretty sure this 
> is 
> > the same row because the uuid is still the same. And so, all the updated 
> > handles was incremented by 1 from the original handles. I wonder why the 
> > handle table has an entry of [handle]/0. Is this expected? With regards 
> to 
> > my issue of the handles that are off by 1 from the original handle, how 
> can 
> > I fix it? I suppose this should be done in the database level. Please 
> > advise for the appropriate sql query. 
> > 
> > Thanks in advance, 
> > euler 
> > 
> > On Wednesday, June 28, 2017 at 9:11:03 PM UTC+8, Claudia Jürgen wrote: 
> >> Hello euler, 
> >> 
> >> did you backup your db prior to updating the handle sequence? 
> >> Actually the handle_id is taken to build the new handle rather than the 
> >> existing handle. 
> >> You may take a look at the handle table in the backup and the new one. 
> >> 
> >> I'll file a ticket in JIRA this may have sideeffects on AIP and other 
> >> things. 
> >> 
> >> Hope this helps 
> >> 
> >> Claudia Jürgen 
> >> 
> >> Am 28.06.2017 um 08:37 schrieb euler: 
> >>> Dear All, 
> >>> 
> >>> The repository I'm working on is running with the latest dspace-6_x 
> >> branch. 
> >>> Based on this link: Updating Existing Handle Prefixes 
> >>> < 
> >> 
> https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-UpdatingExistingHandlePrefixes>,
>  
>
> >> 
> >>> I run the following command [dspace]/bin/dspace update-handle-prefix 
> >>> 123456789 20.500.12066 after we received the handle prefix from CNRI 
> and 
> >>> updating the config.dct file. Below is the output of the command: 
> >>> 
> >>> Getting information about handles from database... 
> >>> In your repository will be updated 391 handles to new prefix 
> >> 20.500.12066 
> >>> from original 123456789! 
> >>> 
> >>> Servlet container (e.g. Apache Tomcat, Jetty, Caucho Resin) must be 
> >> running. 
> >>> If it is necessary, please make a backup of the database. 
> >>> Are you ready to continue? [y/n]: y 
> >>> 
> >>> Updating handle table... 391 items updated 
> >>> Updating metadatavalues table... 2 metadata values updated 
> >>> Handles successfully updated in database. 
> >>> 
> >>> Re-creating browse and search indexes... 
> >>> Browse and search indexes are ready now. 
> >>> 
> >>> All done successfully. Please check the DSpace logs! 
> >>> 
> >>> Now, below is a screenshot of an item *before* I ran the update handle 
> >>> command. 
> >>> 
> >>> < 
> >> 
> https://lh3.googleusercontent.com/-OlfqlTpuXno/WVNJdV_8kuI/BfA/RSuaHmeHQ28UpXXqt_ug3ru2zjH61WO4QCLcBGAs/s1600/b4-update-prefix.PNG>
>  
>
> >> 
> >>> Below is the same item *after* the update prefix command: 
> >>> 
> >>> 
> >>> < 
> >> 
> https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/BfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG>Notice
>  
>
> >> 
> >>> that the updated handle is now 20.500.12066/391 which is clearly wrong 
> >>> because it should be 20.500.12066/390 since the original URI was 
> >>> 123456789/390. The handle 20.500.12066/390 is now assigned to the 
> owning 
> >>> collection of the item. Is this a bug? I hope someone from the list 
> can 
> >>> reproduce this. Please help on how to resolve this issue. This could 
> >> really 
> >>> be a problem if you have thousands of records from your demo system 
> that 
> >>> you would like to migrate to a production server. 
> >>> < 
> >> 
> https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/BfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG>Thanks
>  
>
> >> 
> >>> 

Re: [dspace-tech] Re: The 6 RC version of DSpace-CRIS is now available

[danielKim]

Thanks! My installation was successfully completed.
Thanks for you assistance and kindness.
Regards
Daniel

-- 
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] "Date issued" discovery sidebar is frozen at 2015

[David A]

That did the trick, Genevieve! Thanks so much :)
In lieu of a way to show the most recent years, this is the next best thing.

Cheers,
David

On Tue, May 16, 2017 at 7:07 PM,  wrote:

> Hi David,
>
> Have you removed the references to 'searchFilterIssued' in your discovery
> index?  Personally I would leave the searchFilterIssued uncommented, and
> remove/comment out the reference from the 'sidebarFacets' in discovery.xml
> (I have never touched spring-dspace-addon-discovery-configuration-services.xml
> so I don't know about the configuration in there).  e.g.
> homepageConfiguration -> sidebarFacets or defaultConfiguration ->
> sidebarFacets.  From memory the sidebarFacets and list are still required
> in those, but you can effectlvely have an empty list if desired.
>
> Regards,
>
> Genevieve
>
>
> On Friday, 5 May 2017 05:53:41 UTC+10, David A wrote:
>
>> Hi everybody,
>>
>> So I gave up on trying to edit the number of years listed on the sidebar,
>> and have decided to just remove the date-issued bean from the sidebar
>> altogether.
>>
>> However, even this is presenting a challenge. I thought it would be as
>> simple as commenting-out or deleting the following from *discovery.xml*
>>  and *spring-dspace-addon-discovery-configuration-services.xml*
>>
>> 
>> 
>> 
>> 
>> dc.date.issued
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> But when I comment out or delete this code from those two files, it
>> triggers a 404 error. This happens, even after resetting the server and
>> update-discovery-index.
>>
>>
>> 
>>
>>
>>
>> Any hints?
>>
>> Many thanks,
>> David
>>
>>
>> On Wednesday, February 15, 2017 at 2:28:26 PM UTC-5, David A wrote:
>>
>>> Hi everybody,
>>>
>>> An update: I was able to get over the SSH error and am now able to run
>>> the update-discovery-index. After looking more at the documentation
>>> , here's what I
>>> have tried to no avail:
>>>
>>>1. I noticed that unlike Author and Subject sidebar facets, the Date
>>>Issued facet does not offer a "View more" link for what I presume is the
>>>default maximum of 10 entries
>>>2. So I increased the optional >>value="15"/> to  sidebar facet which sorts 
>>> by
>>>dc.date.issued
>>>3. I made this change in two files:
>>>   1. config/spring/discovery/spring-dspace-addon-discovery-config
>>>   uration-services.xml
>>>   2. config/spring/api/discovery.xml
>>>4. Then, I ran [dspace]/bin/dspace *update-discovery-index* and
>>>didn't seem to receive an error:
>>>
>>>INFO [main] (DSpaceKernelInit.java:52) - Created new kernel:
>>>DSpaceKernel:org.dspace:name=18bbb8f5-f9a8-4b1d-8e94-189ebb8
>>>347b0,type=DSpaceKernel:lastLoad=null:loadTime=0:
>>>running=false:kernel=null
>>> INFO [main] (ConfigurationManager.java:1224) - Loading from
>>>classloader: file:/apps/dspace/config/dspace.cfg
>>> INFO [main] (ConfigurationManager.java:1224) - Using dspace
>>>provided log configuration (log.init.config)
>>> INFO [main] (ConfigurationManager.java:1224) - Loading:
>>>/apps/dspace/config/log4j.properties
>>>
>>>5. Then I restarted the server
>>>6. But the problem persists.
>>>
>>>
>>> Has anybody else encounter this?
>>>
>>> FYI, it appears I'm using XMLUI for DSpace version 3.0.
>>>
>>> Thanks,
>>> David
>>>
>>> On Fri, Feb 3, 2017 at 2:38 PM, David A wrote:
>>>
 Greetings!

 The "Date Issued" list on the Discovery sidebar of our website
  seems to be stuck at 2015, despite
 the fact that we have entries for 2016
 
 .
 The *discover.cfg* and
 *spring-dspace-addon-discovery-configuration-services.xml* have not
 been modified recently, so I don't believe the issue lies there.
 I tried to run update-discovery-index through SSH, and appeared to get
 some errors (see attached "Terminal Saved Output" file).

 Does anybody have any tips on how I might resolve this?

 Many thanks,
 David

 --
 You received this message because you are subscribed to a topic in the
 Google Groups "DSpace Technical Support" group.
 To unsubscribe from this topic, visit https://groups.google.com/d/to
 pic/dspace-tech/dOno8dXeKns/unsubscribe.
 To unsubscribe from this group and all its topics, 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.

>>>
>>> --
> You receiv

[dspace-tech] Fwd: Shibboleth problems in DSpace 6.0

[George Kozak]

HI, Everyone:
A few months ago, I reported a problem that I had with Shibboleth (see
below) and DSpace 6.0.  I have been working on this issue off-and-on, and I
finally solved it.  It turns out that my problem was something that I had
in my old DSpace 5.5 config that I carried over to my DSpace 6.0 local.cfg.
The statement was:
event.dispatcher.default.consumers = authority, versioning, discovery,
eperson, harvester

Once I removed the statement from my local.cfg file, shibboleth started to
work.  I just wanted to warn anyone who upgrades from older DSpace to 6.0,
to be careful of just carrying over config settings from their old version
to 6.0.   I spent a lot of time comparing settings, and I missed this one.
-- 
***
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
g...@cornell.edu

-- Forwarded message --
From: George Kozak 
Date: Fri, Apr 7, 2017 at 2:34 PM
Subject: Shibboleth problems in DSpace 6.0
To: DSpace Technical Support 


Hi...
I upgraded to DSpace 6.0 from DSpace 5.5 (modified Mirage2 theme), and we
discovered that we are having a Shibboleth login problem.  The login works,
but we end up with a message: "Authentication Failed".
In the DSpace logs, I see:
2017-04-07 14:05:51,604 ERROR org.dspace.authenticate.ShibAuthentication @
Unable to successfully authenticate using shibboleth for user because of an
exception.java.lang.IllegalStateException: Unable to aquire dispatcher
named default

-- 
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] Wrong handle/url generated when running dspace update-handle-prefix

[Claudia Jürgen]

Hello euler,

5 is the site see:
https://github.com/DSpace/DSpace/blob/dspace-6.0/dspace-api/src/main/java/org/dspace/core/Constants.java

It tested the update handle prefix and this line was the only one
changed see
https://jira.duraspace.org/browse/DS-3632

In your old db did any other lines exist where the handle_id did not
match the number in handle?

Claudia



Am 29.06.2017 um 08:43 schrieb euler:

Hi Claudia,

 From your suggestion to compare the handle table from the backup to the new
one, I found out that the original handle table contains 123456789/0 handle
entry with a value of a 5 in the resource_type_id. When I run the update
handle script, this handle becomes 20.500.12066/1. I'm pretty sure this is
the same row because the uuid is still the same. And so, all the updated
handles was incremented by 1 from the original handles. I wonder why the
handle table has an entry of [handle]/0. Is this expected? With regards to
my issue of the handles that are off by 1 from the original handle, how can
I fix it? I suppose this should be done in the database level. Please
advise for the appropriate sql query.

Thanks in advance,
euler

On Wednesday, June 28, 2017 at 9:11:03 PM UTC+8, Claudia Jürgen wrote:

Hello euler,

did you backup your db prior to updating the handle sequence?
Actually the handle_id is taken to build the new handle rather than the
existing handle.
You may take a look at the handle table in the backup and the new one.

I'll file a ticket in JIRA this may have sideeffects on AIP and other
things.

Hope this helps

Claudia Jürgen

Am 28.06.2017 um 08:37 schrieb euler:

Dear All,

The repository I'm working on is running with the latest dspace-6_x

branch.

Based on this link: Updating Existing Handle Prefixes
<

https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-UpdatingExistingHandlePrefixes>,


I run the following command [dspace]/bin/dspace update-handle-prefix
123456789 20.500.12066 after we received the handle prefix from CNRI and
updating the config.dct file. Below is the output of the command:

Getting information about handles from database...
In your repository will be updated 391 handles to new prefix

20.500.12066

from original 123456789!

Servlet container (e.g. Apache Tomcat, Jetty, Caucho Resin) must be

running.

If it is necessary, please make a backup of the database.
Are you ready to continue? [y/n]: y

Updating handle table... 391 items updated
Updating metadatavalues table... 2 metadata values updated
Handles successfully updated in database.

Re-creating browse and search indexes...
Browse and search indexes are ready now.

All done successfully. Please check the DSpace logs!

Now, below is a screenshot of an item *before* I ran the update handle
command.

<

https://lh3.googleusercontent.com/-OlfqlTpuXno/WVNJdV_8kuI/BfA/RSuaHmeHQ28UpXXqt_ug3ru2zjH61WO4QCLcBGAs/s1600/b4-update-prefix.PNG>


Below is the same item *after* the update prefix command:


<

https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/BfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG>Notice


that the updated handle is now 20.500.12066/391 which is clearly wrong
because it should be 20.500.12066/390 since the original URI was
123456789/390. The handle 20.500.12066/390 is now assigned to the owning
collection of the item. Is this a bug? I hope someone from the list can
reproduce this. Please help on how to resolve this issue. This could

really

be a problem if you have thousands of records from your demo system that
you would like to migrate to a production server.
<

https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/BfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG>Thanks


in advance and hoping for your favorable response,
<

https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/BfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG>


<

https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/BfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG>


euler
<

https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/BfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG>

--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia...@tu-dortmund.de 
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie
ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für
diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender
und vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher
Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines
solchen Schriftstücks per Telefax erfolgen.

[dspace-tech] Re: Add publications to organizations

[gonzalo perl]

I try to excecute 
*org.dspace.app.webui.cris.components.CRISOUConfigurerComponent, 
i get java errors, but i think that it is installed. But i can not see the 
relation *crisitem.author.dept. Does Somebody know what box i need to 
select?

I try to select some box but i get errors.

Regards
Gonzalo



El jueves, 29 de junio de 2017, 7:49:27 (UTC+1), gonzalo perl escribió:
>
> Solved. You only need to add an ID when and a publication.
>
> Regards
> Gonzalo
>
> El miércoles, 28 de junio de 2017, 19:31:21 (UTC+1), gonzalo perl escribió:
>>
>> Hello everybody
>>
>> I added some organizations and publications to my Dspace-Dcris, but i can 
>> not find how add the publications to the organizations.
>>
>>  Does Somebody know how to do it?
>>
>> Regards
>> Gonzalo
>>
>>
>>
>>
>>

-- 
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] Solr index locked for all cores at startup

[Stefano Bocconi]

Hi Mark,

Thanks again for your explanation, at the end I removed the auto deploy from 
the appBase Host (and kept the Contexts)  as I need to control the path of the 
web apps and also which one are deployed.

Stefano

> On 15 Jun 2017, at 15:25, Mark H. Wood  wrote:
> 
> You have explicitly declared a Context for each of the webapp.s, and also 
> have an appBase pointing at what appears to be the target of a DSpace 
> installation, with autoDeploy='true'.  So you've told Tomcat to load 
> individual webapp.s from various directories under /dspace and *also* to 
> deploy any webapp.s found in the directory /home/dspace/dspace/webapps.  
> Probably you need one or the other.  I would remove or comment out the 
>  elements.  (The Tomcat maintainers discourage the use of  
> in server.xml, although it does work.  If you need full control over a 
> Context, you can define it in a separate file as described in the Tomcat 
> documentation, but then don't place the webapp.s in the appBase directory.)
> 
> https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace#InstallingDSpace-Installation
>  lays out two ways of deploying DSpace in Tomcat, which you may find helpful.
> 
> 
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "DSpace Technical Support" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/dspace-tech/FLE1oXDt-vU/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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 
> .

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


signature.asc
Description: Message signed with OpenPGP using GPGMail

R: [dspace-tech] Re: The 6 RC version of DSpace-CRIS is now available

[Pascarelli Luigi Andrea]

Hello,

try to use the content of the example configuration at 
https://github.com/4Science/DSpace/blob/dspace-6_x_x-cris/dspace/config/local.cfg.EXAMPLE

take in mind that in DSpace 6 we have the configuration managed by Apache 
Common Configuration and the config/local.cfg is the place to fill 
configuration parameters.



Inviato dal mio dispositivo Samsung


 Messaggio originale 
Da: danielKim 
Data: 29/06/2017 12:37 (GMT+01:00)
A: DSpace Technical Support 
Cc: dspace-commun...@googlegroups.com, Bollini Andrea 

Oggetto: [dspace-tech] Re: The 6 RC version of DSpace-CRIS is now available

Dear Bollini,

I get an error message when I do "and fresh_install" at database checking part.

test_database:
 [java] Failure during kernel init: Infinite loop in property interpolation 

 of 
${cris.ametrics.elsevier.scopus.enabled}: cris.ametrics.elsevier.scopus.enabl   

  ed
 [java] java.lang.IllegalStateException: Infinite loop in property 
interpola   

  tion of ${cris.ametrics.elsevier.scopus.enabled}: 
cris.ametrics.elsevier.scopus.  

   enabled
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.checkCyclicSubsti   

  
tution(StrSubstitutor.java:701)
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.substitute(StrSub   

  stitutor.java:645)
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.substitute(StrSub   

  stitutor.java:656)
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.substitute(StrSub   

  stitutor.java:563)
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.replace(StrSubsti   

  tutor.java:305)
 [java] at 
org.apache.commons.configuration.PropertyConverter.interpolat   

  
e(PropertyConverter.java:1040)
 [java] at 
org.apache.commons.configuration.AbstractConfiguration.interp   

  
olate(AbstractConfiguration.java:449)
 [java] at 
org.apache.commons.configuration.AbstractConfiguration.interp   

  
olate(AbstractConfiguration.java:436)
 [java] at 
org.apache.commons.configuration.AbstractConfiguration.getLis   

  
t(AbstractConfiguration.java:1128)
 [java] at 
org.apache.commons.configuration.AbstractConfiguration.getLis   

  
t(AbstractConfiguration.java:1117)
 [java] at 
org.apache.commons.configuration.ConfigurationConverter.getPr   

  
operties(ConfigurationConverter.java:113)
 [java] at 
org.dspace.servicemanager.config.DSpaceConfigurationService.g   

  
etProperties(DSpaceConfigurationService.java:98)
 [java] at 
org.dspace.servicemana

[dspace-tech] Re: The 6 RC version of DSpace-CRIS is now available

[danielKim]

>
> Dear Bollini,
>

I get an error message when I do "and fresh_install" at database checking 
part.

test_database:
 [java] Failure during kernel init: Infinite loop in property 
interpolation   

   of ${cris.ametrics.elsevier.scopus.enabled}: 
cris.ametrics.elsevier.scopus.enabl 

ed
 [java] java.lang.IllegalStateException: Infinite loop in property 
interpola   

  tion of ${cris.ametrics.elsevier.scopus.enabled}: 
cris.ametrics.elsevier.scopus. 

enabled
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.checkCyclicSubsti   

  
tution(StrSubstitutor.java:701)
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.substitute(StrSub   

  
stitutor.java:645)
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.substitute(StrSub   

  
stitutor.java:656)
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.substitute(StrSub   

  
stitutor.java:563)
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.replace(StrSubsti   

  
tutor.java:305)
 [java] at 
org.apache.commons.configuration.PropertyConverter.interpolat   

  
e(PropertyConverter.java:1040)
 [java] at 
org.apache.commons.configuration.AbstractConfiguration.interp   

  
olate(AbstractConfiguration.java:449)
 [java] at 
org.apache.commons.configuration.AbstractConfiguration.interp   

  
olate(AbstractConfiguration.java:436)
 [java] at 
org.apache.commons.configuration.AbstractConfiguration.getLis   

  
t(AbstractConfiguration.java:1128)
 [java] at 
org.apache.commons.configuration.AbstractConfiguration.getLis   

  
t(AbstractConfiguration.java:1117)
 [java] at 
org.apache.commons.configuration.ConfigurationConverter.getPr   

  
operties(ConfigurationConverter.java:113)
 [java] at 
org.dspace.servicemanager.config.DSpaceConfigurationService.g   

  
etProperties(DSpaceConfigurationService.java:98)
 [java] at 
org.dspace.servicemanager.config.DSpaceConfigurationService.t   

  
oString(DSpaceConfigurationService.java:553)
 [java] at 
org.dspace.servicemanager.config.DSpaceConfigurationService.l   

  
oadInitialConfig(DSpaceConfigurationService.java:506)
 [java] at 
org.dspace.servicemanager.config.DSpaceConf

[dspace-tech] Delete records from discover box (publications page)

[gonzalo perl]

Hello everybody

I deleted some publications and the researchers, but I did something wrong 
and I can see the list of researchers in the discover box of the 
publications page and on the home page i can see the number of publications.

Is there any way I can delete records without having to re-create the 
database?

Regards
Gonzalo

-- 
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] Re: Internal System Error, :general_jspui_error:java.lang.NullPointerException java.lang.NullPointerExc

[informatique . ensv]

up ... up up  please,

Le mercredi 28 juin 2017 15:05:11 UTC+1, informat...@gmail.com a écrit :
>
> Hi everybody;
>
> i succefully installed dspace 6 on debian jessie, with jspui as webapps, 
> tomcat8, jdk8 
> when i try to create a community,  it displays this error log message 
> shown below, how to fix this error,i reinstalled it three times, whith th 
> same error et every. 
> thank you.
>
> 2017-06-28 15:55:02,137 WARN  org.dspace.app.util.Util @ Unable to 
> recoginze UUID from String "null". Will return null.
> java.lang.IllegalArgumentException: Invalid UUID string: null
> at java.util.UUID.fromString(UUID.java:194)
> at org.dspace.app.util.Util.getUUIDParameter(Util.java:262)
> at 
> org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.doDSPost(EditCommunitiesServlet.java:155)
> 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:648)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
> at 
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
> at 
> org.dspace.app.webui.filter.AdminOnlyFilter.doFilter(AdminOnlyFilter.java:76)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
> at 
> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
> at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:474)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
> at 
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:624)
> at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
> at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:349)
> at 
> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:783)
> at 
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
> at 
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:798)
> at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1434)
> at 
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.lang.Thread.run(Thread.java:748)
> 2017-06-28 15:55:02,138 WARN  org.dspace.app.util.Util @ Unable to 
> recoginze UUID from String "null". Will return null.
> java.lang.IllegalArgumentException: Invalid UUID string: null
> at java.util.UUID.fromString(UUID.java:194)
> at org.dspace.app.util.Util.getUUIDParameter(Util.java:262)
> at 
> org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.processConfirmEditCommunity(EditCommunitiesServlet.java:520)
> at 
> org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.doDSPost(EditCommunitiesServlet.java:237)
> 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:648)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
> at 
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at 
> org.apache.ca