Re: [dspace-tech] Re: Gnome ubuntu stuck

2023-06-09 Thread darryl....@usask.ca

I hate to be "that guy", but this seems pretty clearly a networking issue 
with Ubuntu, and nothing related to DSpace.  I think the question is 
probably best asked elsewhere, and not just because it isn't related to 
DSpace, but because you'll likely get more and better responses from a 
support channel that's dedicated to Ubuntu.

- Darryl


On Friday, June 9, 2023 at 5:28:43 AM UTC-6 Maya Zbitneva wrote:

>
> Letter from Daan Lesing:
>
> >Hi there,
>
> >Enter via the command line with your username and password.
>
> >Then check the following files if they are correct:
>
> >sudo vi /etc/hosts
> >This file holds your physical server name and IP address eg. >192.168.0.1 
> repository.com 
>
> >sudo vi /etc/hostname
> >This file holds your physical server name eg. repository.com
>
> >Could you check that your network settings are correct?
>
> >sudo vi /etc/networks/interfaces
>
> >sudo vi /etc/resolv.conf 
>
> Error 1: String “resolv.conf->../run/system/resolve/stub-resolv.conf” is 
> colored by red color.
> Error 2: File “stub-resolv.conf” does not exist.
>
> Question 1: Should I restore “stub-resolv.conf” and symbolic link 
> “resolv.conf->../run/system/resolve/stub-resolv.conf”?
>
> >make sure that your DNS and gateway configurations are correct.
>
> >Also check that systemd-resolved.service is started - sudo systemctl 
> status systemd->resolved.service
>
> Error 3: Systemd-resolved.service loaded, but failed.
>
> sudo systemctl start system-resolved.service – failed.
>
> Result of “sudo systemctl start systemd-resolved.service”:
> [image: start_resolved.jpg]
>
> Result of “journalctl -xe”:
> [image: journal1.jpg]
> [image: journal2.jpg]
>
> Question 2: Should I make that systemd-resolved.service will be started 
> that is to be active?
>
> >Hope this helps
>
> Letter from Mohammad S. AlMutairi:
>
>
> >To check the service errors it generated.
> >2) sudo journalctl -u systemd-resolved -p err
>
> Result of “sudo journalctl -u systemd-resolved -p err”:
>
> [image: FailedNetworkNameResolution.jpg]
>
> Question: How to correct error “Failed to start network name resolution”?
>
> With respect,
> Maiia,
> Academia.
> середа, 7 червня 2023 р. о 22:14:54 UTC+3 Mohammad S. AlMutairi пише:
>
>> In addition to the previous message and after completing it. it's 
>> possible the cause of the issue you have is the failing of the start of 
>> Network Name Resolution so you need to further check why it's failing. You 
>> can check the service log or the it's errors by running the following 
>> comands.
>>
>> To check the service log.
>> 1) sudo journalctl -u systemd-resolved
>>
>> To check the service errors it generated.
>> 2) sudo journalctl -u systemd-resolved -p err
>>
>> To override it temporarily.
>> 3) cp /etc/resolv.conf /etc/resolv.conf-orig && echo "nameserver 8.8.8.8" 
>> > /etc/resolv.conf
>>
>> Update & Upgrade your server.
>> 4) sudo apt update -y && sudo apt upgrade -y && sudo shutdown -r now
>>
>> Hope it helps & Good luck
>>
>> Mo.
>>
>> [image: terminal2.jpg]
>> On Wednesday, June 7, 2023 at 9:22:39 PM UTC+3 Mohammad S. AlMutairi 
>> wrote:
>>
>>> It's an OS issue and for sure it's fixable but without more in-depth 
>>> details I'm shooting in the dark. Trying to help. Try the steps you see 
>>> below in the sequence you see it:
>>>
>>> 1) sudo truncate -s 0 
>>> /var/lib/ubuntu-release-upgrader/release-upgrade-available
>>> 2) sudo dpkg-reconfigure dash
>>> ** make sure to choose no when prompted if you want to (Use dash as the 
>>> default system shell).
>>> 3) ping changelogs.ubuntu.com (make sure if it's resolvable.). If for 
>>> any reason it can't be resolved double check your DNS settings in 
>>> /etc/resolv.conf. You can use google public dns server 8.8.8.8 temporarily.
>>> 4) sudo shutdown -r now
>>> 5) apt update -y && apt upgrade -y && shutdown -r now
>>> 6) You have to upgrade your server to a newer version. You need to.
>>>
>>> Hope it helps.
>>>
>>> Mo.
>>> On Wednesday, June 7, 2023 at 10:23:10 AM UTC+3 Maya Zbitneva wrote:
>>>
 I have Ubuntu 18 LTS and Dspace 6 on another computer which is 
 temporary web server and not real web server. And I have not any such 
 problem which I described above.

 вівторок, 6 червня 2023 р. о 18:58:23 UTC+3 Mohammad S. AlMutairi пише:

> Ubuntu 18.04 LTS reached end of life 6 days ago so I think that what's 
> causing the issues you are facing. Definitely you need to upgrade to a 
> newer Ubuntu version that still supported or as another option you can 
> buy 
> an extended commercial support for the 18.04 version you have to keep 
> using 
> it for a while but still the right decision is to upgrade both the OS and 
> dspae since dspace 6.x will reach end of life too in less than a month 
> from 
> now.
>
> Mo.
>
> On Tuesday, June 6, 2023 at 10:28:05 AM UTC+3 Maya Zbitneva wrote:
>
>> It is not problem with Internet/network, because My Academy Dspace 6 
>> 

Re: [dspace-tech] Re: [dspace-devel] Re: discovery.xml (dspace 7.5)

2023-05-09 Thread darryl....@usask.ca
I've emailed Aroldo my revised discovery.xml directly, but for anyone who 
may come across this thread and be interested, I also created a gist:

https://gist.github.com/g011um/28af989e18e4602d2df63e112cd4428d

- Darryl


On Tuesday, May 9, 2023 at 11:05:33 AM UTC-6 Aroldo Rique wrote:

> Thank you, Darryl!
>
> Please could you send me a copy of your discovery.xml?
>
> You can send it to aro...@gmail.com
>
> Em ter., 9 de mai. de 2023 às 13:51, darryl....@usask.ca <
> darryl@usask.ca> escreveu:
>
>> | That said, maybe someone else on this list can help verify that they've 
>> added custom filters/facets to DSpace 7.
>>
>> We're running DSpace 7.5 on a dev and test server, and have successfully 
>> made changes to the filters.  We re-ordered a couple, removed one or two we 
>> didn't want, and added 3 or 4 based on ETDms metadata (department, program, 
>> degree, etc).  Changes were made to dspace/config/spring/api/discovery.xml
>>
>> I'm never sure what changes DSpace will pick up on the fly and which 
>> require a restart, so now I just always restart Tomcat after every config 
>> change.  In this case I edited discovery.xml, restarted Tomcat, ran the 
>> re-index, restarted Tomcat, then checked the browser to see if the filters 
>> changes were there (they were).
>>
>> I made my changes to both the sidebarFacets and searchFilters sections 
>> of the defaultConfiguration. I wasn't 100% clear on what the difference 
>> between those 2 sections was, but the default Author, Subject (etc) filters 
>> were defined in both places, so I replicated that behaviour.
>>
>> - Darryl
>>
>>
>>
>> On Monday, May 8, 2023 at 1:16:47 PM UTC-6 Aroldo Rique wrote:
>>
>>> Hi, Tim
>>>
>>> Reindexed base, no errors.
>>>
>>> [image: image.png]
>>>
>>> But the new filter still does not appear.
>>>
>>> Aroldo
>>>
>>> Em seg., 8 de mai. de 2023 às 14:29, DSpace Technical Support <
>>> dspac...@googlegroups.com> escreveu:
>>>
>>>> Hi Aroldo,
>>>>
>>>> Make sure that you perform a reindex after adding the new 
>>>> configuration.  You must reindex (./dspace index-discovery -b) all content 
>>>> before new filters/facets will show up.
>>>>
>>>> Developers have added new filters to the codebase during the DSpace 7 
>>>> development process.  As you can see in your screenshots, there's a large 
>>>> number of new filters we've added to support Configurable Entities. So, 
>>>> this should all work.  That said, maybe someone else on this list can help 
>>>> verify that they've added custom filters/facets to DSpace 7.
>>>>
>>>> You may also want to verify that no errors are being thrown in the 
>>>> dspace.log when you perform a reindex, etc.
>>>>
>>>> Tim
>>>>
>>>> On Monday, May 8, 2023 at 12:18:00 PM UTC-5 aro...@gmail.com wrote:
>>>>
>>>>> Hello Tim.
>>>>>
>>>>> Thanks for your help. In dspace6, I can easily add filters, but in 
>>>>> dspace 7.5, even performing the settings you indicated, the new filter 
>>>>> still doesn't appear. Below is the changes I made to my discovery.xml:
>>>>>
>>>>> [image: image.png]
>>>>>
>>>>> I also created the searchFilterUnidade, with the metadata I want and 
>>>>> the bean sortUnidade:
>>>>>
>>>>> [image: image.png]
>>>>>
>>>>> [image: image.png]
>>>>>
>>>>>
>>>>> Even so, the filter still does not appear on the screen.
>>>>>
>>>>> Has anyone already working with dspace 7.x successfully added filters?
>>>>>
>>>>> Aroldo
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Em seg., 8 de mai. de 2023 às 13:03, DSpace Technical Support <
>>>>> dspac...@googlegroups.com> escreveu:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I believe you need to change the "sidebarFacets" under the 
>>>>>> "defaultConfiguration" (which is the one used by default on the search 
>>>>>> page) around here in the discovery.xml:
>>>>>>
>>>>>> https://github.com/DSpace/DSpace/blob/main/dspace/config/spring/api/discovery.xml#L166-L174

Re: [dspace-tech] Re: [dspace-devel] Re: discovery.xml (dspace 7.5)

2023-05-09 Thread darryl....@usask.ca
| That said, maybe someone else on this list can help verify that they've 
added custom filters/facets to DSpace 7.

We're running DSpace 7.5 on a dev and test server, and have successfully 
made changes to the filters.  We re-ordered a couple, removed one or two we 
didn't want, and added 3 or 4 based on ETDms metadata (department, program, 
degree, etc).  Changes were made to dspace/config/spring/api/discovery.xml

I'm never sure what changes DSpace will pick up on the fly and which 
require a restart, so now I just always restart Tomcat after every config 
change.  In this case I edited discovery.xml, restarted Tomcat, ran the 
re-index, restarted Tomcat, then checked the browser to see if the filters 
changes were there (they were).

I made my changes to both the sidebarFacets and searchFilters sections of 
the defaultConfiguration. I wasn't 100% clear on what the difference 
between those 2 sections was, but the default Author, Subject (etc) filters 
were defined in both places, so I replicated that behaviour.

- Darryl



On Monday, May 8, 2023 at 1:16:47 PM UTC-6 Aroldo Rique wrote:

> Hi, Tim
>
> Reindexed base, no errors.
>
> [image: image.png]
>
> But the new filter still does not appear.
>
> Aroldo
>
> Em seg., 8 de mai. de 2023 às 14:29, DSpace Technical Support <
> dspac...@googlegroups.com> escreveu:
>
>> Hi Aroldo,
>>
>> Make sure that you perform a reindex after adding the new configuration.  
>> You must reindex (./dspace index-discovery -b) all content before new 
>> filters/facets will show up.
>>
>> Developers have added new filters to the codebase during the DSpace 7 
>> development process.  As you can see in your screenshots, there's a large 
>> number of new filters we've added to support Configurable Entities. So, 
>> this should all work.  That said, maybe someone else on this list can help 
>> verify that they've added custom filters/facets to DSpace 7.
>>
>> You may also want to verify that no errors are being thrown in the 
>> dspace.log when you perform a reindex, etc.
>>
>> Tim
>>
>> On Monday, May 8, 2023 at 12:18:00 PM UTC-5 aro...@gmail.com wrote:
>>
>>> Hello Tim.
>>>
>>> Thanks for your help. In dspace6, I can easily add filters, but in 
>>> dspace 7.5, even performing the settings you indicated, the new filter 
>>> still doesn't appear. Below is the changes I made to my discovery.xml:
>>>
>>> [image: image.png]
>>>
>>> I also created the searchFilterUnidade, with the metadata I want and the 
>>> bean sortUnidade:
>>>
>>> [image: image.png]
>>>
>>> [image: image.png]
>>>
>>>
>>> Even so, the filter still does not appear on the screen.
>>>
>>> Has anyone already working with dspace 7.x successfully added filters?
>>>
>>> Aroldo
>>>
>>>
>>>
>>>
>>>
>>>
>>> Em seg., 8 de mai. de 2023 às 13:03, DSpace Technical Support <
>>> dspac...@googlegroups.com> escreveu:
>>>
 Hi,

 I believe you need to change the "sidebarFacets" under the 
 "defaultConfiguration" (which is the one used by default on the search 
 page) around here in the discovery.xml:

 https://github.com/DSpace/DSpace/blob/main/dspace/config/spring/api/discovery.xml#L166-L174

 The docs on this are here: 
 https://wiki.lyrasis.org/display/DSDOC7x/Discovery#Discovery-ConfiguringlistsofsidebarFacetsandsearchFilters
 And here's how to create a brand new filter/facet: 
 https://wiki.lyrasis.org/display/DSDOC7x/Discovery#Discovery-Searchfilters
   
 (There are plenty of examples in the discovery.xml near the bottom)

 Keep in mind, as it says in the documentation, you will need to do a 
 *full reindex of all content* before the changes will take effect.

 Tim
 On Saturday, May 6, 2023 at 2:46:02 PM UTC-5 aro...@gmail.com wrote:

> In short, Tim: after searching for a term (blue), where in the 
> discovery.xml (which section) should I change to include a filter (red)?
> [image: image.png]
>
>
>
>
> Em sex., 5 de mai. de 2023 às 12:59, 'Tim Donohue' via DSpace 
> Developers  escreveu:
>
>> Hi Aroldo,
>>
>> As far as I'm aware, adding filters in DSpace 7 should be the same as 
>> in DSpace 6.  While there have been new sections added to the 
>> discovery.xml, the structure of that file is unchanged.  So, the 
>> existing 
>> documentation *should still be accurate* for DSpace 7.  If you are 
>> finding 
>> it is *not* accurate, then please do let us know and we can look into it 
>> further.
>>
>> Tim
>>
>> On Thursday, May 4, 2023 at 8:47:09 PM UTC-5 aro...@gmail.com wrote:
>>
>>> Hey guys!
>>>
>>> I'm having trouble inserting new filters into dspace 7.5 search. We 
>>> are migrating a digital repository from version 6 to version 7.5 and, 
>>> one 
>>> of our demands is the addition of filters to the filters that already 
>>> exist, by default, in dspace 7.5.
>>>
>>> I checked the dspace 6 discovery.xml 

[dspace-tech] Re: index-discovery

2023-05-02 Thread darryl....@usask.ca

Are you sure your Solr server is running on port 8080?  I think the default 
port is 8983.

- Darryl


On Tuesday, May 2, 2023 at 1:54:09 PM UTC-6 Matías Javier Saavedra Gajardo 
wrote:

> Help I don't know how to solve this error with solr when indexing my 
> database.
>
> Exception: Server refused connection at: http://localhost:8080/solr/search
> org.dspace.discovery.SearchServiceException: Server refused connection at: 
> http://localhost:8080/solr/search
> at 
> org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:494)
> at org.dspace.discovery.IndexClient.main(IndexClient.java:151)
> 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)
> Caused by: org.apache.solr.client.solrj.SolrServerException: Server 
> refused connection at: http://localhost:8080/solr/search
> at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:559)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
> at 
> org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:91)
> at org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:310)
> at 
> org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:465)
> ... 7 more
> Caused by: java.net.ConnectException: Conexión rehusada (Connection 
> refused)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at 
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at 
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at 
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:607)
> at 
> org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:117)
> at 
> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
> at 
> org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
> at 
> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
> at 
> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
> at 
> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:882)
> at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
> at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:448)
> ... 12 more
>

-- 
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/d9b0967e-4e29-4a4f-a340-15111d935a9an%40googlegroups.com.


Re: [dspace-tech] [DSpace Angular] Adding new modules & routes to RouterModule from a theme

2023-05-01 Thread darryl....@usask.ca
I'm in the same boat here.  I'm wanting/needing to create some (themed) 
local components for things like an About page, FAQ, submission guidelines 
etc.  The closest examples I can see are the privacy policy and end user 
license agreement pages.  These seem to be controlled by the Info module in 
src/app/info. I'd happily have my URLs be something like "info/about" and 
"info/faq" if there were some easy way to have that info module implement a 
"hook" (as Abel said) or some sort of route/component mapping (similar to 
what's being done in info-routing-paths.ts and info-routing.module.ts) that 
we could define in our theme.  i.e. some localized way to add to that 
RouterModule that's being built in info-routing.module.ts so we could 
easily add components and paths without changing that core code.

Sadly, I'm not familiar enough with Angular to design and implement that.  
Looks like I may have to resort to a more global hack, like Mark did.

- Darryl


On Monday, April 17, 2023 at 10:09:54 AM UTC-6 Abel Gómez wrote:

> Ouch!
>
> I'm sorry to hear that modifying the stock routing module was the only 
> way...
>
> Anyway, it's true that, although it's a "hack", the modifications can be 
> minimal.
>
> Thanks for sharing your experience on this. Let's see if a "hooking" 
> mechanism is added to the routing module in the future... If I have time, 
> I'll try to implement something more portable/themable.
>
> Cheers,
>
> Abel
>
> El viernes, 14 de abril de 2023 a las 15:20:29 UTC+2, Mark H. Wood 
> escribió:
>
>> On Thu, Apr 13, 2023 at 01:58:51PM -0700, Abel Gómez wrote: 
>> > I've been working on a theme and customization for DSpace 7, and I've 
>> > stumbled upon a problem I'm not really sure whether it's solvable or 
>> not. 
>> > 
>> > I'd like to add some additional routes and modules to serve some 
>> additional 
>> > sections in the DSpace site (mostly static HTML) but keeping the look 
>> and 
>> > feel of my custom theme, and keeping the breadcrumbs and navigation 
>> > features if possible. After inspecting the code, I've figured out the 
>> way 
>> > to do it by modifying the "base app" (e.g., AppRoutingModule, and 
>> adding 
>> > the needed modules under src/app/...), but I'd like to keep my 
>> > modifications as modular and isolated as possible. 
>> > 
>> > Is there any way to achieve the same by modifying only my custom theme 
>> in 
>> > "src/themes/mytheme", and without changing the "base code" of DSpace 
>> > angular in "src/app"? 
>>
>> I haven't found a way to completely eliminate hacks to the stock 
>> routing module, but I did manage a static "About Us" page that exists 
>> within our local theme and requires only a reference in 
>> 'src/app/app-routing.module.ts': 
>>
>>  src/app/app-routing.module.ts 
>>  
>> index d426b041c..2d5b27797 100644 
>> @@ -41,9 +41,12 @@ import { ServerCheckGuard } from 
>> './core/server-check/server-check.guard'; 
>> import { MenuResolver } from './menu.resolver'; 
>> import { ThemedPageErrorComponent } from 
>> './page-error/themed-page-error.component'; 
>>
>> +import { AboutComponent } from 
>> '../themes/scholarworks/app/static/about/about-page.component'; 
>> + 
>> @NgModule({ 
>> imports: [ 
>> RouterModule.forRoot([ 
>> + { path: 'about', component: AboutComponent }, 
>> { path: INTERNAL_SERVER_ERROR, component: 
>> ThemedPageInternalServerErrorComponent }, 
>> { path: ERROR_PAGE , component: ThemedPageErrorComponent }, 
>> { 
>>
>> AboutComponent consists of an empty class, an empty stylesheet, and a 
>> single 'div' providing a basic description of the repo. plus links to 
>> further reading and a 'mailto:'. 
>>
>> The close coupling between stock and theme led me to leave this commit 
>> message: 
>>
>> Add a link and an About page. 
>>
>> This required adding the route in the main routing module, pointing into 
>> our 
>> theme. That is a nasty hack and should be fixed when I find out how to 
>> put 
>> the route into our theme's module. 
>>
>> -- 
>> Mark H. Wood 
>> Lead Technology Analyst 
>>
>> University Library 
>> Indiana University - Purdue University Indianapolis 
>> 755 W. Michigan Street 
>> Indianapolis, IN 46202 
>> 317-274-0749 <(317)%20274-0749> 
>> www.ulib.iupui.edu 
>>
>

-- 
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/b826fc77-6bed-478e-bfff-ffb7a3e8ffe2n%40googlegroups.com.


[dspace-tech] Re: UI 500 error when run in yarn start:dev

2023-04-20 Thread darryl....@usask.ca
This might be CORS related.  I've been doing frontend theme development on 
my local workstation, with the backend running on our remote dev server.  
Because "localhost" doesn't match the hostname of the backend server in 
this configuration, it triggers CORS issues and all I see on the frontend 
is a 500 error.

To fix this I had to adjust rest.cors.allowed-origins in local.cfg on the 
backend server like this:

rest.cors.allowed-origins = ${dspace.ui.url}, http://localhost:4000

That allowed both the prod built frontend on the remote server and the dev 
mode on my local machine to work.  So I'd recommend checking the browser to 
see if CORS errors might be the reason you're seeing that 500.

- Darryl


On Thursday, April 20, 2023 at 7:28:07 AM UTC-6 amtuan...@gmail.com wrote:

> Hi all
>
> I am trying to do customization of the theme and following the 
> instructions here 
> https://wiki.lyrasis.org/plugins/servlet/mobile?contentId=208342816#content/view/208342816
>
> I have identical config.dev.yml and config.prod.yml
>
> When I run the UI with yarn start:dev, the UI shows error 500 but is 
> working perfectly with yarn start:prod
>
> I have checked the backend logs and there is no error whatsoever as it is 
> running perfectly with the UI in prod mode.
>
> I'd appreciate any help with best practices for doing UI customization.
>
>
> Thanks,
> Tuan
>

-- 
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/418a933f-a2d2-4efd-bb47-791cf576cd85n%40googlegroups.com.


[dspace-tech] Re: Permanent URI for this community http://localhost:4000/handle/...

2023-04-13 Thread darryl....@usask.ca
Have a look at the handle.canonical.prefix and handle.prefix in your 
local.cfg file.  There's some documentation (in the form of comments) in 
dspace.cfg and also 
here: https://wiki.lyrasis.org/display/DSDOC7x/Configuration+Reference in 
the Handle Server Configuration section.

The default value for handle.canonical.prefix  is  ${dspace.ui.url}/handle/ and 
your dspace.ui.url must be http://localhost:4000 which is why you are 
seeing community/collections URLs like that.

- Darryl


On Thursday, April 13, 2023 at 12:11:38 PM UTC-6 Costantino, Fernán wrote:

> Hi, I was trying to understand how to fix this.
>
> "Permanent URI for this community" link to http://localhost:4000/handle/... 
> instead of dspace.ui.url (dspace.cfg)
>
> There are some discussions/issues on github (for example: 
> https://github.com/DSpace/dspace-angular/issues/887 ), but is difficult 
> to me to follow the thread. Can someone explain the procedure to solve it? 
> It seems that I need to modify some code? Thanks.
> -- 
>
> *Costantino, Fernán*
> División Nuevas Tecnologías
> Biblioteca Central Francisco P. Moreno
> Universidad Nacional del Comahue
> Santa Fe y Leloir (Q8300) Neuquén Cap.- Tel 54(0299)4490398
>
>

-- 
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/52edda77-b00c-4c12-b09e-8de5937acf26n%40googlegroups.com.


[dspace-tech] Re: Cover Pages with 7.x?

2023-04-04 Thread darryl....@usask.ca
Just as an FYI to anyone that might stumble across this, through trial and 
error I discovered that removing the citation-page.enabled_communities 
setting from my local.cfg solved the problem. I haven't looked into the 
DSpace code to sort out why that may be.  The communities we had listed in 
that setting existed.  We only wanted cover page generation on a couple of 
our communities, so I was able to just list the collections individually in 
citation-page.enabled_collections and achieve the same effect.

- Darryl


On Tuesday, April 4, 2023 at 3:37:20 PM UTC-6 darryl@usask.ca wrote:

> Is anyone using the cover page generation with 7.x (specifically 7.5)?
>
> Building the backend seems to work without issue, but when I include the 
> settings from citation-page.cfg in my local.cfg file I get the errors below 
> in my dspace.log during startup.
>
> We're attempting to enable this for just a couple of collections using the 
> citation-page.enabled_collections setting, and the other settings are 
> just local tweaks to the default examples (using our own institution names, 
> URL etc).
>
> Is anyone using cover pages with 7.x?  Any hints on what might be causing 
> the error below?
>
> Thanks!
>
> - Darryl
>
>
>
> 2023-04-04 14:00:15,814 WARN  unknown unknown 
> org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext
>  
> @ Exception encountered during context initialization - cancelling refresh 
> attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: 
> Error creating bean with name 'bitstreamRestController': Unsatisfied 
> dependency expressed through field 'citationDocumentService'; nested 
> exception is org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 
> 'org.dspace.disseminate.CitationDocumentServiceImpl#0' defined in file 
> [/data/dspace/config/spring/api/core-services.xml]: Invocation of init 
> method failed; nested exception is java.lang.UnsupportedOperationException
> 2023-04-04 14:00:15,837 INFO  unknown unknown 
> org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener
>  
> @
>
> Error starting ApplicationContext. To display the conditions report re-run 
> your application with 'debug' enabled.
> 2023-04-04 14:00:15,873 ERROR unknown unknown 
> org.springframework.boot.SpringApplication @ Application run failed
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
> creating bean with name 'bitstreamRestController': Unsatisfied dependency 
> expressed through field 'citationDocumentService'; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating 
> bean with name 'org.dspace.disseminate.CitationDocumentServiceImpl#0' 
> defined in file [/data/dspace/config/spring/api/core-services.xml]: 
> Invocation of init method failed; nested exception is 
> java.lang.UnsupportedOperationException
> at 
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.resolveFieldValue(AutowiredAnnotationBeanPostProcessor.java:659)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
> at 
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:639)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
> at 
> org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:119)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
> at 
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:399)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1431)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:619)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
> at 
> org.springframework.beans.factory.s

[dspace-tech] Cover Pages with 7.x?

2023-04-04 Thread darryl....@usask.ca
Is anyone using the cover page generation with 7.x (specifically 7.5)?

Building the backend seems to work without issue, but when I include the 
settings from citation-page.cfg in my local.cfg file I get the errors below 
in my dspace.log during startup.

We're attempting to enable this for just a couple of collections using the 
citation-page.enabled_collections setting, and the other settings are just 
local tweaks to the default examples (using our own institution names, URL 
etc).

Is anyone using cover pages with 7.x?  Any hints on what might be causing 
the error below?

Thanks!

- Darryl



2023-04-04 14:00:15,814 WARN  unknown unknown 
org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext
 
@ Exception encountered during context initialization - cancelling refresh 
attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: 
Error creating bean with name 'bitstreamRestController': Unsatisfied 
dependency expressed through field 'citationDocumentService'; nested 
exception is org.springframework.beans.factory.BeanCreationException: Error 
creating bean with name 
'org.dspace.disseminate.CitationDocumentServiceImpl#0' defined in file 
[/data/dspace/config/spring/api/core-services.xml]: Invocation of init 
method failed; nested exception is java.lang.UnsupportedOperationException
2023-04-04 14:00:15,837 INFO  unknown unknown 
org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener
 
@

Error starting ApplicationContext. To display the conditions report re-run 
your application with 'debug' enabled.
2023-04-04 14:00:15,873 ERROR unknown unknown 
org.springframework.boot.SpringApplication @ Application run failed
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'bitstreamRestController': Unsatisfied dependency 
expressed through field 'citationDocumentService'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating 
bean with name 'org.dspace.disseminate.CitationDocumentServiceImpl#0' 
defined in file [/data/dspace/config/spring/api/core-services.xml]: 
Invocation of init method failed; nested exception is 
java.lang.UnsupportedOperationException
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.resolveFieldValue(AutowiredAnnotationBeanPostProcessor.java:659)
 
~[spring-beans-5.3.20.jar:5.3.20]
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:639)
 
~[spring-beans-5.3.20.jar:5.3.20]
at 
org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:119)
 
~[spring-beans-5.3.20.jar:5.3.20]
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:399)
 
~[spring-beans-5.3.20.jar:5.3.20]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1431)
 
~[spring-beans-5.3.20.jar:5.3.20]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:619)
 
~[spring-beans-5.3.20.jar:5.3.20]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542)
 
~[spring-beans-5.3.20.jar:5.3.20]
at 
org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
 
~[spring-beans-5.3.20.jar:5.3.20]
at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
 
~[spring-beans-5.3.20.jar:5.3.20]
at 
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)
 
~[spring-beans-5.3.20.jar:5.3.20]
at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
 
~[spring-beans-5.3.20.jar:5.3.20]
at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:953)
 
~[spring-beans-5.3.20.jar:5.3.20]
at 
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918)
 
~[spring-context-5.3.20.jar:5.3.20]
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583)
 
~[spring-context-5.3.20.jar:5.3.20]
at 
org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145)
 
~[spring-boot-2.6.8.jar:2.6.8]
at 
org.springframework.boot.SpringApplication.refresh(SpringApplication.java:745) 

Re: [dspace-tech] Re: handle server quits after ubuntu upgrade

2023-03-24 Thread darryl....@usask.ca
A million thanks to you Edmund!  I patched our RHEL 7 server last night and 
got bit by this.  I was able to drop your JAR file into place and get us 
back up and running fairly quickly.

- Darryl

On Monday, December 12, 2022 at 6:52:29 AM UTC-6 Sean Carte wrote:

> Thank you for this, Edmund!
>
> Sean
>
> On Tue, 15 Nov 2022 at 00:58, Edmund Balnaves  
> wrote:
>
>> The compiled handle.jar file is available at 
>> https://release.prosentient.com.au/handle62/handle.jar.gz
>> It can be used to replace the handle-6.2.jar reference in the dspace 6.4 
>> build or copied directly to the target directly to the target directories - 
>> particularly of course lib
>>
>> ./lib/handle-6.2.jar
>> ./webapps/jspui/WEB-INF/lib/handle-6.2.jar
>> ./webapps/xmlui/WEB-INF/lib/handle-6.2.jar
>> ./webapps/swordv2/WEB-INF/lib/handle-6.2.jar
>> ./webapps/rdf/WEB-INF/lib/handle-6.2.jar
>> ./webapps/rest/WEB-INF/lib/handle-6.2.jar
>> ./webapps/sword/WEB-INF/lib/handle-6.2.jar
>> ./webapps/oai/WEB-INF/lib/handle-6.2.jar
>>
>> I have shared the build source at 
>> https://release.prosentient.com.au/handle62/handle6.2patched.tar.gz
>>
>> The base is hdl 6.2.05 code from handle.net
>>
>> Note that this does not contain the cnriutil references.
>>
>> I compiled lib/cnriutil.jar derived from the classes in the dspace 
>> version of handle-6.2.jar
>>
>> To achieve a distribution I modified the build.xml to remove references 
>> to the admintools. I'm guessing this must have been done before with the 
>> dspace distro.
>>
>> I modified
>> ./net/handle/server/Main.java
>> to remove System.runFinalizersOnExit(true);
>>
>> Further work could be done to replace this with an alternative code
>> Runtime.addShutdownHook(new Runnable() {
>> public void run(){
>> // do whatever handle.net needs to exit cleaning on error();
>> }
>> });
>>
>> However I have tested the above simple change successfully in an updated 
>> ubuntu server running the dspace handle resolver.
>> Not tested for long term service operation, so there is a risk the above 
>> change might lead to some memory leakage. However the fact that the handle 
>> service runs seperately makes it easy to monitor.
>>
>> The build process is:
>> ant clean
>> ant server
>> ant distjar
>>
>> The build output is in the dist folder
>>
>> Hope this helps.
>>
>> Edmund
>>
>>
>> On Tuesday, November 15, 2022 at 2:03:43 AM UTC+11 cpgr...@gmail.com 
>> wrote:
>>
>>> Thank you for your message.
>>>
>>> We are considering rolling back our server to Nov 10th when the Ubuntu 
>>> upgrade happened. Your fixed jar file would be a better quick fix.
>>> Would you please send me a copy of the jar file and where I should put 
>>> it? I notice multiple copies of that jar all over the server and I don't 
>>> know which one it is crucial to replace and what to do to make it active.
>>>
>>> On Saturday, November 12, 2022 at 6:36:46 AM UTC-5 edmund@gmail.com 
>>> wrote:
>>>
 This is a problem with the latest release of java (openjdk version 
 "1.8.0_352").  It has now removed the deprecated class runFinalizersOnExit 

 This class is used by the embedded handle.net jar classes to provide 
 the resolver functions for the handle server.

 This is distributed via the maven libraries.There is testing going 
 on upgraded to use a later handle.net distribution.  

 I have tested a working alternative by rebuilding handle-6.2.jar with a 
 minor change to ./net/handle/server/Main.java to comment out the now 
 discontinued class at line 124
 //System.runFinalizersOnExit(true);

 After rebuild the handle jar and replacing it in the target 
 directories, the Handle server starts successfully and I have tested with 
 a 
 live configuration - handle resolving completes successfuling.

 This could provide alternative for some to get a server live.

 Happy to share the build to project the above jar and/or the jar itself

 Gives us a fall-back solution at least.  Hopefully formal fix will be 
 out soon.

 On Saturday, November 12, 2022 at 3:17:40 AM UTC+11 cpgr...@gmail.com 
 wrote:

> We did an upgrade to Ubuntu last night and now our handle server quits 
> immediately on trying to start it. Unfortunately, the person who set 
> up 
> our handle server has left our organization.
>
> Our handle-server.log reports:
>
> "2022/11/11 10:27:43 EST" 25 Rotating log files
> Error: null
> (see the error log for details.)
>
> Shutting down...
>
> and the error.log reports:
>
> "2022/11/11 10:27:43 EST" 25 Started new run.
> java.lang.UnsupportedOperationException
>  at java.lang.Runtime.runFinalizersOnExit(Runtime.java:287)
>  at java.lang.System.runFinalizersOnExit(System.java:1059)
>  at net.handle.server.Main.initialize(Main.java:124)
>  at net.handle.server.Main.main(Main.java:75)
> 

Re: [dspace-tech] ORCID autohority in DSpac 7.5

2023-03-07 Thread darryl....@usask.ca
(sorry, hit the post button too soon)

I'm now seeing the same error in the logs you noted in  8436 
https://github.com/DSpace/DSpace/issues/8436#issuecomment-1249577192 

While I'm a little bummed the ORCID stuff is still not quite there yet, its 
at least reassuring to know that my setup is working as well as can be 
expected right now.

Thanks again!

- Darryl

On Tuesday, March 7, 2023 at 11:27:16 AM UTC-6 darryl@usask.ca wrote:

> Thanks Sean.  With the sections of orcid-authority-services.xml 
> uncommented, and a correction to a typo in my local.cfg I'm now seeing 
> results back from the ORCID API. Like you, I'm using the public URLs for 
> both orcid.api-url and orcid.public-url.
>
> On Tuesday, March 7, 2023 at 10:31:59 AM UTC-6 Sean Kalynuk wrote:
>
>> Hi Darryl and Milos,
>>
>>  
>>
>> You do need to uncomment the proper sections in 
>> orcid-authority-services.xml. I had the same “No bean named 
>> ‘AuthoritySource’ available” error until I modified the configuration. The 
>> relevant comment is the one I made here: 
>>
>> https://github.com/DSpace/DSpace/issues/8436#issuecomment-1248565724
>>
>>  
>>
>> However, Milos, I compared your orcid-authority-services.xml to mine and 
>> they are identical (ignoring whitespace).
>>
>>  
>>
>> One difference I did notice in the config is that I am using the public 
>> ORCID API for testing:
>>
>>  
>>
>> orcid.api-url = https://pub.orcid.org/v3.0
>>
>>  
>>
>> whereas you are using the member API:
>>
>>  
>>
>> orcid.api-url = https://api.orcid.org/v3.0
>>
>>  
>>
>> I have not configured full ORCID integration yet, and am only using the 
>> public API for author lookup. Perhaps you could try with the public API 
>> just for author lookup to see if that would work first? I have been using 
>> the developer credentials for my personal ORCID account for testing and it 
>> has connected and found ORCID records while searching for a 
>> dc.contributor.author value in a submission form.
>>
>>  
>>
>> One thing to point out though is that there is an outstanding bug with 
>> the “will be generated” authority keys related to ORCID authority records:
>>
>>  
>>
>> https://github.com/DSpace/DSpace/issues/8490
>>
>>  
>>
>> This occurs with newly found ORCID records from the ORCID API (not those 
>> in your authority Solr core) since they need to have authority keys 
>> generated.
>>
>>  
>>
>> --
>>
>> Sean
>>
>>  
>>
>> *From: *dspac...@googlegroups.com  on behalf 
>> of darryl@usask.ca 
>> *Date: *Monday, March 6, 2023 at 5:35 PM
>> *To: *DSpace Technical Support 
>> *Subject: *Re: [dspace-tech] ORCID autohority in DSpac 7.5
>>
>> *Caution:* This message was sent from outside the University of Manitoba.
>>
>>
>> Milos, do you see anything in your logs/dspace.log file related to 
>> ORCID?  I can't seem to get the ORCID lookup working either.  I've double 
>> and triple checked all my config and I can't find any issues.  However, in 
>> my DSpace logs I see the same "No bean named 'AuthoritySource' available" 
>> and " org.dspace.content.authority.SolrAuthority @ external source for 
>> authority not configured" warnings mentioned in issue 8436 -- 
>> https://github.com/DSpace/DSpace/issues/8436 and I'm curious if that is 
>> showing up for you as well.
>>
>>  
>>
>> There's a comment in that issue that mentions uncommenting some code 
>> in dspace/config/spring/api/orcid-authority-services.xml which I haven't 
>> looked into yet.  I also see that this issue was moved to the DSpace 7.6 
>> To-Do list by Tim Donohue.  I wondering if maybe the ORCID lookup stuff is 
>> still not quite ready for production usage?
>>
>>  
>>
>> - Darryl
>>
>>  
>>
>>  
>>
>>  
>>
>> On Monday, March 6, 2023 at 7:12:03 AM UTC-6 Milos Ivanovic wrote:
>>
>> Besides author lookup using ORCID (which is my primary use case), in 
>> order to check the communication with ORCID API, I also tried to configure 
>> ORCID authentication. No luck. The ORCID account has a publicly visible 
>> email, bound to the DSpace account, my site is HTTPS enabled, but it's 
>> still not working :( 
>>
>>  
>>
>> Can anyone send me an anonymized working config or any other advice on 
>> what to check? Thanks in advance.
>>
>>  
>>
>> Kind regards
>>
>> Mi

Re: [dspace-tech] ORCID autohority in DSpac 7.5

2023-03-07 Thread darryl....@usask.ca
Thanks Sean.  With the sections of orcid-authority-services.xml 
uncommented, and a correction to a typo in my local.cfg I'm now seeing 
results back from the ORCID API. Like you, I'm using the public URLs for 
both orcid.api-url and orcid.public-url.

On Tuesday, March 7, 2023 at 10:31:59 AM UTC-6 Sean Kalynuk wrote:

> Hi Darryl and Milos,
>
>  
>
> You do need to uncomment the proper sections in 
> orcid-authority-services.xml. I had the same “No bean named 
> ‘AuthoritySource’ available” error until I modified the configuration. The 
> relevant comment is the one I made here: 
>
> https://github.com/DSpace/DSpace/issues/8436#issuecomment-1248565724
>
>  
>
> However, Milos, I compared your orcid-authority-services.xml to mine and 
> they are identical (ignoring whitespace).
>
>  
>
> One difference I did notice in the config is that I am using the public 
> ORCID API for testing:
>
>  
>
> orcid.api-url = https://pub.orcid.org/v3.0
>
>  
>
> whereas you are using the member API:
>
>  
>
> orcid.api-url = https://api.orcid.org/v3.0
>
>  
>
> I have not configured full ORCID integration yet, and am only using the 
> public API for author lookup. Perhaps you could try with the public API 
> just for author lookup to see if that would work first? I have been using 
> the developer credentials for my personal ORCID account for testing and it 
> has connected and found ORCID records while searching for a 
> dc.contributor.author value in a submission form.
>
>  
>
> One thing to point out though is that there is an outstanding bug with the 
> “will be generated” authority keys related to ORCID authority records:
>
>  
>
> https://github.com/DSpace/DSpace/issues/8490
>
>  
>
> This occurs with newly found ORCID records from the ORCID API (not those 
> in your authority Solr core) since they need to have authority keys 
> generated.
>
>  
>
> --
>
> Sean
>
>  
>
> *From: *dspac...@googlegroups.com  on behalf 
> of darryl@usask.ca 
> *Date: *Monday, March 6, 2023 at 5:35 PM
> *To: *DSpace Technical Support 
> *Subject: *Re: [dspace-tech] ORCID autohority in DSpac 7.5
>
> *Caution:* This message was sent from outside the University of Manitoba.
>
>
> Milos, do you see anything in your logs/dspace.log file related to ORCID?  
> I can't seem to get the ORCID lookup working either.  I've double and 
> triple checked all my config and I can't find any issues.  However, in my 
> DSpace logs I see the same "No bean named 'AuthoritySource' available" and 
> " org.dspace.content.authority.SolrAuthority @ external source for 
> authority not configured" warnings mentioned in issue 8436 -- 
> https://github.com/DSpace/DSpace/issues/8436 and I'm curious if that is 
> showing up for you as well.
>
>  
>
> There's a comment in that issue that mentions uncommenting some code 
> in dspace/config/spring/api/orcid-authority-services.xml which I haven't 
> looked into yet.  I also see that this issue was moved to the DSpace 7.6 
> To-Do list by Tim Donohue.  I wondering if maybe the ORCID lookup stuff is 
> still not quite ready for production usage?
>
>  
>
> - Darryl
>
>  
>
>  
>
>  
>
> On Monday, March 6, 2023 at 7:12:03 AM UTC-6 Milos Ivanovic wrote:
>
> Besides author lookup using ORCID (which is my primary use case), in order 
> to check the communication with ORCID API, I also tried to configure ORCID 
> authentication. No luck. The ORCID account has a publicly visible email, 
> bound to the DSpace account, my site is HTTPS enabled, but it's still not 
> working :( 
>
>  
>
> Can anyone send me an anonymized working config or any other advice on 
> what to check? Thanks in advance.
>
>  
>
> Kind regards
>
> Milos
>
>  
>
> петак, 3. март 2023. у 17:34:24 UTC+1 Milos Ivanovic је написао/ла:
>
> Sorry, I have forgotten to mention it. This setting is ok too. 
>
>  
>
>  
>
> петак, 3. март 2023. у 16:46:43 UTC+1 Sean Kalynuk је написао/ла:
>
> Hi Milos,
>
>  
>
> Do you also have:
>
>  
>
> plugin.named.org.dspace.content.authority.ChoiceAuthority = \
>
>   org.dspace.content.authority.SolrAuthority = SolrAuthorAuthority
>
>  
>
> I don’t see it in your config (at least in this message).
>
>  
>
> It is commented out by default in 
> [your-dspace-home]/config/modules/authority.cfg
>
>  
>
> --
>
> Sean
>
>  
>
> *From: *dspac...@googlegroups.com  on behalf 
> of Milos Ivanovic 
> *Date: *Friday, March 3, 2023 at 4:17 AM
> *To: *DSpace Technical Support 
> *Subject: *[dspace-tech] ORCID autohority in 

Re: [dspace-tech] ORCID autohority in DSpac 7.5

2023-03-06 Thread darryl....@usask.ca
Milos, do you see anything in your logs/dspace.log file related to ORCID?  
I can't seem to get the ORCID lookup working either.  I've double and 
triple checked all my config and I can't find any issues.  However, in my 
DSpace logs I see the same "No bean named 'AuthoritySource' available" and 
" org.dspace.content.authority.SolrAuthority @ external source for 
authority not configured" warnings mentioned in issue 8436 
-- https://github.com/DSpace/DSpace/issues/8436 and I'm curious if that is 
showing up for you as well.

There's a comment in that issue that mentions uncommenting some code 
in dspace/config/spring/api/orcid-authority-services.xml which I haven't 
looked into yet.  I also see that this issue was moved to the DSpace 7.6 
To-Do list by Tim Donohue.  I wondering if maybe the ORCID lookup stuff is 
still not quite ready for production usage?

- Darryl



On Monday, March 6, 2023 at 7:12:03 AM UTC-6 Milos Ivanovic wrote:

> Besides author lookup using ORCID (which is my primary use case), in order 
> to check the communication with ORCID API, I also tried to configure ORCID 
> authentication. No luck. The ORCID account has a publicly visible email, 
> bound to the DSpace account, my site is HTTPS enabled, but it's still not 
> working :( 
>
> Can anyone send me an anonymized working config or any other advice on 
> what to check? Thanks in advance.
>
> Kind regards
> Milos
>
> петак, 3. март 2023. у 17:34:24 UTC+1 Milos Ivanovic је написао/ла:
>
>> Sorry, I have forgotten to mention it. This setting is ok too. 
>>
>>
>> петак, 3. март 2023. у 16:46:43 UTC+1 Sean Kalynuk је написао/ла:
>>
>>> Hi Milos,
>>>
>>>  
>>>
>>> Do you also have:
>>>
>>>  
>>>
>>> plugin.named.org.dspace.content.authority.ChoiceAuthority = \
>>>
>>>   org.dspace.content.authority.SolrAuthority = SolrAuthorAuthority
>>>
>>>  
>>>
>>> I don’t see it in your config (at least in this message).
>>>
>>>  
>>>
>>> It is commented out by default in 
>>> [your-dspace-home]/config/modules/authority.cfg
>>>
>>>  
>>>
>>> --
>>>
>>> Sean
>>>
>>>  
>>>
>>> *From: *dspac...@googlegroups.com  on behalf 
>>> of Milos Ivanovic 
>>> *Date: *Friday, March 3, 2023 at 4:17 AM
>>> *To: *DSpace Technical Support 
>>> *Subject: *[dspace-tech] ORCID autohority in DSpac 7.5
>>>
>>> *Caution:* This message was sent from outside the University of 
>>> Manitoba.
>>>
>>>  
>>>
>>> Dear All,
>>>
>>>  
>>>
>>> I am trying to enable ORCID authority according to 
>>> https://wiki.lyrasis.org/display/DSDOC7x/ORCID+Authority. However,  the 
>>> suggestions from the ORCID API do not appear in the  Author field of the 
>>> "Submit new item" component. The relevant part of *local.cfg* looks 
>>> like this:
>>>
>>>  
>>>
>>> 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
>>> auto-update-items = true
>>> event.dispatcher.default.consumers = authority, versioning, discovery, 
>>> eperson
>>> orcid.domain-url= https://orcid.org
>>> orcid.api-url = https://api.orcid.org/v3.0
>>> orcid.public-url = https://pub.orcid.org/v3.0
>>> orcid.application-client-id = APP- 
>>> orcid.application-client-secret = 
>>>
>>>  
>>>
>>> The API is normally enabled in my ORCID profile. Also, 
>>> *orcid-authority-services.xml* is attached. There are no traces of 
>>> erroneous (or any other) ORCID API requests in DSpace and Tomcat logs. 
>>>
>>>  
>>>
>>> Am I missing something obvious?
>>>
>>>  
>>>
>>> Thanks in advance
>>>
>>> Milos
>>>
>>> -- 
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/dspace-tech/588f9cbd-cb46-4738-9794-8f2fad2deb37n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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/41a3de95-fa83-411a-98f9-2608cd31eb7bn%40googlegroups.com.


[dspace-tech] DSpace 7.x Best practice for creating custom themes?

2023-02-22 Thread darryl....@usask.ca
Any recommendations or best practices tips on creating and managing custom 
themes?

The UI customization page lists a number of methods -- edit the existing 
DSpace or custom theme, make a copy of the DSpace or custom theme, create 
an entirely new theme from scratch, or possibly "extend" the existing 
DSpace/custom theme -- but I'm wondering if anyone has practical 
experience/tips now that we're 5 major revisions into the 7.x release.  
i.e. how are you managing the inclusion of any fixes to those core 
DSpace/custom themes into your own theme as new versions of the DSpace UI 
are released?  Creating a copy of one of the existing themes seems like it 
would make the job of incorporating fixes harder.

I've been toying with the idea of creating a branch from the current 
release (from the  dspace-7.5 tag for example) and then just making changes 
in the "custom" theme directory.  When 7.6 is released, I should 
(hopefully) be able to just merge the dspace-7.6 tag into my working branch 
and easily get all the fixes that were made to the custom theme. I've yet 
to put that to the test though.

How are the rest of you dealing with themes and version upgrades?

- Darryl


*-**Darryl Friesen*
*, BSc*Programmer/Analyst

*University of Saskatchewan**ICT / University Library*

-- 
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/680cc6fb-57ae-443b-9a24-8f35168186e7n%40googlegroups.com.


[dspace-tech] Re: Dspace7 : adding facet/filter by community/collection?

2022-05-10 Thread darryl....@usask.ca
Marie-Hélène, it seems the existing 6.x ability to facet during browse was 
only available in the XMLUI (not JSPUI), and the DSpace 7.x frontend seems 
to draw more from JSPUI.  So as I understand it, the ability to 
filter/facet is only available for search results, not while browsing 
communities or collections. These 2 threads have some additional details:

 https://groups.google.com/g/dspace-tech/c/Dlyuxgd2Ci0/m/L1eyYkAGAwAJ
 https://groups.google.com/g/dspace-tech/c/Ba0_imRV4_E/m/lWSsIAOTAAAJ

- Darryl



On Tuesday, May 10, 2022 at 7:31:20 AM UTC-6 mh.vezi...@gmail.com wrote:

> May I ask again if there are any plans to add a filter/facet by collection 
> ? Actually, with the ScopeSelector added, the collection must be chosen at 
> the very beginning of the search process. It would be usefull to be able to 
> filter results by collections.
>
> Many thanks,
>
> Marie-Hélène V.
>
> Le mercredi 13 avril 2022 à 15 h 49 min 29 s UTC-4, Marie-Hélène Vézina - 
> UdeM a écrit :
>
>> Bonjour Tim,
>>
>> Regarding the Scope Search:
>>
>> Indeed, turning on "showScopeSelector" does have the UI display the scope 
>> selector box, thank you.
>>
>> However, this scope box with the choice of the collection is not shown on 
>> the results page (as it is in Dspace 6.x XMLUI).
>> Thus 1) the user does not see clearly that his/her search was done only 
>> in a specific collection and 2) if the user wants to restart his/her search 
>> and/or do a second search in the same collection, he/she has to go back to 
>> the previous page to reselect the collection in question. Does 
>> the  "showScopeSelector" have to be turned on somewhere else in the code to 
>> also appear at the top of the result list? If it's not the case, I think 
>> this design could be improved. (I could add this comment in the Github 
>> ticket if deemed relevant).
>>
>> Regarding the filter/facet by collection : Are there any plans for this?
>>
>> Thank you,
>>
>> Marie-Hélène V.
>>
>> Le lundi 11 avril 2022 à 11 h 39 min 50 s UTC-4, Tim Donohue a écrit :
>>
>>> Hi  Marie-Hélène, 
>>>
>>> Somewhere along the way, we accidentally turned off (or broke) the 
>>> feature which allows you to search within a Community/Collection. 
>>> We're working on fixing it in this ticket 
>>> https://github.com/DSpace/dspace-angular/issues/1588
>>>
>>> You also might be able to simply turn it back on by default by changing 
>>> "showScopeSelector" to "true" in the SearchFormComponent: 
>>> https://github.com/DSpace/dspace-angular/blob/main/src/app/shared/search-form/search-form.component.ts#L70
>>>   
>>> (I'll admit though that I'm not sure if this will resolve the issue 
>>> entirely...but follow that ticket for more info.
>>>
>>> Tim
>>>
>>> On Monday, April 11, 2022 at 9:04:50 AM UTC-5 mh.vezi...@gmail.com 
>>> wrote:
>>>

 I'm sorry if this has been mentioned before. I don't see an easy and 
 direct way to add a community/collection search facet in the config file: 
 config/spring/api/discovery.xml 

 How can I allow my end users to filter their global item search results 
 by collections as it was possible before (Dspace 6.x XMLUI)?

 and is it possible to allow end users to search within a single 
 community/collection, not All of Dspace?

 Thank you,

 Marie-Hélène V.

>>>

-- 
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/cc561efe-24a5-4d75-9f89-7ee50585a63cn%40googlegroups.com.


[dspace-tech] DS7.x: Suppress or replace abstract for embargoed items

2022-05-09 Thread darryl....@usask.ca
We are looking to suppress the abstract for items with an embargo, or 
perhaps replace the abstract with some sort of "This item is under an 
embargo" message.  99.9% of the time this will be for theses deposited into 
DSpace via SWORD, wo they will have a value set for the embargo.field.lift 
field.  
This is how we've handled it for our current DSpace 6.x instance  -- by 
modifying crosswalks and the item display and using the presence of that 
field as an indicator of when to replace the abstract.

I've (successfully) experimented a bit with similar changes to the Angular 
frontend, but it seems the better place to tackle this in DSpace 7.x would 
be in the backend, in the API code somewhere, so that the abstract isn't 
exposed via the API at all.

Has anyone tackled something like this before?  Any hints on where in the 
backend I might begin?  I assume I'd be looking to modify code in the 
dspace-api module?  Perhaps during some stage where the 
browse/search/individual record is assembled and converted to JSON for 
return?

Thanks!

- Darryl



-- 
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/223c021b-1026-4694-8f6a-3e0e8df7b7d3n%40googlegroups.com.


[dspace-tech] Re: OAI-PMH DSpace 7.2

2022-05-06 Thread darryl....@usask.ca
Jan, did you remember to run the OAI import task 
-- https://wiki.lyrasis.org/display/DSDOC7x/OAI#OAI-OAI-PMHServerMaintenance

I had some similarly weird issues with OAI and it was because I forgot to 
run that, and thus had no actual OAI data to serve up.

- Darryl



On Friday, May 6, 2022 at 2:51:38 AM UTC-6 jan.b...@gmail.com wrote:

> Hi,
> we installed DSpace 7.2 and migrated the database from our previous 
> version.
> Everything seems to be working fine, seen here - 
> https://sulis29.zcu.cz/home,
> however there is something missing/bad within OAI-MPH interface , can be 
> checked on https://sulis29.zcu.cz/server/oai/.
> Do you have any suggestion what might help?
> Thanks
> Jan
>

-- 
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/d062ef35-8a42-4c9d-8c9b-e9f0f084e429n%40googlegroups.com.


[dspace-tech] Re: Dspace 7: Help in customizing DSpace New Item Form

2022-05-06 Thread darryl....@usask.ca
The documentation for configuring the submission forms in DSpace 7.x can be 
found 
here: https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface

If I read them correctly, the submission system does not work the way you 
want it to.  You can define multiple different submission forms, but they 
can't be triggered based on the selected value of a dropdown.  Instead, 
each form is linked to a specific collection.  So if you had, for example, 
a collection to hold "Exam Papers" or "Dissertations and Theses", then when 
a person chose to submit to one of those collections, they would be 
presented with the appropriate submission form.  This is exactly what we 
do.  We have one default submission form for all DSpace submissions, and 
one specific to our Thesis collection, so when people submit a thesis they 
get fields customized for ETDs (degree name, program, etc).

It appears DSpace 7 also introduced the concept of Configurable Entities -- 
see: https://wiki.lyrasis.org/display/DSDOC7x/Configurable+Entities -- 
which sound more like what you might be looking for.  I have absolutely no 
experience with enties though, so it's possible they won't help you achieve 
what you want.

- Darryl


On Friday, May 6, 2022 at 1:33:48 PM UTC-6 banjia...@gmail.com wrote:

> Can any please help with this or recommend a paid service.
>
> Thank you. 
>
> On Saturday, 30 April 2022 at 23:18:10 UTC+1 Seun Adewoye wrote:
>
>> Please I need help in adding a dropdown field in the New Item form called 
>> “Resource Type”. This field will be placed at the top near the “Collection” 
>> dropdown field. The following options will be shown in Resource Type 
>> dropdown
>> • Exam Papers
>> • Dissertation and Thesis
>> • Journal Article
>> • Awards & Recognition (Accolades)
>>
>> Each of the resource type dropdown option will load a unique form. 
>>
>> For example when submitter selects “Exam Paper” option, exam paper form 
>> fields load
>>
>> • Module Title* (Normal Entry Text)
>> • Day (Dropdown) (Options are Monday to Sunday)
>> • Date* (Date Field) ( MM DD)
>> • Time (Duration) (Normal Entry Text)
>> • Total Pages (Normal Entry Text)
>> • School* (Dropdown)
>> • Degree Name* (Normal Entry Text)
>>
>>
>>
>>

-- 
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/f6de853a-b420-445c-85f2-b7990782534bn%40googlegroups.com.


[dspace-tech] Re: DS7.x: Item page customization and custom themes

2022-05-05 Thread darryl....@usask.ca
Just an update on this.  As per Agustina's suggestion above, this was 
relatively straightforward. I following Paulo Graça's comment on 
the https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Customization 
page and defined this an entry component.  The untyped-item component is a 
little different than the publication component, but what I have seems to 
work.

Thanks  Agustina (and Paulo, and Art Lowel)!

- Darryl

On Wednesday, May 4, 2022 at 10:48:29 AM UTC-6 darryl@usask.ca wrote:

> Thanks Agustina.  I read those comments, and that was where I was headed 
> next, but I thought I'd double check with folks here before I got started.  
> Partly because of this statement "This part of the  code might be 
> refactored in a subsequent release, so this is kind of a temporary 
> solution.".  But it's reassuring to know others are using the same strategy.
>
> I mean. if you had some code or tips to share, I wouldn't turn that 
> down.  :)   I've done a bit of work with Vue but, like you, Angular is new 
> to me.  I welcome any help I can get.
>
> As for workflow, we started with a Git clone, then created a local branch 
> from the 7.2 release, to keep our customizations separate.  My plan is to 
> then merge the 7.3 release into my branch to keep it up to date.  By 
> starting with a copy of the custom theme though, I'll need to manually move 
> any 7.3 changes to "custom" into my theme, so I'm wondering if that that 
> copy was a good decision, and whether I should have just made changes 
> directly to "custom".  I too welcome any suggestions on the best way to 
> manage things going forward.
>
> Thanks again Agustina!
>
> - Darryl
>
> On Wednesday, May 4, 2022 at 6:12:03 AM UTC-6 Agustina Martinez wrote:
>
>> Hi Darryl,
>>
>> We are currently at the same stage as you are regarding custom theming. I 
>> have opted for now to take a copy of the custom theme and use it as the 
>> basis for our institutional theme (to make updates a bit easier going 
>> forward I've removed all of those customisations from the custom theme that 
>> we do not use for now). But like you, do not know whether this is the best 
>> approach. I found the documentation pages really good: 
>> https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Customization 
>> and in particular the comments at the end answer your question about 
>> customising components such as the "untyped item". I have successfully done 
>> that in our test instance and happy to share with you if you don't get it 
>> working based on the info in the docs pages.
>>
>> It would be great if someone could comment on best ways forward for 
>> customising in ways that make future upgrades simpler. I am really knew to 
>> angular so just slowly finding our ways!
>>
>> Agustina
>>
>> On Tuesday, 3 May 2022 at 21:02:24 UTC+1 darryl@usask.ca wrote:
>>
>>>
>>> How are people theming DSpace 7.x? Is it better to create a new theme 
>>> from a copy of "custom" (and deal with integrating any future changes made 
>>> to "custom" manually), or just create a local branch of the dspace-angular 
>>> repo and modify the "custom" theme directly (and then pull in changes to 
>>> "custom" via a merge request from the main branch)?
>>>
>>> Also, can anyone point me in the right direction to make changes to the 
>>> simple item view? It seems the default for items in DSpace is "untyped 
>>> item" (I haven't enabled any of the entity stuff).  I've modified 
>>> src/app/item-page/simple/item-types/untyped-item/untyped-item.component.html
>>>  
>>> to get the results I want, but it seems like a bad idea to modify the 
>>> global code rather than something in my theme.
>>>
>>> The "custom" theme contains simple page templates for Publication items, 
>>> -- src/themes/limestone/app/item-page/simple/item-types/publication -- but 
>>> not untyped items.  Simply copying the "untyped-item" folder from the 
>>> global code into that "item-types" folder didn't seem to work.  I assume 
>>> there some additional changes required in a .ts file somewhere I also need 
>>> to update, but I'm, not quite sure which ones.  Or do I need to copy the 
>>> entire src/app/item-page directory tree into my theme?
>>>
>>> Unless there's some other (easier) way to add additional metadata fields 
>>> to the simple display that I've not discovered??
>>>
>>> Thanks,
>>>
>>> - Darryl
>>>
>>>
>>>
&

[dspace-tech] Re: Correct permissions prior to using Maven and Ant while installing Dspace 6.3

2022-05-04 Thread darryl....@usask.ca
Ashim, those permissions look pretty restrictive.  Does the build and 
install actually work for you?

I know the install docs mention the "dspace" user, but it also states "you 
must ensure the Tomcat owner also owns [dspace], OR you can create a new '
dspace' user account, and ensure that Tomcat also runs as that account".  
We went with the former (because that was easier and more standard than 
changing the account Tomcat runs as), and made sure the "tomcat" user and 
group owned all the files.

This is mostly from memory, but for the [dspace] directory I did something 
like:

 sudo mkdir [dspace]
 sudo chown tomcat:tomcat [dspace]
 sudo chmod 2775 [dspace]

And for the [dspace-source] directory I did something like:

 # Set the permissions
 sudo chown -R tomcat:tomcat [dspace-source]
 sudo chmod -R ug+rw [dspace-source]
 # Build DSpace
 sudo su - tomcat
 cd [dspace-source]
 $ Install
 mvn package
 cd dspace/target/dspace-installer
 ant fresh_install

I won't say that that's the only way, or even the correct way, but that 
worked for us.

- Darryl

On Wednesday, May 4, 2022 at 4:02:46 PM UTC-6 fru9...@gmail.com wrote:

> Hello, 
>
> Does setting these permissions allow you tu run ant ?
>
> Kind regards,
>
> On Wednesday, April 28, 2021 at 3:51:32 PM UTC+1 ashim@nipfp.org.in 
> wrote:
>
>> Dear Dspace Experts, 
>>
>> I wish to know the correct permissions for the directories [dspace] 
>> and [dspace-source] prior to running Maven and Ant. 
>>
>> I am using the definitions of [dspace] and [dspace-source] as on this 
>> page: 
>>
>> https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace 
>>
>> Here is what I have been doing till now: 
>>
>> For Running Maven (as user dspace): 
>> I first make sure that the dspace user owns the [dspace-source] 
>> directory. 
>>
>> sudo chmod 700 -R [dspace-source] 
>> ( Basically rwx for [dspace-source]) 
>> mvn package 
>>
>> For Running Ant as user dspace: 
>>
>> sudo chmod 500 -R [dspace-source] 
>> ( Basically READ and EXECUTE permission for [dspace-source]) 
>> sudo chmod 200 -R [dspace] 
>> ( Amounts to WRITE permission for [dspace]) 
>> sudo chmod u+x -R [dspace] 
>> This is so that the installed files can be executed 
>> sudo chmod g+s -R [dspace] 
>> This is so that the newly created files in [dspace] should inherit the 
>> group ( which is the same as the dspace user). so that permissions are 
>> inherited. 
>> sudo chmod 700 -R [dspace-source] 
>>
>> Then I do, as user dspace:- 
>> cd [dspace-source]/dspace/target/dspace-installer 
>> ant fresh_install 
>>
>> Can someone here comment on my attempt ? Please share the best practice. 
>>
>> Thank you, 
>> Ashim 
>>
>

-- 
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/93d3d862-38ff-4951-b66e-2d3e0d14c39dn%40googlegroups.com.


[dspace-tech] Re: ant fresh_install fails

2022-05-04 Thread darryl....@usask.ca
On our servers, Tomcat runs as the "tomcat" user, so all our source files 
are owned by that user and group, as is the DSpace target group.  It's been 
a while since I did a fresh install, but I probably did the initial setup 
of our target directory something like this:

 sudo mkdir /dspace
 sudo chown tomcat:tomcat /dspace
 sudo chmod 2775 /dspace

Then I would have run the "ant fresh_install" as the "tomcat" user.

Your setup make be slightly different of course, but it looks to me like 
whatever user you are running "ant" as does not have permissions to 
actually write to your "/dspace" directory.  I'd start with looking at 
permissions.

- Darryl




On Wednesday, May 4, 2022 at 4:02:46 PM UTC-6 fru9...@gmail.com wrote:

> Hello, 
>
> I am following the steps to installing dspace but I run into an issue when 
> I run *ant fresh_install*
>
> Here's the output I get
>
> [image: ant_install.PNG]
>
> Please help
>
> 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/115632f7-46e2-4bd5-a154-3ab98a1d389cn%40googlegroups.com.


[dspace-tech] Re: DS7.x: Item page customization and custom themes

2022-05-04 Thread darryl....@usask.ca
Thanks Agustina.  I read those comments, and that was where I was headed 
next, but I thought I'd double check with folks here before I got started.  
Partly because of this statement "This part of the  code might be 
refactored in a subsequent release, so this is kind of a temporary 
solution.".  But it's reassuring to know others are using the same strategy.

I mean. if you had some code or tips to share, I wouldn't turn that 
down.  :)   I've done a bit of work with Vue but, like you, Angular is new 
to me.  I welcome any help I can get.

As for workflow, we started with a Git clone, then created a local branch 
from the 7.2 release, to keep our customizations separate.  My plan is to 
then merge the 7.3 release into my branch to keep it up to date.  By 
starting with a copy of the custom theme though, I'll need to manually move 
any 7.3 changes to "custom" into my theme, so I'm wondering if that that 
copy was a good decision, and whether I should have just made changes 
directly to "custom".  I too welcome any suggestions on the best way to 
manage things going forward.

Thanks again Agustina!

- Darryl

On Wednesday, May 4, 2022 at 6:12:03 AM UTC-6 Agustina Martinez wrote:

> Hi Darryl,
>
> We are currently at the same stage as you are regarding custom theming. I 
> have opted for now to take a copy of the custom theme and use it as the 
> basis for our institutional theme (to make updates a bit easier going 
> forward I've removed all of those customisations from the custom theme that 
> we do not use for now). But like you, do not know whether this is the best 
> approach. I found the documentation pages really good: 
> https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Customization and 
> in particular the comments at the end answer your question about 
> customising components such as the "untyped item". I have successfully done 
> that in our test instance and happy to share with you if you don't get it 
> working based on the info in the docs pages.
>
> It would be great if someone could comment on best ways forward for 
> customising in ways that make future upgrades simpler. I am really knew to 
> angular so just slowly finding our ways!
>
> Agustina
>
> On Tuesday, 3 May 2022 at 21:02:24 UTC+1 darryl@usask.ca wrote:
>
>>
>> How are people theming DSpace 7.x? Is it better to create a new theme 
>> from a copy of "custom" (and deal with integrating any future changes made 
>> to "custom" manually), or just create a local branch of the dspace-angular 
>> repo and modify the "custom" theme directly (and then pull in changes to 
>> "custom" via a merge request from the main branch)?
>>
>> Also, can anyone point me in the right direction to make changes to the 
>> simple item view? It seems the default for items in DSpace is "untyped 
>> item" (I haven't enabled any of the entity stuff).  I've modified 
>> src/app/item-page/simple/item-types/untyped-item/untyped-item.component.html 
>> to get the results I want, but it seems like a bad idea to modify the 
>> global code rather than something in my theme.
>>
>> The "custom" theme contains simple page templates for Publication items, 
>> -- src/themes/limestone/app/item-page/simple/item-types/publication -- but 
>> not untyped items.  Simply copying the "untyped-item" folder from the 
>> global code into that "item-types" folder didn't seem to work.  I assume 
>> there some additional changes required in a .ts file somewhere I also need 
>> to update, but I'm, not quite sure which ones.  Or do I need to copy the 
>> entire src/app/item-page directory tree into my theme?
>>
>> Unless there's some other (easier) way to add additional metadata fields 
>> to the simple display that I've not discovered??
>>
>> Thanks,
>>
>> - Darryl
>>
>>
>>
>> --
>> *Darryl Friesen, BSc*
>> Programmer/Analyst
>> *University of Saskatchewan*
>> *ICT / University Library*
>>
>>
>>

-- 
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/b0519090-eeaa-4f02-b27e-5964f6ba2ecdn%40googlegroups.com.


[dspace-tech] DS7.x: Item page customization and custom themes

2022-05-03 Thread darryl....@usask.ca

How are people theming DSpace 7.x? Is it better to create a new theme from 
a copy of "custom" (and deal with integrating any future changes made to 
"custom" manually), or just create a local branch of the dspace-angular 
repo and modify the "custom" theme directly (and then pull in changes to 
"custom" via a merge request from the main branch)?

Also, can anyone point me in the right direction to make changes to the 
simple item view? It seems the default for items in DSpace is "untyped 
item" (I haven't enabled any of the entity stuff).  I've modified 
src/app/item-page/simple/item-types/untyped-item/untyped-item.component.html 
to get the results I want, but it seems like a bad idea to modify the 
global code rather than something in my theme.

The "custom" theme contains simple page templates for Publication items, -- 
src/themes/limestone/app/item-page/simple/item-types/publication -- but not 
untyped items.  Simply copying the "untyped-item" folder from the global 
code into that "item-types" folder didn't seem to work.  I assume there 
some additional changes required in a .ts file somewhere I also need to 
update, but I'm, not quite sure which ones.  Or do I need to copy the 
entire src/app/item-page directory tree into my theme?

Unless there's some other (easier) way to add additional metadata fields to 
the simple display that I've not discovered??

Thanks,

- Darryl



--
*Darryl Friesen, BSc*
Programmer/Analyst
*University of Saskatchewan*
*ICT / University Library*


-- 
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/00851c29-f3a4-4012-a1b5-3d83e14a11d1n%40googlegroups.com.


[dspace-tech] Re: DSpace 7.2: missing sidebar facets in browse

2022-04-28 Thread darryl....@usask.ca
I noticed that behavior with Iowa as well.  I'm curious how they made that 
work.  If I add a "scope" argument to our test and dev server URLs (or to 
the demo site), DSpace is not treating that as a search; the display 
remains as if I was browsing and no facets appear.

I think for us though, the biggest loss would be the inability to have 
facets customized per collection. We have a custom set for our ETD 
collection that makes use of the additional metadata fields available in 
ETD-ms (department, program, degree level etc). I assume that since facets 
now only display on search results, they must all fall within the default 
set.

- Darryl



On Thursday, April 28, 2022 at 10:42:16 AM UTC-6 al...@vt.edu wrote:

> We also want the facets to appear in collection pages. Since there is no 
> longer browse links, it's the only way to browse a collection. We want the 
> interface to be like other discovery interfaces that offer facets. We have 
> not tried it, but it seems like it might be possible to force the facets to 
> appear by making the links to collections be search queries. 
>
> For example clicking on a collection link in dspace demo leads to a 
> collection page without facets, 
> https://demo7.dspace.org/communities/6465ceac-442e-4bc8-8e07-1f28f7b320eb.
>
> Clicking on a collection link in the Iowa State repository leads to 
> https://dr.lib.iastate.edu/collections/71537944-3990-4d99-9351-64b7a4f83125?scope=71537944-3990-4d99-9351-64b7a4f83125,
>  
> which does have facets. I believe this is a search query. 
>
> Thanks, Anne
> On Thursday, April 28, 2022 at 12:30:51 PM UTC-4 darryl@usask.ca 
> wrote:
>
>> Thanks for the pointer.  I did try and search the group but it seems I 
>> missed that tread somehow.
>>
>> Very disappointing though.  Our users are really going to miss facets.  
>> And if they only ever appear for search results, I think it renders quite a 
>> bit of the Discovery documentation -- 
>> https://wiki.lyrasis.org/display/DSDOC7x/Discovery -- incorrect, as 
>> there is no way to actually display facets on the community/collection 
>> pages nor tailor them to specific communities or collections.
>>
>> - Darryl
>>
>>
>>
>> On Thursday, April 28, 2022 at 9:11:26 AM UTC-6 al...@vt.edu wrote:
>>
>>> Darryl,
>>>
>>> This relates to the DSpace thread, 
>>> https://groups.google.com/g/dspace-tech/c/Dlyuxgd2Ci0/m/P5sN4WcCAwAJ.
>>>
>>> On Wednesday, April 27, 2022 at 12:29:14 PM UTC-4 darryl@usask.ca 
>>> wrote:
>>>
>>>>
>>>> We're upgrading from 6.3 (XMLUI) to 7.x and I've noticed that none of 
>>>> the sidebar facets we had before are appearing while browsing 
>>>> communities/collections.  Search filters appear on the left hand side, but 
>>>> facets don't seem to display anywhere.
>>>>
>>>> Did I just miss some configuration somewhere?  I've checked our 
>>>> local.cfg and discovery.xml and everything looks in order there.  I've 
>>>> noticed that the DSpace 7 demo site also lacks any sidebar facets.  Is 
>>>> this 
>>>> a feature that's not available in 7.x yet (we're running 7.2.1 on our test 
>>>> server)?
>>>>
>>>> Thanks,
>>>>
>>>> - Darryl
>>>>
>>>>
>>>>
>>>> --
>>>> *Darryl Friesen, BSc*
>>>> Programmer/Analyst
>>>> *University of Saskatchewan*
>>>> *ICT / University Library*
>>>>
>>>>

-- 
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/a955-c35f-4121-b9f3-30c09e458405n%40googlegroups.com.


[dspace-tech] Re: DSpace 7.2: missing sidebar facets in browse

2022-04-28 Thread darryl....@usask.ca
Thanks for the pointer.  I did try and search the group but it seems I 
missed that tread somehow.

Very disappointing though.  Our users are really going to miss facets.  And 
if they only ever appear for search results, I think it renders quite a bit 
of the Discovery documentation 
-- https://wiki.lyrasis.org/display/DSDOC7x/Discovery -- incorrect, as 
there is no way to actually display facets on the community/collection 
pages nor tailor them to specific communities or collections.

- Darryl



On Thursday, April 28, 2022 at 9:11:26 AM UTC-6 al...@vt.edu wrote:

> Darryl,
>
> This relates to the DSpace thread, 
> https://groups.google.com/g/dspace-tech/c/Dlyuxgd2Ci0/m/P5sN4WcCAwAJ.
>
> On Wednesday, April 27, 2022 at 12:29:14 PM UTC-4 darryl@usask.ca 
> wrote:
>
>>
>> We're upgrading from 6.3 (XMLUI) to 7.x and I've noticed that none of the 
>> sidebar facets we had before are appearing while browsing 
>> communities/collections.  Search filters appear on the left hand side, but 
>> facets don't seem to display anywhere.
>>
>> Did I just miss some configuration somewhere?  I've checked our local.cfg 
>> and discovery.xml and everything looks in order there.  I've noticed that 
>> the DSpace 7 demo site also lacks any sidebar facets.  Is this a feature 
>> that's not available in 7.x yet (we're running 7.2.1 on our test server)?
>>
>> Thanks,
>>
>> - Darryl
>>
>>
>>
>> --
>> *Darryl Friesen, BSc*
>> Programmer/Analyst
>> *University of Saskatchewan*
>> *ICT / University Library*
>>
>>

-- 
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/56dba178-1ebc-4064-9a3b-7325a6d8e852n%40googlegroups.com.


[dspace-tech] DSpace 7.2: missing sidebar facets in browse

2022-04-27 Thread darryl....@usask.ca

We're upgrading from 6.3 (XMLUI) to 7.x and I've noticed that none of the 
sidebar facets we had before are appearing while browsing 
communities/collections.  Search filters appear on the left hand side, but 
facets don't seem to display anywhere.

Did I just miss some configuration somewhere?  I've checked our local.cfg 
and discovery.xml and everything looks in order there.  I've noticed that 
the DSpace 7 demo site also lacks any sidebar facets.  Is this a feature 
that's not available in 7.x yet (we're running 7.2.1 on our test server)?

Thanks,

- Darryl



--
*Darryl Friesen, BSc*
Programmer/Analyst
*University of Saskatchewan*
*ICT / University Library*

-- 
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/bfb5cdcc-252b-43a3-a47b-3e2eb785834en%40googlegroups.com.


[dspace-tech] Re: User Interface Customization

2022-04-27 Thread darryl....@usask.ca
We ran across that same issue as well.  If you click in that navbar section 
does it then load all the menu items properly?  That's what our test 
instance was doing.

I *think* this tiny tweak to src/app/navbar/navbar.component.html may fix 
the issue:


 
https://github.com/DSpace/dspace-angular/commit/2830da955739b61c91c15f587051b0d75f4e5464

We're working on our own theme and used a copy of custom as the starting 
point.  I know I made the above change to our theme and haven't noticed 
this particular issue since.


--
*Darryl Friesen**, BSc*
Programmer/Analyst
*University of Saskatchewan*
*ICT / University Library*


On Wednesday, April 27, 2022 at 8:24:43 AM UTC-6 jos...@udel.edu wrote:

> Hi,
>
> We are developing a Dspace repository by using DSpace 7.2. On the 
> frontend, in the config.dev.yml file, if I set the name of the theme to 
> "dspace", the home page shows all three menus (Communities & Collections, 
> All of DSpace, Statistics). However, if I change it to "custom", it shows 
> only one menu like this:
> [image: image.png]
>
> Can anyone have the same issue? Can anyone help us out?
>
>
> 
> Joshua Kim
> Web Developer, Library IT
> Library, Museums and Press
> University of Delaware
>
>

-- 
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/377ee1ca-1717-4696-b484-e41b4ed72edcn%40googlegroups.com.


[dspace-tech] Re: DSpace 7.2 unable to login on frontend

2022-04-11 Thread darryl....@usask.ca
In that last screenshot it looks like you're mixing HTTP and HTTPS URLs.  
I'd double check the config.*.yml files for frontend and the local.cfg on 
the backend, to ensure everything is matching up.

- Darryl



On Monday, April 11, 2022 at 12:06:44 PM UTC-6 joem...@gmail.com wrote:

> Dear DSpace Colleagues,
>
> I have installed DSpace 7.2 and created initial admin user from 7.2 
> backend and when I try to logon to frontend it loads endlessly, please see 
> attached screenshots.
>
> Regards,
> Lewatle  
>

-- 
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/1e053681-da44-4b84-b4b9-89cb9af9a102n%40googlegroups.com.


[dspace-tech] Re: DSpace 7.2 - ORCID integration failure

2022-04-07 Thread darryl....@usask.ca
Tim, are there any screenshot of how should the OCRID integrations look in 
7.x?  I see that the docs still show the 6.x screenshots.

Filippo, I'm seeing those same warnings you are (I'm running DSpace 
7.2.1).  I'm able to deposit an item successfully though.  Neither the 
submission nor edit forms have anything that resembles the old 
ORCID/Authority Control "Lookup" button though.  All I see is a standard 
text input field.  And the "authority" index in Solr remains empty after 
depositing an item, even after running 'index-authority' on the command 
line.

I feel I'm missing something here, but I can't quite figure out what.

- Darryl


On Monday, March 28, 2022 at 8:54:42 AM UTC-6 Tim Donohue wrote:

> Hi Filippo,
>
> Those lines in your logs are just warning (See how it starts with 
> "WARN").  If it is NOT followed by an ERROR line, then that means it was 
> able to find that bean through a different route.  So, it can be safely 
> ignored, as it's not a bug or issue.  You'd want to instead look for ERROR 
> lines in the log.
>
> (As a sidenote, these warnings are a bit "loud" as we probably don't need 
> the full stacktrace there...so, I'll see if there's a way we can quiet them 
> down a bit.)
>
> Here's our troubleshooting guide for more reference: 
> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>
> Tim
> On Monday, March 28, 2022 at 9:00:29 AM UTC-5 santoro...@gmail.com wrote:
>
>> Dear Community,
>>
>>  I'm trying to enable ORCID integration, but so far unsuccessful. I 
>> modified dspace.cfg according to the indications given in 
>> https://wiki.lyrasis.org/display/DSDOC7x/ORCID+Integration. However, 
>> when I add an item to a collection, typing the author's lastname, doesn't 
>> show anything. Going to take a look at dspace.log I noticed that the 
>> following warning appears:
>>
>> 2022-03-28 15:04:06,979 WARN  f80a1e23-ca75-489a-adde-04a24d333744 
>> e256d6ec-c1b2-4e8d-84e8-2ed9c5d8dd2d 
>> org.dspace.servicemanager.DSpaceServiceManager @ *Unable to locate bean 
>> by name or id=AuthoritySource*. Will try to look up bean by typ
>> e next.
>> org.springframework.beans.factory.NoSuchBeanDefinitionException: *No 
>> bean named 'AuthoritySource' available*
>> at 
>> org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:808)
>>  
>> ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
>> at 
>> org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1279)
>>  
>> ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
>>
>> [OMISSIS]
>>
>> Could you give me some suggestion?
>> Thanks in advance.
>>
>> Filippo Santoro
>>
>>

-- 
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/052c5d45-3ba5-44e3-9b60-6289f5c435dbn%40googlegroups.com.


Re: [dspace-tech] Dspace 7 shibboleth error

2021-10-01 Thread darryl....@usask.ca
Ciprian, did you manage to sort this out?  I'm running into the same 
situation.  DSpace logs show:

2021-10-01 12:01:34,276 DEBUG unknown unknown 
org.dspace.authenticate.ShibAuthentication @ ShibAuthentication - attribute 
uid is empty!
2021-10-01 12:01:34,276 DEBUG unknown unknown 
org.dspace.authenticate.ShibAuthentication @ ShibAuthentication - attribute 
mail is empty!
2021-10-01 12:01:34,276 ERROR unknown unknown 
org.dspace.authenticate.ShibAuthentication @ Shibboleth authentication was 
not able to find a NetId, Email, or Tomcat Remote user for which to 
indentify a user from.
2021-10-01 12:01:34,276 DEBUG unknown unknown 
org.dspace.authenticate.ShibAuthentication @ ShibAuthentication - attribute 
uid is empty!
2021-10-01 12:01:34,276 DEBUG unknown unknown 
org.dspace.authenticate.ShibAuthentication @ ShibAuthentication - attribute 
mail is empty!
2021-10-01 12:01:34,276 DEBUG unknown unknown 
org.dspace.authenticate.ShibAuthentication @ ShibAuthentication - attribute 
nickname is empty!
2021-10-01 12:01:34,277 DEBUG unknown unknown 
org.dspace.authenticate.ShibAuthentication @ ShibAuthentication - attribute 
sn is empty!
2021-10-01 12:01:34,283 ERROR unknown unknown 
org.dspace.authenticate.ShibAuthentication @ Unable to register new eperson 
because we are unable to find an email address along with first and last 
name for the user.
NetId Header: 'uid'='null' (Optional)
Email Header: 'mail'='null'
First Name Header: 'nickname'='null'
Last Name Header: 'sn'='null'


but /Shibboleth.sso/Session does indeed show that SHib auth was successful 
and that the attributes returned match my local.cfg values.   Nothing else 
in the logs really stands out as an issue. It seems to me that DSpace isn't 
getting the Shib attributes.  I've tried with ShibHeaders on and off; I 
have the AJP stuff setup correctly (I think).

I'm curious if and how you managed to get this to work

Thanks!

*Darryl Friesen**, BSc*
Programmer/Analyst


*University of Saskatchewan**ICT / University Library*


On Tuesday, August 4, 2020 at 9:55:33 AM UTC-6 Tim Donohue wrote:

> Have you double checked in your Shibboleth setup that your "email-header" 
> is named "mail"?
>
> I still think this setting looks odd to me:
>
> authentication-shibboleth.email-header = mail
>
> It is completely possible that I'm wrong.  But, almost every error message 
> (and info message) you've passed along references a "null" or "empty" value 
> for "mail" (or email).  That implies to me that this setting may not be 
> correct for your Shibboleth setup.
>
> All that said, I have to admit here, I'm hitting up against the limits of 
> my Shibboleth knowledge.  I'm *not* a Shibboleth expert, but can only 
> advise you on which configurations might not be working as expected.  In 
> this scenario, it seems likely to me that your "email-header" setting is 
> incorrect...but, I don't know what it should be changed to (you may need to 
> talk to your Shibboleth administrator). 
>
> I wish I had better advice, but maybe someone else on this list might have 
> an idea of what is going on.  This doesn't seem like a DSpace 7 specific 
> issue to me, but more like a possible misconfiguration of the DSpace 
> Shibboleth settings.
>
> Tim
> --
> *From:* Ciprian Pinzaru 
> *Sent:* Tuesday, August 4, 2020 10:38 AM
>
> *To:* Tim Donohue ; DSpace Technical Support <
> dspac...@googlegroups.com>
> *Subject:* Re: [dspace-tech] Dspace 7 shibboleth error
>
> I find an message like:
>
>
> INFO  org.dspace.app.rest.security.EPersonRestAuthenticationProvider @ 
> anonymous::failed_login:email=null, result=4
>
>
>
> 2020-08-04 18:12:57,053 INFO  
> org.springframework.security.web.DefaultSecurityFilterChain @ Creating 
> filter chain: Ant [pattern='/api/**'], 
> [org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@43d7f719,
>  
> org.springframework.security.web.context.SecurityContextPersistenceFilter@e5c20f0,
>  
> org.springframework.security.web.header.HeaderWriterFilter@148a6d4b, 
> org.springframework.web.filter.CorsFilter@8eb6f8d, 
> org.dspace.app.rest.security.StatelessAuthenticationFilter@1bd3eb22, 
> org.dspace.app.rest.security.StatelessLoginFilter@44823e3, 
> org.dspace.app.rest.security.ShibbolethAuthenticationFilter@785b634c, 
> org.springframework.security.web.authentication.logout.LogoutFilter@1f754887, 
> org.dspace.app.rest.security.AnonymousAdditionalAuthorizationFilter@2b9feccd, 
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter@1ab55f03,
>  
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@60b02a97,
>  
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter@2f918867,
>  
> org.springframework.security.web.session.SessionManagementFilter@3fa4fdb9, 
> org.springframework.security.web.access.ExceptionTranslationFilter@5e08, 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor@647f6f74]

[dspace-tech] Re: ORCID lookup extremely slow

2021-01-20 Thread darryl....@usask.ca
We're seeing the same behavior.  I can't offer and help or pointers yet.  I 
was just going to do a fresh install of DSpace to rule out any local 
customizations we've done; it's good to know the issue appears to not just 
be us.

- Darryl


*Darryl Friesen**, BSc*
Programmer/Analyst


*University of Saskatchewan**ICT / University Library*
On Tuesday, January 19, 2021 at 4:08:54 PM UTC-6 graham@uwaterloo.ca 
wrote:

> Hi all,
>
>  
>
> We are experiencing incredibly long lookup times for ORCIDs in the author 
> lookup in submission form. We are running DSpace 5.10 on Ubuntu, running 
> XMLUI Mirage 2. 
>
>  
>
> Sometimes the lookup is ~10 seconds (which already feels a little slow, 
> IMO), but today it is stretching to 2-3 MINUTES for a lookup to complete. 
>
>  
>
> I tested on demo.dspace.org and it was experiencing timeouts for the 
> ORCID lookup, so I’m wondering if it’s an issue at ORCID. Is anyone else 
> experiencing delays in the lookup?
>
>  
>
> If I go to orcid.org directly and do an author search in the UI, it’s 
> almost instantaneous. 
>
>  
>
> Any pointers are appreciated.
>
>  
>
> Cheers,
>
> Graham
>
>  
>
> -
> Graham Faulkner
> Web Developer / Programmer
> Digital Initiatives, Library
> University of Waterloo
> Waterloo, Ontario N2L 3G1 CANADA
> 519-888-4567 x42461 <(519)%20888-4567>
> graham@uwaterloo.ca 
> 
>
>  
>

-- 
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/313ec955-8a22-4c61-aa4d-d45f4a721720n%40googlegroups.com.