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] Admin user with no privileges

2023-03-06 Thread Douglas Eder Uno Silva
Hi everybody,

Anyone have the problem of the admin menu showing few items or not showing 
at all?

Deploy of DSpace 7.4 results in few items on menu and DSpace 7.5 menu 
displays nothing.

Backend and frontend seems to be fine. Database migrations returns Sucess 
on all items, can access HAL Browser, authentication, etc...

The user administrator created by `/dspace/bin/dspace create-administrator` 
is linked with a group named 'Administrator'

What am i could be doing wrong?

Thank you in advance for your attention and patience.

-- 
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/f387d190-bb70-4f55-8e41-58868fb90999n%40googlegroups.com.


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

2023-03-06 Thread Milos Ivanovic
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/f5dc20ef-7214-4f2d-8205-816ca51a7ff8n%40googlegroups.com.