[dspace-tech] orcid lookup problem (not using orcid authentication)
orcid lookup problem (not using orcid authentication) In the user submission form the author field does a lookup and correctly finds authors that have been retrieved from ORCID. This author (name that was in the orcid record) is then added to the item. Here is what is in the database: select dspace_object_id,element,qualifier,text_value from metadatavalue,metadatafieldregistry where dspace_object_id='91d02f1b-8b2b-40e0-9d07-02e88a7fdef1' and metadatafieldregistry.metadata_field_id=metadatavalue.metadata_field_id; dspace_object_id | element | qualifier | text_value --+-++-- - 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | description | provenance | Submitted by Caroline Winter (mad...@uvic.ca) on 2024-03-01T21:21:29Z workflow start=Step: editstep - action:claimaction+ | || No. of bitstreams: 1 + | || BlankTestDoc.pdf: 133256 bytes, checksum: 323367c40f7b0d43d0f58119eb498c99 (MD5) 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | contributor | author | Winter, Caroline 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | contributor | author | Winter, Caroline 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | contributor | author | Winter, Caroline 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | date| issued | 2024 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | title || Test lookup tool 2 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | description | abstract | 1. ORCID in Solr field + | || 2. Author ID in Solr field + | || 3. ORCID iD in ORCID field Then the item is accepted and made public to the world but the authors name that was retrieved from ORCID disappears. Here is what is in the database: select dspace_object_id,element,qualifier,text_value from metadatavalue,metadatafieldregistry where dspace_object_id='91d02f1b-8b2b-40e0-9d07-02e88a7fdef1' and metadatafieldregistry.metadata_field_id=metadatavalue.metadata_field_id; dspace_object_id | element | qualifier | text_value --+-+-+- - 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | description | provenance | Submitted by Caroline Winter (mad...@uvic.ca) on 2024-03-01T21:21:29Z workflow start=Step: editstep - action:claimaction + | | | No. of bitstreams: 1 + | | | BlankTestDoc.pdf: 133256 bytes, checksum: 323367c40f7b0d43d0f58119eb498c99 (MD5) 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | contributor | author | Winter, Caroline 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | contributor | author | Winter, Caroline 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | contributor | author | 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | title | | Test lookup tool 2 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | description | abstract| 1. ORCID in Solr field + | | | 2. Author ID in Solr field + | | | 3. ORCID iD in ORCID field 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | description | provenance | Step: editstep - action:editaction Approved for entry into archive by Caroline Winter(madeup@uvic.c a) on 2024-03-01T21:38:16Z (GMT) 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | identifier | uri | https://hdl.handle.net/1828/16034 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | date| accessioned | 2024-03-01T21:38:16Z 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | date| available | 2024-03-01T21:38:16Z 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | date| issued | 2024 91d02f1b-8b2b-40e0-9d07-02e88a7fdef1 | description | provenance | Made available in DSpace on 2024-03-01T21:38:16Z (GMT). No. of bitstreams: 1 + | | | BlankTestDoc.pdf: 133256 bytes, checksum: 323367c40f7b0d43d0f58119eb498c99 (MD5) + | | | Previous issue date: 2024 my configs: ##
Re: [dspace-tech] Re: Submitting items using dspace 7 REST APTI
Tim, I created a test collection with just one field (dc.title) to test
submitting an item via rest API. I am able to submit successfully. I now
also want to include a pdf. Do you know what my json should look like?
Currently it looks like this (without the pdf file):
[
{
"op": "add",
"path": "/sections/teste/dc.title",
"value": [
{
"authority": null,
"confidence": -1,
"display": "TEST REST AROLDO WORKFLOW-155743",
"language": null,
"otherInformation": null,
"place": 0,
"value": "TEST REST AROLDO WORKFLOW-155743"
}
]
},
{
"op": "add",
"path": "/sections/license/granted",
"value": "true"
}
]
Aroldo
Em ter., 16 de jan. de 2024 às 14:51, DSpace Technical Support <
dspace-tech@googlegroups.com> escreveu:
> All,
>
> For future reference, we also have a page in our REST Contract describing
> the steps to performing a submission via the REST API:
> https://github.com/DSpace/RestContract/blob/main/submission.md
>
> Tim
>
> On Saturday, January 13, 2024 at 10:40:00 PM UTC-6 aro...@gmail.com wrote:
>
>> Guys, I finally learned how to perform a full submission here. After the
>> user authenticates, you need to obtain an id for the item: POST
>> server/api/submission/workspaceitems?owningCollection={collection id}
>>
>> Then call PATCH server/api/submission/workspaceitems/{item id} with JSON
>> (I created a test collection whose items only have one field):
>>
>> [
>> {
>> "op": "add",
>> "path": "/sections/teste/dc.title",
>> "value": [
>> {
>> "authority": null,
>> "confidence": -1,
>> "display": "AROLDO TEST WITH REST",
>> "language": null,
>> "otherInformation": null,
>> "place": 0,
>> "value": "AROLDO TEST WITH REST"
>> }
>> ]
>> },
>> {
>> "op": "add",
>> "path": "/sections/license/granted",
>> "value": "true"
>> }
>> ]
>>
>> Finally, to submit the item to the workflow, POST
>> /server/api/workflow/workflowitems passing as data
>> /server/api/submission/workspaceitems/{item id}.
>>
>> Aroldo
>>
>> Em sex., 12 de jan. de 2024 às 18:53, Aroldo Rique Júnior <
>> aro...@gmail.com> escreveu:
>>
>>> Guys, is anyone using the Dspace 7.x REST API to submit items?
>>>
>>> I can log in and check the status normally. I've already learned the
>>> /server/api/authn/login and /server/api/authn/status calls.
>>>
>>> I haven't been able to submit an item yet. From what I understand, first
>>> I authenticate and then I look for an id passing the uuid of the collection
>>> as a parameter, through the REST call
>>> /server/api/submission/workspaceitems?owningCollection=c57788fc-ad35-4e86-9b3c-764bad9d8bca
>>>
>>> And then, how do I submit my form fields? With which REST call? I
>>> created a test form with just one metadata: dc.title.
>>>
>>> Checking how the submission process occurs in the Chrome inspector, I
>>> saw that the REST call /server/api/submission/workspaceitems/155687 is
>>> executed with PATCH. Wouldn't it be POST?
>>>
>>> [image: image.png]
>>>
>>> Does anyone have a complete example of item submission using the REST
>>> API?
>>>
>>> Att,
>>>
>> --
> 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/f8f3def7-c0f8-4e24-9be1-162fe8195576n%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/CACKFi%2BdWfC0ck2pZOtaqV9M7BitgHjNNEWkbL%3DYvcdy8khUSew%40mail.gmail.com.
Re: [Extern] [dspace-tech] Abstract visualization
Hi Agustín,
Am 19.02.24 um 14:13 schrieb 'Agustín Alfieri' via DSpace Technical Support:
Hi Michael,
I like your solution. If the change for Dspace 7 is mainly made in
Angular I should be able to set it up.
[…]
sorry for the long delay.
We also have done this into a component, so this here is a bit old
and[…] limited.
This uses the ng-bootstrap NgbCollapse, so you need to include it in
your themes' eager-theme.module.ts:
import { NgbCollapseModule} from '@ng-bootstrap/ng-bootstrap';
[…]
@NgModule({
imports: [
[…]
NgbCollapseModule
]
Look if it transpiles flawlessly.
In the theme
/app/item-page/simple/item-types/untyped-item/untyped-item.component.html
add the following code:
object.metadata['dcterms.abstract']| keyvalue">
{{ abstract.value.language }}
{{ abstract.value.value }}
Beware our metadate for abstracts is dcterms.abstract , so change it in
the above code. For flags instead of text a bit more work is needed…
CU
Michael
--
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/ef4f5352-ab70-4166-9101-fc459031e7d6%40bibliothek.uni-kassel.de.
smime.p7s
Description: Kryptografische S/MIME-Signatur
[dspace-tech] Whitelabel error on ORCID
Hello all,
I just setup ORCID authentication, when I try to login, I see the following
error
[image: Screenshot 2024-03-01 at 11.43.02 PM.png]
Here I would like to know whether the
orcid.redirect-url=${dspace.serverl/url}/api/authn/orcid is valid or not.
Best Regards,
Zel
--
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/55a03adf-5dce-414f-9d41-e641bf67846an%40googlegroups.com.
[dspace-tech] Re: 7.6.1 ORCID authentification fail
UPD: ORCID authentification still fails in some browsers like older Chrome 109 (Win7). пʼятницю, 1 березня 2024 р. о 00:34:51 UTC+2 Andrew K пише: UPD: It's the same issue https://github.com/DSpace/DSpace/issues/9109 Moving *plugin.sequence.org.dspace.authenticate.AuthenticationMethod = org.dspace.authenticate.PasswordAuthentication* before *plugin.sequence.org.dspace.authenticate.AuthenticationMethod = org.dspace.authenticate.OrcidAuthentication* fixed the ORCID authentification. Also, ORCID login button moved down where it was before. Great -- 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/a4d3bbd8-4f47-48cf-9304-686e8525b8d5n%40googlegroups.com.
[dspace-tech] Re: item with many files not working.
Not directly answering your question but you could tune your nginx settings e.g. proxy_busy_buffers_size 512k; proxy_buffers 4 512k; proxy_buffer_size 256k; or disable buffering proxy_buffering off; which I wouldn't recommend for performance reasons. BR Maruan Sahyoun FileAffairs GmbH bens...@gmail.com schrieb am Freitag, 1. März 2024 um 01:43:23 UTC+1: > In dspace 7.6.1 I had an item with 25 files in it. > > after an image was generated for each pdf the page would not load. > > **pm2 is behind nginx and the nginx log says: > > 2024/02/29 16:00:50 [error] 25186#0: *3824 upstream sent too big header > while reading response header from upstream, > client: 142.104.201.218, server: dspace.library.uvic.ca, request: "GET > /items/b94e7193-a7dd-42ef-b551-5f31808291fb HTTP/1.1", > upstream: "http://[::1]:4000/items/b94e7193-a7dd-42ef-b551-5f31808291fb;, > host: "dspace.library.uvic.ca" > > when I removed all the generated images it worked again. > > My question: Is there a best practice to limit the number of files in an > item? > > Thanks, > Ben > -- 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/f384b729-0206-4fa6-9609-d8982ef2ca7bn%40googlegroups.com.
