[dspace-tech] Re: DSpace 7.1 - Can't Log In
See my other post, "SSL between Angular and REST" to find out how this was
resolved.
On Wednesday, December 22, 2021 at 4:10:14 PM UTC-6 Glenn G wrote:
> I found the information at the following link, and will continue once I
> have some other things sorted out.
>
>
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
>
> On Wednesday, December 22, 2021 at 3:30:35 PM UTC-6 Glenn G wrote:
>
>> More information from Chrome developer tools:
>>
>> {"timestamp":"2021-12-22T21:13:29.565+00:00","status":403,"error":"Forbidden","message":"Access
>>
>> is denied. Invalid CSRF token.","path":"/server/api/eperson/registrations"}
>>
>> On Tuesday, December 21, 2021 at 11:55:28 AM UTC-6 Glenn G wrote:
>>
>>> So I finally got this DSpace 7.1 sorta working, but it won't let me log
>>> in through the user interface. If I enter my email address and password, a
>>> pink balloon appears with the message: "Invalid email or password." Chrome
>>> developer tools says, "zone-evergreen.js:2845 POST
>>> https://d7test.ourschool.edu/server/api/authn/login 403".
>>>
>>> If I try to register as a new user, a pink error balloon pops up for
>>> several seconds. It says, "Error when trying to register email
>>> An error occured when registering the following email address: ..."
>>>
>>> The same thing happens if I choose "Have you forgotten your password?"
>>>
>>> For these actions, Chrome developer tools says, "zone-evergreen.js:2845
>>> POST https://d7test.ourschool.edu/server/api/eperson/registrations 403"
>>>
>>> Depending on the action, the Tomcat log says, "'POST
>>> /server/api/authn/login HTTP/1.1' 403" or 'POST
>>> /server/api/eperson/registrations HTTP/1.1' 403".
>>>
>>> DSpace is configured to use only password authentication. These are
>>> some of the possibly relevant settings I'm using in
>>> [dspace]/config/local.cfg:
>>>
>>> dspace.server.url = https://d7test.ourschool.edu/server
>>> dspace.ui.url = https://d7test.ourschool.edu
>>> authentication-password.domain.valid = ourschool.edu
>>> rest.cors.allowed-origins = ${dspace.ui.url}, http://127.0.0.1
>>> proxies.trusted.ipranges = 127.0.0.1,172.31.
>>> plugin.sequence.org.dspace.authenticate.AuthenticationMethod =
>>> org.dspace.authenticate.PasswordAuthentication
>>> rest.cors.allowed-origins = ${dspace.ui.url}, http://127.0.0.1,
>>> http://localhost:4000, http://172.31.57.198:4000, https://127.0.0.1,
>>> https://localhost:4000, https://172.31.57.198:4000
>>>
>>> My OS is Ubuntu 20.04 LTS. All my DSpace backend files are owned by
>>> tomcat:tomcat. The Angular files are owned by dspace:dspace. This is a
>>> single-server setup.
>>>
>>> What should I look at next?
>>>
>>> Thanks,
>>> Glenn
>>>
>>
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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/fb0dcd21-cdcc-4303-b747-1ec168a8d779n%40googlegroups.com.
[dspace-tech] Re: SSL between Angular and REST
It seems that since my setup uses Apache as a proxy, Apache does the SSL
work between the front end and back end. Other web servers I manage are
happy enough to have only the server certificate and the root certificate
designated in the Apache configuration. For DSpace 7.1, I found that the
chain certificate was also needed. Once that was in place, "yarn
config:check:rest" gave a more promising response, and I was able to
configure environment.prod.ts as shown below. After re-running "yarn run
build:prod", the server works, and I am able to log in.
environment.prod.ts
export const environment = {
ui: {
ssl: false,
host: 'localhost',
port: 4000,
nameSpace: '/'
},
rest: {
ssl: true,
host: 'test.ourschool.edu',
port: 443,
nameSpace: '/server',
},
};
On Thursday, December 23, 2021 at 11:32:49 AM UTC-6 Glenn G wrote:
> Following the DSpace 7.1 installation guide here,
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace, I am unable
> to proceed past step 4.a. When I run "yarn config:check:rest", it produces
> this error message:
>
> ERROR connecting to REST API
> Error: write EPROTO 140676344637312:error:1408F10B:SSL
> routines:ssl3_get_record:wrong version
> number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
>
> My environment.prod.ts:
>
> export const environment = {
> ui: {
> ssl: false,
> host: 'localhost',
> port: 4000,
> nameSpace: '/'
> },
> rest: {
> ssl: true,
> host: 'test.ourschool.edu',
> port: 8080,
> nameSpace: '/server',
> },
> };
>
> If I change the "rest: ssl:" to false, the yarn check passes, but then I
> am unable to log in via the user interface. It looks like an SSL problem,
> but I don't understand where the REST server or the Angular front end are
> supposed to find their SSL certificates. Is it the Java keystore, or the
> operating system certificate store, or somewhere else? Do both the front
> end and the back end use the same certificate store, or does it depend on
> which user each runs under?
>
> My operating system is Ubuntu 20.04 LTS, using Tomcat 9.
>
> Thanks for any assistance.
>
> Glenn
>
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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/caea0918-c316-42b4-b6e9-406f5139d477n%40googlegroups.com.
[dspace-tech] SSL between Angular and REST
Following the DSpace 7.1 installation guide here,
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace, I am unable to
proceed past step 4.a. When I run "yarn config:check:rest", it produces
this error message:
ERROR connecting to REST API
Error: write EPROTO 140676344637312:error:1408F10B:SSL
routines:ssl3_get_record:wrong version
number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
My environment.prod.ts:
export const environment = {
ui: {
ssl: false,
host: 'localhost',
port: 4000,
nameSpace: '/'
},
rest: {
ssl: true,
host: 'test.ourschool.edu',
port: 8080,
nameSpace: '/server',
},
};
If I change the "rest: ssl:" to false, the yarn check passes, but then I am
unable to log in via the user interface. It looks like an SSL problem, but
I don't understand where the REST server or the Angular front end are
supposed to find their SSL certificates. Is it the Java keystore, or the
operating system certificate store, or somewhere else? Do both the front
end and the back end use the same certificate store, or does it depend on
which user each runs under?
My operating system is Ubuntu 20.04 LTS, using Tomcat 9.
Thanks for any assistance.
Glenn
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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/d524-09a4-46bb-8bb8-46aaa1dec0a7n%40googlegroups.com.
[dspace-tech] Re: DSpace 7.1 - Can't Log In
I found the information at the following link, and will continue once I
have some other things sorted out.
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
On Wednesday, December 22, 2021 at 3:30:35 PM UTC-6 Glenn G wrote:
> More information from Chrome developer tools:
>
> {"timestamp":"2021-12-22T21:13:29.565+00:00","status":403,"error":"Forbidden","message":"Access
>
> is denied. Invalid CSRF token.","path":"/server/api/eperson/registrations"}
>
> On Tuesday, December 21, 2021 at 11:55:28 AM UTC-6 Glenn G wrote:
>
>> So I finally got this DSpace 7.1 sorta working, but it won't let me log
>> in through the user interface. If I enter my email address and password, a
>> pink balloon appears with the message: "Invalid email or password." Chrome
>> developer tools says, "zone-evergreen.js:2845 POST
>> https://d7test.ourschool.edu/server/api/authn/login 403".
>>
>> If I try to register as a new user, a pink error balloon pops up for
>> several seconds. It says, "Error when trying to register email
>> An error occured when registering the following email address: ..."
>>
>> The same thing happens if I choose "Have you forgotten your password?"
>>
>> For these actions, Chrome developer tools says, "zone-evergreen.js:2845
>> POST https://d7test.ourschool.edu/server/api/eperson/registrations 403"
>>
>> Depending on the action, the Tomcat log says, "'POST
>> /server/api/authn/login HTTP/1.1' 403" or 'POST
>> /server/api/eperson/registrations HTTP/1.1' 403".
>>
>> DSpace is configured to use only password authentication. These are some
>> of the possibly relevant settings I'm using in [dspace]/config/local.cfg:
>>
>> dspace.server.url = https://d7test.ourschool.edu/server
>> dspace.ui.url = https://d7test.ourschool.edu
>> authentication-password.domain.valid = ourschool.edu
>> rest.cors.allowed-origins = ${dspace.ui.url}, http://127.0.0.1
>> proxies.trusted.ipranges = 127.0.0.1,172.31.
>> plugin.sequence.org.dspace.authenticate.AuthenticationMethod =
>> org.dspace.authenticate.PasswordAuthentication
>> rest.cors.allowed-origins = ${dspace.ui.url}, http://127.0.0.1,
>> http://localhost:4000, http://172.31.57.198:4000, https://127.0.0.1,
>> https://localhost:4000, https://172.31.57.198:4000
>>
>> My OS is Ubuntu 20.04 LTS. All my DSpace backend files are owned by
>> tomcat:tomcat. The Angular files are owned by dspace:dspace. This is a
>> single-server setup.
>>
>> What should I look at next?
>>
>> Thanks,
>> Glenn
>>
>
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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/ba64ed18-214a-4e54-93df-6370a1676d7en%40googlegroups.com.
[dspace-tech] Re: DSpace 7.1 - Can't Log In
More information from Chrome developer tools:
{"timestamp":"2021-12-22T21:13:29.565+00:00","status":403,"error":"Forbidden","message":"Access
is denied. Invalid CSRF token.","path":"/server/api/eperson/registrations"}
On Tuesday, December 21, 2021 at 11:55:28 AM UTC-6 Glenn G wrote:
> So I finally got this DSpace 7.1 sorta working, but it won't let me log in
> through the user interface. If I enter my email address and password, a
> pink balloon appears with the message: "Invalid email or password." Chrome
> developer tools says, "zone-evergreen.js:2845 POST
> https://d7test.ourschool.edu/server/api/authn/login 403".
>
> If I try to register as a new user, a pink error balloon pops up for
> several seconds. It says, "Error when trying to register email
> An error occured when registering the following email address: ..."
>
> The same thing happens if I choose "Have you forgotten your password?"
>
> For these actions, Chrome developer tools says, "zone-evergreen.js:2845
> POST https://d7test.ourschool.edu/server/api/eperson/registrations 403"
>
> Depending on the action, the Tomcat log says, "'POST
> /server/api/authn/login HTTP/1.1' 403" or 'POST
> /server/api/eperson/registrations HTTP/1.1' 403".
>
> DSpace is configured to use only password authentication. These are some
> of the possibly relevant settings I'm using in [dspace]/config/local.cfg:
>
> dspace.server.url = https://d7test.ourschool.edu/server
> dspace.ui.url = https://d7test.ourschool.edu
> authentication-password.domain.valid = ourschool.edu
> rest.cors.allowed-origins = ${dspace.ui.url}, http://127.0.0.1
> proxies.trusted.ipranges = 127.0.0.1,172.31.
> plugin.sequence.org.dspace.authenticate.AuthenticationMethod =
> org.dspace.authenticate.PasswordAuthentication
> rest.cors.allowed-origins = ${dspace.ui.url}, http://127.0.0.1,
> http://localhost:4000, http://172.31.57.198:4000, https://127.0.0.1,
> https://localhost:4000, https://172.31.57.198:4000
>
> My OS is Ubuntu 20.04 LTS. All my DSpace backend files are owned by
> tomcat:tomcat. The Angular files are owned by dspace:dspace. This is a
> single-server setup.
>
> What should I look at next?
>
> Thanks,
> Glenn
>
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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/943efa94-beea-4004-bc72-d901412795acn%40googlegroups.com.
[dspace-tech] DSpace 7.1 - Can't Log In
So I finally got this DSpace 7.1 sorta working, but it won't let me log in
through the user interface. If I enter my email address and password, a
pink balloon appears with the message: "Invalid email or password." Chrome
developer tools says, "zone-evergreen.js:2845 POST
https://d7test.ourschool.edu/server/api/authn/login 403".
If I try to register as a new user, a pink error balloon pops up for
several seconds. It says, "Error when trying to register email
An error occured when registering the following email address: ..."
The same thing happens if I choose "Have you forgotten your password?"
For these actions, Chrome developer tools says, "zone-evergreen.js:2845
POST https://d7test.ourschool.edu/server/api/eperson/registrations 403"
Depending on the action, the Tomcat log says, "'POST
/server/api/authn/login HTTP/1.1' 403" or 'POST
/server/api/eperson/registrations HTTP/1.1' 403".
DSpace is configured to use only password authentication. These are some
of the possibly relevant settings I'm using in [dspace]/config/local.cfg:
dspace.server.url = https://d7test.ourschool.edu/server
dspace.ui.url = https://d7test.ourschool.edu
authentication-password.domain.valid = ourschool.edu
rest.cors.allowed-origins = ${dspace.ui.url}, http://127.0.0.1
proxies.trusted.ipranges = 127.0.0.1,172.31.
plugin.sequence.org.dspace.authenticate.AuthenticationMethod =
org.dspace.authenticate.PasswordAuthentication
rest.cors.allowed-origins = ${dspace.ui.url}, http://127.0.0.1,
http://localhost:4000, http://172.31.57.198:4000, https://127.0.0.1,
https://localhost:4000, https://172.31.57.198:4000
My OS is Ubuntu 20.04 LTS. All my DSpace backend files are owned by
tomcat:tomcat. The Angular files are owned by dspace:dspace. This is a
single-server setup.
What should I look at next?
Thanks,
Glenn
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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/b6912677-d907-4e4e-98a4-e98a1a81cc95n%40googlegroups.com.
[dspace-tech] Re: Problems with loading front home page Dspace-Cris 7
I had the same problem at some point. I traced it to the fact that yarn could not read my environment.prod.ts file, so it was building DSpace with the default environment values. These include a server at api.dspace.org. Check the syntax of your environment.prod.ts file, and pay attention to any errors revealed by " yarn config:check:rest" before building. Glenn On Tuesday, November 23, 2021 at 3:22:42 PM UTC-6 pilar@pucp.edu.pe wrote: > Hi, i've installed the backend and frontend of Dspace-cris 7 > My main problem is that when i started frontend with pm2, the home page > looks like this: > [image: WhatsApp Image 2021-11-23 at 3.54.36 PM.jpeg] > That seem like the loading of searching data is not working. > As i use pm2 to start dspace-angular.json, i wanted to know what was the > problem using pm2 logs, and the result was this: > [image: WhatsApp Image 2021-11-23 at 3.57.19 PM.jpeg] > [image: unknown.png] > I am not sure what does it mean and what can i do to solve it, so i'll be > gratefull if somebody could help me with this problem. thanks > > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- 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/aa4a3127-9514-4e40-bcca-51c8f4947b48n%40googlegroups.com.
[dspace-tech] DSpace 7.1 in a Subdirectory?
I'm working on an upgrade from DSpace 6.3 to DSpace 7.1. The base URL
includes a subdirectory, but it doesn't work with DSpace 7.1. When I
browse to https://test.ourschool.edu/uta-ir, I get the basic DSpace 7.1
page, but none of the content, theme or CSS. Chrome developer tools shows
that it is looking for these items in the root directory rather than the
/uta-ir directory. I have a feeling it is a misconfiguration somewhere,
but I haven't been able to find it. I'll include the items I've checked
below. Any ideas on how to fix it?
When I browse to https://test.ourschool.edu/server, I see the HAL Browser
page, although my browser says I'm actually at
https://test.ourschool.edu/server/#/server/api.
Thanks,
Glenn
*environment.prod.ts*
export const environment = {
ui: {
ssl: false,
host: 'localhost',
port: 4000,
nameSpace: '/uta-ir'
},
rest: {
ssl: true,
host: 'test.ourschool.edu',
port: 443,
nameSpace: '/server',
},
};
*Apache virtual host configuration file*
ProxyPass /uta-ir http://localhost:4000/uta-ir
ProxyPassReverse /uta-ir http://localhost:4000/uta-ir
*/etc/hosts*
172.31.57.198 test.ourschool.edu
*[dspace]/config/local.cfg*
dspace.server.url = http://localhost:8080/server
dspace.ui.url = http://localhost:4000/uta-ir
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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/a467fe4e-a817-4450-9fc4-62a110eb80f9n%40googlegroups.com.
[dspace-tech] Re: ORCID Patch Functionality Missing
Hello, Jolien, I applied the patch to my restored test system today, but unfortunately the results are the same, even with the orcid_icon.png file in place before and after running the patch. When I submit a test document, I can select an author with an ORCID ID and add her to the item submission. When I click the button to submit the item, it takes more than 90 seconds to acknowledge the submission. After the item is submitted, no ORCID icon appears by the author's name and the name is not clickable. Thanks for any help. Glenn On Tuesday, January 14, 2020 at 4:33:13 AM UTC-6, Jolien (Atmire) wrote: > > Hi Glenn and Alex, > > Thanks for checking. The orcid_icon.png file should have been added into > the right folder automatically when you installed the patch, hence my > question about the path. I'll try to do the installation on a vanilla > DSpace again to see if it renders the same problem for me. If so, we'll > make sure to get this fixed. > > To already fix the issue on your DSpace right now, you can indeed just > download the file and add it to > [dspace]/webapps/xmlui/themes/Mirage2/images as Alex already suggested. If > that does not work, let me know. > > Best, > > Jolien > > On Monday, January 13, 2020 at 5:52:25 PM UTC+1, Alex Fletcher wrote: >> >> Glenn: >> >> I downloaded the orcid_icon.png file that Jolene mentioned earlier and >> put it here: >> >> - [dspace]/webapps/xmlui/themes/Mirage2/images >>> >> >> That seemed to do the trick for us. >> >> Alex >> >> >> On Monday, 13 January 2020 11:11:12 UTC-5, Glenn G wrote: >>> >>> Jolien, >>> >>> Our DSpace installation does not have the path you mentioned. The >>> Mirage2 directory is located here: >>> >>> [dspace]/webapps/xmlui/themes/Mirage2 >>> >>> Our [dspace] directory is not literally "dspace". It has the format, >>> id-dspace. Also, our modules directory is located here: >>> >>> [dspace]/config/modules >>> >>> There are various possible reasons why our installation is different >>> from that anticipated by the patch: >>> >>> - It has been upgraded multiple times. >>> - It was moved to a standalone server after being hosted on a server >>> with several other DSpace installations. >>> - It was originally upgraded to 6.3 using the binary install. I added >>> the [dspace-source] later in order to install patches. >>> >>> Nonetheless, Alex indicates the patch could be installed if I do one or >>> both of the following beforehand: >>> >>> - Put a copy of orcid_icon.png in [dspace]/webapps/xmlui/themes/Mirage2 >>> - Create a directory, >>> [dspace]/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2 and put >>> orcid_icon.png there. >>> >>> Does either approach seem reasonable? >>> >>> Thanks, >>> Glenn >>> >>> On Monday, January 13, 2020 at 2:16:51 AM UTC-6, Jolien (Atmire) wrote: >>>> >>>> In fact, the file should be contained in the patch. You can see that >>>> here (for the DSpace 6 version): >>>> https://github.com/atmire/expanded-ORCID-support/blob/stable_6x/dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2/images/orcid_icon.png. >>>> >>>> For some reason, it looks like it is not accessed correctly when you do >>>> the >>>> installation. >>>> >>>> What could be happening is that in your DSpace installation, the path >>>> dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2 does not exist >>>> or exists under a different name. Could you check that? >>>> >>>> On Tuesday, December 3, 2019 at 12:10:42 AM UTC+1, Glenn G wrote: >>>>> >>>>> After applying the ORCID patch, the functionality my users were most >>>>> interested in is missing. The ORCID logo does not appear next to the >>>>> author's name, and the name is not clickable, so a list of the author's >>>>> publications cannot be retrieved from ORCID as promised. The ability to >>>>> search by ORCID number does now appear in the list of search modifiers, >>>>> but >>>>> it only works when the entire number is supplied with the "equals" >>>>> operand. The patch and functionality are described here: >>>>> https://atmire.github.io/expanded-ORCID-support/#/ >>>>> >>>>> If you have any idea why the logo and linked name don't appear, please >>>>> let me know. We are using the Mirage 2 theme. >>>>> >>>>> Thanks, >>>>> Glenn >>>>> >>>> -- 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/2943c8b5-a511-4b1f-a3fe-08c94dfa7bd6%40googlegroups.com.
[dspace-tech] Re: ORCID Patch Functionality Missing
Jolien and Alex, Thanks for the information! I will give it another shot as soon as I get my test server rebuilt. Glen On Tuesday, January 14, 2020 at 4:33:13 AM UTC-6, Jolien (Atmire) wrote: > > Hi Glenn and Alex, > > Thanks for checking. The orcid_icon.png file should have been added into > the right folder automatically when you installed the patch, hence my > question about the path. I'll try to do the installation on a vanilla > DSpace again to see if it renders the same problem for me. If so, we'll > make sure to get this fixed. > > To already fix the issue on your DSpace right now, you can indeed just > download the file and add it to > [dspace]/webapps/xmlui/themes/Mirage2/images as Alex already suggested. If > that does not work, let me know. > > Best, > > Jolien > > On Monday, January 13, 2020 at 5:52:25 PM UTC+1, Alex Fletcher wrote: >> >> Glenn: >> >> I downloaded the orcid_icon.png file that Jolene mentioned earlier and >> put it here: >> >> - [dspace]/webapps/xmlui/themes/Mirage2/images >>> >> >> That seemed to do the trick for us. >> >> Alex >> >> >> On Monday, 13 January 2020 11:11:12 UTC-5, Glenn G wrote: >>> >>> Jolien, >>> >>> Our DSpace installation does not have the path you mentioned. The >>> Mirage2 directory is located here: >>> >>> [dspace]/webapps/xmlui/themes/Mirage2 >>> >>> Our [dspace] directory is not literally "dspace". It has the format, >>> id-dspace. Also, our modules directory is located here: >>> >>> [dspace]/config/modules >>> >>> There are various possible reasons why our installation is different >>> from that anticipated by the patch: >>> >>> - It has been upgraded multiple times. >>> - It was moved to a standalone server after being hosted on a server >>> with several other DSpace installations. >>> - It was originally upgraded to 6.3 using the binary install. I added >>> the [dspace-source] later in order to install patches. >>> >>> Nonetheless, Alex indicates the patch could be installed if I do one or >>> both of the following beforehand: >>> >>> - Put a copy of orcid_icon.png in [dspace]/webapps/xmlui/themes/Mirage2 >>> - Create a directory, >>> [dspace]/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2 and put >>> orcid_icon.png there. >>> >>> Does either approach seem reasonable? >>> >>> Thanks, >>> Glenn >>> >>> On Monday, January 13, 2020 at 2:16:51 AM UTC-6, Jolien (Atmire) wrote: >>>> >>>> In fact, the file should be contained in the patch. You can see that >>>> here (for the DSpace 6 version): >>>> https://github.com/atmire/expanded-ORCID-support/blob/stable_6x/dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2/images/orcid_icon.png. >>>> >>>> For some reason, it looks like it is not accessed correctly when you do >>>> the >>>> installation. >>>> >>>> What could be happening is that in your DSpace installation, the path >>>> dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2 does not exist >>>> or exists under a different name. Could you check that? >>>> >>>> On Tuesday, December 3, 2019 at 12:10:42 AM UTC+1, Glenn G wrote: >>>>> >>>>> After applying the ORCID patch, the functionality my users were most >>>>> interested in is missing. The ORCID logo does not appear next to the >>>>> author's name, and the name is not clickable, so a list of the author's >>>>> publications cannot be retrieved from ORCID as promised. The ability to >>>>> search by ORCID number does now appear in the list of search modifiers, >>>>> but >>>>> it only works when the entire number is supplied with the "equals" >>>>> operand. The patch and functionality are described here: >>>>> https://atmire.github.io/expanded-ORCID-support/#/ >>>>> >>>>> If you have any idea why the logo and linked name don't appear, please >>>>> let me know. We are using the Mirage 2 theme. >>>>> >>>>> Thanks, >>>>> Glenn >>>>> >>>> -- 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/0e4416c0-9ce9-4742-815e-fc06fe28f767%40googlegroups.com.
[dspace-tech] Re: ORCID Patch Functionality Missing
Oh, now it occurs to me that you meant [dspace-source]/dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2. Yes, we have that directory, and no, orcid_icon.png does not exist there. Should I copy it there before applying the patch? Thanks, Glenn On Monday, January 13, 2020 at 10:11:12 AM UTC-6, Glenn G wrote: > > Jolien, > > Our DSpace installation does not have the path you mentioned. The Mirage2 > directory is located here: > > [dspace]/webapps/xmlui/themes/Mirage2 > > Our [dspace] directory is not literally "dspace". It has the format, > id-dspace. Also, our modules directory is located here: > > [dspace]/config/modules > > There are various possible reasons why our installation is different from > that anticipated by the patch: > > - It has been upgraded multiple times. > - It was moved to a standalone server after being hosted on a server with > several other DSpace installations. > - It was originally upgraded to 6.3 using the binary install. I added the > [dspace-source] later in order to install patches. > > Nonetheless, Alex indicates the patch could be installed if I do one or > both of the following beforehand: > > - Put a copy of orcid_icon.png in [dspace]/webapps/xmlui/themes/Mirage2 > - Create a directory, > [dspace]/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2 and put > orcid_icon.png there. > > Does either approach seem reasonable? > > Thanks, > Glenn > > On Monday, January 13, 2020 at 2:16:51 AM UTC-6, Jolien (Atmire) wrote: >> >> In fact, the file should be contained in the patch. You can see that here >> (for the DSpace 6 version): >> https://github.com/atmire/expanded-ORCID-support/blob/stable_6x/dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2/images/orcid_icon.png. >> >> For some reason, it looks like it is not accessed correctly when you do the >> installation. >> >> What could be happening is that in your DSpace installation, the path >> dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2 does not exist >> or exists under a different name. Could you check that? >> >> On Tuesday, December 3, 2019 at 12:10:42 AM UTC+1, Glenn G wrote: >>> >>> After applying the ORCID patch, the functionality my users were most >>> interested in is missing. The ORCID logo does not appear next to the >>> author's name, and the name is not clickable, so a list of the author's >>> publications cannot be retrieved from ORCID as promised. The ability to >>> search by ORCID number does now appear in the list of search modifiers, but >>> it only works when the entire number is supplied with the "equals" >>> operand. The patch and functionality are described here: >>> https://atmire.github.io/expanded-ORCID-support/#/ >>> >>> If you have any idea why the logo and linked name don't appear, please >>> let me know. We are using the Mirage 2 theme. >>> >>> Thanks, >>> Glenn >>> >> -- 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/de6606ce-8715-4bde-b59a-67ca1428b22c%40googlegroups.com.
[dspace-tech] Re: ORCID Patch Functionality Missing
Jolien, Our DSpace installation does not have the path you mentioned. The Mirage2 directory is located here: [dspace]/webapps/xmlui/themes/Mirage2 Our [dspace] directory is not literally "dspace". It has the format, id-dspace. Also, our modules directory is located here: [dspace]/config/modules There are various possible reasons why our installation is different from that anticipated by the patch: - It has been upgraded multiple times. - It was moved to a standalone server after being hosted on a server with several other DSpace installations. - It was originally upgraded to 6.3 using the binary install. I added the [dspace-source] later in order to install patches. Nonetheless, Alex indicates the patch could be installed if I do one or both of the following beforehand: - Put a copy of orcid_icon.png in [dspace]/webapps/xmlui/themes/Mirage2 - Create a directory, [dspace]/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2 and put orcid_icon.png there. Does either approach seem reasonable? Thanks, Glenn On Monday, January 13, 2020 at 2:16:51 AM UTC-6, Jolien (Atmire) wrote: > > In fact, the file should be contained in the patch. You can see that here > (for the DSpace 6 version): > https://github.com/atmire/expanded-ORCID-support/blob/stable_6x/dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2/images/orcid_icon.png. > > For some reason, it looks like it is not accessed correctly when you do the > installation. > > What could be happening is that in your DSpace installation, the path > dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2 does not exist > or exists under a different name. Could you check that? > > On Tuesday, December 3, 2019 at 12:10:42 AM UTC+1, Glenn G wrote: >> >> After applying the ORCID patch, the functionality my users were most >> interested in is missing. The ORCID logo does not appear next to the >> author's name, and the name is not clickable, so a list of the author's >> publications cannot be retrieved from ORCID as promised. The ability to >> search by ORCID number does now appear in the list of search modifiers, but >> it only works when the entire number is supplied with the "equals" >> operand. The patch and functionality are described here: >> https://atmire.github.io/expanded-ORCID-support/#/ >> >> If you have any idea why the logo and linked name don't appear, please >> let me know. We are using the Mirage 2 theme. >> >> Thanks, >> Glenn >> > -- 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/2ae93969-4009-4bce-935a-46fdf4c50248%40googlegroups.com.
[dspace-tech] Re: ORCID Patch Functionality Missing
Hello, Jolien, No, the file does not exist in that location. Thanks, Glenn On Thursday, January 9, 2020 at 7:37:04 AM UTC-6, Jolien (Atmire) wrote: > > Hello again Glenn, > > Thank you for the details and sorry for the late reply! To follow-up on > your problem, could you maybe check if the following file exists within the > install-directory: > > webapps/xmlui/themes/Mirage2/images/orcid_icon.png > > Thanks! > > Best regards, > > Jolien > > On Tuesday, December 3, 2019 at 12:10:42 AM UTC+1, Glenn G wrote: >> >> After applying the ORCID patch, the functionality my users were most >> interested in is missing. The ORCID logo does not appear next to the >> author's name, and the name is not clickable, so a list of the author's >> publications cannot be retrieved from ORCID as promised. The ability to >> search by ORCID number does now appear in the list of search modifiers, but >> it only works when the entire number is supplied with the "equals" >> operand. The patch and functionality are described here: >> https://atmire.github.io/expanded-ORCID-support/#/ >> >> If you have any idea why the logo and linked name don't appear, please >> let me know. We are using the Mirage 2 theme. >> >> Thanks, >> Glenn >> > -- 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/5380858b-8a42-4b83-8a42-f85f252a0b9e%40googlegroups.com.
[dspace-tech] Re: ORCID Patch Functionality Missing
ons/src/main/java/com/atmire/dspace/authority/OrcidAuthorityValueServiceImpl.java cleanly. Applied patch dspace/modules/additions/src/main/java/com/atmire/dspace/discovery/ORCIDIdIndexingPlugin.java cleanly. Applied patch dspace/modules/additions/src/main/java/org/dspace/authority/AuthorityUtil.java cleanly. Applied patch dspace/modules/additions/src/main/java/org/dspace/authority/AuthorityValueFinder.java cleanly. Applied patch dspace/modules/additions/src/main/java/org/dspace/authority/PersonAuthorityValue.java cleanly. Applied patch dspace/modules/additions/src/main/java/org/dspace/authority/orcid/Orcidv2AuthorityValue.java cleanly. Applied patch dspace/modules/rest/src/main/java/org/dspace/rest/AuthoritiesResource.java cleanly. Applied patch dspace/modules/rest/src/main/java/org/dspace/rest/CollectionsResource.java cleanly. Applied patch dspace/modules/rest/src/main/java/org/dspace/rest/ItemsResource.java cleanly. Applied patch dspace/modules/rest/src/main/java/org/dspace/rest/RestIndex.java cleanly. Applied patch dspace/modules/rest/src/main/java/org/dspace/rest/common/Item.java cleanly. Applied patch dspace/modules/rest/src/main/webapp/WEB-INF/web.xml cleanly. Applied patch dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2/styles/_style.scss cleanly. Applied patch dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2/xsl/additions.xsl cleanly. Applied patch dspace/modules/xmlui/src/main/java/org/dspace/app/xmlui/cocoon/DSpaceMETSGenerator.java cleanly. Applied patch dspace/modules/xmlui/src/main/java/org/dspace/app/xmlui/objectmanager/AbstractAdapter.java cleanly. Applied patch dspace/modules/xmlui/src/main/java/org/dspace/app/xmlui/objectmanager/ItemAdapter.java cleanly. Applied patch dspace/modules/xmlui/src/main/resources/aspects/Discovery/i18n/messages.xml cleanly. Applied patch dspace/modules/xmlui/src/main/webapp/themes/Mirage/Mirage.xsl cleanly. Applied patch dspace/modules/xmlui/src/main/webapp/themes/Mirage/lib/css/style.css cleanly. Applied patch dspace/modules/xmlui/src/main/webapp/themes/Mirage/lib/xsl/additions.xsl cleanly. Applied patch dspace/pom.xml cleanly. Applied patch dspace/solr/search/conf/schema.xml cleanly. After applying the patch, I removed existing files in the installer directory and ran Maven: [glenn@rctest dspace-6.3-release]$ mvn -U clean package -Dmirage2.on=true *...* [INFO] Copying files to /ebs/dspace-source/dspace-6.3-release/dspace/target/dspace-installer [INFO] [INFO] Reactor Summary: [INFO] [INFO] DSpace Addon Modules ... SUCCESS [ 1.105 s] [INFO] DSpace Kernel :: Additions and Local Customizations SUCCESS [ 12.330 s] [INFO] DSpace XML-UI Mirage2 Theme :: Local Customisations SUCCESS [02:04 min] [INFO] DSpace XML-UI (Manakin) :: Local Customizations SUCCESS [ 25.179 s] [INFO] DSpace JSP-UI :: Local Customizations .. SUCCESS [ 6.990 s] [INFO] DSpace RDF :: Local Customizations . SUCCESS [ 7.367 s] [INFO] DSpace REST :: Local Customizations SUCCESS [ 13.744 s] [INFO] DSpace SWORD :: Local Customizations ... SUCCESS [ 5.532 s] [INFO] DSpace SWORD v2 :: Local Customizations SUCCESS [ 5.744 s] [INFO] DSpace SOLR :: Local Customizations SUCCESS [ 8.435 s] [INFO] DSpace OAI-PMH :: Local Customizations . SUCCESS [ 8.241 s] [INFO] DSpace Assembly and Configuration 6.3 .. SUCCESS [01:03 min] [INFO] [INFO] BUILD SUCCESS I added orcid.connector.url = https://orcid.org/ to local.cfg in [dspace-source]/dspace-6.3-release/dspace/target/dspace-installer/config/local.cfg. Then I ran "ant update" and restarted Tomcat. Hope you can tell me where I went wrong. Thanks, Glenn On Wednesday, December 11, 2019 at 5:54:43 AM UTC-6, Jolien (Atmire) wrote: > > Dear Glenn, > > First and foremost, thank you for your interest in the patch we created. > It is good to hear that it finds resonance in the DSpace user community. > > About the problem you encountered, could you tell us a little more about > how you installed the patch and what DSpace version you are using? > > Thanks in advance. > > Best regards, > > Jolien > > On Tuesday, December 3, 2019 at 12:10:42 AM UTC+1, Glenn G wrote: >> >> After applying the ORCID patch, the functionality my users were most >> interested in is missing. The ORCID logo does not appear next to the >> author's name, and the name is not clickable, so a list of the author's >> publications cannot be retrieved from ORCID as promised. The ability to >> search by ORCID number does now appear in the list of search modifiers, but >> it only works when the entire number is su
[dspace-tech] ORCID Patch Functionality Missing
After applying the ORCID patch, the functionality my users were most interested in is missing. The ORCID logo does not appear next to the author's name, and the name is not clickable, so a list of the author's publications cannot be retrieved from ORCID as promised. The ability to search by ORCID number does now appear in the list of search modifiers, but it only works when the entire number is supplied with the "equals" operand. The patch and functionality are described here: https://atmire.github.io/expanded-ORCID-support/#/ If you have any idea why the logo and linked name don't appear, please let me know. We are using the Mirage 2 theme. Thanks, Glenn -- 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/1ab91d51-f6d3-40c9-afd7-de8a8e520aea%40googlegroups.com.
[dspace-tech] Re: New features for DSpace 5 and 6 ORCID integration
Yes, I encountered exactly the same problem. Sorry I don't have a solution, just wanted to confirm your finding. Possibly something needs to be added to build.xml, but I have no idea what. -Glenn. On Tuesday, November 5, 2019 at 2:29:50 AM UTC-6, Muhammad Yousaf wrote: > > Hi Everyone, > > I am pretty new to this whole Dspace installation and build. Recently we > upgraded from Dspace 6.2 to Dspace 6.3 with xmlui enabled (Mirage 2 theme). > It is working just fine as we haven't faced any issue till now. On Oct > 22nd, 2019 Atmire released a patch for orcid integration onto Dspace 5.9+ > and 6.3+ versions ( > https://www.atmire.com/articles/detail/new-features-for-dspace-5-and-6-orcid-integration). > > > > I went over there github page ( > https://atmire.github.io/expanded-ORCID-support/#/), followed all the > steps, fulfilled all the prerequisites (maven version, git installed etc.), > deployed the patch, did a *clean maven build* but when doing *ant update* > it gives me an error at the beginning saying that "*orcid.connector.url > is circularly defined*"! and then fails. I went over their github code > and it seems like an entry in *dspace.cfg* is causing this issue as shown > below: > > > https://github.com/atmire/expanded-ORCID-support/compare/dspace_6x%E2%80%A6stable_6x.diff > > > https://github.com/atmire/expanded-ORCID-support/compare/dspace_6x...stable_6x > > [image: Screen Shot 2019-11-05 at 9.51.41 AM.png] > > > For now I have commented it out as not to cause any failure during ant > deployment and it deploys without any error but as expected, orcid is not > working :( . > > > > > Has anyone faced a similar issue while doing orcid integration or is there > a bug in their code? I am stuck with it and any help will be highly > appreciated. > > Thank You. > > Regards. > -- 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/fd0d12d0-cb24-4e1d-b30c-cc99a0a7a514%40googlegroups.com.
[dspace-tech] Re: How to Apply Patch for CommunityFiliator?
Well, I take it back. We're still getting the same error message with the -r switch. Anyone else figured out how to make it work? On Wednesday, July 24, 2019 at 11:11:06 AM UTC-5, Glenn G wrote: > > Thought I would update this thread in case anyone has the same question. > > In the absence of any instructions on how to apply a patch, I decided to > try some things on a test server. I made a copy of our DSpace 6.3 > production server and went to update the two files, CommunityFiliator.java > and Community.java, with the patched files. I couldn't find the files on > the server, and I determined that our server had been installed with the > precompiled version of DSpace. > > So I copied the sources to the [dspace-source] directory. Then I copied > the new CommunityFiliator.java and Community.java files to their respective > places and recompiled DSpace. Only nothing changed. I tried it a few more > times and eventually became aware that the compile process was not using > the new sources. I guess this was due to the original installation being > precompiled. > > A colleague who is more of a developer suggested installing a new test > system from scratch using the sources. Once the new system was installed, > we could copy the dspace binary file from it to our original test system. > This worked, but not without a hitch. > > The build failed with the message, "log4j package does not exist". My > developer colleague helped determine that this was a result of the log4j > specification in Community.java being different from the existing log4j > version in DSpace 6.3. Once we changed the spec in the patch file back to > its pre-patch version, the compile operation proceeded. > > For reference, the line that we changed: > > org.apache.logging.log4j.Logger; > > We changed it to: > > org.apache.log4j.Logger; > > > On Wednesday, June 5, 2019 at 11:00:52 AM UTC-5, Glenn G wrote: >> >> Apologies if this is a dumb question, but how do you apply a patch? >> We're running DSpace 6.3, and we need to get the CommunityFiliator running >> with the new functionality described in GitHub pull request DS-3914. >> >> I replaced CommunityFiliator.java and Community.java files on the system, >> but it didn't made any difference. On our system, those file are located >> here: >> >> >> [dspace-source]/dspace-api/src/main/java/org/dspace/administer/CommunityFiliator.java >> >> [dspace-source]/dspace-rest/src/main/java/org/dspace/rest/common/Community.java >> [dspace-source]/dspace-api/src/main/java/org/dspace/content/Community.java >> >> I tried rebuilding, but that didn't make a difference either. I used >> these commands to do the rebuild: >> >> mvn -U clean package -Dmirage2.on=true >> ant update >> >> We still get the following error when we run [dspace]/bin/dspace >> community-filiator -r -p x/x -c x/ >> >> Exception: null >> java.lang.UnsupportedOperationException >> at java.util.AbstractList.remove(AbstractList.java:161) >> at java.util.AbstractList$Itr.remove(AbstractList.java:374) >> at >> java.util.AbstractCollection.remove(AbstractCollection.java:293) >> at >> org.dspace.administer.CommunityFiliator.defiliate(CommunityFiliator.java:264) >> at >> org.dspace.administer.CommunityFiliator.main(CommunityFiliator.java:164) >> 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:497) >> at >> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229) >> at >> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81) >> >> What am I missing? >> >> Thanks, >> Glenn >> > -- 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/06d770e3-b3e9-4d47-9c73-0a3643778881%40googlegroups.com.
[dspace-tech] More Fun with Missing Stats
>From the home page of our DSpace 6.3 site, we click Statistics in the Administrative box. This brings up a page containing a General Overview and Archive Information. Under that is an Items Viewed section subtitled "(more than 20 times)". The list of items below ends, somewhat predictably, with items viewed at least 20 times. Yesterday someone asked me to allow DSpace to display statistics for each view of an item, rather than for the default minimum 20 views. I found I could change the default by changing the value of "item.floor=20" in the dstat.cfg file. Now the Items Viewed section displays items viewed at least once. However, if we click on any of the monthly reports links, the Items Viewed in the subsequent window is still "(more than 20 times)". This is true of all the monthly reports except the current month, where Items Viewed is subtitled "(more than 1 times)". Is there a way to make all the previous monthly reports display items viewed at least once? -- 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/e2bb8700-a646-4a4b-9a01-1dd5650e34fc%40googlegroups.com.
[dspace-tech] Re: How to Apply Patch for CommunityFiliator?
Thought I would update this thread in case anyone has the same question. In the absence of any instructions on how to apply a patch, I decided to try some things on a test server. I made a copy of our DSpace 6.3 production server and went to update the two files, CommunityFiliator.java and Community.java, with the patched files. I couldn't find the files on the server, and I determined that our server had been installed with the precompiled version of DSpace. So I copied the sources to the [dspace-source] directory. Then I copied the new CommunityFiliator.java and Community.java files to their respective places and recompiled DSpace. Only nothing changed. I tried it a few more times and eventually became aware that the compile process was not using the new sources. I guess this was due to the original installation being precompiled. A colleague who is more of a developer suggested installing a new test system from scratch using the sources. Once the new system was installed, we could copy the dspace binary file from it to our original test system. This worked, but not without a hitch. The build failed with the message, "log4j package does not exist". My developer colleague helped determine that this was a result of the log4j specification in Community.java being different from the existing log4j version in DSpace 6.3. Once we changed the spec in the patch file back to its pre-patch version, the compile operation proceeded. For reference, the line that we changed: org.apache.logging.log4j.Logger; We changed it to: org.apache.log4j.Logger; On Wednesday, June 5, 2019 at 11:00:52 AM UTC-5, Glenn G wrote: > > Apologies if this is a dumb question, but how do you apply a patch? We're > running DSpace 6.3, and we need to get the CommunityFiliator running with > the new functionality described in GitHub pull request DS-3914. > > I replaced CommunityFiliator.java and Community.java files on the system, > but it didn't made any difference. On our system, those file are located > here: > > > [dspace-source]/dspace-api/src/main/java/org/dspace/administer/CommunityFiliator.java > > [dspace-source]/dspace-rest/src/main/java/org/dspace/rest/common/Community.java > [dspace-source]/dspace-api/src/main/java/org/dspace/content/Community.java > > I tried rebuilding, but that didn't make a difference either. I used > these commands to do the rebuild: > > mvn -U clean package -Dmirage2.on=true > ant update > > We still get the following error when we run [dspace]/bin/dspace > community-filiator -r -p x/x -c x/ > > Exception: null > java.lang.UnsupportedOperationException > at java.util.AbstractList.remove(AbstractList.java:161) > at java.util.AbstractList$Itr.remove(AbstractList.java:374) > at java.util.AbstractCollection.remove(AbstractCollection.java:293) > at > org.dspace.administer.CommunityFiliator.defiliate(CommunityFiliator.java:264) > at > org.dspace.administer.CommunityFiliator.main(CommunityFiliator.java:164) > 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:497) > at > org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229) > at > org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81) > > What am I missing? > > Thanks, > Glenn > -- 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/0b1649c6-cda9-4a9d-a222-e16ee271099d%40googlegroups.com.
[dspace-tech] View Usage Statistics Quit for a While
We are using DSpace 6.3. This week someone notified me that "View Usage Statistics" had stopped showing new statistics in January. I think this resulted from the old GeoLiteCity.dat database being specified in [dspace]/config/modules/usage-statistics.cfg. As soon as I got the new GeoLite2-City.mmdb database and changed usage-statistics.cfg to reflect the change, statistics began to accrue. However, statistics from January until this week are still missing. I ran index-discovery -b and solr-reindex-statistics. This adds csv files to [dspace]/solr-export. The csv files have the statistics in them going back to January. I also ran solr-import-statistics and stats-util -o, but still no luck viewing the stats when we click "View Usage Statistics." Is there a way to make those stats show? -- 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/c82bc1d0-aa73-4381-a943-67f8d77cbc4b%40googlegroups.com.
[dspace-tech] Compilation Failure
I'm trying to install DSpace 6.3 on an Amazon Linux server (kernel 4.14) running Tomcat 7. Following step 7 in the instructions, where I enter "mvn package -Dmirage2.on=true", the build fails with the error messages below. Can anyone suggest a fix? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile (default-compile) on project dspace-api: Compilation failure: Compilation failure: [ERROR] /ebs/dspace-source/dspace-6.3-release/dspace-api/src/main/java/org/dspace/content/Community.java:[27,32] package org.apache.logging.log4j does not exist [ERROR] /ebs/dspace-source/dspace-6.3-release/dspace-api/src/main/java/org/dspace/content/Community.java:[55,26] cannot find symbol [ERROR] symbol: class Logger [ERROR] location: class org.dspace.content.Community -- 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/70d78905-06af-47fb-863b-f78c401fe459%40googlegroups.com.
[dspace-tech] Re: How to Apply Patch for CommunityFiliator?
Suggestions anyone? On Wednesday, June 5, 2019 at 11:00:52 AM UTC-5, Glenn G wrote: > > Apologies if this is a dumb question, but how do you apply a patch? We're > running DSpace 6.3, and we need to get the CommunityFiliator running with > the new functionality described in GitHub pull request DS-3914. > > I replaced CommunityFiliator.java and Community.java files on the system, > but it didn't made any difference. On our system, those file are located > here: > > > [dspace-source]/dspace-api/src/main/java/org/dspace/administer/CommunityFiliator.java > > [dspace-source]/dspace-rest/src/main/java/org/dspace/rest/common/Community.java > [dspace-source]/dspace-api/src/main/java/org/dspace/content/Community.java > > I tried rebuilding, but that didn't make a difference either. I used > these commands to do the rebuild: > > mvn -U clean package -Dmirage2.on=true > ant update > > We still get the following error when we run [dspace]/bin/dspace > community-filiator -r -p x/x -c x/ > > Exception: null > java.lang.UnsupportedOperationException > at java.util.AbstractList.remove(AbstractList.java:161) > at java.util.AbstractList$Itr.remove(AbstractList.java:374) > at java.util.AbstractCollection.remove(AbstractCollection.java:293) > at > org.dspace.administer.CommunityFiliator.defiliate(CommunityFiliator.java:264) > at > org.dspace.administer.CommunityFiliator.main(CommunityFiliator.java:164) > 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:497) > at > org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229) > at > org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81) > > What am I missing? > > Thanks, > Glenn > -- 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/d957c0be-28d8-4d2f-824b-f05c68523ae7%40googlegroups.com.
[dspace-tech] Re: ORCID Authority Control & DSpace 6.0
Having the same problem after upgrading from 5.5 to 6.3. Tried adding the
link to handlebars 4.0.0, but that doesn't work.
Any new ideas?
Thanks,
Glenn
On Wednesday, October 26, 2016 at 5:04:03 AM UTC-5, Sean Carte wrote:
> Since upgrading to DSpace 6.0, I've noticed that the Lookup button doesn't
> seem to do anything anymore. Nothing in the dspace log either. This is both
> during the initial item submission and in the edit item page.
>
> I have the following in my local.cfg file:
>
> event.dispatcher.default.consumers = authority, versioning, discovery,
> eperson
> (the wiki page <
> https://wiki.duraspace.org/display/DSDOC6x/ORCID+Integration> includes
> 'harvester' at the end of that line, but the new dspace.cfg omits it, and
> it causes problems during submission: 'No class configured for consumer
> named: harvester')
>
> plugin.named.org.dspace.content.authority.ChoiceAuthority = \
> org.dspace.content.authority.SolrAuthority = SolrAuthorAuthority
>
> solr.authority.server=${solr.server}/authority
> choices.plugin.dc.contributor.author = SolrAuthorAuthority
> choices.presentation.dc.contributor.author = authorLookup
> authority.controlled.dc.contributor.author = true
> authority.author.indexer.field.1=dc.contributor.author
>
>
> Is ORCID authority control working for others using DSpace 6.0?
>
> Sean
>
--
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] Re: 6.3 Upgrade, No Content
Never mind. This was due to our solr webapp having a non-default name. Once we corrected the entry in local.cfg (solr.server = http://localhost:8080/solr), the links reappeared. Thanks for your patience, Glenn On Thursday, October 11, 2018 at 12:02:10 PM UTC-5, Glenn G wrote: > We're testing an upgrade from DSpace 5.5-SNAPSHOT to 6.3 on a Linux > server. First we upgrade the Postgresql database from 9.2 to 9.6. > Everything is still working. Then we follow the instructions to do the > upgrade. When all steps are completed, the site appears functional. > Graphics, page format and headings are good, and we can navigate to the > various communities. But there are no links to content. For example, > we're missing a number of "Recent Submissions" links that should appear on > each page. If we search for a common term that should bring up a number of > titles, the search finds nothing. I'm including some error messages from > the DSpace log. Any pointers appreciated. > > Glenn > > 2018-10-11 09:09:28,450 ERROR > org.dspace.app.xmlui.aspect.discovery.SidebarFacetsTransformer @ > anonymous:session_id=242A3F99B3B8ED5EC46141769F53C786:ip > _addr=172.31.66.8:Error in Discovery while setting up date facet > range:date facet\colon; dateIssued.year > org.dspace.discovery.SearchServiceException: Error executing query > ... > Caused by: org.apache.solr.client.solrj.SolrServerException: Error > executing query > ... > Caused by: org.apache.http.ParseException: Invalid content type: > at org.apache.http.entity.ContentType.parse(ContentType.java:273) > ... > 2018-10-11 09:09:28,502 ERROR > org.dspace.app.xmlui.aspect.discovery.AbstractRecentSubmissionTransformer @ > Caught SearchServiceException while retrievin > g recent submission for: home page > org.dspace.discovery.SearchServiceException: Error executing query > ... > Caused by: org.apache.solr.client.solrj.SolrServerException: Error > executing query > ... > Caused by: org.apache.http.ParseException: Invalid content type: > at org.apache.http.entity.ContentType.parse(ContentType.java:273) > > > -- 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] 6.3 Upgrade, No Content
We're testing an upgrade from DSpace 5.5-SNAPSHOT to 6.3 on a Linux server. First we upgrade the Postgresql database from 9.2 to 9.6. Everything is still working. Then we follow the instructions to do the upgrade. When all steps are completed, the site appears functional. Graphics, page format and headings are good, and we can navigate to the various communities. But there are no links to content. For example, we're missing a number of "Recent Submissions" links that should appear on each page. If we search for a common term that should bring up a number of titles, the search finds nothing. I'm including some error messages from the DSpace log. Any pointers appreciated. Glenn 2018-10-11 09:09:28,450 ERROR org.dspace.app.xmlui.aspect.discovery.SidebarFacetsTransformer @ anonymous:session_id=242A3F99B3B8ED5EC46141769F53C786:ip _addr=172.31.66.8:Error in Discovery while setting up date facet range:date facet\colon; dateIssued.year org.dspace.discovery.SearchServiceException: Error executing query ... Caused by: org.apache.solr.client.solrj.SolrServerException: Error executing query ... Caused by: org.apache.http.ParseException: Invalid content type: at org.apache.http.entity.ContentType.parse(ContentType.java:273) ... 2018-10-11 09:09:28,502 ERROR org.dspace.app.xmlui.aspect.discovery.AbstractRecentSubmissionTransformer @ Caught SearchServiceException while retrievin g recent submission for: home page org.dspace.discovery.SearchServiceException: Error executing query ... Caused by: org.apache.solr.client.solrj.SolrServerException: Error executing query ... Caused by: org.apache.http.ParseException: Invalid content type: at org.apache.http.entity.ContentType.parse(ContentType.java:273) -- 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.
