Re: [dspace-tech] dspace7 installation on remote server with apache

[Paul Warner]

Hi Tim,

I got this error message in catalina.out:

java.lang.IllegalArgumentException: Invalid character found in method name. 
HTTP method names must be tokens

I found this information on stackoverflow:

https://stackoverflow.com/questions/42218237/java-lang-illegalargumentexception-invalid-character-found-in-method-name-http

It indicates that the incoming information, which is encoded for tls/ssl, 
is not being read correctly by the java.  Does that ring a bell for someone?

Thanks!
Paul


On Monday, August 10, 2020 at 3:17:57 PM UTC+2, Paul Warner wrote:
>
> Hi Tim,
>
> Thanks for the info.  I tried using the list for my 
> rest.cors.allow-origins, but I am still getting the cors errors.
>
> rest.cors.allowed-origins = ${dspace.ui.url}, https://repo7-test.amad.org
>
> Is there anything else I can try?  Where can I look to see where things 
> are going wrong? 
>
> Thanks again,
> Paul
>
>
> On Friday, August 7, 2020 at 8:33:48 PM UTC+2, Tim Donohue wrote:
>>
>> Hi Paul,
>>
>> You may want to leave your "dspace.ui.url" as it is, and directly 
>> override "rest.cors.allow-origins" in your local.cfg
>>
>> By default, "rest.cors.allow-origins" is ONLY the "dspace.ui.url" as 
>> noted here:
>> https://github.com/DSpace/DSpace/blob/main/dspace/config/modules/rest.cfg#L10
>>
>> However, you can provide it a *list* of URLs that you want the REST API 
>> to respond to.  So, you could modify it to be something like:
>>
>> rest.cors.allowed-origins = ${dspace.ui.url}, http://127.0.0.1:8355, 
>> http://another.url, https://yetanother.url
>>
>> The list can include as many URLs as you want.  The key is that it *MUST* 
>> include "dspace.ui.url" as one of those URLs.  The other URLs can be 
>> whatever you want.
>>
>> Keep in mind that, as we are still in active development, not all of this 
>> is written down. But the expectation is that while *many sites* can leave 
>> the "rest.cors.allow-origins" at it's default setting...some sites 
>> (especially those using proxies or just wanting several URL to access their 
>> REST API for other needs) may need to modify it.
>>
>> Tim
>>
>> --
>> *From:* dspac...@googlegroups.com  on behalf 
>> of Paul Warner 
>> *Sent:* Thursday, August 6, 2020 11:27 PM
>> *To:* DSpace Technical Support 
>> *Subject:* Re: [dspace-tech] dspace7 installation on remote server with 
>> apache 
>>  
>> Hi Tim, 
>>
>> The error is:
>>
>> Cross-Origin Request Blocked: The Same Origin Policy disallows reading 
>> the remote resource at http://127.0.0.1:8355/server/api/authn/status
>>
>> So it is the case that tomcat is refusing the connection.
>>
>> I have tomcat listening only on 127.0.0.1:8355.  And Angular is 
>> listening at localhost:4000.
>>
>> The problem is, I am using apache as a proxy, so I have 3 addresses, 
>> these two, plus our domain name.  Apache passes the requests to 
>> localhost:4000.  
>>
>> I have tried plugging the domain name in for the dspace.ui.url.  I get 
>> the same CORS error.
>>
>> How else can I present the app to the outside world?  I do not think 
>> pointing the Angular server directly out on our domain name is a good idea, 
>> and I do not know how to set up ssh/tls for this server, anyway.  How is 
>> one supposed to run this arrangement when one goes live?  I just need to 
>> make this instance available for my team to test it.
>>
>> Best regards, and thanks for the help!
>> Paul
>>
>>
>>
>> On Tuesday, August 4, 2020 at 4:38:02 PM UTC+2, Tim Donohue wrote: 
>>
>> Hi Paul,
>>
>> Could you provide more info on the CORS errors? 
>>
>> The reason I ask, is that I wonder what URL the backend thinks you are 
>> sending requests from.  CORS errors should only occur if the URL sending 
>> requests (to the REST API) is *not* listed in the 
>> "rest.cors.allowed-origins" 
>> setting.  So, that makes me suspect that the UI is sending requests under a 
>> URL that is *not* identical to what you set for "dspace.ui.url" in the 
>> backend.
>>
>> Generally speaking, the frontend configuration and backend configuration 
>> need to be identical, or you will hit problems.
>>
>> So, this means, in the Angular UI, the "ui" environment settings:
>>
>> https://github.com/DSpace/dspace-angular/blob/main/src/environments/environment.common.ts#L10-L16
>> need to *match* what you configure as "dsp

Re: [dspace-tech] dspace7 installation on remote server with apache

[Paul Warner]

Hi Tim,

Thanks for the info.  I tried using the list for my 
rest.cors.allow-origins, but I am still getting the cors errors.

rest.cors.allowed-origins = ${dspace.ui.url}, https://repo7-test.amad.org

Is there anything else I can try?  Where can I look to see where things are 
going wrong? 

Thanks again,
Paul


On Friday, August 7, 2020 at 8:33:48 PM UTC+2, Tim Donohue wrote:
>
> Hi Paul,
>
> You may want to leave your "dspace.ui.url" as it is, and directly override 
> "rest.cors.allow-origins" in your local.cfg
>
> By default, "rest.cors.allow-origins" is ONLY the "dspace.ui.url" as noted 
> here:
> https://github.com/DSpace/DSpace/blob/main/dspace/config/modules/rest.cfg#L10
>
> However, you can provide it a *list* of URLs that you want the REST API to 
> respond to.  So, you could modify it to be something like:
>
> rest.cors.allowed-origins = ${dspace.ui.url}, http://127.0.0.1:8355, 
> http://another.url, https://yetanother.url
>
> The list can include as many URLs as you want.  The key is that it *MUST* 
> include "dspace.ui.url" as one of those URLs.  The other URLs can be 
> whatever you want.
>
> Keep in mind that, as we are still in active development, not all of this 
> is written down. But the expectation is that while *many sites* can leave 
> the "rest.cors.allow-origins" at it's default setting...some sites 
> (especially those using proxies or just wanting several URL to access their 
> REST API for other needs) may need to modify it.
>
> Tim
>
> --
> *From:* dspac...@googlegroups.com   > on behalf of Paul Warner >
> *Sent:* Thursday, August 6, 2020 11:27 PM
> *To:* DSpace Technical Support >
> *Subject:* Re: [dspace-tech] dspace7 installation on remote server with 
> apache 
>  
> Hi Tim, 
>
> The error is:
>
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the 
> remote resource at http://127.0.0.1:8355/server/api/authn/status
>
> So it is the case that tomcat is refusing the connection.
>
> I have tomcat listening only on 127.0.0.1:8355.  And Angular is listening 
> at localhost:4000.
>
> The problem is, I am using apache as a proxy, so I have 3 addresses, these 
> two, plus our domain name.  Apache passes the requests to localhost:4000.  
>
> I have tried plugging the domain name in for the dspace.ui.url.  I get the 
> same CORS error.
>
> How else can I present the app to the outside world?  I do not think 
> pointing the Angular server directly out on our domain name is a good idea, 
> and I do not know how to set up ssh/tls for this server, anyway.  How is 
> one supposed to run this arrangement when one goes live?  I just need to 
> make this instance available for my team to test it.
>
> Best regards, and thanks for the help!
> Paul
>
>
>
> On Tuesday, August 4, 2020 at 4:38:02 PM UTC+2, Tim Donohue wrote: 
>
> Hi Paul,
>
> Could you provide more info on the CORS errors? 
>
> The reason I ask, is that I wonder what URL the backend thinks you are 
> sending requests from.  CORS errors should only occur if the URL sending 
> requests (to the REST API) is *not* listed in the "rest.cors.allowed-origins" 
> setting.  So, that makes me suspect that the UI is sending requests under a 
> URL that is *not* identical to what you set for "dspace.ui.url" in the 
> backend.
>
> Generally speaking, the frontend configuration and backend configuration 
> need to be identical, or you will hit problems.
>
> So, this means, in the Angular UI, the "ui" environment settings:
>
> https://github.com/DSpace/dspace-angular/blob/main/src/environments/environment.common.ts#L10-L16
> need to *match* what you configure as "dspace.ui.url" on the backend.
>
> Similar, in the Angular UI, the "rest" environment settings:
>
> https://github.com/DSpace/dspace-angular/blob/main/src/environments/environment.common.ts#L20-L26
> need to *match* what you configure as "dspace.server.url" on the backend.
>
> If the "ui" settings don't match, you are likely to end up with CORS 
> errors, as the UI will be sending requests from a slightly different URL 
> and the REST API will block those requests.  This is my _best guess_ at 
> what you might be seeing.
>
> Tim
>
>
> --
> *From:* dspac...@googlegroups.com  on behalf 
> of Paul Warner 
> *Sent:* Tuesday, August 4, 2020 12:32 AM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] dspace7 installation on remote server with apache 
>  
> Hi, 
>
> My team wants very much to test dspace 7, and I have an installation on

Re: [dspace-tech] dspace7 installation on remote server with apache

[Paul Warner]

Hi Tim,

The error is:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the 
remote resource at http://127.0.0.1:8355/server/api/authn/status

So it is the case that tomcat is refusing the connection.

I have tomcat listening only on 127.0.0.1:8355.  And Angular is listening 
at localhost:4000.

The problem is, I am using apache as a proxy, so I have 3 addresses, these 
two, plus our domain name.  Apache passes the requests to localhost:4000.  

I have tried plugging the domain name in for the dspace.ui.url.  I get the 
same CORS error.

How else can I present the app to the outside world?  I do not think 
pointing the Angular server directly out on our domain name is a good idea, 
and I do not know how to set up ssh/tls for this server, anyway.  How is 
one supposed to run this arrangement when one goes live?  I just need to 
make this instance available for my team to test it.

Best regards, and thanks for the help!
Paul



On Tuesday, August 4, 2020 at 4:38:02 PM UTC+2, Tim Donohue wrote:
>
> Hi Paul,
>
> Could you provide more info on the CORS errors? 
>
> The reason I ask, is that I wonder what URL the backend thinks you are 
> sending requests from.  CORS errors should only occur if the URL sending 
> requests (to the REST API) is *not* listed in the "rest.cors.allowed-origins" 
> setting.  So, that makes me suspect that the UI is sending requests under a 
> URL that is *not* identical to what you set for "dspace.ui.url" in the 
> backend.
>
> Generally speaking, the frontend configuration and backend configuration 
> need to be identical, or you will hit problems.
>
> So, this means, in the Angular UI, the "ui" environment settings:
>
> https://github.com/DSpace/dspace-angular/blob/main/src/environments/environment.common.ts#L10-L16
> need to *match* what you configure as "dspace.ui.url" on the backend.
>
> Similar, in the Angular UI, the "rest" environment settings:
>
> https://github.com/DSpace/dspace-angular/blob/main/src/environments/environment.common.ts#L20-L26
> need to *match* what you configure as "dspace.server.url" on the backend.
>
> If the "ui" settings don't match, you are likely to end up with CORS 
> errors, as the UI will be sending requests from a slightly different URL 
> and the REST API will block those requests.  This is my _best guess_ at 
> what you might be seeing.
>
> Tim
>
>
> --
> *From:* dspac...@googlegroups.com   > on behalf of Paul Warner >
> *Sent:* Tuesday, August 4, 2020 12:32 AM
> *To:* DSpace Technical Support >
> *Subject:* [dspace-tech] dspace7 installation on remote server with apache 
>  
> Hi, 
>
> My team wants very much to test dspace 7, and I have an installation on a 
> remote server that uses apache as the frontend proxy.  I did this so I can 
> offer the site to my team with ssl/tls.  They cannot get to the command 
> line on the server, and a command line browser (w3m) does not work with 
> angular anyway.  So they need a url that is external.
>
> I have set the rest.cors settings in local.cfg:
>
> rest.cors.allowed-origins = ${dspace.ui.url}
>
> and have set the dspace.ui.url to the url to apache.  I am still getting 
> cors errors in the browser (Firefox).  There are no errors anywhere else in 
> the logs.
>
> Is there a better way to set up dspace 7 so it is visible from a domain 
> externally?
>
> Best regards,
> Paul
>
> -- 
> All messages to this mailing list should adhere to the DuraSpace Code of 
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> --- 
> You received this message because you are subscribed to the Google Groups 
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to dspac...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/dspace-tech/ee9bb9f8-117d-4113-a0d3-548861121d45o%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/dspace-tech/ee9bb9f8-117d-4113-a0d3-548861121d45o%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/806ba430-b794-4490-9e5b-6371e7654819o%40googlegroups.com.

[dspace-tech] dspace7 installation on remote server with apache

[Paul Warner]

Hi,

My team wants very much to test dspace 7, and I have an installation on a 
remote server that uses apache as the frontend proxy.  I did this so I can 
offer the site to my team with ssl/tls.  They cannot get to the command 
line on the server, and a command line browser (w3m) does not work with 
angular anyway.  So they need a url that is external.

I have set the rest.cors settings in local.cfg:

rest.cors.allowed-origins = ${dspace.ui.url}

and have set the dspace.ui.url to the url to apache.  I am still getting 
cors errors in the browser (Firefox).  There are no errors anywhere else in 
the logs.

Is there a better way to set up dspace 7 so it is visible from a domain 
externally?

Best regards,
Paul

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/ee9bb9f8-117d-4113-a0d3-548861121d45o%40googlegroups.com.

[dspace-tech] Re: DSpace 7 new item page question

[Paul Warner]

I have a related problem: I cannot add a new collection or community via 
the Angular frontend, because the popup window does not work.  I posted the 
question here 
, with a 
screenshot.  Nothing shows up in any of the logs.

Thanks,
Paul

On Wednesday, July 22, 2020 at 9:59:28 PM UTC+2, Bill Tantzen wrote:
>
> DSpace 7, beta 3:
>
> On the "new item"  submission form, there is a button labeled "Lookup" 
> next to the Author fields that leads to a popup search form.  Sorry if I'm 
> missing something in the documentation, but what's that all about (and how 
> do I enable it)?
>
> Cheers!
> ~~ Bill
>
> -- 
> Human wheels spin round and round
> While the clock keeps the pace... -- John Mellencamp
> 
> Bill TantzenUniversity of Minnesota Libraries
> 612-626-9949 (U of M)612-325-1777 (cell)
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/1312e61d-4f3c-4877-8f64-09cc342fc386o%40googlegroups.com.

Re: [dspace-tech] Re: problems with dspace-angular-beta3

[Paul Warner]

Hi Tim,

Doing this stopped the CORS errors, and allows me to log in via 
localhost:4000 on my local machine.  Thanks!  A big step forward.

However, I still have a problem when trying to add a collection.  Here is a 
screenshot of my attempt to add a new collection:

[image: dspace7-new-collection.png]

There is nothing new in the DSpace Angular log, and nothing new in the 
DSpace log or in the Tomcat log.  Clicking on the popup window does 
nothing.  Any thoughts?

Thanks,
Paul

On Monday, July 13, 2020 at 5:31:52 PM UTC+2, Tim Donohue wrote:
>
> Bill,
>
> As of Beta3, the backend (REST API) has an "allow list" of frontend(s) 
> that it responds to.  This setting corresponds to the value(s) of the 
> "Access-Control-Allow-Origin" header which will be automatically set by the 
> backend webapp...and setting "Access-Control-Allow-Origin" to an asterisk 
> (wildcard) is _no longer supported_.  These settings are for security 
> purposes.  
>
> See this config in the rest.cfg: 
> https://github.com/DSpace/DSpace/blob/master/dspace/config/modules/rest.cfg#L10
>   
> It existed prior to beta3, but was officially enabled as part of beta3 (it 
> didn't work properly in beta2).
>
> My suspicion is this is the issue you are hitting.  Chances are you need 
> to change this setting's value (or the default value in dspace.ui.url) in 
> your local.cfg.
>
> Tim
> --
> *From:* 'Bill Tantzen' via DSpace Technical Support <
> dspac...@googlegroups.com >
> *Sent:* Friday, July 10, 2020 2:58 PM
> *To:* DSpace Technical Support >
> *Subject:* [dspace-tech] Re: problems with dspace-angular-beta3 
>  
> Hi all! 
>
> A little followup information regarding my problems getting 
> dspace-angular-beta03 up and running.  The client works if it is installed 
> and running on my localhost:4000 against the test api 
> at dspace7.4science.cloud.  Running the client on localhost on any other 
> port, or against my own server results in the preflight/cors errors 
> described below.  It all means that nobody but me can see the latest 
> version (it seems that nobody wants to come to my house anymore...). Sorry 
> this is long, so thanks in advance for reading through!!
>
> Closer examination shows that the 403 Errors I am catching are preflight 
> requests from the browser.  My attempts at a fix include setting the 
> Access-Control-Allow-Origin="*" both in apache and in tomcat. Neither of 
> which helped.  What is strange is that the preflight seems to be a result 
> of a simple GET request, which I think should not trigger such a request, 
> but I'm a little out of my depth with this.  Here is the complete request 
> info (from Chrome in this case):
>
>
>- *General*
>   - *Request URL: *https://udc-prd.lib.umn.edu/server/api/authn/status
>   - *Request Method: *OPTIONS
>   - *Status Code: *403 403
>   - *Remote Address: *128.101.65.121:443
>   - *Referrer Policy: *no-referrer-when-downgrade
>- *Response Headers*view source
>   - *Cache-Control: *no-cache, no-store, max-age=0, must-revalidate
>   - *Connection: *Keep-Alive
>   - *Date: *Fri, 10 Jul 2020 13:39:00 GMT
>   - *Expires: *0
>   - *Keep-Alive: *timeout=5, max=100
>   - *Pragma: *no-cache
>   - *Server: *Apache/2.4.6 (Red Hat Enterprise Linux) 
>   OpenSSL/1.0.2k-fips mod_jk/1.2.48
>   - *Strict-Transport-Security: *max-age=31536000 ; includeSubDomains
>   - *Transfer-Encoding: *chunked
>   - *Vary: *
>   Origin,Access-Control-Request-Method,Access-Control-Request-Headers
>   - *X-Content-Type-Options: * nosniff
>   - *X-Frame-Options: *DENY
>   - *X-XSS-Protection: *1; mode=block
>- *Request Headers*view source
>   - *Accept: **/*
>   - *Accept-Encoding: *gzip, deflate, br
>   - *Accept-Language: *en-US,en;q=0.9
>   - *Access-Control-Request-Headers: *content-type
>   - *Access-Control-Request-Method: *GET
>   - *Connection: *keep-alive
>   - *Host: *udc-prd.lib.umn.edu
>   - *Origin: *https://udc-dev.lib.umn.edu:3000
>   - *Referer: *https://udc-dev.lib.umn.edu:3000/
>   - *Sec-Fetch-Dest: *empty
>   - *Sec-Fetch-Mode: *cors
>   - *Sec-Fetch-Site: *same-site
>   - 
>   *User-Agent: *Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) 
>   AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 
> Safari/537.36
>
> and a snippet from the javascript console for the same request:
>
> Access to XMLHttpRequest at '
> https://udc-prd.lib.umn.edu/server/api/authn/status' from origin '
> https://udc-dev.lib.umn.edu:3000' has been blocked by CORS policy: 
> Response to preflight request doesn't pass access control check: No 
> 'Access-Control-Allow-Origin' header is present on the requested resource.
>
>
> zone.js.pre-build-optimizer.js:3372 GET 
> https://udc-prd.lib.umn.edu/server/api/authn/status net::ERR_FAILED
>
>
> And this is the result in my apache logs:
>
> 10.21.37.74 - - [10/Jul/2020:08:39:00 -

Re: [dspace-tech] Re: DSpace7 Rest Server - two installations, one works, one does not

[Paul Warner]

Hi Michael,

Thanks again for the reply!  I also got a tip from Tim Donohue, who said to 
check the firewall and Tomcat, since the situation did not sound like it 
had to do with DSpace.  That advice chimed in with yours, Michael, and 
caused me to look again at my server installation.

I had been careful to open all the right ports already, so I looked closer 
at the startup of Tomcat.  I found it was using the variable JRE_HOME, 
which I had not set, and it was using another version of Java, not the JDK 
11 that I installed for DSpace.  So I made sure JRE_HOME pointed to the 
correct Java installation, and now I have a working DSpace REST Server.  I 
can log in from the HAL Browser, and see the content of DSpace (which for 
now is empty).

I made sure my local.cfg file in DSpace had the correct domain name for my 
site, (another suggestion from Tim Donohue) and I started the Angular 
server.  It connected with the backend server, displaying all the content 
and formatting.  And when I send a page, for instance to view items by 
author, I get a line in the DSpace log.  However, log in does not work, and 
sometimes making a selection does not finish, and I have to resend the page 
in order to get a response.  I think I will close this thread here, and 
start a new thread regarding the failing login and page resending, since 
they are quite different issues.

Thanks again for the help!

Best regards,
Paul



On Monday, July 20, 2020 at 6:31:18 PM UTC+2, Michael Plate wrote:
>
> Hi Paul, 
>
> Am 19.07.20 um 12:40 schrieb Paul Warner: 
> > Hello everyone, 
>
> sorry for the delay… 
> > 
> > I have 2 DSpace 7 installations running on Ubuntu 18.04 machines, and 
> > have concluded that something among the software requirements for DSpace 
> > 7 is not well-supported by Suse SLES 12 patch 2.  I haven't got any 
> > evidence for this theory, because there is nothing in any of the logs to 
> > explain what is happening.  I do know that some new-ish software cannot 
> > be installed on SLES 12, so, it seems reasonable. 
>
> I'm not running DSpace 7 currently, however I did much with REST lately 
> and nobody else answered you… so I stepped forward. 
>
> some points: 
> - Postgres 9.6 should be OK, but you might enable SQL-Logging to be sure 
> - laptop uses "localhost" as hostname ? server uses what ? 
> - tomcat versions on laptop and server ? 
> - log files you checked, e.g. tomcat's log files 
>
> CU 
>
> Michael 
>
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/90aed806-d305-45ca-bc9f-101474ea6eebo%40googlegroups.com.

[dspace-tech] Re: DSpace7 Rest Server - two installations, one works, one does not

[Paul Warner]

Hello everyone,

I have 2 DSpace 7 installations running on Ubuntu 18.04 machines, and have 
concluded that something among the software requirements for DSpace 7 is 
not well-supported by Suse SLES 12 patch 2.  I haven't got any evidence for 
this theory, because there is nothing in any of the logs to explain what is 
happening.  I do know that some new-ish software cannot be installed on 
SLES 12, so, it seems reasonable.

Best regards,
Paul



On Wednesday, July 15, 2020 at 11:54:59 AM UTC+2, Paul Warner wrote:
>
> Hi,
>
> I have installed the DSpace 7 REST server on my laptop, and I can login 
> with a script using curl.  I have installed the same version REST server on 
> a server at work, and it returns a 404 when I try to log in.
>
> The servers have the same DSpace 7 (Beta 3), the same java (OpenJDK 11), 
> the same maven, the same solr, and the same ant.
>
> Differences:
>
> Laptop:
> Operating system: Ubuntu 18
> Database: Postgresql 10.16
>
> Server:
> Operating system: Suse SLES 12 service pack 2
> Database Postgres 9.6
>
> I have reinstalled the DSpace 7 and all components on the server, to try 
> to ensure they are as identical as possible.  I use the same installation 
> files, and the installations have their own Java.  I still get the 404s 
> when I use the same login script that works on my laptop.
>
> I should say that the installation on the server returns a 404 for every 
> query except the base query: http://host:port/server
>
> Any ideas?
>
> Best regards,
> Paul
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/bfd7a2b5-a430-47d7-b8e5-0e5a062359d9o%40googlegroups.com.

[dspace-tech] Re: DSpace7 Rest Server - two installations, one works, one does not

[Paul Warner]

Hi Michael,

Thanks for the reply!  I have opened the tomcat port in the firewall 
temporarily so I can use a browser.  But I cannot see anything in the 
browser tools with Firefox. The 404s come up with no additional 
information.  Can you suggest something? 

Remember I am now working only with the REST server that runs with tomcat.  
I decided to bypass the angular app for the moment, so I can see what is 
causing the problem in the backend server.  The basic url 
http://host:port/server gives me the HAL browser, but only the top few 
links, none of the other information or options or formatting.  Then 
logging in does not work, and any other REST command returns a 404.

Thanks,
Paul

On Wednesday, July 15, 2020 at 11:54:59 AM UTC+2, Paul Warner wrote:
>
> Hi,
>
> I have installed the DSpace 7 REST server on my laptop, and I can login 
> with a script using curl.  I have installed the same version REST server on 
> a server at work, and it returns a 404 when I try to log in.
>
> The servers have the same DSpace 7 (Beta 3), the same java (OpenJDK 11), 
> the same maven, the same solr, and the same ant.
>
> Differences:
>
> Laptop:
> Operating system: Ubuntu 18
> Database: Postgresql 10.16
>
> Server:
> Operating system: Suse SLES 12 service pack 2
> Database Postgres 9.6
>
> I have reinstalled the DSpace 7 and all components on the server, to try 
> to ensure they are as identical as possible.  I use the same installation 
> files, and the installations have their own Java.  I still get the 404s 
> when I use the same login script that works on my laptop.
>
> I should say that the installation on the server returns a 404 for every 
> query except the base query: http://host:port/server
>
> Any ideas?
>
> Best regards,
> Paul
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/96854787-eaab-4dd3-b7e0-dfcc7c14d0e1o%40googlegroups.com.

[dspace-tech] Re: DSpace7 Rest Server - two installations, one works, one does not

[Paul Warner]

Ok, I have switched the database for the instance on the server from 9.6 to 
10.12.  I thought it might be the older version of Postgresql.  But that 
has not helped, I still get 404s for everything except 
http://host:port/server.  And I should mention, there is no peep in the 
logs, either the tomcat log or the dspace log.

Best regards,
Paul



On Wednesday, July 15, 2020 at 11:54:59 AM UTC+2, Paul Warner wrote:
>
> Hi,
>
> I have installed the DSpace 7 REST server on my laptop, and I can login 
> with a script using curl.  I have installed the same version REST server on 
> a server at work, and it returns a 404 when I try to log in.
>
> The servers have the same DSpace 7 (Beta 3), the same java (OpenJDK 11), 
> the same maven, the same solr, and the same ant.
>
> Differences:
>
> Laptop:
> Operating system: Ubuntu 18
> Database: Postgresql 10.16
>
> Server:
> Operating system: Suse SLES 12 service pack 2
> Database Postgres 9.6
>
> I have reinstalled the DSpace 7 and all components on the server, to try 
> to ensure they are as identical as possible.  I use the same installation 
> files, and the installations have their own Java.  I still get the 404s 
> when I use the same login script that works on my laptop.
>
> I should say that the installation on the server returns a 404 for every 
> query except the base query: http://host:port/server
>
> Any ideas?
>
> Best regards,
> Paul
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/b1b85600-110d-4e78-a588-a3062c9696b7o%40googlegroups.com.

[dspace-tech] DSpace7 Rest Server - two installations, one works, one does not

[Paul Warner]

Hi,

I have installed the DSpace 7 REST server on my laptop, and I can login 
with a script using curl.  I have installed the same version REST server on 
a server at work, and it returns a 404 when I try to log in.

The servers have the same DSpace 7 (Beta 3), the same java (OpenJDK 11), 
the same maven, the same solr, and the same ant.

Differences:

Laptop:
Operating system: Ubuntu 18
Database: Postgresql 10.16

Server:
Operating system: Suse SLES 12 service pack 2
Database Postgres 9.6

I have reinstalled the DSpace 7 and all components on the server, to try to 
ensure they are as identical as possible.  I use the same installation 
files, and the installations have their own Java.  I still get the 404s 
when I use the same login script that works on my laptop.

I should say that the installation on the server returns a 404 for every 
query except the base query: http://host:port/server

Any ideas?

Best regards,
Paul

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/d21561d4-b67e-43c3-8894-939e243122bfo%40googlegroups.com.

[dspace-tech] Re: dspace 7 angular not connecting with remote rest server

[Paul Warner]

One other thing:  I spoke too soon when I said it worked with the default 
DSpace backend, https://dspace7.4science.cloud/server/ 
<https://www.google.com/url?q=https%3A%2F%2Fdspace7.4science.cloud%2Fserver%2F&sa=D&sntz=1&usg=AFQjCNGj8IKwAD8tXS9fqyYMFCFJwjsrow>,
 I 
get the front page without the images, and none of the links work: they all 
lead to the error page:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request *GET 
/communities/d9c483ca-89d2-437f-aedc-9da0935fd533 
<https://repo7-test.amad.org/communities/d9c483ca-89d2-437f-aedc-9da0935fd533>*
.

Reason: *DNS lookup failure for: localhost:4000communities*

Additionally, a 502 Bad Gateway error was encountered while trying to use 
an ErrorDocument to handle the request.

I see that this is because I am serving my Angular app via apache with a 
proxy to localhost:4000.  So the domain name for my app is not listed in 
environment.ts, only localhost:4000. I am using apache as the front facing 
server because it is robust, allows me to use port 80, and handles the tls.


How should I configure it so it works?


Thanks again for any help!


Best regards,
Paul





On Thursday, July 9, 2020 at 2:44:19 PM UTC+2, Paul Warner wrote:
>
> Hello,
>
> I am working on getting DSpace 7 running, and I have installed the Angular 
> frontend on one machine in our network, and the Rest Backend on another.  I 
> can reach the REST machine from the Angular machine using a browser, with 
> host ip address and port (8255).  But Angular is not connecting, generating 
> this error:
>
> statusText: 'Unknown Error',
>   message:
>'Http failure response for http://localhost:8255/server/api/core/sites: 
> 0 Unknown Error' }
>
> I have entered the settings for the REST server in 
> angular-dir/src/environment/environment.ts, and I can see them in 
> angular-dir/dist/server.js, with the server address and port, 8255.  
> Angular is getting the port right, but substituting localhost for my server 
> address.
>
> What do you need to know to help me?  The stack trace is quite long.  I 
> can provide whatever information you may need.
>
> I have tested the Angular install with the DSpace default backend: 
> https://dspace7.4science.cloud/server/ 
> <https://www.google.com/url?q=https%3A%2F%2Fdspace7.4science.cloud%2Fserver%2F&sa=D&sntz=1&usg=AFQjCNGj8IKwAD8tXS9fqyYMFCFJwjsrow>
> and it works. The settings were entered, again, in 
> src/environment/environement.ts.  Why would it not work with my server?  I 
> do not have a hostname for my internal REST server - I am using its ip 
> address.
>
> Thanks in advance for any tips!
>
> Best regards,
> Paul
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/d6eb0b4b-5bdb-4e12-b467-43a1efab9b48o%40googlegroups.com.

[dspace-tech] dspace 7 angular not connecting with remote rest server

[Paul Warner]

Hello,

I am working on getting DSpace 7 running, and I have installed the Angular 
frontend on one machine in our network, and the Rest Backend on another.  I 
can reach the REST machine from the Angular machine using a browser, with 
host ip address and port (8255).  But Angular is not connecting, generating 
this error:

statusText: 'Unknown Error',
  message:
   'Http failure response for http://localhost:8255/server/api/core/sites: 
0 Unknown Error' }

I have entered the settings for the REST server in 
angular-dir/src/environment/environment.ts, and I can see them in 
angular-dir/dist/server.js, with the server address and port, 8255.  
Angular is getting the port right, but substituting localhost for my server 
address.

What do you need to know to help me?  The stack trace is quite long.  I can 
provide whatever information you may need.

I have tested the Angular install with the DSpace default 
backend: https://dspace7.4science.cloud/server/
and it works. The settings were entered, again, in 
src/environment/environement.ts.  Why would it not work with my server?  I 
do not have a hostname for my internal REST server - I am using its ip 
address.

Thanks in advance for any tips!

Best regards,
Paul

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/c8226d91-d73a-4010-b2e4-69e3239b6173o%40googlegroups.com.

[dspace-tech] dspace 7 angular not connecting with remote rest server

[Paul Warner]

Hello,

For my DSpace 7 installation, I tried installing the Angular part on the 
external facing machine, and the rest server on another machine.  I can 
reach the rest server from the external machine with a browser, but angular 
cannot find it.  I have the rest properties in 
angular-dir/src/environment/environment.ts, with the hostname and port 
number (for our server, the port is 8255).  So on startup, angular prints 
this error message:

statusText: 'Unknown Error',
  message:
   'Http failure response for http://localhost:8255/server/api/core/sites: 
0 Unknown Error' }

So it is getting the port right, but the hostname gets converted to 
localhost.

The stacktrace is quite long, please let me know what you would find useful.

I just downloaded the code last week, so it is DSpace 7 Beta 2.

Angular machine: OS: Suse LES 12

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/ee5f1a04-7b09-4222-a074-604dd6b903bdo%40googlegroups.com.

[dspace-tech] Re: datacite mds test no longer available

[Paul Warner]

Hi,

I got a further info email from DataCite to say that, in fact, they had 
technical problems with mds.test.datacite.org, and these have been fixed.  
It wasn't shut down. I tested it and indeed it is working!  So please 
ignore my initial message.  Sorry for the confusion.

Best regards,
Paul

On Tuesday, May 26, 2020 at 5:15:47 PM UTC+2, Paul Warner wrote:
>
> Hi,
>
> The nice person at DataCite informed us that DataCite does not support a 
> test version anymore for the mds interface that DSpace uses.  DataCite now 
> has a REST Api as their main offering, and they offer a test version, 
> api.test.datacite.org.  We are in the midst of a test for our Beta phase 
> of our project, and want to use our test account.  I tried using the 
> Fabrica url, doi.test.datacite.org, but while I can login myself directly 
> here, DSpace gets a 404 when trying to register an item.  
>
> 2020-05-26 17:09:00,626 WARN  org.dspace.identifier.doi.DataCiteConnector 
> @ While registration of DOI doi:10.0042/amad-22553, we got a http status 
> code 404 and the message "
> 
> 
> 
> Error
> 
> 
> Cannot POST /doi/
> 
> 
> ".
>
>
> We are running DSpace 6.3 with Postgresql 9.6.3.  Any suggestions?
>
> Best regards,
> Paul
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/5d79c860-4be3-460a-9301-ad128db7e80a%40googlegroups.com.

[dspace-tech] datacite mds test no longer available

[Paul Warner]

Hi,

The nice person at DataCite informed us that DataCite does not support a 
test version anymore for the mds interface that DSpace uses.  DataCite now 
has a REST Api as their main offering, and they offer a test version, 
api.test.datacite.org.  We are in the midst of a test for our Beta phase of 
our project, and want to use our test account.  I tried using the Fabrica 
url, doi.test.datacite.org, but while I can login myself directly here, 
DSpace gets a 404 when trying to register an item.  

2020-05-26 17:09:00,626 WARN  org.dspace.identifier.doi.DataCiteConnector @ 
While registration of DOI doi:10.0042/amad-22553, we got a http status code 
404 and the message "



Error


Cannot POST /doi/


".


We are running DSpace 6.3 with Postgresql 9.6.3.  Any suggestions?

Best regards,
Paul

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/39465010-c8e8-45bd-9a55-037ea8f609ae%40googlegroups.com.

[dspace-tech] facet synonyms

[Paul Warner]

Hi,

I am running DSpace 6.3 with Postgresql.

I have a repository of historical documents, and the sidebar facet for 
subject has a list of terms, including:

History
900.History
900 History
Geschichte
900.Geschichte

These are all synonyms, and my clients find it ugly that they are all 
listed separately.  How can I join them as synonyms, so there is only one?

I have set some of these values in 

dspace/solr/search/conf/synonyms.txt and 
dspace/solr/statistics/conf/synonyms.txt, and
dspace/solr/authority/conf/synonyms.txt
 
but it does not affect the facets.

Thanks for any suggestions!

Best regards,
Paul Warner

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/a304435c-769e-4384-9f5c-c2562f4232d8%40googlegroups.com.

Re: [dspace-tech] DSpace 6.3 REST 405 Error when posting new collection

[Paul Warner]

Hi Tim,

Thanks for your very nice reply!  You saved me considerable time, but I am 
sorry to have wasted your time with such a dumb mistake.  :-(

Best regards,
Paul

On Friday, December 6, 2019 at 4:48:57 PM UTC+1, Tim Donohue wrote:
>
> Hi Paul,
>
> It looks (to me) like you are POSTing to the wrong endpoint (based on the 
> docs you linked to)
>
> Your POST looks like this:
>
> POST /rest/communities/cb69484b-1669-4832-b0aa-8acb902db531
>
> But, the correct POST to create a collection is:
>
> POST /rest/communities/cb69484b-1669-4832-b0aa-8acb902db531/collections
>
> So, the error you are seeing is correct.  You cannot POST to just the 
> /communities/{uuid} endpoint...that endpoint only accepts GET (to get info 
> about that Community), DELETE (to delete that community) and PUT (to update 
> that community).  If you want to add a collection, you have to POST to the 
> /collections subresource for that community.
>
> Hopefully that helps!
>
> Tim
>
> ------
> *From:* dspac...@googlegroups.com   > on behalf of Paul Warner >
> *Sent:* Friday, December 6, 2019 3:07 AM
> *To:* DSpace Technical Support >
> *Subject:* [dspace-tech] DSpace 6.3 REST 405 Error when posting new 
> collection 
>  
> I am attempting to add a collection, and am getting a 405 Method Not 
> Allowed error.  DSpace 6.3.  Thanks in advance for any suggestions! --Paul 
>
> In the output below, note the line: < Allow: DELETE,GET,OPTIONS,PUT
>
> POST is not on the list!  Why?
>
> According to the documentation, creation of a collection uses a POST 
> request. 
> https://wiki.lyrasis.org/display/DSDOC6x/REST+API#RESTAPI-Communities
>
> Here is the server output:
> *   Trying 127.0.0.1...
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  
> Speed
>   0 00 00 0  0  0 --:--:-- --:--:-- --:--:--  
>0* Connected to 127.0.0.1 (127.0.0.1) port 8345 (#0)
> > POST /rest/communities/cb69484b-1669-4832-b0aa-8acb902db531 HTTP/1.1
> > User-Agent: curl/7.37.0
> > Host: 127.0.0.1:8345
> > Accept: */*
> > Cookie: JSESSIONID=1041D8EFC72B7F930B6D3363406220FA
> > Content-Type: application/json
> > Content-Length: 526
> > 
> } [data not shown]
> * upload completely sent off: 526 out of 526 bytes
> < HTTP/1.1 405 
> < Allow: DELETE,GET,OPTIONS,PUT
> < Content-Type: text/html;charset=utf-8
> < Content-Language: en
> < Content-Length: 1090
> < Date: Fri, 06 Dec 2019 08:45:03 GMT
> < 
> { [data not shown]
> 100  1616  100  1090  100   526   334k   161k --:--:-- --:--:-- --:--:--  
> 532k
> * Connection #0 to host 127.0.0.1 left intact
> HTTP Status 405 – Method Not 
> Allowedh1 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
>  
> h2 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
>  
> h3 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
>  
> body 
> {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} b 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} 
> p 
> {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}
>  
> a {color:black;} a.name {color:black;} .line 
> {height:1px;background-color:#525D76;border:none;}HTTP
>  
> Status 405 – Method Not AllowedType 
> Status ReportMessage Method Not 
> AllowedDescription The method received in the request-line is 
> known by the origin server but not supported by the target resource. class="line" />Apache Tomcat/8.5.20
>
>
> In anticipation of possible questions, here is the way I make the REST 
> call:
>
> I allow Tomcat access only on localhost, and my script is on the same 
> machine.  I make the call with curl:
>
> add_cmd = ['curl', '-v', '--cookie', self.sessionid, '--header', 
> 'Content-Type: application/json', '-X', 'POST', item_link, '-d', json_str]
>
> item_link = 'using 
> http://127.0.0.1/rest/communities/cb69484b-1669-4832-b0aa-8acb902db531'
> json_str = '''
> {
> "copyrightText": "",
> "expand": [
> "parentCommunityList",
> "parentCommunity",
> "items",
> "license",
> "logo",
> "all"
> ],
> "introductoryText&q

[dspace-tech] DSpace 6.3 REST 405 Error when posting new collection

[Paul Warner]

I am attempting to add a collection, and am getting a 405 Method Not 
Allowed error.  DSpace 6.3.  Thanks in advance for any suggestions! --Paul

In the output below, note the line: < Allow: DELETE,GET,OPTIONS,PUT

POST is not on the list!  Why?

According to the documentation, creation of a collection uses a POST 
request. 
https://wiki.lyrasis.org/display/DSDOC6x/REST+API#RESTAPI-Communities

Here is the server output:
*   Trying 127.0.0.1...
  % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
 Dload  Upload   Total   SpentLeft  
Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:--
 0* Connected to 127.0.0.1 (127.0.0.1) port 8345 (#0)
> POST /rest/communities/cb69484b-1669-4832-b0aa-8acb902db531 HTTP/1.1
> User-Agent: curl/7.37.0
> Host: 127.0.0.1:8345
> Accept: */*
> Cookie: JSESSIONID=1041D8EFC72B7F930B6D3363406220FA
> Content-Type: application/json
> Content-Length: 526
> 
} [data not shown]
* upload completely sent off: 526 out of 526 bytes
< HTTP/1.1 405 
< Allow: DELETE,GET,OPTIONS,PUT
< Content-Type: text/html;charset=utf-8
< Content-Language: en
< Content-Length: 1090
< Date: Fri, 06 Dec 2019 08:45:03 GMT
< 
{ [data not shown]
100  1616  100  1090  100   526   334k   161k --:--:-- --:--:-- --:--:--  
532k
* Connection #0 to host 127.0.0.1 left intact
HTTP Status 405 – Method Not 
Allowedh1 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
 
h2 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
 
h3 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
 
body 
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} b 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} 
p 
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}
 
a {color:black;} a.name {color:black;} .line 
{height:1px;background-color:#525D76;border:none;}HTTP 
Status 405 – Method Not AllowedType 
Status ReportMessage Method Not 
AllowedDescription The method received in the request-line is 
known by the origin server but not supported by the target resource.Apache Tomcat/8.5.20


In anticipation of possible questions, here is the way I make the REST call:

I allow Tomcat access only on localhost, and my script is on the same 
machine.  I make the call with curl:

add_cmd = ['curl', '-v', '--cookie', self.sessionid, '--header', 
'Content-Type: application/json', '-X', 'POST', item_link, '-d', json_str]

item_link = 'using 
http://127.0.0.1/rest/communities/cb69484b-1669-4832-b0aa-8acb902db531'
json_str = '''
{
"copyrightText": "",
"expand": [
"parentCommunityList",
"parentCommunity",
"items",
"license",
"logo",
"all"
],
"introductoryText": "Willkommen zu der neue Sammlung 1!",
"items": [],
"license": null,
"logo": null,
"name": "Neue Sammlung 1",
"shortDescription": "eine Sammlung via REST erzeugt",
"sidebarText": "",
"type": "collection"
}
'''

Thanks,
Paul

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/76c0d141-87d1-4ae4-aeb1-0d1aa0f2c75d%40googlegroups.com.

[dspace-tech] Re: Error connection - DB - Dspace 6.0

[Paul Warner]

Oops, I see this post is 2 years old.  Did you find an answer?

Regards,
Paul

On Wednesday, May 31, 2017 at 8:53:26 PM UTC+2, Brendow Adriel wrote:
>
> 2017-05-30 16:58:32,475 INFO  org.dspace.storage.rdbms.DatabaseUtils @ 
> Loading Flyway DB migrations from: filesystem:/dspace/etc/postgres, 
> classpath:org.dspace.storage.rdbms.sqlmigration.postgres, 
> classpath:org.dspace.storage.rdbms.migration
> 2017-05-30 16:58:32,497 INFO  org.flywaydb.core.internal.util.VersionPrinter 
> @ Flyway 4.0.3 by Boxfuse
> 2017-05-30 16:58:32,538 INFO  
> org.flywaydb.core.internal.dbsupport.DbSupportFactory @ Database: 
> jdbc:postgresql://localhost:5432/dspace (PostgreSQL 9.4)
> 2017-05-30 16:58:32,616 INFO  org.dspace.storage.rdbms.DatabaseUtils @ DSpace 
> database schema is up to date
> 2017-05-30 16:58:32,629 INFO  org.dspace.event.EventServiceImpl @ 
> EventService dispatcher pool initialized
> 2017-05-30 16:58:32,839 INFO  org.hibernate.annotations.common.Version @ 
> HCANN01: Hibernate Commons Annotations {4.0.2.Final}
> 2017-05-30 16:58:32,845 INFO  org.hibernate.Version @ HHH000412: Hibernate 
> Core {4.2.21.Final}
> 2017-05-30 16:58:32,847 INFO  org.hibernate.cfg.Environment @ HHH000206: 
> hibernate.properties not found
> 2017-05-30 16:58:32,848 INFO  org.hibernate.cfg.Environment @ HHH21: 
> Bytecode provider name : javassist
> 2017-05-30 16:58:32,873 INFO  org.hibernate.cfg.Configuration @ HHH44: 
> Configuring from URL: file:/dspace/config/hibernate.cfg.xml
> 2017-05-30 16:58:32,926 INFO  org.hibernate.cfg.Configuration @ HHH41: 
> Configured SessionFactory: null
> 2017-05-30 16:58:33,109 INFO  org.hibernate.dialect.Dialect @ HHH000400: 
> Using dialect: 
> org.dspace.storage.rdbms.hibernate.postgres.DSpacePostgreSQL82Dialect
> 2017-05-30 16:58:33,122 INFO  
> org.hibernate.engine.jdbc.internal.LobCreatorBuilder @ HHH000424: Disabling 
> contextual LOB creation as createClob() method threw error : 
> java.lang.reflect.InvocationTargetException
> 2017-05-30 16:58:33,130 INFO  org.hibernate.type.BasicTypeRegistry @ 
> HHH000270: Type registration [pg-uuid] overrides previous : 
> org.hibernate.type.PostgresUUIDType@765f490b
> 2017-05-30 16:58:33,131 INFO  org.hibernate.type.BasicTypeRegistry @ 
> HHH000270: Type registration [java.util.UUID] overrides previous : 
> org.hibernate.type.UUIDBinaryType@4c1e9e97
> 2017-05-30 16:58:33,389 WARN  org.hibernate.mapping.RootClass @ HHH39: 
> Composite-id class does not override hashCode(): 
> org.dspace.eperson.Group2GroupCache
> 2017-05-30 16:58:33,390 WARN  org.hibernate.mapping.RootClass @ HHH38: 
> Composite-id class does not override equals(): 
> org.dspace.checker.MostRecentChecksum
> 2017-05-30 16:58:33,390 WARN  org.hibernate.mapping.RootClass @ HHH39: 
> Composite-id class does not override hashCode(): 
> org.dspace.checker.MostRecentChecksum
> 2017-05-30 16:58:33,396 INFO  
> org.hibernate.engine.transaction.internal.TransactionFactoryInitiator @ 
> HHH000399: Using default transaction strategy (direct JDBC transactions)
> 2017-05-30 16:58:33,401 INFO  
> org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory @ HHH000397: Using 
> ASTQueryTranslatorFactory
> 2017-05-30 16:58:33,442 WARN  net.sf.ehcache.config.ConfigurationFactory @ No 
> configuration found. Configuring ehcache from ehcache-failsafe.xml  found in 
> the classpath: 
> jar:file:/C:/dspace/webapps/jspui/WEB-INF/lib/ehcache-core-2.4.3.jar!/ehcache-failsafe.xml
> 2017-05-30 16:58:33,451 WARN  net.sf.ehcache.CacheManager @ Creating a new 
> instance of CacheManager using the diskStorePath "C:\Program Files\Apache 
> Software Foundation\Tomcat 7.68\temp " which is already used by an existing 
> CacheManager.
> The source of the configuration was 
> net.sf.ehcache.config.generator.ConfigurationSource$DefaultConfigurationSource@33e55fd5.
> The diskStore path for this CacheManager will be set to C:\Program 
> Files\Apache Software Foundation\Tomcat 7.68\temp 
> \ehcache_auto_created_1496174313451.
> To avoid this warning consider using the CacheManager factory methods to 
> create a singleton CacheManager or specifying a separate ehcache 
> configuration (ehcache.xml) for each CacheManager instance.
> 2017-05-30 16:58:33,452 INFO  org.hibernate.cache.spi.UpdateTimestampsCache @ 
> HHH000250: Starting update timestamps cache at region: 
> org.hibernate.cache.spi.UpdateTimestampsCache
> 2017-05-30 16:58:33,455 WARN  
> org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory @ HHH020003: Could 
> not find a specific ehcache configuration for cache named 
> [org.hibernate.cache.spi.UpdateTimestampsCache]; using defaults.
> 2017-05-30 16:58:33,466 INFO  org.hibernate.cfg.Configuration @ HHH44: 
> Configuring from URL: file:/dspace/config/hibernate.cfg.xml
> 2017-05-30 16:58:33,471 INFO  org.hibernate.cfg.Configuration @ HHH41: 
> Configured SessionFactory: null
> 2017-05-30 16:58:33,478 INFO  org.hibernate.dialect.Dialect @ HHH000400: 
> Using dialect: 
> org.dspace.

[dspace-tech] Re: Error connection - DB - Dspace 6.0

[Paul Warner]

Hi Brendow,

Have you entered all your database login information in local.cfg?

Are you using Java 8?

Regards,
Paul

On Wednesday, May 31, 2017 at 8:53:26 PM UTC+2, Brendow Adriel wrote:
>
> 2017-05-30 16:58:32,475 INFO  org.dspace.storage.rdbms.DatabaseUtils @ 
> Loading Flyway DB migrations from: filesystem:/dspace/etc/postgres, 
> classpath:org.dspace.storage.rdbms.sqlmigration.postgres, 
> classpath:org.dspace.storage.rdbms.migration
> 2017-05-30 16:58:32,497 INFO  org.flywaydb.core.internal.util.VersionPrinter 
> @ Flyway 4.0.3 by Boxfuse
> 2017-05-30 16:58:32,538 INFO  
> org.flywaydb.core.internal.dbsupport.DbSupportFactory @ Database: 
> jdbc:postgresql://localhost:5432/dspace (PostgreSQL 9.4)
> 2017-05-30 16:58:32,616 INFO  org.dspace.storage.rdbms.DatabaseUtils @ DSpace 
> database schema is up to date
> 2017-05-30 16:58:32,629 INFO  org.dspace.event.EventServiceImpl @ 
> EventService dispatcher pool initialized
> 2017-05-30 16:58:32,839 INFO  org.hibernate.annotations.common.Version @ 
> HCANN01: Hibernate Commons Annotations {4.0.2.Final}
> 2017-05-30 16:58:32,845 INFO  org.hibernate.Version @ HHH000412: Hibernate 
> Core {4.2.21.Final}
> 2017-05-30 16:58:32,847 INFO  org.hibernate.cfg.Environment @ HHH000206: 
> hibernate.properties not found
> 2017-05-30 16:58:32,848 INFO  org.hibernate.cfg.Environment @ HHH21: 
> Bytecode provider name : javassist
> 2017-05-30 16:58:32,873 INFO  org.hibernate.cfg.Configuration @ HHH44: 
> Configuring from URL: file:/dspace/config/hibernate.cfg.xml
> 2017-05-30 16:58:32,926 INFO  org.hibernate.cfg.Configuration @ HHH41: 
> Configured SessionFactory: null
> 2017-05-30 16:58:33,109 INFO  org.hibernate.dialect.Dialect @ HHH000400: 
> Using dialect: 
> org.dspace.storage.rdbms.hibernate.postgres.DSpacePostgreSQL82Dialect
> 2017-05-30 16:58:33,122 INFO  
> org.hibernate.engine.jdbc.internal.LobCreatorBuilder @ HHH000424: Disabling 
> contextual LOB creation as createClob() method threw error : 
> java.lang.reflect.InvocationTargetException
> 2017-05-30 16:58:33,130 INFO  org.hibernate.type.BasicTypeRegistry @ 
> HHH000270: Type registration [pg-uuid] overrides previous : 
> org.hibernate.type.PostgresUUIDType@765f490b
> 2017-05-30 16:58:33,131 INFO  org.hibernate.type.BasicTypeRegistry @ 
> HHH000270: Type registration [java.util.UUID] overrides previous : 
> org.hibernate.type.UUIDBinaryType@4c1e9e97
> 2017-05-30 16:58:33,389 WARN  org.hibernate.mapping.RootClass @ HHH39: 
> Composite-id class does not override hashCode(): 
> org.dspace.eperson.Group2GroupCache
> 2017-05-30 16:58:33,390 WARN  org.hibernate.mapping.RootClass @ HHH38: 
> Composite-id class does not override equals(): 
> org.dspace.checker.MostRecentChecksum
> 2017-05-30 16:58:33,390 WARN  org.hibernate.mapping.RootClass @ HHH39: 
> Composite-id class does not override hashCode(): 
> org.dspace.checker.MostRecentChecksum
> 2017-05-30 16:58:33,396 INFO  
> org.hibernate.engine.transaction.internal.TransactionFactoryInitiator @ 
> HHH000399: Using default transaction strategy (direct JDBC transactions)
> 2017-05-30 16:58:33,401 INFO  
> org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory @ HHH000397: Using 
> ASTQueryTranslatorFactory
> 2017-05-30 16:58:33,442 WARN  net.sf.ehcache.config.ConfigurationFactory @ No 
> configuration found. Configuring ehcache from ehcache-failsafe.xml  found in 
> the classpath: 
> jar:file:/C:/dspace/webapps/jspui/WEB-INF/lib/ehcache-core-2.4.3.jar!/ehcache-failsafe.xml
> 2017-05-30 16:58:33,451 WARN  net.sf.ehcache.CacheManager @ Creating a new 
> instance of CacheManager using the diskStorePath "C:\Program Files\Apache 
> Software Foundation\Tomcat 7.68\temp " which is already used by an existing 
> CacheManager.
> The source of the configuration was 
> net.sf.ehcache.config.generator.ConfigurationSource$DefaultConfigurationSource@33e55fd5.
> The diskStore path for this CacheManager will be set to C:\Program 
> Files\Apache Software Foundation\Tomcat 7.68\temp 
> \ehcache_auto_created_1496174313451.
> To avoid this warning consider using the CacheManager factory methods to 
> create a singleton CacheManager or specifying a separate ehcache 
> configuration (ehcache.xml) for each CacheManager instance.
> 2017-05-30 16:58:33,452 INFO  org.hibernate.cache.spi.UpdateTimestampsCache @ 
> HHH000250: Starting update timestamps cache at region: 
> org.hibernate.cache.spi.UpdateTimestampsCache
> 2017-05-30 16:58:33,455 WARN  
> org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory @ HHH020003: Could 
> not find a specific ehcache configuration for cache named 
> [org.hibernate.cache.spi.UpdateTimestampsCache]; using defaults.
> 2017-05-30 16:58:33,466 INFO  org.hibernate.cfg.Configuration @ HHH44: 
> Configuring from URL: file:/dspace/config/hibernate.cfg.xml
> 2017-05-30 16:58:33,471 INFO  org.hibernate.cfg.Configuration @ HHH41: 
> Configured SessionFactory: null
> 2017-05-30 16:58:33,478 INFO  org.hibernate.dialect.Dialect @ HHH

[dspace-tech] REST API text bitstreams not found

[Paul Warner]

I am querying items in DSpace, and using the uuid to find the bitstreams 
for each item.  But for some items I do not get the bundleName: TEXT 
bitstreams, even though they are there in the list when I view it through 
the browser.  Why?  What am I missing?  This works for other items, but for 
some items all I get are the bundleName: ORIGINAL files.

Thanks for any tips!

Regards,
Paul

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

Re: [dspace-tech] REST get bitstreams gives only 20

[Paul Warner]

Thanks, Terry! I am sure that’s it, but as I am on a break til the new
year, I can‘t try it out til then. ;-) I will post a proper response then.

Thanks again,
Paul

Terry Brady  schrieb am Fr. 21. Dez. 2018 um
18:05:

> Paul,
>
> Try setting limit=100 to bring back a large list.  Or, you can set
> offset=20 to paginate through the results.
>
>
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-rest/src/main/java/org/dspace/rest/ItemsResource.java#L286
>
> I think that there may be code that caps the maximum size that limit can
> be set to.
>
> The limit and offset parameters should exist on most enpoints that return
> a list.
>
> Terry
>
> On Fri, Dec 21, 2018 at 6:42 AM Paul Warner  wrote:
>
>> Hi,
>>
>> I am using this command:
>>
>>
>>- GET /items/{item id}/bitstreams - Return item bitstreams.
>>
>> to get the bitstream information for an item.  I have some items with
>> more than 20 bitstreams, but I seem to get only the first 20 with the REST
>> API.  I get the file information for the item with this command, then I go
>> through the list and find the BUNDLE: TEXT files that are at the end, and
>> capture the text.  But if these files are not in the list, because it cuts
>> off at 20, then my program fails for those items.  How do I get the whole
>> list via REST?
>>
>> Thanks in advance for any tips.
>>
>> Best regards,
>> Paul Warner
>>
>> --
>> All messages to this mailing list should adhere to the DuraSpace Code of
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to dspace-tech+unsubscr...@googlegroups.com.
>
>
>> To post to this group, send email to dspace-tech@googlegroups.com.
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Terry Brady
> Applications Programmer Analyst
> Georgetown University Library Information Technology
> https://github.com/terrywbrady/info
> 425-298-5498 (Seattle, WA)
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "DSpace Technical Support" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/dspace-tech/qYtTDZG4z1I/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.
>

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

[dspace-tech] REST get bitstreams gives only 20

[Paul Warner]

Hi,

I am using this command:


   - GET /items/{item id}/bitstreams - Return item bitstreams.

to get the bitstream information for an item.  I have some items with more 
than 20 bitstreams, but I seem to get only the first 20 with the REST API.  
I get the file information for the item with this command, then I go 
through the list and find the BUNDLE: TEXT files that are at the end, and 
capture the text.  But if these files are not in the list, because it cuts 
off at 20, then my program fails for those items.  How do I get the whole 
list via REST?

Thanks in advance for any tips.

Best regards,
Paul Warner

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

[dspace-tech] jspui, Thumbnails, slow loading page

[Paul Warner]

Hi,

This project uses DSpace 6.1.

We are using thumbnails of PDFs as buttons for accessing and viewing the 
PDF.  This happens in the context of jspui, and the jsp page is 
(dspace-src)/dspace/modules/jspui/src/main/webapp/display-item.jsp.  The 
problem is that when we use the thumbnail, the page takes between 15-40 
seconds to load.  In Firefox and Chrome, for instance, the thumbnail 
appears with the rest of the page immediately, but the page continues to 
download (i.e., the wheel in the browser tab keeps spinning).  In Internet 
Explorer, the thumbnail loads only at the end, and if we are using the 
thumbnail as a button, the user cannot access the PDF for up to 40 seconds 
or more.

The display-item.jsp page uses a custom jsp tag created in 
(dspace-src)/dspace/modules/jspui/src/main/java/org/dspace/app/webui/jsptag/ItemTag.java,
 
and this is the source of the problem.  If you search in this file for 
thumbs  or showThumbs, you will eventually land on a line that has 

if (thumbs.size() > 0) && showThumbs)

in it.  If you scroll down, you will see that the name and a link for the 
thumbnail are searched for and produced, and then a bit of html is sent 
back to the browser:

out.print("");

If I comment this section out, the page loads in a second or two.  When I 
test it by commenting it back in, the page takes, once again, up to 40 
seconds to load.  I do not understand what the problem is.  All the 
searching and preparation for this bit of out.print work is being done in 
either case.  Only the submission of the html to the page is the 
difference.  I have taken the thumbnail out and replaced it with a plain 
button, and the page loads very quickly (1-2 seconds).  But my client would 
prefer the image.  I am stumped.  I do not understand how this small, 
inocuous-seeming html (and tiny image) should cause the page to take so 
long to load.

I found this post on the list, "DSpace 6.2 with collection home page too 
slow to load if items have lots of bitsteams", but this refers to xmlui, 
and the solution seems to be xmlui-specific, if I understand it correctly.  
Does anyone have a solution for the problem in jspui?  Or an idea about how 
this happens?

Thanks for any suggestions or ideas!

Best regards,
Paul


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

Re: [dspace-tech] webui.collectionhome.browse-name

[Paul Warner]

Hello Claudia,

Thanks very much for this explanation.  Very helpful.

Best regards,
Paul

On Fri, Mar 23, 2018 at 11:28 AM, Claudia Jürgen <
claudia.juer...@tu-dortmund.de> wrote:

>
> Hello Paul,
>
> the column for sorting is derived from the default sorting of the browse
> index used, in the collection case: title
> https://github.com/DSpace/DSpace/blob/master/dspace/config/
> dspace.cfg#L1157
>
> You may set another sort option with:
> https://github.com/DSpace/DSpace/blob/master/dspace/config/
> dspace.cfg#L1167
>
> Supposing this is a configured sort option:
> https://github.com/DSpace/DSpace/blob/master/dspace/config/
> dspace.cfg#L1061
>
> The difference between item and metadata browse, is that item has a
> single item per entry, whereas metadata points to a list of items with
> the metadata.
> So a browse by title will give you a list of items (even if the same
> title occurs in different items)
> http://demo.dspace.org/xmlui/browse?type=title
> A browse by a metadata will aggregate the same metadata in one entry
> http://demo.dspace.org/xmlui/browse?type=subject (see Coaching)
>
> Hope this helps
>
> Claudia Jürgen
>
>
> Am 23.03.2018 um 10:38 schrieb Paul Warner:
>
>> Hi,
>>
>> We are using Dspace 6.1, and the ui is jspui.
>>
>> The library for whom we are setting up a dspace repository would like the
>> default sort for collection-home.jsp to be date created, a metadata item.
>> It is a list of concerts, and the most meaningful list is by concert date.
>> Sorting by title is a useful option, but not what they want by default.
>> They also would like it to be a descending list.
>>
>> How do I do this?
>>
>> The column for sorting is set in dspace.cfg by
>>
>> webui.collectionhome.browse-name
>>
>> It says that one has to use an "item" type of browse index.  I could use a
>> short primer on the difference between an "item" type and a metadata type
>> in the dspace.cfg file.  And then we need to know how to customize this...
>> Can I set a metadata item as an "item" for the config file?
>>
>> Thanks for any help!
>>
>> Best regards,
>> Paul
>>
>>
> --
> 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.juer...@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.
>
> Important note: The information included in this e-mail is confidential.
> It is solely intended for the recipient. If you are not the intended
> recipient of this e-mail please contact the sender and delete this message.
> Thank you. Without prejudice of e-mail correspondence, our statements are
> only legally binding when they are made in the conventional written form
> (with personal signature) or when such documents are sent by fax.
>
>
> --
> 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/ofWBP3Gxj6g/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.

[dspace-tech] webui.collectionhome.browse-name

[Paul Warner]

Hi,

We are using Dspace 6.1, and the ui is jspui.

The library for whom we are setting up a dspace repository would like the 
default sort for collection-home.jsp to be date created, a metadata item.  
It is a list of concerts, and the most meaningful list is by concert date.  
Sorting by title is a useful option, but not what they want by default.  
They also would like it to be a descending list.  

How do I do this?

The column for sorting is set in dspace.cfg by

webui.collectionhome.browse-name

It says that one has to use an "item" type of browse index.  I could use a 
short primer on the difference between an "item" type and a metadata type 
in the dspace.cfg file.  And then we need to know how to customize this...  
Can I set a metadata item as an "item" for the config file?

Thanks for any help!

Best regards,
Paul

-- 
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] DOI Update Bug?

[Paul Warner]

Hi Tom,

Thanks very much!  That was it.

Best regards,
Paul

On Tuesday, March 13, 2018 at 2:43:30 PM UTC+1, Tom Desair (Atmire) wrote:
>
> Hi Paul,
>
> The issue you describe is related to the "uncacheEntity(doi)" call in the 
> DOIOrganiser class.
>
> The "uncacheEntity" contained a bug in 6.1 which caused some database 
> changes to be lost. This has been corrected in 6.2.
>
>  
> [image: logo] Tom Desair
> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
> Gaston Geenslaan 14, Leuven 3001, Belgium
> www.atmire.com 
> <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomdesair>
>
>
> Op di 13 mrt. 2018 om 09:38 schreef Paul Warner  >:
>
>> Hi,
>>
>> We have set up our DataCite DOI account in our Dspace 6.1 instance, and 
>> we are having a problem when we run the update from the command line 
>> script, doi-organiser.
>>
>> When I make a change to metadata in our Dspace instance in the web site, 
>> this causes a change in the item's status in the doi table in the 
>> database.  The status changes from 3 to 6.  Then, the next time I run the 
>> command line program, doi-organiser, the status after the update to 
>> DataCite should be changed back to 3.  In the java code, it appears that 
>> the change is being made, but in the database, the status does not change, 
>> it is still 6.  This means that the next time doi-organiser runs, it will 
>> try to make another update for this item.  It succeeds at DataCite, and 
>> another instance appears on the revisions list, but the status never 
>> changes in the database.
>>
>> In our file, DOIIdentifierProvider.java, which provides the updating 
>> functions for both the website update process and the command line program, 
>> the method updateMetadata handles the website update, and the method 
>> updateMetadataOnline handles the update from the doi-organiser command line 
>> program.  Both methods report success, but only updateMetadata actually 
>> updates the database.
>>
>> Thanks in advance for any suggestions.
>>
>> Best regards,
>> Paul
>>
>>
>> -- 
>> 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.

[dspace-tech] DOI Update Bug?

[Paul Warner]

Hi,

We have set up our DataCite DOI account in our Dspace 6.1 instance, and we 
are having a problem when we run the update from the command line script, 
doi-organiser.

When I make a change to metadata in our Dspace instance in the web site, 
this causes a change in the item's status in the doi table in the 
database.  The status changes from 3 to 6.  Then, the next time I run the 
command line program, doi-organiser, the status after the update to 
DataCite should be changed back to 3.  In the java code, it appears that 
the change is being made, but in the database, the status does not change, 
it is still 6.  This means that the next time doi-organiser runs, it will 
try to make another update for this item.  It succeeds at DataCite, and 
another instance appears on the revisions list, but the status never 
changes in the database.

In our file, DOIIdentifierProvider.java, which provides the updating 
functions for both the website update process and the command line program, 
the method updateMetadata handles the website update, and the method 
updateMetadataOnline handles the update from the doi-organiser command line 
program.  Both methods report success, but only updateMetadata actually 
updates the database.

Thanks in advance for any suggestions.

Best regards,
Paul


-- 
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] DOI registration on existing Dspace items

[Paul Warner]

@Paul Münch:

This may be helpful, but I am unfortunately not familiar with the process
you are describing...

We have had success registering our existing items by modifiying the doi
table directly, and then running the doi-organiser script.  I have 50 items
that are now registered with DataCite.  I do not see the automatic change
of status, however, and I need to ask the list for help with that.

@Tech List:

I intially listed all my existing items with status 7 so they were updated
when I ran the script, and they all appeared in DataCite in our account.
They were not yet registered, however, and the status column remained
unchanged with 7 for all rows.

I registerd them all this morning, by changing the status of the instances
manually to 1, and running the script again.  Now there are links in
DataCite, in www.doi.org, and the dc.identifier.uri in my dspace is set
correctly in our dspace metadata.  All this is super!  Like magic!

One problem remains: the status column is not always correctly changed.
First of all, the status remained 1 for all 50 rows.  This means that the
next time my cron runs, it would try to register all 50 items again,
although they are already registered.  I believe the script should change
all the 1's to 3's, indicating that the items have been registered.

I was worried about this 2x registration, and changed the status to 3 -
again manually.  I know this is wrong, I am just testing!

I then tried editing some metadata, and the status does change correctly
when I do this - it changed to a 6.  But after I run the update with the
script (doi-organiser -u), which ran successfully, the status column was
not converted back to what it was.  It remained 6.  Does this have to do
with some setting in the configuration?  Or is there some database setting
that needs to be changed, since I am dealing with existing items...

Thanks in advance for any suggestions!

Best regards,
Paul

On Mon, Mar 12, 2018 at 8:28 AM, Paul Münch 
wrote:

> Hello there,
>
> I followed your interesting conversation because the same issue will
> bother us soon.
>
> Isn't it easier to export the existing Items as AIP, delete them and
> reimporting them with -s flag? Just a thought that I had.
>
> Best regards,
> Paul M.
>
>
> Zitat von Paul Warner :
>
> Hello Claudia,
>>
>> Somehow I missed commenting this in in the file
>> dspace-src/dspace/config/spring/api/identifier-service.xml:
>>
>> > class="org.dspace.identifier.DOIIdentifierProvider"
>> scope="singleton">
>> > ref="org.dspace.services.ConfigurationService" />
>> > ref="org.dspace.identifier.doi.DOIConnector" />
>> 
>>
>> Duh.
>>
>> Now that it is no longer commented out, doi-organiser works.
>>
>> Thanks!
>> -Paul
>>
>> On Fri, Mar 9, 2018 at 4:49 PM, Paul Warner 
>> wrote:
>>
>> Hello Claudia,
>>>
>>> Sorry for another question - now I am getting a null pointer exception
>>> whenever I run something, and it is happening on the line with the
>>> provider, for instance:
>>>
>>> try {
>>>
>>> provider.registerOnline(context,
>>> dso,
>>>
>>> DOI.SCHEME + doiRow.getDoi());
>>>
>>> etc...
>>>
>>> Have I missed some configuration item?
>>>
>>> Best regards,
>>> Paul
>>>
>>> On Fri, Mar 9, 2018 at 4:30 PM, Paul Warner 
>>> wrote:
>>>
>>> Hi Claudia,
>>>>
>>>> Excellent!  Thank you!
>>>>
>>>> Best regards,
>>>> Paul
>>>>
>>>> On Fri, Mar 9, 2018 at 4:23 PM, Claudia Jürgen <
>>>> claudia.juer...@tu-dortmund.de> wrote:
>>>>
>>>> Hi Paul,
>>>>>
>>>>> here is the list:
>>>>> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/
>>>>> src/main/java/org/dspace/identifier/DOIIdentifierProvider.java#L75
>>>>> 7 is the step before registering, setting the local metadata.
>>>>>
>>>>> Hope this helps
>>>>>
>>>>> Claudia Jürgen
>>>>>
>>>>>
>>>>>
>>>>> Am 09.03.2018 um 16:08 schrieb Paul Warner:
>>>>>
>>>>> Hello Claudia,
>>>>>>
>>>>>> Thanks once again for the super tip.  :-)  We are running Dspace 6.1,
>>>>>> so I
>>>>>> do need the uuid.  I got the list of all uuids from the Dspace rest
>>>>>> int

Re: [dspace-tech] DOI registration on existing Dspace items

[Paul Warner]

Hello Claudia,

Somehow I missed commenting this in in the file
dspace-src/dspace/config/spring/api/identifier-service.xml:






Duh.

Now that it is no longer commented out, doi-organiser works.

Thanks!
-Paul

On Fri, Mar 9, 2018 at 4:49 PM, Paul Warner  wrote:

> Hello Claudia,
>
> Sorry for another question - now I am getting a null pointer exception
> whenever I run something, and it is happening on the line with the
> provider, for instance:
>
> try {
>
> provider.registerOnline(context,
> dso,
>
> DOI.SCHEME + doiRow.getDoi());
>
> etc...
>
> Have I missed some configuration item?
>
> Best regards,
> Paul
>
> On Fri, Mar 9, 2018 at 4:30 PM, Paul Warner  wrote:
>
>> Hi Claudia,
>>
>> Excellent!  Thank you!
>>
>> Best regards,
>> Paul
>>
>> On Fri, Mar 9, 2018 at 4:23 PM, Claudia Jürgen <
>> claudia.juer...@tu-dortmund.de> wrote:
>>
>>> Hi Paul,
>>>
>>> here is the list:
>>> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/
>>> src/main/java/org/dspace/identifier/DOIIdentifierProvider.java#L75
>>> 7 is the step before registering, setting the local metadata.
>>>
>>> Hope this helps
>>>
>>> Claudia Jürgen
>>>
>>>
>>>
>>> Am 09.03.2018 um 16:08 schrieb Paul Warner:
>>>
>>>> Hello Claudia,
>>>>
>>>> Thanks once again for the super tip.  :-)  We are running Dspace 6.1,
>>>> so I
>>>> do need the uuid.  I got the list of all uuids from the Dspace rest
>>>> interface, and then made this simplified insert:
>>>>
>>>> insert into doi (doi_id,doi,resource_type_id,r
>>>> esource_id,status,dspace_object)
>>>> values (nextval('doi_seq'), concat('10./namespacesepar
>>>> ator-',currval('
>>>> doi_seq')),2,null,7,'272017e2-9e50-48de-8385-cb599bbc615f');
>>>>
>>>> Following your suggestion, I set the status to 7.  This seems to make
>>>> the
>>>> items ready for update.  But I have not registered them yet, they are
>>>> not
>>>> known to DataCite. How can I find the statuses and their numbers?
>>>>
>>>> Thanks!
>>>>
>>>> Best regards,
>>>> Paul
>>>>
>>>>
>>>>
>>>> On Fri, Mar 9, 2018 at 12:43 PM, Claudia Jürgen <
>>>> claudia.juer...@tu-dortmund.de> wrote:
>>>>
>>>> Hello Paul,
>>>>>
>>>>> we retrospectively added DOI's to our existing instance and had the
>>>>> same
>>>>> problem, only items ingested after the doi service is up and running
>>>>> are
>>>>> added to the doi table.
>>>>> There is afaik not yet a job to insert existing ones.
>>>>>
>>>>> We manipulated the db - The usual WARNING, backup and be sure what you
>>>>> are doing.
>>>>> This was on a 4.2 instance but should work on 5.x, too,  on 6 you have
>>>>> the uuid.
>>>>>
>>>>> INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
>>>>> SELECT nextval('doi_seq'),
>>>>> concat('YOURPREFIX/YOURNAMESPACESEPERATOR-',currval('doi_seq')), 2,
>>>>> item_id, 7 FROM item WHERE in_archive=true and item_id not in (select
>>>>> resource_id from doi where resource_type_id=2);
>>>>>
>>>>> Hope this helps
>>>>>
>>>>> Claudia
>>>>>
>>>>>
>>>>> Am 09.03.2018 um 11:35 schrieb Paul Warner:
>>>>>
>>>>> Hi,
>>>>>>
>>>>>> I have 52 items in my dspace test instance, and we now have a contract
>>>>>> with
>>>>>> DataCite to create dois for our items.  I read an old post in which
>>>>>> Pascal-Nicolas Becker explained that the new items (those loaded in
>>>>>> after
>>>>>> the doi configuration is complete) are seen as ready for doi
>>>>>> processing.
>>>>>> How do I tell Dspace that all my 52 items are 'new', so that they get
>>>>>> loaded into the doi table for processing?  Right now, when I run the
>>>>>> commands, I get these results.
>>>>>>
>>>>>> dspace@m

Re: [dspace-tech] DOI registration on existing Dspace items

[Paul Warner]

Hello Claudia,

Sorry for another question - now I am getting a null pointer exception
whenever I run something, and it is happening on the line with the
provider, for instance:

try
{

provider.registerOnline(context,
dso,

DOI.SCHEME + doiRow.getDoi());

etc...

Have I missed some configuration item?

Best regards,
Paul

On Fri, Mar 9, 2018 at 4:30 PM, Paul Warner  wrote:

> Hi Claudia,
>
> Excellent!  Thank you!
>
> Best regards,
> Paul
>
> On Fri, Mar 9, 2018 at 4:23 PM, Claudia Jürgen <
> claudia.juer...@tu-dortmund.de> wrote:
>
>> Hi Paul,
>>
>> here is the list:
>> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/
>> src/main/java/org/dspace/identifier/DOIIdentifierProvider.java#L75
>> 7 is the step before registering, setting the local metadata.
>>
>> Hope this helps
>>
>> Claudia Jürgen
>>
>>
>>
>> Am 09.03.2018 um 16:08 schrieb Paul Warner:
>>
>>> Hello Claudia,
>>>
>>> Thanks once again for the super tip.  :-)  We are running Dspace 6.1, so
>>> I
>>> do need the uuid.  I got the list of all uuids from the Dspace rest
>>> interface, and then made this simplified insert:
>>>
>>> insert into doi (doi_id,doi,resource_type_id,r
>>> esource_id,status,dspace_object)
>>> values (nextval('doi_seq'), concat('10./namespacesepar
>>> ator-',currval('
>>> doi_seq')),2,null,7,'272017e2-9e50-48de-8385-cb599bbc615f');
>>>
>>> Following your suggestion, I set the status to 7.  This seems to make the
>>> items ready for update.  But I have not registered them yet, they are not
>>> known to DataCite. How can I find the statuses and their numbers?
>>>
>>> Thanks!
>>>
>>> Best regards,
>>> Paul
>>>
>>>
>>>
>>> On Fri, Mar 9, 2018 at 12:43 PM, Claudia Jürgen <
>>> claudia.juer...@tu-dortmund.de> wrote:
>>>
>>> Hello Paul,
>>>>
>>>> we retrospectively added DOI's to our existing instance and had the same
>>>> problem, only items ingested after the doi service is up and running are
>>>> added to the doi table.
>>>> There is afaik not yet a job to insert existing ones.
>>>>
>>>> We manipulated the db - The usual WARNING, backup and be sure what you
>>>> are doing.
>>>> This was on a 4.2 instance but should work on 5.x, too,  on 6 you have
>>>> the uuid.
>>>>
>>>> INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
>>>> SELECT nextval('doi_seq'),
>>>> concat('YOURPREFIX/YOURNAMESPACESEPERATOR-',currval('doi_seq')), 2,
>>>> item_id, 7 FROM item WHERE in_archive=true and item_id not in (select
>>>> resource_id from doi where resource_type_id=2);
>>>>
>>>> Hope this helps
>>>>
>>>> Claudia
>>>>
>>>>
>>>> Am 09.03.2018 um 11:35 schrieb Paul Warner:
>>>>
>>>> Hi,
>>>>>
>>>>> I have 52 items in my dspace test instance, and we now have a contract
>>>>> with
>>>>> DataCite to create dois for our items.  I read an old post in which
>>>>> Pascal-Nicolas Becker explained that the new items (those loaded in
>>>>> after
>>>>> the doi configuration is complete) are seen as ready for doi
>>>>> processing.
>>>>> How do I tell Dspace that all my 52 items are 'new', so that they get
>>>>> loaded into the doi table for processing?  Right now, when I run the
>>>>> commands, I get these results.
>>>>>
>>>>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -u
>>>>> There are no objects in the database whose metadata needs an update.
>>>>> dspace@plmachinenameton:~/dspace_instance> bin/dspace doi-organiser -s
>>>>> There are no objects in the database that could be reserved.
>>>>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -r
>>>>> There are no objects in the database that could be registered.
>>>>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -d
>>>>> There are no objects in the database that could be deleted.
>>>>>
>>>>> There is nothing in the doi table in Postgres, presumably because only
>>>>> new
>>>>&

Re: [dspace-tech] DOI registration on existing Dspace items

[Paul Warner]

Hi Claudia,

Excellent!  Thank you!

Best regards,
Paul

On Fri, Mar 9, 2018 at 4:23 PM, Claudia Jürgen <
claudia.juer...@tu-dortmund.de> wrote:

> Hi Paul,
>
> here is the list:
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/
> src/main/java/org/dspace/identifier/DOIIdentifierProvider.java#L75
> 7 is the step before registering, setting the local metadata.
>
> Hope this helps
>
> Claudia Jürgen
>
>
>
> Am 09.03.2018 um 16:08 schrieb Paul Warner:
>
>> Hello Claudia,
>>
>> Thanks once again for the super tip.  :-)  We are running Dspace 6.1, so I
>> do need the uuid.  I got the list of all uuids from the Dspace rest
>> interface, and then made this simplified insert:
>>
>> insert into doi (doi_id,doi,resource_type_id,r
>> esource_id,status,dspace_object)
>> values (nextval('doi_seq'), concat('10./namespacesepar
>> ator-',currval('
>> doi_seq')),2,null,7,'272017e2-9e50-48de-8385-cb599bbc615f');
>>
>> Following your suggestion, I set the status to 7.  This seems to make the
>> items ready for update.  But I have not registered them yet, they are not
>> known to DataCite. How can I find the statuses and their numbers?
>>
>> Thanks!
>>
>> Best regards,
>> Paul
>>
>>
>>
>> On Fri, Mar 9, 2018 at 12:43 PM, Claudia Jürgen <
>> claudia.juer...@tu-dortmund.de> wrote:
>>
>> Hello Paul,
>>>
>>> we retrospectively added DOI's to our existing instance and had the same
>>> problem, only items ingested after the doi service is up and running are
>>> added to the doi table.
>>> There is afaik not yet a job to insert existing ones.
>>>
>>> We manipulated the db - The usual WARNING, backup and be sure what you
>>> are doing.
>>> This was on a 4.2 instance but should work on 5.x, too,  on 6 you have
>>> the uuid.
>>>
>>> INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
>>> SELECT nextval('doi_seq'),
>>> concat('YOURPREFIX/YOURNAMESPACESEPERATOR-',currval('doi_seq')), 2,
>>> item_id, 7 FROM item WHERE in_archive=true and item_id not in (select
>>> resource_id from doi where resource_type_id=2);
>>>
>>> Hope this helps
>>>
>>> Claudia
>>>
>>>
>>> Am 09.03.2018 um 11:35 schrieb Paul Warner:
>>>
>>> Hi,
>>>>
>>>> I have 52 items in my dspace test instance, and we now have a contract
>>>> with
>>>> DataCite to create dois for our items.  I read an old post in which
>>>> Pascal-Nicolas Becker explained that the new items (those loaded in
>>>> after
>>>> the doi configuration is complete) are seen as ready for doi processing.
>>>> How do I tell Dspace that all my 52 items are 'new', so that they get
>>>> loaded into the doi table for processing?  Right now, when I run the
>>>> commands, I get these results.
>>>>
>>>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -u
>>>> There are no objects in the database whose metadata needs an update.
>>>> dspace@plmachinenameton:~/dspace_instance> bin/dspace doi-organiser -s
>>>> There are no objects in the database that could be reserved.
>>>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -r
>>>> There are no objects in the database that could be registered.
>>>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -d
>>>> There are no objects in the database that could be deleted.
>>>>
>>>> There is nothing in the doi table in Postgres, presumably because only
>>>> new
>>>> items are recognized as needing dois.
>>>>
>>>> Best regards,
>>>> Paul
>>>>
>>>>
>>>> --
>>> 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.juer...@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. Vie

Re: [dspace-tech] DOI registration on existing Dspace items

[Paul Warner]

Hello Claudia,

Ok, I tested it, using the list function:

doi-organiser -l

I simply updated a row, trying the various numbers between 1 and 8.  Here
they are:

Register:  1
Reservation: 2
Update:7
Delete: 8

Best regards,
Paul

On Fri, Mar 9, 2018 at 4:08 PM, Paul Warner  wrote:

> Hello Claudia,
>
> Thanks once again for the super tip.  :-)  We are running Dspace 6.1, so I
> do need the uuid.  I got the list of all uuids from the Dspace rest
> interface, and then made this simplified insert:
>
> insert into doi (doi_id,doi,resource_type_id,r
> esource_id,status,dspace_object) values (nextval('doi_seq'),
> concat('10./namespaceseparator-',currval('doi_seq')),2,
> null,7,'272017e2-9e50-48de-8385-cb599bbc615f');
>
> Following your suggestion, I set the status to 7.  This seems to make the
> items ready for update.  But I have not registered them yet, they are not
> known to DataCite. How can I find the statuses and their numbers?
>
> Thanks!
>
> Best regards,
> Paul
>
>
>
> On Fri, Mar 9, 2018 at 12:43 PM, Claudia Jürgen <
> claudia.juer...@tu-dortmund.de> wrote:
>
>> Hello Paul,
>>
>> we retrospectively added DOI's to our existing instance and had the same
>> problem, only items ingested after the doi service is up and running are
>> added to the doi table.
>> There is afaik not yet a job to insert existing ones.
>>
>> We manipulated the db - The usual WARNING, backup and be sure what you
>> are doing.
>> This was on a 4.2 instance but should work on 5.x, too,  on 6 you have
>> the uuid.
>>
>> INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
>> SELECT nextval('doi_seq'),
>> concat('YOURPREFIX/YOURNAMESPACESEPERATOR-',currval('doi_seq')), 2,
>> item_id, 7 FROM item WHERE in_archive=true and item_id not in (select
>> resource_id from doi where resource_type_id=2);
>>
>> Hope this helps
>>
>> Claudia
>>
>>
>> Am 09.03.2018 um 11:35 schrieb Paul Warner:
>>
>>> Hi,
>>>
>>> I have 52 items in my dspace test instance, and we now have a contract
>>> with
>>> DataCite to create dois for our items.  I read an old post in which
>>> Pascal-Nicolas Becker explained that the new items (those loaded in after
>>> the doi configuration is complete) are seen as ready for doi processing.
>>> How do I tell Dspace that all my 52 items are 'new', so that they get
>>> loaded into the doi table for processing?  Right now, when I run the
>>> commands, I get these results.
>>>
>>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -u
>>> There are no objects in the database whose metadata needs an update.
>>> dspace@plmachinenameton:~/dspace_instance> bin/dspace doi-organiser -s
>>> There are no objects in the database that could be reserved.
>>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -r
>>> There are no objects in the database that could be registered.
>>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -d
>>> There are no objects in the database that could be deleted.
>>>
>>> There is nothing in the doi table in Postgres, presumably because only
>>> new
>>> items are recognized as needing dois.
>>>
>>> Best regards,
>>> Paul
>>>
>>>
>> --
>> 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.juer...@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.
>>
>> Important note: The information included in this e-mail is confidential.
>> It is solely intended for the recipient. If you are not the intended
>> recipient of this e-mail please contact the sender and delete this message.
>> Thank you. Without prejudice of e-mail correspondence, our sta

Re: [dspace-tech] Re: DOI registration on existing Dspace items

[Paul Warner]

Ok, thanks! I will take a look.

Best regards,
Paul

On Fri, Mar 9, 2018 at 4:06 PM, Mark H. Wood  wrote:

> You may be interested in trying out the pull request
> https://github.com/DSpace/DSpace/pull/1857 associated with
> https://jira.duraspace.org/browse/DS-2670
>
> It creates a new curation task for finding objects with missing
> identifiers and creating those missing identifiers.  It is written for the
> upcoming DSpace 7 but probably isn't too difficult to back-port.  It needs
> testers. :-/
>
> --
> 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/fBwxAlcjPZA/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.

Re: [dspace-tech] DOI registration on existing Dspace items

[Paul Warner]

Hello Claudia,

Thanks once again for the super tip.  :-)  We are running Dspace 6.1, so I
do need the uuid.  I got the list of all uuids from the Dspace rest
interface, and then made this simplified insert:

insert into doi (doi_id,doi,resource_type_id,resource_id,status,dspace_object)
values (nextval('doi_seq'), concat('10./namespaceseparator-',currval('
doi_seq')),2,null,7,'272017e2-9e50-48de-8385-cb599bbc615f');

Following your suggestion, I set the status to 7.  This seems to make the
items ready for update.  But I have not registered them yet, they are not
known to DataCite. How can I find the statuses and their numbers?

Thanks!

Best regards,
Paul



On Fri, Mar 9, 2018 at 12:43 PM, Claudia Jürgen <
claudia.juer...@tu-dortmund.de> wrote:

> Hello Paul,
>
> we retrospectively added DOI's to our existing instance and had the same
> problem, only items ingested after the doi service is up and running are
> added to the doi table.
> There is afaik not yet a job to insert existing ones.
>
> We manipulated the db - The usual WARNING, backup and be sure what you
> are doing.
> This was on a 4.2 instance but should work on 5.x, too,  on 6 you have
> the uuid.
>
> INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
> SELECT nextval('doi_seq'),
> concat('YOURPREFIX/YOURNAMESPACESEPERATOR-',currval('doi_seq')), 2,
> item_id, 7 FROM item WHERE in_archive=true and item_id not in (select
> resource_id from doi where resource_type_id=2);
>
> Hope this helps
>
> Claudia
>
>
> Am 09.03.2018 um 11:35 schrieb Paul Warner:
>
>> Hi,
>>
>> I have 52 items in my dspace test instance, and we now have a contract
>> with
>> DataCite to create dois for our items.  I read an old post in which
>> Pascal-Nicolas Becker explained that the new items (those loaded in after
>> the doi configuration is complete) are seen as ready for doi processing.
>> How do I tell Dspace that all my 52 items are 'new', so that they get
>> loaded into the doi table for processing?  Right now, when I run the
>> commands, I get these results.
>>
>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -u
>> There are no objects in the database whose metadata needs an update.
>> dspace@plmachinenameton:~/dspace_instance> bin/dspace doi-organiser -s
>> There are no objects in the database that could be reserved.
>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -r
>> There are no objects in the database that could be registered.
>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -d
>> There are no objects in the database that could be deleted.
>>
>> There is nothing in the doi table in Postgres, presumably because only new
>> items are recognized as needing dois.
>>
>> Best regards,
>> Paul
>>
>>
> --
> 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.juer...@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.
>
> Important note: The information included in this e-mail is confidential.
> It is solely intended for the recipient. If you are not the intended
> recipient of this e-mail please contact the sender and delete this message.
> Thank you. Without prejudice of e-mail correspondence, our statements are
> only legally binding when they are made in the conventional written form
> (with personal signature) or when such documents are sent by fax.
>
>
> --
> 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/fBwxAlcjPZA/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.

[dspace-tech] DOI registration on existing Dspace items

[Paul Warner]

Hi,

I have 52 items in my dspace test instance, and we now have a contract with 
DataCite to create dois for our items.  I read an old post in which 
Pascal-Nicolas Becker explained that the new items (those loaded in after 
the doi configuration is complete) are seen as ready for doi processing.  
How do I tell Dspace that all my 52 items are 'new', so that they get 
loaded into the doi table for processing?  Right now, when I run the 
commands, I get these results.

dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -u
There are no objects in the database whose metadata needs an update.
dspace@plmachinenameton:~/dspace_instance> bin/dspace doi-organiser -s
There are no objects in the database that could be reserved.
dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -r
There are no objects in the database that could be registered.
dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -d
There are no objects in the database that could be deleted.

There is nothing in the doi table in Postgres, presumably because only new 
items are recognized as needing dois.

Best regards,
Paul

-- 
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: REST API not working

[Paul Warner]

Hi,

It sounds like you are having other problems, George, but I just struggled 
with Dspace's Rest interface, and I can confirm the Apache 
Proxy/ReverseProxy problem.  That stumped me for a while, because we are 
running https through Apache, and I thought I should leave the https in.  
But we are not using https for Tomcat, of course (duh!), since it is 
running behind Apache - so I had to comment out the https segment in the 
Rest config before I could get it to work.  I have tomcat configured to 
listen only on localhost, so I can now access the Rest interface only on 
that machine.  I use curl on the command line.  Everything works.  But I 
have not included rest in the Proxy/ReverseProxy list for Apache, so it is 
not available in the browser.  I get a 404 just like you do, George.  I do 
not want everyone to be able to use it online, so this suits me.  

I post this because these kinds of fine points can be overlooked.  I hope 
it helps someone.

Best regards,
Paul


On Monday, January 22, 2018 at 7:30:22 PM UTC+1, George Kozak wrote:
>
> Hi...
> I wrote about this back on January 8th, but didn't get any replies...so I 
> am trying again :-)
> In our DSpace 6.2 installation, if I try to access the REST API, the 
> system responds with "Page Not Found" as if I had typed in an inaccurate 
> URL.  It does this even when I try:
> curl https:///rest/test
>
> In the tomcat server.xml, I have:
>   
>
> Does anyone have any ideas why the code would not recognize the REST API?
> (PS: it worked fine in DSpace 5.5)
> Thanks!
>
> -- 
> ***
> George Kozak
> Digital Library Specialist
> Cornell University Library - IT
> 218 Olin Library
> Cornell University
> Ithaca, NY 14853
> 607-255-8924
> gs...@cornell.edu  
>

-- 
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] itemupdate command line delete bitstream

[Paul Warner]

Dear Claudia,

I found my problem.  I finally disabled the  block in
the web.xml file in the rest directory in tomcat/webapps, as it says in the
docs (https://wiki.duraspace.org/display/DSDOC6x/REST+API)  and now it is
working.  I had thought that, since we are using https, disabling https was
not applicable for us, and so I had not commented out that section until
just now.  My stupidity - we are using https in apache, which is then
calling tomcat over plain http.  Duh.  Sorry for the confusion, and thanks
very much for the spot-on help!

Best regards,
Paul

On Mon, Jan 15, 2018 at 4:30 PM, Claudia Jürgen <
claudia.juer...@tu-dortmund.de> wrote:

> Hello Paul,
>
> what do you get  with
>
> https://my.project.url/rest/test
>
> should return "REST api is running"
>
> supposing you did deploy the rest application as rest.
>
> Then are the bitstreams of this item or the item restricted?
> If so, I think you must authenticate (but I actually never used the REST
> API)
> https://wiki.duraspace.org/display/DSDOC6x/REST+API#RESTAPI-
> Index/Authentication
>
>
> Claudia Jürgen
>
>
>
>
>
>
> Am 15.01.2018 um 15:56 schrieb Paul Warner:
>
>> Hello Claudia,
>>
>> Thanks for the tip!  I see it works on the demo, but on our dev site, I
>> get
>> a 404 with exactly the same format in the url and with my uuid:
>>
>> https://my.project.url/rest/items/4da73e7c-1eeb-4772-9648-5c
>> 972632e9ad/bitstreams
>>
>> if I use curl on the server itself:
>>
>> curl -s -H "Accept: application/xml"
>> https://localhost:8080/rest/items/4da73e7c-1eeb-4772-9648-5c
>> 972632e9ad/bitstreams
>> | xmllint --format -
>>
>> I get this error:
>>
>> -:1: parser error : Document is empty
>>
>> I have not tried to use the rest api until now, and I see I am missing
>> something, something big, and maybe simple.  What am I missing?
>>
>> Best regards,
>> Paul
>>
>>
>>
>>
>> On Mon, Jan 15, 2018 at 2:01 PM, Claudia Jürgen <
>> claudia.juer...@tu-dortmund.de> wrote:
>>
>> Hi Paul,
>>>
>>> as the name must not be unique, you will need the UUID or legacy ID to
>>> delete a bitstream.
>>> You may get a list of all bistreams belonging to an item via the REST API
>>> https://demo.dspace.org/rest/
>>> GET /items/{item id}/bitstreams - Return bitstreams of the specified
>>> item.
>>> e.g.
>>> https://demo.dspace.org/rest/items/99819176-b29f-4d18-a4e1-9
>>> bf6b93bb443/bitstreams
>>>
>>> Hope this helps
>>>
>>> Claudia Jürgen
>>>
>>>
>>>
>>> Am 15.01.2018 um 13:27 schrieb Paul Warner:
>>>
>>> Hi,
>>>>
>>>> I want to delete a bitstream from an item.  I have a delete_contents
>>>> file
>>>> inside my SimpleArchiveFormat folder.  The delete_contents file has the
>>>> filename of the file I want to delete, but I get an error message that
>>>> indicates the uuid is needed, not the name of the file.  How do I get
>>>> the
>>>> uuid of the file from the command line?
>>>>
>>>> Below is the command and the error message.
>>>>
>>>> Best regards,
>>>> Paul
>>>>
>>>>
>>>> command:
>>>>
>>>> bin/dspace itemupdate -e p.war...@myemailaddress.com -s
>>>> /opt/dspace/SimpleArchiveFormat_421000732 --deletebitstreams
>>>>
>>>> Error message:
>>>>
>>>> Exception processing item item_1: java.lang.IllegalArgumentException:
>>>> Invalid UUID string: test_421000732.pdf
>>>> java.lang.IllegalArgumentException: Invalid UUID string:
>>>> test_421000732.pdf
>>>> at java.util.UUID.fromString(UUID.java:194)
>>>> at
>>>> org.dspace.content.BitstreamServiceImpl.findByIdOrLegacyId(B
>>>> itstreamServiceImpl.java:426)
>>>> at
>>>> org.dspace.content.BitstreamServiceImpl.findByIdOrLegacyId(B
>>>> itstreamServiceImpl.java:41)
>>>> at
>>>> org.dspace.app.itemupdate.DeleteBitstreamsAction.execute(Del
>>>> eteBitstreamsAction.java:66)
>>>> at org.dspace.app.itemupdate.ItemUpdate.processArchive(ItemUpda
>>>> te.java:442)
>>>> at org.dspace.app.itemupdate.ItemUpdate.main(ItemUpdate.java:355)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(Nat

Re: [dspace-tech] itemupdate command line delete bitstream

[Paul Warner]

Hello Claudia,

Thanks for the tip!  I see it works on the demo, but on our dev site, I get
a 404 with exactly the same format in the url and with my uuid:

https://my.project.url/rest/items/4da73e7c-1eeb-4772-9648-5c972632e9ad/bitstreams

if I use curl on the server itself:

curl -s -H "Accept: application/xml"
https://localhost:8080/rest/items/4da73e7c-1eeb-4772-9648-5c972632e9ad/bitstreams
| xmllint --format -

I get this error:

-:1: parser error : Document is empty

I have not tried to use the rest api until now, and I see I am missing
something, something big, and maybe simple.  What am I missing?

Best regards,
Paul




On Mon, Jan 15, 2018 at 2:01 PM, Claudia Jürgen <
claudia.juer...@tu-dortmund.de> wrote:

> Hi Paul,
>
> as the name must not be unique, you will need the UUID or legacy ID to
> delete a bitstream.
> You may get a list of all bistreams belonging to an item via the REST API
> https://demo.dspace.org/rest/
> GET /items/{item id}/bitstreams - Return bitstreams of the specified item.
> e.g.
> https://demo.dspace.org/rest/items/99819176-b29f-4d18-a4e1-9
> bf6b93bb443/bitstreams
>
> Hope this helps
>
> Claudia Jürgen
>
>
>
> Am 15.01.2018 um 13:27 schrieb Paul Warner:
>
>> Hi,
>>
>> I want to delete a bitstream from an item.  I have a delete_contents file
>> inside my SimpleArchiveFormat folder.  The delete_contents file has the
>> filename of the file I want to delete, but I get an error message that
>> indicates the uuid is needed, not the name of the file.  How do I get the
>> uuid of the file from the command line?
>>
>> Below is the command and the error message.
>>
>> Best regards,
>> Paul
>>
>>
>> command:
>>
>> bin/dspace itemupdate -e p.war...@myemailaddress.com -s
>> /opt/dspace/SimpleArchiveFormat_421000732 --deletebitstreams
>>
>> Error message:
>>
>> Exception processing item item_1: java.lang.IllegalArgumentException:
>> Invalid UUID string: test_421000732.pdf
>> java.lang.IllegalArgumentException: Invalid UUID string:
>> test_421000732.pdf
>> at java.util.UUID.fromString(UUID.java:194)
>> at
>> org.dspace.content.BitstreamServiceImpl.findByIdOrLegacyId(B
>> itstreamServiceImpl.java:426)
>> at
>> org.dspace.content.BitstreamServiceImpl.findByIdOrLegacyId(B
>> itstreamServiceImpl.java:41)
>> at
>> org.dspace.app.itemupdate.DeleteBitstreamsAction.execute(Del
>> eteBitstreamsAction.java:66)
>> at org.dspace.app.itemupdate.ItemUpdate.processArchive(ItemUpda
>> te.java:442)
>> at org.dspace.app.itemupdate.ItemUpdate.main(ItemUpdate.java:355)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptL
>> auncher.java:229)
>> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
>>
>>
> --
> 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.juer...@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.
>
> Important note: The information included in this e-mail is confidential.
> It is solely intended for the recipient. If you are not the intended
> recipient of this e-mail please contact the sender and delete this message.
> Thank you. Without prejudice of e-mail correspondence, our statements are
> only legally binding when they are made in the conventional written form
> (with personal signature) or when such documents are sent by fax.
>
>
> --
> 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/iP9a_8Lk89U/unsubscribe.
> To unsubscribe from this

[dspace-tech] itemupdate command line delete bitstream

[Paul Warner]

Hi,

I want to delete a bitstream from an item.  I have a delete_contents file 
inside my SimpleArchiveFormat folder.  The delete_contents file has the 
filename of the file I want to delete, but I get an error message that 
indicates the uuid is needed, not the name of the file.  How do I get the 
uuid of the file from the command line?

Below is the command and the error message.

Best regards,
Paul


command:

bin/dspace itemupdate -e p.war...@myemailaddress.com -s 
/opt/dspace/SimpleArchiveFormat_421000732 --deletebitstreams

Error message:

Exception processing item item_1: java.lang.IllegalArgumentException: 
Invalid UUID string: test_421000732.pdf
java.lang.IllegalArgumentException: Invalid UUID string: test_421000732.pdf
at java.util.UUID.fromString(UUID.java:194)
at 
org.dspace.content.BitstreamServiceImpl.findByIdOrLegacyId(BitstreamServiceImpl.java:426)
at 
org.dspace.content.BitstreamServiceImpl.findByIdOrLegacyId(BitstreamServiceImpl.java:41)
at 
org.dspace.app.itemupdate.DeleteBitstreamsAction.execute(DeleteBitstreamsAction.java:66)
at org.dspace.app.itemupdate.ItemUpdate.processArchive(ItemUpdate.java:442)
at org.dspace.app.itemupdate.ItemUpdate.main(ItemUpdate.java:355)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)

-- 
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] Digest for dspace-tech@googlegroups.com - 1 update in 1 topic

[Paul Warner]

I thought I would add the Dspace version to this thread - it would seem
natural that the question would come up.  We are using DSpace 6.1.

-Paul

On Thu, Jan 4, 2018 at 1:26 PM, Paul Warner  wrote:

> Ok, I found the fix.  At the top of the 20 or so compiler errors was an
> error referencing the lack of the module javax.servlet.jsp.  I tried adding
> a dependency for javax.servlet.jsp-api to the pom.xml inside the
> dspace-src/dspace/modules/jspui directory.  Now I can compile without
> errors, and all 3 of my changed java files are in dspace-src/dspace/modules/
> jspui/src/main/java/org/dspace/app/webui/jsptag or servlet directories.
> And they are overriding the original files in the corresponding
> dspace-src/dspace-jspui directory.  Ahh!  How wonderful.  I hope this
> information helps someone!
>
> Best regards,
> Paul
>
> On Tue, Jan 2, 2018 at 11:33 AM, Paul Warner 
> wrote:
>
>> Hi,
>>
>> I have not been able to copy a java file from within the
>> jspui/src/main/java/org/dspace/app/webui directory into the modules
>> directory without getting a long string of compiler errors.  @Andy Osborne,
>> you are doing something right, that I have not figured out.  What's the
>> secret: how do you make it compile?  :-)
>>
>> Thanks for any tips!
>>
>> Best regards,
>> Paul
>>
>> On Sat, Dec 30, 2017 at 4:11 PM,  wrote:
>>
>>> dspace-tech@googlegroups.com
>>> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/dspace-tech/topics>
>>>  Google
>>> Groups
>>> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview>
>>> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview>
>>> Topic digest
>>> View all topics
>>> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/dspace-tech/topics>
>>>
>>>- Fw: Citation Cover Sheet
>>>
>>> <#m_7145022642774669187_m_9046385738656962673_m_-768085488296373371_group_thread_0>
>>>- 1 Update
>>>
>>> Fw: Citation Cover Sheet
>>> <http://groups.google.com/group/dspace-tech/t/6c85c608ffae3634?utm_source=digest&utm_medium=email>
>>> caosborne...@gmail.com: Dec 29 07:13AM -0800
>>>
>>> I was able to solve this mostly by looking at xmlui implementation of
>>> DisseminateServiceFactory. I've attached a copy of the
>>> jspui/src/main/java/org/dspace/app/webui/servlet/BitstreamServlet.java
>>> file
>>> that I added to the modules directory in order to overlay the original
>>> file.
>>>
>>> On Tuesday, December 12, 2017 at 5:04:54 PM UTC-5, Andy Osborne wrote:
>>> Back to top
>>> <#m_7145022642774669187_m_9046385738656962673_m_-768085488296373371_digest_top>
>>> You received this digest because you're subscribed to updates for this
>>> group. You can change your settings on the group membership page
>>> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/dspace-tech/join>
>>> .
>>> To unsubscribe from this group and stop receiving emails from it send an
>>> email to dspace-tech+unsubscr...@googlegroups.com.
>>>
>>
>>
>

-- 
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] Digest for dspace-tech@googlegroups.com - 1 update in 1 topic

[Paul Warner]

Ok, I found the fix.  At the top of the 20 or so compiler errors was an
error referencing the lack of the module javax.servlet.jsp.  I tried adding
a dependency for javax.servlet.jsp-api to the pom.xml inside the
dspace-src/dspace/modules/jspui directory.  Now I can compile without
errors, and all 3 of my changed java files are in
dspace-src/dspace/modules/jspui/src/main/java/org/dspace/app/webui/jsptag
or servlet directories.  And they are overriding the original files in the
corresponding dspace-src/dspace-jspui directory.  Ahh!  How wonderful.  I
hope this information helps someone!

Best regards,
Paul

On Tue, Jan 2, 2018 at 11:33 AM, Paul Warner  wrote:

> Hi,
>
> I have not been able to copy a java file from within the
> jspui/src/main/java/org/dspace/app/webui directory into the modules
> directory without getting a long string of compiler errors.  @Andy Osborne,
> you are doing something right, that I have not figured out.  What's the
> secret: how do you make it compile?  :-)
>
> Thanks for any tips!
>
> Best regards,
> Paul
>
> On Sat, Dec 30, 2017 at 4:11 PM,  wrote:
>
>> dspace-tech@googlegroups.com
>> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/dspace-tech/topics>
>>  Google
>> Groups
>> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview>
>> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview>
>> Topic digest
>> View all topics
>> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/dspace-tech/topics>
>>
>>- Fw: Citation Cover Sheet
>><#m_9046385738656962673_m_-768085488296373371_group_thread_0> - 1
>>Update
>>
>> Fw: Citation Cover Sheet
>> <http://groups.google.com/group/dspace-tech/t/6c85c608ffae3634?utm_source=digest&utm_medium=email>
>> caosborne...@gmail.com: Dec 29 07:13AM -0800
>>
>> I was able to solve this mostly by looking at xmlui implementation of
>> DisseminateServiceFactory. I've attached a copy of the
>> jspui/src/main/java/org/dspace/app/webui/servlet/BitstreamServlet.java
>> file
>> that I added to the modules directory in order to overlay the original
>> file.
>>
>> On Tuesday, December 12, 2017 at 5:04:54 PM UTC-5, Andy Osborne wrote:
>> Back to top <#m_9046385738656962673_m_-768085488296373371_digest_top>
>> You received this digest because you're subscribed to updates for this
>> group. You can change your settings on the group membership page
>> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/dspace-tech/join>
>> .
>> To unsubscribe from this group and stop receiving emails from it send an
>> email to dspace-tech+unsubscr...@googlegroups.com.
>>
>
>

-- 
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] Digest for dspace-tech@googlegroups.com - 1 update in 1 topic

[Paul Warner]

Hi,

I have not been able to copy a java file from within the
jspui/src/main/java/org/dspace/app/webui directory into the modules
directory without getting a long string of compiler errors.  @Andy Osborne,
you are doing something right, that I have not figured out.  What's the
secret: how do you make it compile?  :-)

Thanks for any tips!

Best regards,
Paul

On Sat, Dec 30, 2017 at 4:11 PM,  wrote:

> dspace-tech@googlegroups.com
> 
>  Google
> Groups
> 
> 
> Topic digest
> View all topics
> 
>
>- Fw: Citation Cover Sheet <#m_-768085488296373371_group_thread_0> - 1
>Update
>
> Fw: Citation Cover Sheet
> 
> caosborne...@gmail.com: Dec 29 07:13AM -0800
>
> I was able to solve this mostly by looking at xmlui implementation of
> DisseminateServiceFactory. I've attached a copy of the
> jspui/src/main/java/org/dspace/app/webui/servlet/BitstreamServlet.java
> file
> that I added to the modules directory in order to overlay the original
> file.
>
> On Tuesday, December 12, 2017 at 5:04:54 PM UTC-5, Andy Osborne wrote:
> Back to top <#m_-768085488296373371_digest_top>
> You received this digest because you're subscribed to updates for this
> group. You can change your settings on the group membership page
> 
> .
> To unsubscribe from this group and stop receiving emails from it send an
> email to dspace-tech+unsubscr...@googlegroups.com.
>

-- 
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] dspace indexing for create date not working

[Paul Warner]

Hi all,

ok, I am getting 2 hits for creation date.  I ran ./dspace index-discovery
a few days ago, and got no immediate results.  But now, after a couple of
days, I am getting partial results, 2 out 4 of my test examples.  They all
have creation dates in the metadata.  Why are only two showing up?

Best regards,
Paul

On Tue, Dec 5, 2017 at 11:37 AM, Paul Warner  wrote:

> Hi,
>
> I am running DSpace 6.1 on Suse 12.2 with Postgres.
>
> I need to index the creation date and other fields.  These fields exist in
> my test data, but even after I run dspace index-discovery, I get "There are
> no entries in the index" when I try the basic search on our list of
> concerts page.  Can someone give me a tip what I may be doing wrong?  The
> Author and Title fields are indexed, but the create date and key words
> fields are not.
>
> Thanks for any help!
>
> Best regards,
> Paul
>
> --
> 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/fm8gxmr_NTk/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.

[dspace-tech] dspace indexing for create date not working

[Paul Warner]

Hi,

I am running DSpace 6.1 on Suse 12.2 with Postgres.

I need to index the creation date and other fields.  These fields exist in 
my test data, but even after I run dspace index-discovery, I get "There are 
no entries in the index" when I try the basic search on our list of 
concerts page.  Can someone give me a tip what I may be doing wrong?  The 
Author and Title fields are indexed, but the create date and key words 
fields are not.

Thanks for any help!

Best regards,
Paul

-- 
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] custom permission level

[Paul Warner]

Thanks for this tip, Tim!  I will try out the metadata suggestion, and post
back how it worked out.

Best regards,
Paul

On Wed, Nov 29, 2017 at 9:56 PM, Tim Donohue  wrote:

> Hi Paul,
>
> Yes, what you've discovered is unfortunately true. It's not easy to
> override or customize DSpace permission levels without a lot of code
> changes.
>
> Your workaround seems reasonable.  Another possible workaround could be to
> have some sort of custom metadata field/value to designate items that are
> "streamable".  DSpace's metadata fields are quite easily customizable.  So,
> one could imagine a field like "local.streamable" = "true"  or
> "local.streamable" = "[Group Name]" (where Group Name is a DSpace Group who
> can stream it).  Then, you could check this metadata value(s) and/or the
> user's groups to see if they are allowed to stream a specific file/item.
>
> It's still obviously not ideal, as permissions don't really belong in
> metadata. But, it's something else to consider as a workaround.  (If you do
> go this route, I'd recommend creating a "local" metadata schema, or
> similar, and not using the default "dc" schema. That'd just ensure this
> field doesn't automatically appear in OAI-PMH or similar.)
>
> - Tim
>
> On Wed, Nov 29, 2017 at 7:37 AM Paul Warner  wrote:
>
>> Hi again,
>>
>> I found the answer to my question: it is basically, no.  The permissions
>> (they are called actions in the authorization process) for DSpace are
>> listed in the file dspace-api/src/main/java/org/dspace/core/Constants.java,
>> along with other constants of various types.  They are not in the
>> database.  So the code has to call for the field it needs directly from
>> Constants.  This means that in order to allow the head librarian in our
>> project to open up some files for streaming, we have to agree on some
>> combination of existing permissions values, and set them for that file, and
>> say that when the group is anonymous, and these permissions are set, then
>> the anonymous user can stream the audio file.
>>
>> If anyone has a better idea, please let me know.  Sigh.
>>
>> Thanks,
>> Paul
>>
>> On Fri, Nov 24, 2017 at 11:44 AM, Paul Warner 
>> wrote:
>>
>>> Hi,
>>>
>>> Can I add a custom permission level to the standard read, write, delete,
>>> etc. list?  I want to specify if anonymous users can stream an mp3 or all
>>> mp3's in an item, so 'stream' would be a likely name.
>>>
>>> I searched for the answer, but could not find it...
>>>
>>> Best regards,
>>> Paul
>>>
>> --
>>> 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/w0ln5Z_tsVg/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.
>>
> --
>
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>
>

-- 
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] custom permission level

[Paul Warner]

Hi again,

I found the answer to my question: it is basically, no.  The permissions
(they are called actions in the authorization process) for DSpace are
listed in the file dspace-api/src/main/java/org/dspace/core/Constants.java,
along with other constants of various types.  They are not in the
database.  So the code has to call for the field it needs directly from
Constants.  This means that in order to allow the head librarian in our
project to open up some files for streaming, we have to agree on some
combination of existing permissions values, and set them for that file, and
say that when the group is anonymous, and these permissions are set, then
the anonymous user can stream the audio file.

If anyone has a better idea, please let me know.  Sigh.

Thanks,
Paul

On Fri, Nov 24, 2017 at 11:44 AM, Paul Warner  wrote:

> Hi,
>
> Can I add a custom permission level to the standard read, write, delete,
> etc. list?  I want to specify if anonymous users can stream an mp3 or all
> mp3's in an item, so 'stream' would be a likely name.
>
> I searched for the answer, but could not find it...
>
> Best regards,
> Paul
>
> --
> 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/w0ln5Z_tsVg/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.

Re: [dspace-tech] dspace 6.1 delete community foreignkey-constraint community2community_child_comm_id_fkey

[Paul Warner]

Hi,

Just in case it helps someone, I ended up deleting the row in the
community2community table for each of the collections I needed to delete.
Then I could delete them from the admin interface.  I can confirm that
there does not seem to be any fallout from doing this, and now my site is
reorganized in the way the client wanted.

Here is a tip for anyone faced with this situation.  The uuid you need to
find the right row in the community2community table is a uuid, not a
string.  But you can still find it in postgresql by converting it to a
string and comparing it to the beginning of the uuid using like:

select * from community2community where child_comm_id::varchar like '06f%';
delete from community2community where child_comm_id::varchar like '06f%';

Best regards,
Paul

On Thu, Nov 23, 2017 at 10:39 AM, Paul Warner  wrote:

> Thanks for this, Terry.  That is exactly what I am doing.  I sign on to
> the web ui, in our case jspui, and try to delete the community.  I get an
> error message in the browser that there was a system error, and if it
> continues, I should contact the administrator.  When I look in the dspace
> log, I can see the exception about the foreign key constraint, etc.
>
> I should say, I deleted a few communities just before I tried this one,
> and they went away quietly, without error messages.  Then this community
> threw this error, and any other community deletions that I try now throw
> the same error.  I can see the entry for this community in the
> community2community table as the child of the top level community.
>
> Best regards,
> Paul
>
> On Wed, Nov 22, 2017 at 4:51 PM, Terry Brady 
> wrote:
>
>> This does not directly answer your question, but it might be helpful.
>>
>> I sign into the UI as a repository administrator when I want to delete
>> communities, collections, and items.  The code handles all of the
>> dependencies when deleting.
>>
>> On Wed, Nov 22, 2017 at 6:19 AM, Paul Warner 
>> wrote:
>>
>>> Hi all,
>>>
>>> I am running DSpace 6.1 on Suse.
>>>
>>> I have tried to delete a community I just created, since I found a
>>> different way to solve my organization problem.  I got an error that the
>>> update or delete in the table 'community' violates foreignkey-constraint
>>> 'community2community_child_comm_id_fkey' from the table
>>> 'community2community'.
>>>
>>> I have seen some posts from earlier versions of dspace saying that these
>>> constraints and even the tables themselves are no longer needed.  Should I
>>> be seeing this error then with DSpace 6.1?  I will alter or delete the
>>> tables if that is what I should do - but I just want to make sure that is
>>> still the right thing to do.  I presume it is irreversible, and I don't
>>> want to damage my installation.
>>>
>>> Thanks!
>>>
>>> Best regards,
>>> Paul
>>>
>>> --
>>> 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.
>>>
>>
>>
>>
>> --
>> Terry Brady
>> Applications Programmer Analyst
>> Georgetown University Library Information Technology
>> https://github.com/terrywbrady/info
>> 425-298-5498 <(425)%20298-5498> (Seattle, WA)
>>
>> --
>> 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/Ihb0hInEqFU/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.

[dspace-tech] custom permission level

[Paul Warner]

Hi,

Can I add a custom permission level to the standard read, write, delete, 
etc. list?  I want to specify if anonymous users can stream an mp3 or all 
mp3's in an item, so 'stream' would be a likely name.

I searched for the answer, but could not find it...

Best regards,
Paul

-- 
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] dspace 6.1 delete community foreignkey-constraint community2community_child_comm_id_fkey

[Paul Warner]

Thanks for this, Terry.  That is exactly what I am doing.  I sign on to the
web ui, in our case jspui, and try to delete the community.  I get an error
message in the browser that there was a system error, and if it continues,
I should contact the administrator.  When I look in the dspace log, I can
see the exception about the foreign key constraint, etc.

I should say, I deleted a few communities just before I tried this one, and
they went away quietly, without error messages.  Then this community threw
this error, and any other community deletions that I try now throw the same
error.  I can see the entry for this community in the community2community
table as the child of the top level community.

Best regards,
Paul

On Wed, Nov 22, 2017 at 4:51 PM, Terry Brady 
wrote:

> This does not directly answer your question, but it might be helpful.
>
> I sign into the UI as a repository administrator when I want to delete
> communities, collections, and items.  The code handles all of the
> dependencies when deleting.
>
> On Wed, Nov 22, 2017 at 6:19 AM, Paul Warner 
> wrote:
>
>> Hi all,
>>
>> I am running DSpace 6.1 on Suse.
>>
>> I have tried to delete a community I just created, since I found a
>> different way to solve my organization problem.  I got an error that the
>> update or delete in the table 'community' violates foreignkey-constraint
>> 'community2community_child_comm_id_fkey' from the table
>> 'community2community'.
>>
>> I have seen some posts from earlier versions of dspace saying that these
>> constraints and even the tables themselves are no longer needed.  Should I
>> be seeing this error then with DSpace 6.1?  I will alter or delete the
>> tables if that is what I should do - but I just want to make sure that is
>> still the right thing to do.  I presume it is irreversible, and I don't
>> want to damage my installation.
>>
>> Thanks!
>>
>> Best regards,
>> Paul
>>
>> --
>> 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.
>>
>
>
>
> --
> Terry Brady
> Applications Programmer Analyst
> Georgetown University Library Information Technology
> https://github.com/terrywbrady/info
> 425-298-5498 <(425)%20298-5498> (Seattle, WA)
>
> --
> 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/Ihb0hInEqFU/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.

[dspace-tech] dspace 6.1 delete community foreignkey-constraint community2community_child_comm_id_fkey

[Paul Warner]

Hi all,

I am running DSpace 6.1 on Suse.

I have tried to delete a community I just created, since I found a 
different way to solve my organization problem.  I got an error that the 
update or delete in the table 'community' violates foreignkey-constraint 
'community2community_child_comm_id_fkey' from the table 
'community2community'.

I have seen some posts from earlier versions of dspace saying that these 
constraints and even the tables themselves are no longer needed.  Should I 
be seeing this error then with DSpace 6.1?  I will alter or delete the 
tables if that is what I should do - but I just want to make sure that is 
still the right thing to do.  I presume it is irreversible, and I don't 
want to damage my installation.

Thanks!

Best regards,
Paul

-- 
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] full-text import via SAF

[Paul Warner]

Hey!

I seem to have found it, thanks to a post from Bill T on this list in 
2016.  He said the bundle TEXT is the one that gets indexed, so I tried 
that and it worked!  It indexed my ocr'd text.  The ocr program had a bit 
of a hard time with this text, and it converted Kirchenmusiker to 
Kuchenmumker.  :-)  So I searched for Kuchenmumker, knowing it would not 
appear anywhere else, and I got a hit on my latest import.  Juchuu!  :-)))

Thanks,
Paul

On Thursday, November 16, 2017 at 12:18:03 PM UTC+1, Paul Warner wrote:
>
> Hello Claudia and all,
>
> I have created a test import zip file, with the ocr'd text files listed as 
> \tbundle:FULLTEXT.  This text is not showing up in DSpace, which is 
> correct.  However, it seems it has not been indexed in Solr along with the 
> metadata.  So I can search successfully for things in the metadata, but 
> nothing shows up that is in the text files. By the way, I have page scans 
> as tif images that I am using ocr to read into text files.  That is why the 
> filter-media is not appropriate here.  So if I use EXTRACTEDTEXT for the 
> bundle name, will that then be read by Solr and thereby searchable?  Or is 
> there another step I am missing?
>
> Thanks!
>
> Paul Warner
>
> On Monday, November 6, 2017 at 9:18:49 AM UTC+1, Claudia Jürgen wrote:
>>
>> Hallo Paul, 
>>
>> you can do this by importing the text as extracted text. 
>> In SAF you can specify the bundle to which a file belongs with: 
>> \tbundle:BUNDLENAME 
>> assuming that the filter-media does not generate proper extracted text 
>> for the original files you got. 
>>
>> Hope this helps 
>>
>> Claudia Jürgen 
>>
>>
>> Am 06.11.2017 um 08:54 schrieb Paul Warner: 
>> > Hallo, 
>> > 
>> > We are converting scans of concert programs to text with OCR, and using 
>> > this for full text search in DSpace.  I have as an example imported the 
>> > text in a meta-data field, which is then displayed in our development 
>> > instance DSpace site with the other meta-data.  This works for 
>> full-text 
>> > search nicely, however, the text output from the OCR is often not 
>> > beautiful, and our client is, quite reasonably, objecting to having 
>> this 
>> > text so prominently displayed.  We are also setting up an automated 
>> import 
>> > process using the Simple Archive Format system.  I got the idea 
>> recently at 
>> > the Anwendertreffen in Stuttgart that one can import full text in the 
>> SAF 
>> > zip file, but unfortunately I did not follow up on it at that time to 
>> find 
>> > out exactly how that is accomplished, (or if I understood correctly 
>> that 
>> > this was possible). 
>> > 
>> > So my question:  Is it possible to import a full-text search text chunk 
>> > that will then be hidden from display?  Can one do this via the Simple 
>> > Archive Format process, or is there another way to do this, applying 
>> the 
>> > full-text search text to the imported item? 
>> > 
>> > Thanks for any help! 
>> > 
>> > Best regards, 
>> > Paul Warner 
>> > 
>>
>> -- 
>> 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. 
>>
>> Important note: The information included in this e-mail is confidential. 
>> It is solely intended for the recipient. If you are not the intended 
>> recipient of this e-mail please contact the sender and delete this message. 
>> Thank you. Without prejudice of e-mail correspondence, our statements are 
>> only legally binding when they are made in the conventional written form 
>> (with personal signature) or when such documents are sent by fax. 
>>
>

-- 
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] full-text import via SAF

[Paul Warner]

Hello Claudia and all,

I have created a test import zip file, with the ocr'd text files listed as 
\tbundle:FULLTEXT.  This text is not showing up in DSpace, which is 
correct.  However, it seems it has not been indexed in Solr along with the 
metadata.  So I can search successfully for things in the metadata, but 
nothing shows up that is in the text files. By the way, I have page scans 
as tif images that I am using ocr to read into text files.  That is why the 
filter-media is not appropriate here.  So if I use EXTRACTEDTEXT for the 
bundle name, will that then be read by Solr and thereby searchable?  Or is 
there another step I am missing?

Thanks!

Paul Warner

On Monday, November 6, 2017 at 9:18:49 AM UTC+1, Claudia Jürgen wrote:
>
> Hallo Paul, 
>
> you can do this by importing the text as extracted text. 
> In SAF you can specify the bundle to which a file belongs with: 
> \tbundle:BUNDLENAME 
> assuming that the filter-media does not generate proper extracted text 
> for the original files you got. 
>
> Hope this helps 
>
> Claudia Jürgen 
>
>
> Am 06.11.2017 um 08:54 schrieb Paul Warner: 
> > Hallo, 
> > 
> > We are converting scans of concert programs to text with OCR, and using 
> > this for full text search in DSpace.  I have as an example imported the 
> > text in a meta-data field, which is then displayed in our development 
> > instance DSpace site with the other meta-data.  This works for full-text 
> > search nicely, however, the text output from the OCR is often not 
> > beautiful, and our client is, quite reasonably, objecting to having this 
> > text so prominently displayed.  We are also setting up an automated 
> import 
> > process using the Simple Archive Format system.  I got the idea recently 
> at 
> > the Anwendertreffen in Stuttgart that one can import full text in the 
> SAF 
> > zip file, but unfortunately I did not follow up on it at that time to 
> find 
> > out exactly how that is accomplished, (or if I understood correctly that 
> > this was possible). 
> > 
> > So my question:  Is it possible to import a full-text search text chunk 
> > that will then be hidden from display?  Can one do this via the Simple 
> > Archive Format process, or is there another way to do this, applying the 
> > full-text search text to the imported item? 
> > 
> > Thanks for any help! 
> > 
> > Best regards, 
> > Paul Warner 
> > 
>
> -- 
> 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. 
>
> Important note: The information included in this e-mail is confidential. 
> It is solely intended for the recipient. If you are not the intended 
> recipient of this e-mail please contact the sender and delete this message. 
> Thank you. Without prejudice of e-mail correspondence, our statements are 
> only legally binding when they are made in the conventional written form 
> (with personal signature) or when such documents are sent by fax. 
>

-- 
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] full-text import via SAF

[Paul Warner]

Hallo,

We are converting scans of concert programs to text with OCR, and using 
this for full text search in DSpace.  I have as an example imported the 
text in a meta-data field, which is then displayed in our development 
instance DSpace site with the other meta-data.  This works for full-text 
search nicely, however, the text output from the OCR is often not 
beautiful, and our client is, quite reasonably, objecting to having this 
text so prominently displayed.  We are also setting up an automated import 
process using the Simple Archive Format system.  I got the idea recently at 
the Anwendertreffen in Stuttgart that one can import full text in the SAF 
zip file, but unfortunately I did not follow up on it at that time to find 
out exactly how that is accomplished, (or if I understood correctly that 
this was possible).

So my question:  Is it possible to import a full-text search text chunk 
that will then be hidden from display?  Can one do this via the Simple 
Archive Format process, or is there another way to do this, applying the 
full-text search text to the imported item?

Thanks for any help!

Best regards,
Paul Warner

-- 
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: jspui language switcher top menu bar links to localhost

[Paul Warner]

Dear Claudia,

Brilliant, thank you! I see I should have found this myself...

So, here is the problem.  On line 133, the links for the Language menu item
are set using the variable currentPage, which on my system has the value
localhost:8080.  All other links (href) are set using
request.getContextPath().
I switched this line to request.getContextPath(), and now it works fine.

currentPage is set on line 49:

String currentPage = UIUtil.getOriginalURL(request);

In UIUtil.java, getOriginalURL(request) returns
request.getAttribute("dspace.original.url").

public static String getOriginalURL(HttpServletRequest request)
{
initialize();

// Make sure there's a URL in the
attribute

storeOriginalURL(request);

return ((String) request.getAttribute("dspace.original.url"));
}


Should this be noted as a bug?

Best regards,
Paul

On Wed, Oct 11, 2017 at 10:43 AM, Claudia Jürgen <
claudia.juer...@tu-dortmund.de> wrote:

> Hello Paul,
>
> the link is set here:
> https://github.com/DSpace/DSpace/blob/dspace-6.1/dspace-jspu
> i/src/main/webapp/layout/navbar-default.jsp#L133
>
> Hope this helps
>
> Claudia Jürgen
>
>
>
> Am 11.10.2017 um 09:58 schrieb Paul Warner:
>
>> I am on using dspace 6.1, tomcat 8, apache 2.4, Suse 12.2.
>>
>> On Wednesday, October 11, 2017 at 9:55:10 AM UTC+2, Paul Warner wrote:
>>
>>> Hi all,
>>>
>>> In my dspace, in the top menu bar, by the Language/Sprache dropdown, the
>>> links refer to 'localhost', and not to my site's domain name.  All the
>>> other links link correctly to my site's domain name.  Anyone have an idea
>>> where this language link gets set, and how I could fix it?
>>>
>>> I recently set Apache in front of Tomcat, using Apaches ProxyPass and
>>> ProxyPassReverse modules.  This change to getting localhost with the
>>> Language dropdown seems to have appeared about the time I made the
>>> changeover to Apache.
>>>
>>> ProxyPass /jspui  http://localhost:8080/jspui
>>> ProxyPassReverse  /jspui  http://localhost:8080/jspui
>>>
>>> I set Tomcat to listen only on localhost and to pick up Apache's
>>> x-forwarded-for header:
>>>
>>> >>  unpackWARs="true" autoDeploy="true">
>>>
>>>  >> directory="logs"
>>> prefix="localhost_access_log" suffix=".txt"
>>> pattern="%h %l %u %t "%r" %s %b" />
>>>  >> remoteIpHeader="x-forwarded-for"
>>> />
>>>  >> allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1"/>
>>>
>>>
>>> I am using IPAuthentication and PasswordAuthentication, and the
>>> IPAuthentication picks up the x-forwarded-for correctly, and so does the
>>> log.  I am wondering if the Language setting looks at the incoming IP
>>> address, and thereby determines which language to use.  If the IP address
>>> is coming in localhost or empty, then perhaps that is why I am getting
>>> localhost in this menu link.  But I have not been able to find where this
>>> link gets set.
>>>
>>> Thanks for any help.
>>>
>>> Best regards,
>>> Paul
>>>
>>>
>>>
> --
> 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.juer...@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.
>
> Important note: The information included in this e-mail is confidential.
> It is solely intended for the recipient. If you are not the intended
> recipient of this e-mail please contact the sender and delete this message.
> Thank you. Without prejudice of e-mail correspondence, our statements are
> only legally binding when they are made in the conventional written form
> (with personal signature) or when such doc

[dspace-tech] Re: jspui language switcher top menu bar links to localhost

[Paul Warner]

One more thing, the link shows localhost:8080, and with Apache, I am using 
SSL/TLS on port 443.  So there should be no port visible.  It sounds like 
an old configuration holdover, but in my dspace.cfg and local.cfg, the only 
references to localhost are for solr and postgresql.

Thanks,
Paul

On Wednesday, October 11, 2017 at 9:58:38 AM UTC+2, Paul Warner wrote:
>
> I am on using dspace 6.1, tomcat 8, apache 2.4, Suse 12.2.
>
> On Wednesday, October 11, 2017 at 9:55:10 AM UTC+2, Paul Warner wrote:
>>
>> Hi all,
>>
>> In my dspace, in the top menu bar, by the Language/Sprache dropdown, the 
>> links refer to 'localhost', and not to my site's domain name.  All the 
>> other links link correctly to my site's domain name.  Anyone have an idea 
>> where this language link gets set, and how I could fix it?
>>
>> I recently set Apache in front of Tomcat, using Apaches ProxyPass and 
>> ProxyPassReverse modules.  This change to getting localhost with the 
>> Language dropdown seems to have appeared about the time I made the 
>> changeover to Apache.
>>
>> ProxyPass /jspui  http://localhost:8080/jspui
>> ProxyPassReverse  /jspui  http://localhost:8080/jspui
>>
>> I set Tomcat to listen only on localhost and to pick up Apache's 
>> x-forwarded-for header:
>>
>> > unpackWARs="true" autoDeploy="true">
>>
>> > directory="logs"
>>prefix="localhost_access_log" suffix=".txt"
>>pattern="%h %l %u %t "%r" %s %b" />
>> >remoteIpHeader="x-forwarded-for"
>>/>
>> >allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1"/>
>>   
>>
>> I am using IPAuthentication and PasswordAuthentication, and the 
>> IPAuthentication picks up the x-forwarded-for correctly, and so does the 
>> log.  I am wondering if the Language setting looks at the incoming IP 
>> address, and thereby determines which language to use.  If the IP address 
>> is coming in localhost or empty, then perhaps that is why I am getting 
>> localhost in this menu link.  But I have not been able to find where this 
>> link gets set.
>>
>> Thanks for any help.
>>
>> Best regards,
>> Paul
>>
>>

-- 
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: jspui language switcher top menu bar links to localhost

[Paul Warner]

I am on using dspace 6.1, tomcat 8, apache 2.4, Suse 12.2.

On Wednesday, October 11, 2017 at 9:55:10 AM UTC+2, Paul Warner wrote:
>
> Hi all,
>
> In my dspace, in the top menu bar, by the Language/Sprache dropdown, the 
> links refer to 'localhost', and not to my site's domain name.  All the 
> other links link correctly to my site's domain name.  Anyone have an idea 
> where this language link gets set, and how I could fix it?
>
> I recently set Apache in front of Tomcat, using Apaches ProxyPass and 
> ProxyPassReverse modules.  This change to getting localhost with the 
> Language dropdown seems to have appeared about the time I made the 
> changeover to Apache.
>
> ProxyPass /jspui  http://localhost:8080/jspui
> ProxyPassReverse  /jspui  http://localhost:8080/jspui
>
> I set Tomcat to listen only on localhost and to pick up Apache's 
> x-forwarded-for header:
>
>  unpackWARs="true" autoDeploy="true">
>
>  directory="logs"
>prefix="localhost_access_log" suffix=".txt"
>pattern="%h %l %u %t "%r" %s %b" />
> remoteIpHeader="x-forwarded-for"
>/>
> allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1"/>
>   
>
> I am using IPAuthentication and PasswordAuthentication, and the 
> IPAuthentication picks up the x-forwarded-for correctly, and so does the 
> log.  I am wondering if the Language setting looks at the incoming IP 
> address, and thereby determines which language to use.  If the IP address 
> is coming in localhost or empty, then perhaps that is why I am getting 
> localhost in this menu link.  But I have not been able to find where this 
> link gets set.
>
> Thanks for any help.
>
> Best regards,
> Paul
>
>

-- 
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] jspui language switcher top menu bar links to localhost

[Paul Warner]

Hi all,

In my dspace, in the top menu bar, by the Language/Sprache dropdown, the 
links refer to 'localhost', and not to my site's domain name.  All the 
other links link correctly to my site's domain name.  Anyone have an idea 
where this language link gets set, and how I could fix it?

I recently set Apache in front of Tomcat, using Apaches ProxyPass and 
ProxyPassReverse modules.  This change to getting localhost with the 
Language dropdown seems to have appeared about the time I made the 
changeover to Apache.

ProxyPass /jspui  http://localhost:8080/jspui
ProxyPassReverse  /jspui  http://localhost:8080/jspui

I set Tomcat to listen only on localhost and to pick up Apache's 
x-forwarded-for header:






  

I am using IPAuthentication and PasswordAuthentication, and the 
IPAuthentication picks up the x-forwarded-for correctly, and so does the 
log.  I am wondering if the Language setting looks at the incoming IP 
address, and thereby determines which language to use.  If the IP address 
is coming in localhost or empty, then perhaps that is why I am getting 
localhost in this menu link.  But I have not been able to find where this 
link gets set.

Thanks for any help.

Best regards,
Paul

-- 
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] ip authentication, how do I log in?

[Paul Warner]

Dear Tim,

Thanks for your reply.  What you describe is exactly what we need.  I can
see my use of the phrase 'logging in' was misleading.  I have everything
set up to verify ip authentication/authorization, as far as I know.  But
when I come to my dspace in the browser, and it is clear from the log that
dspace knows the ip address, and it matches what is in
authentication-ip.cfg, it still does not put the user in the desired group
or give the user permission to listen to the audio files.  It sounds, from
your email, that this is supposed to just work, one does not need to do
anything more than come to the site from the designated ip address, in
order to have access to the files.

Originally I thought that perhaps the authentication module was not getting
the right ip address, since I am using apache in front of tomcat, but then
I found that the module has this built in, when you uncomment useProxies =
true in the dspace.cfg.  And having done that, I can see the ip in the
dspace log file.  But the user still does not land in the right group...

Best regards,
Paul


On Tue, Oct 3, 2017 at 4:21 PM, Tim Donohue  wrote:

> Hi Paul,
>
> IP Authentication is a slight misnomer.  It's not truly *authentication*
> but rather *authorization*.  So, you don't need to login at all, but you
> are provided specific access rights based on your IP address.
>
> So, the point of IP Auth is that you are essentially "mapping" specific IP
> addresses or ranges to specific DSpace Groups.  Anyone who accesses your
> site from those IP addresses (even anonymously) will be added to that
> DSpace Group for the remainder of their session.  You can then use that
> DSpace Group to assign those users specific access rights.
>
> One example use case for IP Auth is to provide access to all University
> Theses & Dissertations while on campus (or while in the University
> Library).  In such a scenario, the Theses & Dissertations may be access
> restricted to downloading/viewing to the general public, but if a user
> visits your site from an on-campus IP address, they can download/view the
> files without logging in.
>
> I hope that helps clarify the purpose of IP Auth!
>
> Tim
>
> On Mon, Oct 2, 2017 at 5:11 AM Paul Warner  wrote:
>
>> Hi,
>>
>> I have set up ip authentication using apache as a proxy front end for
>> tomcat. The log is seeing the ip address, so it is being correctly passed
>> through from apache to tomcat, and correctly read by dspace.  But it is not
>> logging me in to the group.  My question is, how do I log in?  If I have ip
>> authentication stacked with password authentication, when I click the login
>> button in the top menu on the jspui, I go to the password login page.  If I
>> remove password login from the list in authentication.cfg and have only ip
>> authentication, then when I click the login button I get a page with no
>> form elements at all, nothing.  And, as I said, I am not being logged in to
>> the group automatically.
>>
>> Thanks for any hints or tips!
>>
>> Best regards,
>> Paul
>>
>> dspace 6.1 on Suse 12.2, tomcat 8 and apache 2.4.23
>>
>> Here is the log entry:
>>
>> 2017-10-02 11:55:00,242 INFO  org.dspace.usage.LoggerUsageEventListener
>> @ anonymous:session_id=50601B9E86D5FEC0FC1173927BAF8DA6:ip_addr=1.2.3.4:
>> view_item:handle=123456789/46
>>
>> I have configured dspace so:
>>
>> from dspace.cfg
>>
>>  Proxy Settings ##
>>
>>
>> # uncomment and specify both properties if proxy server
>> required
>>
>> # proxy server for external http requests - use regular hostname without
>> port number
>>
>> http.proxy.host = localhost
>>
>> # port number of proxy server
>>
>>
>> http.proxy.port = 443
>>
>> # If enabled, the logging and the Solr statistics system will look
>> for
>>
>> # an X-Forwarded-For header. If it finds it, it will use this for the
>> user IP address
>>
>> useProxies = true
>>
>> from authentication.cfg
>>
>> plugin.sequence.org.dspace.authenticate.AuthenticationMethod =
>> org.dspace.authenticate.IPAuthentication,org.dspace.authenticate.
>> PasswordAuthentication
>>
>> from authentication-ip.cfg
>>
>> authentication-ip.Hochschule_Bibliothek = 1.2.3.4
>>
>> --
>> 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 dspa

Re: [dspace-tech] passing ssl client certificate from Apache to Dspace

[Paul Warner]

Hi Tim,

I just wanted to acknowledge your kind responses, and let you know that my
boss decided we should not use x.509 certificate authentication for this
project.  We are looking to set up a self-sustaining system, or when it is
not self-sustaining, at least most of the work should fall on the client,
and not on us. We are providing a, so far, free service for them.
Maintaining certificates on the clients' machines was a step too far for
him.  I have pieced together some understanding of this subject, and if I
get the time to wrap it up, I will volunteer to help improve the
documentation and tell my story.  There is very little on the web about
this, and it seems the technique is very rarely used.

We are switching to ip authentication for dspace, and now I am struggling
with that!  ;-)

Best regards,
Paul


Tim Donohue  schrieb am Fr. 8. Sep. 2017 um 16:57:

> Hi Paul,
>
> Again, I admit I've not really used this myself :)
>
> That said, Googling that error message ("FAILED SIGNATURE check
> java.security.SignatureException Signature does not match")  brought up
> this StackOverflow answer which might be applicable:
> https://stackoverflow.com/a/38524172/3750035
>
> Hoping maybe that'll get you one step further.  Admittedly, when
> encountered with oddities like this myself, I jump to googling to error, as
> oftentimes some clues can be found out there in StackOverflow and similar.
>
> Assuming you get this working, I'd also encourage you to consider helping
> us correct/enhance our official documentation around X.509 Certificate
> Authorization (I'll gladly give you edit rights if you are willing).  I
> suspect this documentation is simply lacking / unclear, and enhancing it
> could help others who may follow in your footsteps.
>
> Good luck, and definitely feel free to keep posting your status & other
> errors you come across (and we'll do our best to help find/suggestion
> solutions). At the very least, it will be helpful for others in the future
> (when searching these lists).
>
> Tim
>
>
> On Fri, Sep 8, 2017 at 1:19 AM Paul Warner  wrote:
>
>> Hi Tim,
>>
>> Thanks for the help!  I made two mistakes, and fixed them, following your
>> suggestions, but I am unfortunately still not connecting from Apache to
>> Dspace, although it is now clear the certificate information is being
>> passed through..
>>
>> First, I was using an outdated format for the listing of the two kinds of
>> authentication in authentication.cfg, and your pointer to the 6 version was
>> helpful there.  I had them on the same line, with a comma.  Now they are
>> loading sequentially, with the certificate auth loading first.  I also was
>> not looking at the right log file, duh.  Now I can see some error messages,
>> and can tell that Dspace is grappling with the client certificate, although
>> still failing to validate it.  I tried all variations of the instructions
>> for configuring the authentication-x509.cfg file, but in the end I am
>> getting:
>>
>> 2017-09-08 08:02:34,351 INFO  org.dspace.authenticate.X509Authentication
>> @ anonymous:session_id=EF3D87F4E30DDB194B8C9DCCF2AD45
>> 25:ip_addr=141.2.34.31:authentication:X.509 Certificate FAILED SIGNATURE
>> check\colon; java.security.SignatureException\colon; Signature does not
>> match.
>> 2017-09-08 08:02:34,351 WARN  org.dspace.authenticate.X509Authentication
>> @ anonymous:session_id=EF3D87F4E30DDB194B8C9DCCF2AD45
>> 25:ip_addr=141.2.34.31:authenticate:type=x509certificate,
>> status=BAD_CREDENTIALS (not valid)
>>
>> I installed the client.p12 file in the browser, and the client.pem file
>> in Dspace, using the keystore with the correct password.  I produced my
>> files using these wonderful instructions:
>>
>> https://gist.github.com/mtigas/952344
>>
>> Sorry, still mystified.
>>
>> Best regards,
>> Paul
>>
>> On Thu, Sep 7, 2017 at 6:55 PM, Tim Donohue 
>> wrote:
>>
>>> Hi Paul,
>>>
>>> I'll admit, I've never used the X.509 cert auth myself, but I notice
>>> there are some more notes in the X.509 docs at:
>>> https://wiki.duraspace.org/display/DSDOC6x/Authentication+Plugins#
>>> AuthenticationPlugins-X.509CertificateAuthentication
>>>
>>> Namely, I see that it states:
>>> "If you are using HTTPS with Tomcat, note that the  tag
>>> *must* include the attribute clientAuth="true" so the server requests a
>>> personal Web certificate from the client."
>>>
>>> Not sure if that's the problem here, but you might want to carefully
>>> review the

[dspace-tech] ip authentication, how do I log in?

[Paul Warner]

Hi,

I have set up ip authentication using apache as a proxy front end for 
tomcat. The log is seeing the ip address, so it is being correctly passed 
through from apache to tomcat, and correctly read by dspace.  But it is not 
logging me in to the group.  My question is, how do I log in?  If I have ip 
authentication stacked with password authentication, when I click the login 
button in the top menu on the jspui, I go to the password login page.  If I 
remove password login from the list in authentication.cfg and have only ip 
authentication, then when I click the login button I get a page with no 
form elements at all, nothing.  And, as I said, I am not being logged in to 
the group automatically.

Thanks for any hints or tips!

Best regards,
Paul

dspace 6.1 on Suse 12.2, tomcat 8 and apache 2.4.23

Here is the log entry:

2017-10-02 11:55:00,242 INFO  org.dspace.usage.LoggerUsageEventListener @ 
anonymous:session_id=50601B9E86D5FEC0FC1173927BAF8DA6:ip_addr=1.2.3.4:view_item:handle=123456789/46

I have configured dspace so:

from dspace.cfg

 Proxy Settings 
##  
   

# uncomment and specify both properties if proxy server 
required
   

# proxy server for external http requests - use regular hostname without 
port 
number  
 

http.proxy.host = localhost

# port number of proxy 
server  


http.proxy.port = 443

# If enabled, the logging and the Solr statistics system will look 
for 


# an X-Forwarded-For header. If it finds it, it will use this for the user 
IP 
address 
 

useProxies = true

from authentication.cfg

plugin.sequence.org.dspace.authenticate.AuthenticationMethod = 
org.dspace.authenticate.IPAuthentication,org.dspace.authenticate.PasswordAuthentication

from authentication-ip.cfg

authentication-ip.Hochschule_Bibliothek = 1.2.3.4

-- 
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] changes to ItemTag.java not showing up

[Paul Warner]

Hello Claudia,

Thanks very much for your reply!  Your link saved me - I had forgotten that 
there are two levels for the "mvn package" command: dspace-src and 
dspace-src/dspace.  The first gives you a full build, and the second a 
quick build.  I was always using the quick build option, not realizing that 
it would not recompile my java files.  The full build option, running mvn 
package from dspace-src, was the answer.

I tried using the overlay, but setting a java file in an empty directory 
tree created problems for the compiler:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile 
(default-compile) on project jspui: Compilation failure: Compilation 
failure:
[ERROR] 
/opt/dspace/dspace-6.1-src-hfmdk/dspace/modules/jspui/src/main/java/org/dspace/app/webui/jsptag/ItemTag.java:[24,25]
 
package javax.servlet.jsp does not exist
[ERROR] 
/opt/dspace/dspace-6.1-src-hfmdk/dspace/modules/jspui/src/main/java/org/dspace/app/webui/jsptag/ItemTag.java:[25,25]
 
package javax.servlet.jsp does not exist
[ERROR] 
/opt/dspace/dspace-6.1-src-hfmdk/dspace/modules/jspui/src/main/java/org/dspace/app/webui/jsptag/ItemTag.java:[27,32]
 
package javax.servlet.jsp.tagext does not exist
[ERROR] 
/opt/dspace/dspace-6.1-src-hfmdk/dspace/modules/jspui/src/main/java/org/dspace/app/webui/jsptag/ItemTag.java:[199,30]
 
cannot find symbol

etc.

The overlay option seems to be for jsp files and configuration files, which 
I am using.  Is that correct?

Best regards,
Paul

On Tuesday, September 12, 2017 at 10:24:57 AM UTC+2, Claudia Jürgen wrote:
>
> Hello Paul, 
>
> did you alsready make an overlay at some point, i.e. copying the file to 
> [dspace-source]/dspace/modules/addditions ... 
> as described in 
> https://wiki.duraspace.org/display/DSDOC6x/Advanced+Customisation 
> There you should do your customizations. 
> And this will be used, if present, and not the dspace-jspui/src/main ... 
> one. 
>
> Hope this helps 
>
> Claudia Jürgen 
>
>
>
> Am 12.09.2017 um 10:01 schrieb Paul Warner: 
> > Dear Support, 
> > 
> > I need to make some small changes to the way an item is displayed, and I 
> > have 
> > edited 
> dspace-jspui/src/main/java/org/dspace/app/webui/jsptag/ItemTag.java. 
> >   I ran mvn package, and ant update, and copied the files into Tomcat. 
>  But 
> > none of my changes are appearing.  Why not? 
> > 
> > Thanks, 
> > Paul 
> > 
>
> -- 
> 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. 
>
> Important note: The information included in this e-mail is confidential. 
> It is solely intended for the recipient. If you are not the intended 
> recipient of this e-mail please contact the sender and delete this message. 
> Thank you. Without prejudice of e-mail correspondence, our statements are 
> only legally binding when they are made in the conventional written form 
> (with personal signature) or when such documents are sent by fax. 
>

-- 
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: changes to ItemTag.java not showing up

[Paul Warner]

Sorry, forgot to add version info:  I am running Dspace 6.1 on Suse 12.2.

Thanks!
Paul

On Tuesday, September 12, 2017 at 10:01:24 AM UTC+2, Paul Warner wrote:
>
> Dear Support,
>
> I need to make some small changes to the way an item is displayed, and I 
> have 
> edited dspace-jspui/src/main/java/org/dspace/app/webui/jsptag/ItemTag.java. 
>  I ran mvn package, and ant update, and copied the files into Tomcat.  But 
> none of my changes are appearing.  Why not?
>
> Thanks,
> Paul
>

-- 
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] changes to ItemTag.java not showing up

[Paul Warner]

Dear Support,

I need to make some small changes to the way an item is displayed, and I 
have 
edited dspace-jspui/src/main/java/org/dspace/app/webui/jsptag/ItemTag.java. 
 I ran mvn package, and ant update, and copied the files into Tomcat.  But 
none of my changes are appearing.  Why not?

Thanks,
Paul

-- 
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] WITHDRAWN_READ for .wav files based on user group

[Paul Warner]

Hi,

Our client is a music school library which needs to archive audio files of 
concerts.  These concerts contain some music that cannot legally be 
available for downloading or streaming, except if one is in the library.  
So how can I set WITHDRAWN_READ access for these audio files for all users 
outside of a certain group?  I know I can set WITHDRAWN_READ for each 
individual file based on the group in the admin user interface, but I would 
like to set a policy site-wide for all files with a certain extension 
(.wav, .mp3, .mp4, etc). 

Thanks for any pointers!

-Paul

-- 
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] passing ssl client certificate from Apache to Dspace

[Paul Warner]

Hi Tim,

Thanks for the help!  I made two mistakes, and fixed them, following your
suggestions, but I am unfortunately still not connecting from Apache to
Dspace, although it is now clear the certificate information is being
passed through..

First, I was using an outdated format for the listing of the two kinds of
authentication in authentication.cfg, and your pointer to the 6 version was
helpful there.  I had them on the same line, with a comma.  Now they are
loading sequentially, with the certificate auth loading first.  I also was
not looking at the right log file, duh.  Now I can see some error messages,
and can tell that Dspace is grappling with the client certificate, although
still failing to validate it.  I tried all variations of the instructions
for configuring the authentication-x509.cfg file, but in the end I am
getting:

2017-09-08 08:02:34,351 INFO  org.dspace.authenticate.X509Authentication @
anonymous:session_id=EF3D87F4E30DDB194B8C9DCCF2AD4525:ip_addr=141.2.34.31:authentication:X.509
Certificate FAILED SIGNATURE check\colon;
java.security.SignatureException\colon; Signature does not match.
2017-09-08 08:02:34,351 WARN  org.dspace.authenticate.X509Authentication @
anonymous:session_id=EF3D87F4E30DDB194B8C9DCCF2AD4525:ip_addr=141.2.34.31:authenticate:type=x509certificate,
status=BAD_CREDENTIALS (not valid)

I installed the client.p12 file in the browser, and the client.pem file in
Dspace, using the keystore with the correct password.  I produced my files
using these wonderful instructions:

https://gist.github.com/mtigas/952344

Sorry, still mystified.

Best regards,
Paul

On Thu, Sep 7, 2017 at 6:55 PM, Tim Donohue  wrote:

> Hi Paul,
>
> I'll admit, I've never used the X.509 cert auth myself, but I notice there
> are some more notes in the X.509 docs at:
> https://wiki.duraspace.org/display/DSDOC6x/Authentication+Plugins#
> AuthenticationPlugins-X.509CertificateAuthentication
>
> Namely, I see that it states:
> "If you are using HTTPS with Tomcat, note that the  tag *must* 
> include
> the attribute clientAuth="true" so the server requests a personal Web
> certificate from the client."
>
> Not sure if that's the problem here, but you might want to carefully
> review the instructions here again. If you are still hitting issues, you
> also should check your logs to see if there's any errors being logged
> there, see https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error
>
>
> - Tim
>
> On Thu, Sep 7, 2017 at 7:25 AM Paul Warner  wrote:
>
>> Hi,
>>
>> I have configured Apache with ssl using a self-signed certificate, and
>> then generated a client certificate from the server certificate.  With
>> SSLVerifyClient set to 'require', I can get to Dspace only from a browser
>> with the client certificate installed.  So it works!
>>
>> But getting Dspace to recognize the certificate is my problem. When I try
>> to login with the certificate, at https://myserver/jspui/
>> certificate-login, I get the message: 'You do not seem to have a valid
>> Web certificate.'   I am running Apache 2.4.18, Apache Tomcat/8.5.15, and
>> Dspace 6.1 on Ubuntu 16.04.
>>
>> In my apache conf, I have SSLOptions StdEnvVars ExportCertData.
>>
>> I loaded my client.crt certificate into the tomcat keystore, following
>> the directions in https://wiki.duraspace.org/display/DSDOC6x/Installing+
>> DSpace:
>>
>> Optional – ONLY if you need to accept client certificates for the X.509
>> certificate stackable authentication module See the configuration section
>> for instructions on enabling the X.509 authentication method. Load the
>> keystore with the CA (certifying authority) certificates for the
>> authorities of any clients whose certificates you wish to accept. For
>> example, assuming the client CA certificate is in *client1.pem*:
>>
>>
>> $JAVA_HOME/bin/keytool -import -noprompt -storepass changeit
>> -trustcacerts -keystore $CATALINA_BASE/conf/keystore  -alias client1
>> -file client1.pem
>>
>> I have set authentication.cfg so it includes X509 authentication:
>>
>> plugin.sequence.org.dspace.authenticate.AuthenticationMethod =
>> org.dspace.authenticate.PasswordAuthentication,org.dspace.authenticate.
>> X509Authentication
>>
>> I have set authentication-x509.cfg to include the keystore and password:
>>
>> authentication-x509.keystore.path = /opt/tomcat/conf/keystore
>> authentication-x509.keystore.password = changeit
>>
>> What am I missing?
>>
>> Thanks,
>> Paul
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "D

[dspace-tech] passing ssl client certificate from Apache to Dspace

[Paul Warner]

Hi,

I have configured Apache with ssl using a self-signed certificate, and then 
generated a client certificate from the server certificate.  With 
SSLVerifyClient set to 'require', I can get to Dspace only from a browser 
with the client certificate installed.  So it works!

But getting Dspace to recognize the certificate is my problem. When I try 
to login with the certificate, at https://myserver/jspui/certificate-login, 
I get the message: 'You do not seem to have a valid Web certificate.'   I 
am running Apache 2.4.18, Apache Tomcat/8.5.15, and Dspace 6.1 on Ubuntu 
16.04.

In my apache conf, I have SSLOptions StdEnvVars ExportCertData.

I loaded my client.crt certificate into the tomcat keystore, following the 
directions in https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace:

Optional – ONLY if you need to accept client certificates for the X.509 
certificate stackable authentication module See the configuration section 
for instructions on enabling the X.509 authentication method. Load the 
keystore with the CA (certifying authority) certificates for the 
authorities of any clients whose certificates you wish to accept. For 
example, assuming the client CA certificate is in *client1.pem*:


$JAVA_HOME/bin/keytool -import -noprompt -storepass changeit
-trustcacerts -keystore $CATALINA_BASE/conf/keystore  -alias client1
-file client1.pem

I have set authentication.cfg so it includes X509 authentication:

plugin.sequence.org.dspace.authenticate.AuthenticationMethod = 
org.dspace.authenticate.PasswordAuthentication,org.dspace.authenticate.X509Authentication

I have set authentication-x509.cfg to include the keystore and password:

authentication-x509.keystore.path = /opt/tomcat/conf/keystore
authentication-x509.keystore.password = changeit

What am I missing?

Thanks,
Paul



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