Re: [dspace-tech] SWORD

[genevieve . turner]

For 2, I'm not sure about the other workflow steps but for the 
accept/reject/edit metadata if it has people in it then it will put it into 
the task pool when uploaded via sword.

On Wednesday, 9 November 2016 03:06:55 UTC+11, momeven wrote:
>
> very helpful thanks 
>
> did a bit more reading and this is what I understand now  for my use case, 
> which is submit a brand new item to a collections workflow  
>
> 1) have to configure such that  password authentication is enabled 
> 2) have to figure out how to tell sword to stick the submission into a 
> workflow 
> 3) have to write a  hopefully small script that establishes the connection 
> and pushes a zip file :  metadata plus bitstreams 
> 4) have to figure the format of that zip file out 
>
> 2 and 4  look like they have DSPace specific pieces  - so I am asking you 
> guys - anybody with an answer ? 
> Somebody must have done this or something very similar. 
>
> Monika
>
>  
> Monika Mevenkamp
> mo.m...@gmail.com 
>
> http://mo-meven.tumblr.com/
> http://mcmprogramming.com/mo.meven/
>
>
>
>  
> Monika Mevenkamp
> mo.m...@gmail.com 
>
> http://mo-meven.tumblr.com/
> http://mcmprogramming.com/mo.meven/
>
>
>
> On Nov 7, 2016, at 4:36 PM, Luiz dos Santos  > wrote:
>
> Thank you Andrea, perfect!
>
> Luiz Claudio Santos
> http://luizclaudiosantos.me/
>
> On Mon, Nov 7, 2016 at 4:29 PM, Andrea Schweer  > wrote:
>
>> Hi Monika,
>>
>> On 11/08/2016 10:18 AM, Monika Mevenkamp wrote:
>>
>> We are building a  document submission system in sharepoint, which 
>> collects pdfs and metadata - essentially 
>> At the end we plan to push the docs over to our DSPACE instance; version 
>> 5.5 
>>
>> We’d like to use Sword instead of exporting to a shared filesystem and 
>> then uploading with  /dspace/bin/dspace import 
>> Items need to be put into the workflow of their destination collections. 
>>
>> Where can I learn: 
>>
>> How to put Zip files together - are the same kind of ZIPs that the item 
>> importer uses ? 
>> How to issue the import/deposit request ? 
>> How to define the destination collection ? 
>>
>>
>> Any example code anywhere ? 
>>
>>
>> You can find lots of documentation on SWORD here, including specs: 
>> http://swordapp.org/
>>
>> There's a github repository here: https://github.com/swordapp/
>>
>> There is also a mailing list: 
>> https://lists.sourceforge.net/lists/listinfo/sword-app-tech
>>
>> First of all you'll need to decide whether to use Sword v1 or Sword v2. 
>> v1 is fire-and-forget -- you deposit your Sword package and make no further 
>> changes to it. Sword v2 is designed to let you make changes to the item 
>> after deposit. v1 is simpler; we recently decided to go with v2 for a 
>> fire-and-forget application since there is a Java client library for v2 but 
>> not v1.
>>
>> I fiddled a little with Sword and it looks like it assumes password 
>> authentication. Is that correct ? 
>>
>>
>> That's right. For v1 at least (don't remember for v2) there is a config 
>> flag to let Sword deposits use password auth even if password auth isn't 
>> enabled for 'normal' users.
>>
>> cheers,
>> Andrea
>>
>> -- 
>> Dr Andrea Schweer
>> Lead Software Developer, ITS Information Systems
>> The University of Waikato, Hamilton, New Zealand+64-7-837 9120
>>
>>
>> -- 
>> 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.
>>
>
>
>

-- 
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] Submission made via REST API does not trigger collection workflow approval process.

[Javier Távara]

Hello.
Is this the same behaviour in DSpace 5.5? Are REST submissions bypassing 
the collection's workflow?

El miércoles, 3 de agosto de 2016, 11:42:58 (UTC-5), Emilio Lorenzo 
escribió:
>
> Hi Martin, 
>
> Yes we detected that situation in some instances of Dspace 5.  I have just 
> submitted a JIRA issue  https://jira.duraspace.org/browse/DS-3281  and 
> tomorrow we expect to upload the changes we made to include the workflow.   
>
> Hope this helps.
>
> Best regards
>
> Emilio 
>
>
>
>
>
> El 01/08/2016 a las 15:20, Martin Walk escribió:
>
> Hello, 
>
> I investigated adding items via the REST API and noticed that they are 
> immediately added to the archive, bypassing the collection's workflow.
> Is there a configuration to change this behaviour?
> If not, are others aware of the fact and are there already efforts to 
> change the situation?
>
> Best regards, Martin.
>
>
>
> -- 
> 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.
>
>
>

-- 
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: Embargo settings

[Fitchett, Deborah]

Hi,

It does seem to be using the date in the field specified by embargo.field.terms 
in dspace.cfg.  I’ve successfully got our crosswalk to send across a specific 
date in -mm-dd format into that field, and when the item is approved into 
the collection, the bitstream policy is created with a start-date of that date.

It presumably only doesn’t do the same for the item policy because we’ve kept 
that step out of our submission workflow. (Or possibly it /would/ break if that 
step was there and we just haven’t tried it. :-) )

The potentially confusing thing is that, because the metadata is used to create 
the policy when the item is approved, when you look at the bitstream in 
workflow, no date appears there. But that’s just something for our admin staff 
to look out for.

The manual work for us comes because all our via-Elements items get approved 
into a restricted collection in the first instance, and then we move them into 
an open collection. Inheriting anon policies is fine if we’re making it open 
immediately, but if we’re embargoing the bitstreams then we need to edit the 
policies at that point.

Deborah

From: Andrea Schweer [mailto:schw...@waikato.ac.nz]
Sent: Wednesday, 9 November 2016 10:58 a.m.
To: Fitchett, Deborah ; DSpace Technical 
Support 
Subject: Re: [dspace-tech] RE: Embargo settings

Hi,
On 11/09/2016 10:22 AM, Fitchett, Deborah wrote:
So from some more poking and re-rereading the documentation, I *think* the 
situation is that the embargo.field.terms functionality is only used in the 
pre-DSpace 3.0 embargo model – does this sound right to others?

Yes that's right.


If this is the case then I need to follow up with Symplectic Elements to see if 
they’ll upgrade their embargo interface to let users submit a date instead of a 
term, and in the meantime either do something fancy with the crosswalks, or get 
our repository staff to apply the desired embargo date manually in workflow.

We have very customised embargo functionality, so I'm not too sure on DSpace 
default behaviour. But I think you will need to use the 'manual in workflow' 
option since (IIRC) metadata-based embargoes don't work at all in the new 
model. Embargoes now use the authorisation policies.

cheers,
Andrea



--

Dr Andrea Schweer

Lead Software Developer, ITS Information Systems

The University of Waikato, Hamilton, New Zealand

+64-7-837 9120


P Please consider the environment before you print this email.
"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."

-- 
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] Help with setting up virus scan curation task

[Hardy Pottinger]

Hi, I have a DSpace 5-based pilot project I am setting up on RHEL 6, and
it's mostly working. However, I cannot seem to get the clamd server talking
to DSpace. I have Clamd installed and running on a TCP port bound to
localhost, and the curation task is configured to run as part of the
submission process. However, uploading a file fails no matter what I try.
With virus scanning turned off, I *can* upload a file. When I re-enable it
as part of the submission process, uploading a virus-free file fails, with
just an enigmatic yellow exclamation mark on the upload screen, no error
message. When I attempt to upload an EICAR test file (a well-known way to
test AV software) a similar error condition is shown (yellow exclamation
mark, no errror message). Anyway, I'm hoping this might sound familiar to
someone... this feels like I've missed a configuration somewhere. The
dspace.log file isn't very helpful at the moment. I will try turning on
debug logging to try to get more information. Any other suggestions? Thanks!

--Hardy

-- 
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: Embargo settings

[Andrea Schweer]

  
  
Hi,

On 11/09/2016 10:22 AM, Fitchett,
  Deborah wrote:


  
  
  
  
  So from some
  more poking and re-rereading the documentation, I *think*
  the situation is that the embargo.field.terms functionality is
  only used in the pre-DSpace 3.0 embargo model – does this
  sound right to others?


Yes that's right.


  If this is the case then I need to
  follow up with Symplectic Elements to see if they’ll upgrade
  their embargo interface to let users submit a date instead of
  a term, and in the meantime either do something fancy with the
  crosswalks, or get our repository staff to apply the desired
  embargo date manually in workflow.
  


We have very customised embargo functionality, so I'm not too sure
on DSpace default behaviour. But I think you will need to use the
'manual in workflow' option since (IIRC) metadata-based embargoes
don't work at all in the new model. Embargoes now use the
authorisation policies.

cheers,
Andrea

-- 
Dr Andrea Schweer
Lead Software Developer, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
+64-7-837 9120
  




-- 
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 user dspace

[Mark Wood]

On Monday, November 7, 2016 at 2:16:06 PM UTC-5, hoska...@gmail.com wrote:
>
> thanks for your reply
>
> in my system tomcat run under user tomcat8. i have not changed this.
> i set  the dspace's installation directory owner to user tomcat8. (Chown 
> -R tomcat8:tomcat8 /opt/dspace)
> i afraid for security problems: the database's password is present in 
> dspace.cfg file
> what are the rights permssions that should be set for dspace's 
> configuration directory.
>

You must trust your Servlet container (Tomcat):  it is the process that 
runs DSpace, and thus it must have access to DSpace's configuration.  No 
other user needs any access, so config/dspace.cfg's mode can be 400 or 600 
if you wish.  The DSpace configuration is outside of any webapp. directory 
tree and should not be visible, or even addressable, through Tomcat.

-- 
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] SWORD

[Monika Mevenkamp]

very helpful thanks 

did a bit more reading and this is what I understand now  for my use case, 
which is submit a brand new item to a collections workflow  

1) have to configure such that  password authentication is enabled 
2) have to figure out how to tell sword to stick the submission into a workflow 
3) have to write a  hopefully small script that establishes the connection and 
pushes a zip file :  metadata plus bitstreams 
4) have to figure the format of that zip file out 

2 and 4  look like they have DSPace specific pieces  - so I am asking you guys 
- anybody with an answer ? 
Somebody must have done this or something very similar. 

Monika

 
Monika Mevenkamp
mo.me...@gmail.com

http://mo-meven.tumblr.com/
http://mcmprogramming.com/mo.meven/



 
Monika Mevenkamp
mo.me...@gmail.com

http://mo-meven.tumblr.com/
http://mcmprogramming.com/mo.meven/



> On Nov 7, 2016, at 4:36 PM, Luiz dos Santos  wrote:
> 
> Thank you Andrea, perfect!
> 
> Luiz Claudio Santos
> http://luizclaudiosantos.me/ 
> 
> On Mon, Nov 7, 2016 at 4:29 PM, Andrea Schweer  > wrote:
> Hi Monika,
> 
> On 11/08/2016 10:18 AM, Monika Mevenkamp wrote:
>> We are building a  document submission system in sharepoint, which collects 
>> pdfs and metadata - essentially 
>> At the end we plan to push the docs over to our DSPACE instance; version 5.5 
>> 
>> We’d like to use Sword instead of exporting to a shared filesystem and then 
>> uploading with  /dspace/bin/dspace import 
>> Items need to be put into the workflow of their destination collections. 
>> 
>> Where can I learn: 
>> How to put Zip files together - are the same kind of ZIPs that the item 
>> importer uses ? 
>> How to issue the import/deposit request ? 
>> How to define the destination collection ? 
>> 
>> Any example code anywhere ? 
> 
> You can find lots of documentation on SWORD here, including specs: 
> http://swordapp.org/ 
> 
> There's a github repository here: https://github.com/swordapp/ 
> 
> 
> There is also a mailing list: 
> https://lists.sourceforge.net/lists/listinfo/sword-app-tech 
> 
> 
> First of all you'll need to decide whether to use Sword v1 or Sword v2. v1 is 
> fire-and-forget -- you deposit your Sword package and make no further changes 
> to it. Sword v2 is designed to let you make changes to the item after 
> deposit. v1 is simpler; we recently decided to go with v2 for a 
> fire-and-forget application since there is a Java client library for v2 but 
> not v1.
> 
>> I fiddled a little with Sword and it looks like it assumes password 
>> authentication. Is that correct ? 
> 
> That's right. For v1 at least (don't remember for v2) there is a config flag 
> to let Sword deposits use password auth even if password auth isn't enabled 
> for 'normal' users.
> 
> cheers,
> Andrea
> 
> -- 
> Dr Andrea Schweer
> Lead Software Developer, ITS Information Systems
> The University of Waikato, Hamilton, New Zealand
> +64-7-837 9120 
> 
> -- 
> 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 
> .
> 

-- 
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: Cannot access SOLR remotely

[Chris Gray]

Solr should never be exposed to the Web.  It is the full administrative 
interface for Solr and has no authority control.  Making it available on 
the Web would be huge vulnerability.

Solr is only accessible from localhost.  You can access it by setting up an 
SSH tunnel from your machine to the server and then access the Solr 
interface via the tunnel.

On Monday, November 7, 2016 at 1:33:15 PM UTC-5, Donald Bynum wrote:
>
> I have DSpace 5.5 on Tomcat with Oracle as the DB.  I want to run some 
> SOLR queries from a remote client, i.e. NOT running on the Tomcat server as 
> localhost.  I need to do this in order to create some remote reporting 
> functions.  Accessing SOLR on the Tomcat server as localhost is just fine: 
> http://localhost:8080/solr/...
>
> When I try the same from a remote client:  
> http://myserver.thing.org:8080/solr... I get a 403 error - "*Access to 
> the specified resource has been forbidden."*
>
> Any guidance here would be much appreciated.
>
> Regards,
>
> Don.
>
>
>

-- 
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] Cannot access SOLR remotely

[Donald Bynum]

Hi Bruno,

I am running Tomcat 8 and I have updated my server.xml as the wiki 
suggested.  Here is what my  container looks like now (I highlighted 
what I added):


  
  
  
  


  
  




   
 
  
  


  


I have restarted Tomcat, but now the SOLR instance returns ""*Access to the 
specified resource has been forbidden."*  for all access attempts, 
including localhost.  Further guidance would be much appreciated.

Regards,

Don.

On Monday, November 7, 2016 at 2:31:47 PM UTC-5, Bruno Nocera Zanette wrote:

> Donald,
> This is the expected behavior for SOLR, for security reasons.
>
> Take a look at this wiki to learn how to bypass this restriction:
>
> https://wiki.duraspace.org/display/DSPACE/Solr#Solr-Bypassinglocalhostrestrictiontemporarily
>
> Em seg, 7 de nov de 2016 às 16:33, Donald Bynum  > escreveu:
>
>> I have DSpace 5.5 on Tomcat with Oracle as the DB.  I want to run some 
>> SOLR queries from a remote client, i.e. NOT running on the Tomcat server as 
>> localhost.  I need to do this in order to create some remote reporting 
>> functions.  Accessing SOLR on the Tomcat server as localhost is just fine: 
>> http://localhost:8080/solr/...
>>
>> When I try the same from a remote client:  
>> http://myserver.thing.org:8080/solr... I get a 403 error - "*Access to 
>> the specified resource has been forbidden."*
>>
>> Any guidance here would be much appreciated.
>>
>> Regards,
>>
>> Don.
>>
>>
>> -- 
>> 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.
>>
> -- 
> Bruno Nocera Zanette
> +55 41 9992-2508
>

-- 
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] How to add unit tests to classes in dspace/modules/additions?

[Luiz dos Santos]

Hi Martin,

   After you marked the java folder as test folder, as you said in the
stackoverflow, did you try to refresh the project in IntelliJ?

Best
Luiz

On Tuesday, November 8, 2016, Martin Walk 
wrote:

> Hi,
>
> I write curation tasks (for DSpace 6) that I add
> to dspace/modules/additions.
> I want to add unit tests, of course. But I have problems to find the right
> place for the unit tests, or the right configuration for them to be run.
>
> Here is what I tried and what error messages I get in IntelliJ. I also
> posted the question on Stackoverflow:
> https://stackoverflow.com/questions/40406373/how-to-set-
> up-unit-tests-for-classes-in-dspace-modules-additions
>
> I want to set up unit tests for a curation task that i put in
> dspace/modules/additions. I use intelliJ IDEA and try to configure sources
>  and tests folders. I wanted to use the following folder structure but
> could not get the configuration in intelliJ right.
>
>  [] DSpace Source Folder
>[] dspace
>  [] modules
> [] additions
>[] src
>   [] main
>  [] java
> […]
>   [] test
>  [] java
> […]
> [] jspui
> [] oai
> [] rdf
> […]
>
> Is this structure reasonable?
> How can I configure the folders in intelliJ's Project Structure so that it
> recognises my test folder?
>
> If I try to mark it as "Test Source Folder" in IntelliJ's Project
> Structure I get the following error message:
>
> Source root "/.../DSpace6/dspace/modules/additions/src/test" cannot be
> defined in module "dspace" because it belongs to content of nested module
> "additions"
>
> --
> 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.
>


-- 
Luiz Claudio Santos
http://luizclaudiosantos.me/

-- 
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 add unit tests to classes in dspace/modules/additions?

[Martin Walk]

Hi,

I write curation tasks (for DSpace 6) that I add 
to dspace/modules/additions.
I want to add unit tests, of course. But I have problems to find the right 
place for the unit tests, or the right configuration for them to be run.

Here is what I tried and what error messages I get in IntelliJ. I also 
posted the question on Stackoverflow:
https://stackoverflow.com/questions/40406373/how-to-set-up-unit-tests-for-classes-in-dspace-modules-additions

I want to set up unit tests for a curation task that i put in 
dspace/modules/additions. I use intelliJ IDEA and try to configure sources
 and tests folders. I wanted to use the following folder structure but 
could not get the configuration in intelliJ right.

 [] DSpace Source Folder
   [] dspace
 [] modules
[] additions
   [] src
  [] main
 [] java
[…]
  [] test
 [] java
[…]
[] jspui
[] oai
[] rdf
[…] 

Is this structure reasonable?
How can I configure the folders in intelliJ's Project Structure so that it 
recognises my test folder?

If I try to mark it as "Test Source Folder" in IntelliJ's Project Structure 
I get the following error message:

Source root "/.../DSpace6/dspace/modules/additions/src/test" cannot be 
defined in module "dspace" because it belongs to content of nested module 
"additions"

-- 
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: add new field on request form

[NAUSS Repository]

this solution it is for the input submission form my question about the 
request copy form , sorry regard my post  

On Sunday, November 6, 2016 at 11:51:39 AM UTC+3, NAUSS Repository wrote:
>
> i need  to add new field on request form dspace 5.5 with Mirage2  
> please help
>

-- 
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] Running vagrant-dspace ?

[charlesfrancois . rey]

Thanks for your feedback, Tom.

Here's what allowed me to move forward so far :
- change vagrant_box to 'ubuntu/xenial64'
- and the corresponding vagrant_box_url to 
'https://vagrantcloud.com/ubuntu/xenial64'

It seems that there was an issue with the xenial64 box 
(http://stackoverflow.com/questions/37283269/how-i-can-get-vagrant-folder-on-ubuntu-xenial64/38078133#38078133),
 
that is now solved. And where nothing happened with the 
box-cutter/ubuntu1604 box, now at least some (if not all) provisioning is 
being done with ubuntu/xenial64.

But in the end, I get this error message :
 

> ==> vagrant-dspace: Debug: Finishing transaction 41343800
>
==> vagrant-dspace: Debug: Storing state
> ==> vagrant-dspace: Info: Creating state file 
> /var/lib/puppet/state/state.yaml
> ==> vagrant-dspace: Debug: Stored state in 0.01 seconds
> ==> vagrant-dspace: Notice: Finished catalog run in 2443.84 seconds
> ==> vagrant-dspace: Debug: Using settings: adding file resource 'rrddir': 
> 'File[/var/lib/puppet/rrd]{:path=>"/var/lib/puppet/rrd", :mode=>"750", 
> :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, 
> :links=>:follow, :backup=>false}'
> ==> vagrant-dspace: Debug: /File[/var/lib/puppet/rrd]/ensure: created
> ==> vagrant-dspace: Debug: Finishing transaction 28479260
> ==> vagrant-dspace: Debug: Received report to process from 
> dspace.vagrant.dev
> ==> vagrant-dspace: Debug: Evicting cache entry for environment 
> 'production'
> ==> vagrant-dspace: Debug: Caching environment 'production' (ttl = 0 sec)
> ==> vagrant-dspace: Debug: Processing report from dspace.vagrant.dev with 
> processor Puppet::Reports::Store
> The SSH command responded with a non-zero exit status. Vagrant
> assumes that this means the command failed. The output for this command
> should be in the log above. Please read the output to determine what
> went wrong.
>

(btw, "vagrant ssh" allows me to connect manually)

Any idea ?

++

-- 
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] oai-pmh resumption token error

[Francisco Monreal]

Hello everyone,

When a service provider attempts to collect our repository an error occurs 
when the resumption token reaches 13600 
(http://digitum.um.es/oai/request?verb=ListRecords=oai_dc13600).
 
For example, in Open Archives the following exception occurs:


El c�digo del status de HTTP : 500

El mensaje del error de HTTP : Error Interno del Servidor

Apache Tomcat/7.0.62 - Informe de Error 
Estado HTTP 500 - Request processing failed; nested exception 
is java.lang.NullPointerExceptiontype Informe de Excepciónmensaje 
Request processing failed; nested exception is 
java.lang.NullPointerExceptiondescripción El servidor 
encontró un error interno que hizo que no pudiera rellenar este 
requerimiento.excepción 
org.springframework.web.util.NestedServletException: Request processing 
failed; nested exception is java.lang.NullPointerException

org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:894)

org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:778)
javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
causa raíz java.lang.NullPointerException
org.dspace.xoai.data.DSpaceSolrItem.init(DSpaceSolrItem.java:43)

org.dspace.xoai.services.impl.xoai.DSpaceItemSolrRepository.retrieveItems(DSpaceItemSolrRepository.java:119)

org.dspace.xoai.services.impl.xoai.DSpaceItemSolrRepository.getItems(DSpaceItemSolrRepository.java:102)

com.lyncode.xoai.dataprovider.data.internal.ItemRepositoryHelper.getItems(ItemRepositoryHelper.java:174)

com.lyncode.xoai.dataprovider.handlers.ListRecordsHandler.handle(ListRecordsHandler.java:75)

com.lyncode.xoai.dataprovider.OAIDataProvider.handle(OAIDataProvider.java:213)

org.dspace.xoai.controller.DSpaceOAIDataProvider.contextAction(DSpaceOAIDataProvider.java:104)
sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:606)

org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:213)

org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:126)

org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:96)

org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:617)

org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:578)

org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:80)

org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)

org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)

org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)

org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:778)
javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
nota La traza completa de la causa de este error se 
encuentra en los archivos de diario de Apache Tomcat/7.0.62.Apache Tomcat/7.0.62



Should the resumptiontoken be modified in version 5.4 of DSpace? Is it 
fixed by updating OAI indexes with dspace oai import?

Thanks in advance.

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