Many thanks for clarifying this @Sean. Since this is a key feature for my deployment, I will have to postpone the transition to 7.x and follow closely these bug reports.
Kind regards Milos понедељак, 20. март 2023. у 16:44:23 UTC+1 Sean Kalynuk је написао/ла: > Hi Milos, > > > > I think it is this bug: > > > > https://github.com/DSpace/dspace-angular/issues/1758 > > > > -- > > Sean > > > > *From: *dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf > of Milos Ivanovic <imi...@gmail.com> > *Date: *Sunday, March 19, 2023 at 3:11 PM > *To: *DSpace Technical Support <dspac...@googlegroups.com> > *Subject: *Re: [dspace-tech] ORCID autohority in DSpac 7.5 > > *Caution:* This message was sent from outside the University of Manitoba. > > > > Dear Sean, > > > > I've forgotten to comment on one more issue. When submitting a new item, > one gets suggestions from ORCID API on i.e. *dc.contributor.author* > fields. However, when editing items, the suggestions are missing. If one > types the surname and first name of the author, that author just gets > overwritten in Solr, getting a new authority ID. Is this a bug or a > feature? Is there an option to force those fields to behave the way when > submitting a new item? > > > > Regards > > Milos > > > > среда, 8. март 2023. у 21:40:54 UTC+1 Milos Ivanovic је написао/ла: > > Dear Sean, > > > > Many thanks for your thorough explanation. IMHO the improvement in this > respect is worth considering. > > > > Regards > > Milos > > > > среда, 8. март 2023. у 01:04:30 UTC+1 Sean Kalynuk је написао/ла: > > Hi Milos, > > > > After looking through the DSpace 7.5 code, I don’t see that institution > can be configured to be displayed in the search results. (Although, there > are bits and pieces in the code that seem to indicate that it’s not that > far away from being supported.) > > > > The author search display results are limited to: > > > > last-name > > first-name > > orcid > > insolr (this is an indicator if the result came from the authority Solr > core, and would have a UUID if so, otherwise, it will say “false” in which > case the result came from the ORCID API) > > > > However, there are other ORCID Person values obtained during the search, > including: > > - Keywords > - External identifiers > - Researcher URLs > - Biography > > > > You can see what the ORCID API returns for a Person here: > > > https://github.com/ORCID/orcid-model/blob/master/src/main/resources/record_3.0/person-3.0.xsd > > > > None of these other values are made available for display in the search > results though. However, they are stored in the Solr authority core so > could potentially be used at some point. > > > > Surprisingly, there is an internal “institution” value that could also > potentially be used, but there is no current mapping from the ORCID Person > record to an institution value that DSpace could use for display purposes. > > > > I figure it’s important to point out that there are several other quirks > with the implementation that cause some difficulty in finding ORCID > authors. For example, the ORCID API result list is hard-coded to at most 10 > results. Also, the ORCID API search is so generic that searching for first > name and last name (instead of just last name) can result in not being able > to even find the person you’re looking for (if outside the 10 results > limit). I find better results when only using last name in the search. (Of > course, it all depends on how unique the last name is.) > > > > Perhaps the future lies with ORCID Person entities and not the ORCID > Authority implementation? > > > > -- > > Sean > > > > *From: *dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf > of Milos Ivanovic <imi...@gmail.com> > *Date: *Tuesday, March 7, 2023 at 11:51 AM > *To: *DSpace Technical Support <dspac...@googlegroups.com> > *Subject: *Re: [dspace-tech] ORCID autohority in DSpac 7.5 > > *Caution:* This message was sent from outside the University of Manitoba. > > > > Perfect. Thanks, @Sean, it really works with the public API! This is > something I've been looking for. Will give it a more thorough test. > > > > One more quick question if anyone knows. Do you know how to add the name > of the institution from the ORCID profile to the suggestions? It would make > the process much easier IMHO. > > > > Kind regards! > > Milos > > > > уторак, 7. март 2023. у 18:35:17 UTC+1 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 <dspac...@googlegroups.com> on behalf > of darryl....@usask.ca <darryl....@usask.ca> > *Date: *Monday, March 6, 2023 at 5:35 PM > *To: *DSpace Technical Support <dspac...@googlegroups.com> > *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 <dspac...@googlegroups.com> on behalf > of Milos Ivanovic <imi...@gmail.com> > *Date: *Friday, March 3, 2023 at 4:17 AM > *To: *DSpace Technical Support <dspac...@googlegroups.com> > *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 > > <https://groups.google.com/d/msgid/dspace-tech/588f9cbd-cb46-4738-9794-8f2fad2deb37n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > 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/41a3de95-fa83-411a-98f9-2608cd31eb7bn%40googlegroups.com > > <https://groups.google.com/d/msgid/dspace-tech/41a3de95-fa83-411a-98f9-2608cd31eb7bn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > 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/f88cf364-1138-4f1a-866c-a1694e879c69n%40googlegroups.com > > <https://groups.google.com/d/msgid/dspace-tech/f88cf364-1138-4f1a-866c-a1694e879c69n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > 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/02a75b4d-4a69-4da8-a094-59dee736644bn%40googlegroups.com > > <https://groups.google.com/d/msgid/dspace-tech/02a75b4d-4a69-4da8-a094-59dee736644bn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/a9965fc3-70c0-4caf-88db-a2ce7fe4ff42n%40googlegroups.com.
