Re: [dspace-tech] Re: How to make login mandatory

2017-10-19 Thread Bollini Andrea 
Hi Brendow,
you don't need to customize the software to achieve that.
You should restrict the access to the bitstreams, using the resource policies, 
to a group, say "Registered Users".
To do that:
- you need to use the advanced policies manager to bulk replace the policy on 
all the existent bitstreams, see
http://demo.dspace.org/jspui/tools/authorize
- you should configure all the collections to have a default_bitstream_read 
policy for the group "Registered Users" instead than Anonymous. In this way new 
submission will automatically see their bitstream restricted
https://wiki.duraspace.org/display/DSDOC5x/Functional+Overview#FunctionalOverview-Authorization
- you should configure the authentication to assign the loggedin users to the 
group "Registered Users" automatically, see
https://github.com/DSpace/DSpace/blob/dspace-5.8/dspace/config/modules/authentication-password.cfg#L25
I recommend that you test these steps on a dev environment before to run it in 
production (especially the #1 that will be hard/impossible to reverse).
Andrea

Il 19/10/2017 02:42, Brendow Adriel ha scritto:
You tried alter the web.xml to redirect the users to login page when they 
access the metadata or bitstreams?

Em quarta-feira, 18 de outubro de 2017 18:20:26 UTC-2, Ricardo Campos escreveu:
Hi.

I've got a demand on DSpace 5.6. JSPUI: to make login mandatory. This means 
that a user must have an account in the repository in order to donwload or view 
content. She or he can see items metadata but, as said, cannot access related 
files.

I made somes changes in ItemTag.java so now the unlogged user will see a 
message like:


[https://lh3.googleusercontent.com/-N_WCicMPC7c/WeevVZmDaBI/Aqk/lN5O8XDu8-gW_UXcsHu7RIe64opEj5XGgCLcBGAs/s320/restricao.JPG]

The red message says that the user must log in and if she is not yet a user she 
can sign in clicking the blue link.

Everything works fine but in one simple situation:

1. The user goes into an item page and sees the red message
2. The user logs in and go to the page, again
[now the problem]
3. The user sees the old page with the red message

If the user is not naïve, she will click to reload the page and the problem is 
gone.

Unfortunatelly, most users see this as an error (and indeed it is) and send 
messages asking for help.

It seems the problem is related to caching the pages and I tried to insert 
 tags in the head of the item page but it didn't solve the problem.

As I said I have a DSpace 5.6, JSPUI, running in a Ubuntu 14.04 box with Tomcat 
7.

Any help is welcome.

Thanks.

Ricardo

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

--
Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato non infetto.
Clicca qui per segnalarlo come 
spam.


--
Andrea Bollini
Chief Technology and Innovation Officer

4Science,  www.4science.it
office: Via Edoardo D'Onofrio 304, 00155 Roma, Italy
mobile: +39 333 934 1808
skype: a.bollini
linkedin: andreabollini
orcid: -0002-9029-1854

an Itway Group Company
Italy, France, Spain, Portugal, Greece, Turkey, Lebanon, Qatar, U.A.Emirates

--
Questo messaggio e' stato analizzato da Libra ESVA ed e' risultato non infetto.
This message was scanned by Libra ESVA and is believed to be clean.

-- 
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: dspace 5 rest and embargo

2017-10-19 Thread Anis 

Just to answer my own question.

Just adding groupId, year, month, day query parameters at the bitstream 
creation step should work, but didn't. Problem is, it actually doesn't 
remove the default policy, so I added 
policy.delete();
to here 

 (the 
second for-loop could be refactored out, and do the deletion in the first), 
now it works!

- Anis

On Wednesday, October 18, 2017 at 4:00:36 PM UTC+3, Anis wrote:
>
> Hi! I'm considering doing ingestion through dspace rest api, but I've a 
> question regarding embargo. I got a working idea in my head (which I 
> tested, and it works) and the flow would go something like this: 
> 1. Create item
> 2. Create Bitstream for item
> 3. Fetch policies for the bitstream
> 4. Delete TYPE_INHERITED policy
> 5. Create my own policy with the embargo date.
> This is quite cumbersome and not failsafe (connection failure after step 2 
> leaves the bitstream open), is it possible to somehow pass a policy with 
> creating a bitstream, or is there some special command to add embargoed 
> items? I've tried to read through the documentation, but to no avail. Help 
> would be greatly appreciated, thank you!
>
>
> - Anis
>

-- 
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] managing dspace, user registration error

2017-10-19 Thread Jack-Morel AWAYA 
Hello. I am new in Dspace management and i am working on some project which 
goal is to make an digital library. And actually i am in front of a bug and 
I would like you help me to fix it.  I am working on Dspace 5.5 with 
xmlui.I have used gmail server gateway.  And, when the users conduct the 
self-registration by entering their email, an url is generated and sent to 
that user's email. When the users click on that url, they got an error, 
"Page cannot be found". I don't know how to fix that problem.  Please I 
need your help to fix that problem and I would glad to have your reply as 
soon as possible in order to continue my work on the project. Thank you.
Best regards.
Jack-Morel.

-- 
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: "Key for add operation must be defined" error when starting Tomcat

2017-10-19 Thread uttam dhakal 
Hello,

I have got the exact same problem, did you find the solution to your 
problem?

Thank you

On Wednesday, January 18, 2017 at 7:02:42 PM UTC+1, m.ne...@icm.edu.pl 
wrote:
>
> Thanks, but that is probably not mine case.  I have just removed all 
> spaces unnecessary spaces in both dspace.cfg and local.cfg and DSpace still 
> does not start.  Event
>
> ant update
>
> command would stop at test_database phase:
>
> test_database:
>  [java] Failure during kernel init: Key for add operation must be 
> defined!
>  [java] java.lang.IllegalArgumentException: Key for add operation must 
> be defined!
>  [java] at 
> org.apache.commons.configuration.tree.DefaultExpressionEngine.prepareAdd(DefaultExpressionEngine.java:420)
>  [java] at 
> org.apache.commons.configuration.HierarchicalConfiguration.addPropertyDirect(HierarchicalConfiguration.java:383)
>  [java] at 
> org.apache.commons.configuration.AbstractConfiguration.addPropertyValues(AbstractConfiguration.java:423)
>  [java] at 
> org.apache.commons.configuration.AbstractConfiguration.append(AbstractConfiguration.java:1271)
>  [java] at 
> org.apache.commons.configuration.ConfigurationUtils.convertToHierarchical(ConfigurationUtils.java:252)
>  [java] at 
> org.apache.commons.configuration.CombinedConfiguration$ConfigData.getTransformedRoot(CombinedConfiguration.java:943)
>  [java] at 
> org.apache.commons.configuration.CombinedConfiguration.constructCombinedNode(CombinedConfiguration.java:793)
>  [java] at 
> org.apache.commons.configuration.CombinedConfiguration.getRootNode(CombinedConfiguration.java:626)
>  [java] at 
> org.apache.commons.configuration.HierarchicalConfiguration.fetchNodeList(HierarchicalConfiguration.java:958)
>  [java] at 
> org.apache.commons.configuration.CombinedConfiguration.fetchNodeList(CombinedConfiguration.java:739)
>  [java] at 
> org.apache.commons.configuration.HierarchicalConfiguration.getProperty(HierarchicalConfiguration.java:344)
>  [java] at 
> org.dspace.servicemanager.config.DSpaceConfigurationService.setProperty(DSpaceConfigurationService.java:354)
>  [java] at 
> org.dspace.servicemanager.config.DSpaceConfigurationService.setDynamicProperties(DSpaceConfigurationService.java:539)
>  [java] at 
> org.dspace.servicemanager.config.DSpaceConfigurationService.loadInitialConfig(DSpaceConfigurationService.java:504)
>  [java] at 
> org.dspace.servicemanager.config.DSpaceConfigurationService.(DSpaceConfigurationService.java:87)
>  [java] at 
> org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:148)
>  [java] at 
> org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:128)
>  [java] at 
> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:49)
>  [java] Exception in thread "main" java.lang.IllegalStateException: 
> Failure during kernel init: Key for add operation must be defined!
>  [java] at 
> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:65)
>  [java] Caused by: java.lang.IllegalArgumentException: Key for add 
> operation must be defined!
>  [java] at 
> org.apache.commons.configuration.tree.DefaultExpressionEngine.prepareAdd(DefaultExpressionEngine.java:420)
>  [java] at 
> org.apache.commons.configuration.HierarchicalConfiguration.addPropertyDirect(HierarchicalConfiguration.java:383)
>  [java] at 
> org.apache.commons.configuration.AbstractConfiguration.addPropertyValues(AbstractConfiguration.java:423)
>  [java] at 
> org.apache.commons.configuration.AbstractConfiguration.append(AbstractConfiguration.java:1271)
>  [java] at 
> org.apache.commons.configuration.ConfigurationUtils.convertToHierarchical(ConfigurationUtils.java:252)
>  [java] at 
> org.apache.commons.configuration.CombinedConfiguration$ConfigData.getTransformedRoot(CombinedConfiguration.java:943)
>  [java] at 
> org.apache.commons.configuration.CombinedConfiguration.constructCombinedNode(CombinedConfiguration.java:793)
>  [java] at 
> org.apache.commons.configuration.CombinedConfiguration.getRootNode(CombinedConfiguration.java:626)
>  [java] at 
> org.apache.commons.configuration.HierarchicalConfiguration.fetchNodeList(HierarchicalConfiguration.java:958)
>  [java] at 
> org.apache.commons.configuration.CombinedConfiguration.fetchNodeList(CombinedConfiguration.java:739)
>  [java] at 
> org.apache.commons.configuration.HierarchicalConfiguration.getProperty(HierarchicalConfiguration.java:344)
>  [java] at 
> org.dspace.servicemanager.config.DSpaceConfigurationService.setProperty(DSpaceConfigurationService.java:354)
>  [java] at 
> org.dspace.servicemanager.config.DSpaceConfigurationService.setDynamicProperties(DSpaceConfigurationService.java:539)
>  [java] at 
> org.dspace.servicemanager.config.DSpaceConfigurationService.loa

Re: [dspace-tech] Re: How to make login mandatory

2017-10-19 Thread Ricardo Campos 
Thanks, Brendow and Andrea.

I'll test this procedure.

Grazie mille

Ricardo

Em quinta-feira, 19 de outubro de 2017 05:45:23 UTC-2, Bollini Andrea 
escreveu:
>
> Hi Brendow,
> you don't need to customize the software to achieve that.
> You should restrict the access to the bitstreams, using the resource 
> policies, to a group, say "Registered Users". 
> To do that:
> - you need to use the advanced policies manager to bulk replace the policy 
> on all the existent bitstreams, see
> http://demo.dspace.org/jspui/tools/authorize
> - you should configure all the collections to have a 
> default_bitstream_read policy for the group "Registered Users" instead than 
> Anonymous. In this way new submission will automatically see their 
> bitstream restricted
>
> https://wiki.duraspace.org/display/DSDOC5x/Functional+Overview#FunctionalOverview-Authorization
> - you should configure the authentication to assign the loggedin users to 
> the group "Registered Users" automatically, see 
>
> https://github.com/DSpace/DSpace/blob/dspace-5.8/dspace/config/modules/authentication-password.cfg#L25
> I recommend that you test these steps on a dev environment before to run 
> it in production (especially the #1 that will be hard/impossible to 
> reverse).
> Andrea
>
> Il 19/10/2017 02:42, Brendow Adriel ha scritto:
>
> You tried alter the web.xml to redirect the users to login page when they 
> access the metadata or bitstreams?
>
> Em quarta-feira, 18 de outubro de 2017 18:20:26 UTC-2, Ricardo Campos 
> escreveu: 
>>
>> Hi. 
>>
>> I've got a demand on DSpace 5.6. JSPUI: to make login mandatory. This 
>> means that a user must have an account in the repository in order to 
>> donwload or view content. She or he can see items metadata but, as said, 
>> cannot access related files.
>>
>> I made somes changes in ItemTag.java so now the unlogged user will see a 
>> message like:
>>
>>
>> 
>>
>> The red message says that the user must log in and if she is not yet a 
>> user she can sign in clicking the blue link.
>>
>> Everything works fine but in one simple situation:
>>
>> 1. The user goes into an item page and sees the red message
>> 2. The user logs in and go to the page, again
>> [now the problem]
>> 3. The user sees the old page with the red message
>>
>> If the user is not naïve, she will click to reload the page and the 
>> problem is gone.
>>
>> Unfortunatelly, most users see this as an error (and indeed it is) and 
>> send messages asking for help.
>>
>> It seems the problem is related to caching the pages and I tried to 
>> insert  tags in the head of the item page but it didn't solve the 
>> problem.
>>
>> As I said I have a DSpace 5.6, JSPUI, running in a Ubuntu 14.04 box with 
>> Tomcat 7.
>>
>> Any help is welcome.
>>
>> Thanks.
>>
>> Ricardo
>>
>> -- 
> 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 
> 
> .
>
>
> -- 
> Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato non 
> infetto. 
> Clicca qui per segnalarlo come spam. 
>  
>
>
> -- 
> Andrea Bollini
> Chief Technology and Innovation Officer
>
> 4Science,  www.4science.it
> office: Via Edoardo D'Onofrio 304, 00155 Roma, Italy
> mobile: +39 333 934 1808
> skype: a.bollini
> linkedin: andreabollini
> orcid: -0002-9029-1854
>
> an Itway Group Company
> Italy, France, Spain, Portugal, Greece, Turkey, Lebanon, Qatar, U.A.Emirates
>
> -- 
> This message has been checked by Libra ESVA and is believed to be clean.
>

-- 
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] Re: "Key for add operation must be defined" error when starting Tomcat

2017-10-19 Thread Tim Donohue 
Hi Uttam,

This error sounds like it is related to the configuration of DSpace 6.x,
since it seems to come from the new Apache Commons Configuration settings.

https://wiki.duraspace.org/display/DSDOC6x/Configuration+Reference#ConfigurationReference-ConfigurationFileSyntax

Have you checked that your configuration files for any preceding or
trailing spaces (as described earlier in this thread)?  Did you upgrade
from DSpace 5 and perhaps forget to update the configuration of DSpace (the
configuration system changed between DSpace 5 and 6, see:
https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace#UpgradingDSpace-ReleaseNotes/SignificantChanges

You could also either diffing your configs against the out-of-the-box
configurations to see if that shows any obvious misconfigurations.  Or you
could temporarily revert to the out-of-the-box configurations to see if
that resolves the issue, and then slowly update it to your existing
configuration.

Essentially, this sounds like a configuration issue in one of your *.cfg
files. Unfortunately the Apache Commons Configuration system doesn't seem
to return a very useful error message here, so I cannot say for certain
which file or configuration is the problem.

Good luck, and please let us know on this mailing list if you discover the
issue.  We haven't been able to reproduce this problem yet, so if you find
a way to do so, we can add it to our documentation, etc.

- Tim

On Thu, Oct 19, 2017 at 6:11 AM uttam dhakal  wrote:

> Hello,
>
> I have got the exact same problem, did you find the solution to your
> problem?
>
> Thank you
>
> On Wednesday, January 18, 2017 at 7:02:42 PM UTC+1, m.ne...@icm.edu.pl
> wrote:
>>
>> Thanks, but that is probably not mine case.  I have just removed all
>> spaces unnecessary spaces in both dspace.cfg and local.cfg and DSpace still
>> does not start.  Event
>>
>> ant update
>>
>> command would stop at test_database phase:
>>
>> test_database:
>>  [java] Failure during kernel init: Key for add operation must be
>> defined!
>>  [java] java.lang.IllegalArgumentException: Key for add operation
>> must be defined!
>>  [java] at
>> org.apache.commons.configuration.tree.DefaultExpressionEngine.prepareAdd(DefaultExpressionEngine.java:420)
>>  [java] at
>> org.apache.commons.configuration.HierarchicalConfiguration.addPropertyDirect(HierarchicalConfiguration.java:383)
>>  [java] at
>> org.apache.commons.configuration.AbstractConfiguration.addPropertyValues(AbstractConfiguration.java:423)
>>  [java] at
>> org.apache.commons.configuration.AbstractConfiguration.append(AbstractConfiguration.java:1271)
>>  [java] at
>> org.apache.commons.configuration.ConfigurationUtils.convertToHierarchical(ConfigurationUtils.java:252)
>>  [java] at
>> org.apache.commons.configuration.CombinedConfiguration$ConfigData.getTransformedRoot(CombinedConfiguration.java:943)
>>  [java] at
>> org.apache.commons.configuration.CombinedConfiguration.constructCombinedNode(CombinedConfiguration.java:793)
>>  [java] at
>> org.apache.commons.configuration.CombinedConfiguration.getRootNode(CombinedConfiguration.java:626)
>>  [java] at
>> org.apache.commons.configuration.HierarchicalConfiguration.fetchNodeList(HierarchicalConfiguration.java:958)
>>  [java] at
>> org.apache.commons.configuration.CombinedConfiguration.fetchNodeList(CombinedConfiguration.java:739)
>>  [java] at
>> org.apache.commons.configuration.HierarchicalConfiguration.getProperty(HierarchicalConfiguration.java:344)
>>  [java] at
>> org.dspace.servicemanager.config.DSpaceConfigurationService.setProperty(DSpaceConfigurationService.java:354)
>>  [java] at
>> org.dspace.servicemanager.config.DSpaceConfigurationService.setDynamicProperties(DSpaceConfigurationService.java:539)
>>  [java] at
>> org.dspace.servicemanager.config.DSpaceConfigurationService.loadInitialConfig(DSpaceConfigurationService.java:504)
>>  [java] at
>> org.dspace.servicemanager.config.DSpaceConfigurationService.(DSpaceConfigurationService.java:87)
>>  [java] at
>> org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:148)
>>  [java] at
>> org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:128)
>>  [java] at
>> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:49)
>>  [java] Exception in thread "main" java.lang.IllegalStateException:
>> Failure during kernel init: Key for add operation must be defined!
>>  [java] at
>> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:65)
>>  [java] Caused by: java.lang.IllegalArgumentException: Key for add
>> operation must be defined!
>>  [java] at
>> org.apache.commons.configuration.tree.DefaultExpressionEngine.prepareAdd(DefaultExpressionEngine.java:420)
>>  [java] at
>> org.apache.commons.configuration.HierarchicalConfiguration.addPropertyDirect(HierarchicalConfigura

Re: [dspace-tech] Re: "Key for add operation must be defined" error when starting Tomcat

2017-10-19 Thread uttam dhakal 
Thank you, I copied the default local.cfg file and it worked. I still can't 
figure out the problem with my local.cfg but I now know where the problem 
is.

On Thursday, October 19, 2017 at 4:01:38 PM UTC+2, Tim Donohue wrote:
>
> Hi Uttam,
>
> This error sounds like it is related to the configuration of DSpace 6.x, 
> since it seems to come from the new Apache Commons Configuration settings. 
>
>
> https://wiki.duraspace.org/display/DSDOC6x/Configuration+Reference#ConfigurationReference-ConfigurationFileSyntax
>
> Have you checked that your configuration files for any preceding or 
> trailing spaces (as described earlier in this thread)?  Did you upgrade 
> from DSpace 5 and perhaps forget to update the configuration of DSpace (the 
> configuration system changed between DSpace 5 and 6, see: 
> https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace#UpgradingDSpace-ReleaseNotes/SignificantChanges
>
> You could also either diffing your configs against the out-of-the-box 
> configurations to see if that shows any obvious misconfigurations.  Or you 
> could temporarily revert to the out-of-the-box configurations to see if 
> that resolves the issue, and then slowly update it to your existing 
> configuration.
>
> Essentially, this sounds like a configuration issue in one of your *.cfg 
> files. Unfortunately the Apache Commons Configuration system doesn't seem 
> to return a very useful error message here, so I cannot say for certain 
> which file or configuration is the problem.
>
> Good luck, and please let us know on this mailing list if you discover the 
> issue.  We haven't been able to reproduce this problem yet, so if you find 
> a way to do so, we can add it to our documentation, etc.
>
> - Tim
>
> On Thu, Oct 19, 2017 at 6:11 AM uttam dhakal  > wrote:
>
>> Hello,
>>
>> I have got the exact same problem, did you find the solution to your 
>> problem?
>>
>> Thank you
>>
>> On Wednesday, January 18, 2017 at 7:02:42 PM UTC+1, m.ne...@icm.edu.pl 
>> wrote:
>>>
>>> Thanks, but that is probably not mine case.  I have just removed all 
>>> spaces unnecessary spaces in both dspace.cfg and local.cfg and DSpace still 
>>> does not start.  Event
>>>
>>> ant update
>>>
>>> command would stop at test_database phase:
>>>
>>> test_database:
>>>  [java] Failure during kernel init: Key for add operation must be 
>>> defined!
>>>  [java] java.lang.IllegalArgumentException: Key for add operation 
>>> must be defined!
>>>  [java] at 
>>> org.apache.commons.configuration.tree.DefaultExpressionEngine.prepareAdd(DefaultExpressionEngine.java:420)
>>>  [java] at 
>>> org.apache.commons.configuration.HierarchicalConfiguration.addPropertyDirect(HierarchicalConfiguration.java:383)
>>>  [java] at 
>>> org.apache.commons.configuration.AbstractConfiguration.addPropertyValues(AbstractConfiguration.java:423)
>>>  [java] at 
>>> org.apache.commons.configuration.AbstractConfiguration.append(AbstractConfiguration.java:1271)
>>>  [java] at 
>>> org.apache.commons.configuration.ConfigurationUtils.convertToHierarchical(ConfigurationUtils.java:252)
>>>  [java] at 
>>> org.apache.commons.configuration.CombinedConfiguration$ConfigData.getTransformedRoot(CombinedConfiguration.java:943)
>>>  [java] at 
>>> org.apache.commons.configuration.CombinedConfiguration.constructCombinedNode(CombinedConfiguration.java:793)
>>>  [java] at 
>>> org.apache.commons.configuration.CombinedConfiguration.getRootNode(CombinedConfiguration.java:626)
>>>  [java] at 
>>> org.apache.commons.configuration.HierarchicalConfiguration.fetchNodeList(HierarchicalConfiguration.java:958)
>>>  [java] at 
>>> org.apache.commons.configuration.CombinedConfiguration.fetchNodeList(CombinedConfiguration.java:739)
>>>  [java] at 
>>> org.apache.commons.configuration.HierarchicalConfiguration.getProperty(HierarchicalConfiguration.java:344)
>>>  [java] at 
>>> org.dspace.servicemanager.config.DSpaceConfigurationService.setProperty(DSpaceConfigurationService.java:354)
>>>  [java] at 
>>> org.dspace.servicemanager.config.DSpaceConfigurationService.setDynamicProperties(DSpaceConfigurationService.java:539)
>>>  [java] at 
>>> org.dspace.servicemanager.config.DSpaceConfigurationService.loadInitialConfig(DSpaceConfigurationService.java:504)
>>>  [java] at 
>>> org.dspace.servicemanager.config.DSpaceConfigurationService.(DSpaceConfigurationService.java:87)
>>>  [java] at 
>>> org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:148)
>>>  [java] at 
>>> org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:128)
>>>  [java] at 
>>> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:49)
>>>  [java] Exception in thread "main" java.lang.IllegalStateException: 
>>> Failure during kernel init: Key for add operation must be defined!
>>>  [java] at 
>>> org.dspace.app.launcher.ScriptLaunc

[dspace-tech] Related Items Feature in DSpace 5.8.

2017-10-19 Thread Rosarie Coughlan 
Hi,

In DSpace 5.8 there is a feature called "Related Items" which displays on 
an item record items related by title, author, creator and subject.

We would like to link data items that are stored in a different repository 
(our data repository) so that the end user sees a link to the data item 
(title and persistent link) under "Related Items" in DSpace.

What approach would you suggest?
Cheers
Rosarie 


-- 
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: DSpace 5.x - hide communities/collections from a user

2017-10-19 Thread Brendow Adriel 
https://stackoverflow.com/questions/37122851/hiding-collections-and-sub-collections-in-dspace

Em quinta-feira, 19 de outubro de 2017 14:40:06 UTC-2, Alex Fletcher 
escreveu:
>
> I looked through the documentation and there didn't seem to be a method of 
> doing this built-into the system.
>
> We can hide items within a collection from a user (authorizations), but 
> there doesn't seem a way to hide an entire collection (or community) from a 
> user based on authorizations.
>
> Is this feasible/possible at all?
>
> Thanks,
>
> Alex
>
>

-- 
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] Two OAI problems with DSpace 6.2

2017-10-19 Thread Evgeni Dimitrov 
I have a freshly installed DSpace 6.2 with 15 items in it.
I have not changed anything in the OAI configuration.
Two of the items have READ access for certain groups only. The rest are
accessible to everybody.

Problem 1.
When I run
dspace oai import -c

I get in dspace.log two exceptions (I suppose for each of the restricted
access items):

2017-10-19 17:55:22,650 WARN  org.dspace.xoai.util.ItemUtils @
Authorization denied for action READ on
BITSTREAM:3d21ebf7-ef3e-4d98-a265-c4a516b1740b by user null
org.dspace.authorize.AuthorizeException: Authorization denied for action
READ on BITSTREAM:3d21ebf7-ef3e-4d98-a265-c4a516b1740b by user null

The whole text of the exception is very long.

Problem 2.
After that I am trying
http://localhost:8080/oai/request?verb=Identify
http://localhost:8080/oai/request?verb=ListSets
http://localhost:8080/oai/request?verb=ListMetadataFormats
http://localhost:8080/oai/request?verb=ListIdentifiers&metadataPrefix=xoai
and it all works.

But for
http://localhost:8080/oai/request?verb=GetRecord&identifier=oai:localhost:nls/3&metadataPrefix=xoai
(nls/3 is an item accessible to everybody)
I get in the browser

java.io.IOException:
com.lyncode.xoai.dataprovider.exceptions.WritingXmlException: Error trying
to output ''

org.dspace.xoai.services.impl.cache.DSpaceXOAICacheService.store(DSpaceXOAICacheService.java:113)

The whole text of the exception is very long.

My question is - am I missing something in the configuration or is this a
known problem with DSpace 6.2?


Virus-free.
www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

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