EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #09655
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Sword 2.0 API upload times
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Sword 2.0 API upload times
- From: Martin Brändle <martin.braendle@uzh.ch>
- Date: Fri, 1 Mar 2024 15:48:17 +0000
|
CAUTION: This e-mail originated outside the University of Southampton.
Dear all, since very recently, one faculty of our university deposits its dissertations via Sword 2.0 API. The EP3XML with embedded PDF is deposited. Everything works fine, however, the faculty observes that it takes unproportionally long the bigger the size of the PDF is, until they get process termination feedback:
Is such a behaviour known to you? Any adjusting screws? We do some checks such as scanning for viruses or format determination using Droid. The former is done immediately in the document_validate.pl, the latter is being triggered after the document has been uploaded. So I don’t see any bottleneck
in these processes. Kind regards, Martin -- Dr. Martin Brändle |
- Follow-Ups:
- Re: [EP-tech] Sword 2.0 API upload times
- From: David R Newman <drn@ecs.soton.ac.uk>
- Re: [EP-tech] Sword 2.0 API upload times
- Prev by Date: Re: [EP-tech] 0 byte file uploads
- Next by Date: RE: [EP-tech] 0 byte file uploads
- Previous by thread: [EP-tech] 0 byte file uploads
- Next by thread: Re: [EP-tech] Sword 2.0 API upload times
- Index(es):