> 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
Hi Milos,
I think it is this bug:
https://github.com/DSpace/dspace-angular/issues/1758
--
Sean
From: dspace-tech@googlegroups.com on behalf of
Milos Ivanovic
Date: Sunday, March 19, 2023 at 3:11 PM
To: DSpace Technical Support
Subject: Re: [dspace-tech] ORCID autohority in DSpac 7.5
> 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
e future lies with ORCID Person entities and not the ORCID
> Authority implementation?
>
>
>
> --
>
> Sean
>
>
>
> *From: *dspac...@googlegroups.com on behalf
> of Milos Ivanovic
> *Date: *Tuesday, March 7, 2023 at 11:51 AM
> *To: *DSpace Technica
: [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
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 occ
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 a
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.autho
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
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
>>>
&
;>
>> 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
>>
&
;
> *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.
/authority.cfg
--
Sean
From: dspace-tech@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
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:
14 matches
Mail list logo
