Repository navigation
Enable the access rights modification feature(#63818) #1951
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -889,3 +889,5 @@ WEKO_RECORDS_UI_S3_TRANSFER_USE_THREADS = True | |
| WEKO_RECORDS_UI_S3_TRANSFER_MAX_CONCURRENCY = 10 | ||
| """Number of threads for multipart upload/download for S3 compatible service transfer. Default is 10.""" | ||
|
|
||
| WEKO_SEARCH_FIX_ACCESSRIGHTS = True | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🟡 Medium · Indexing adds per-record database work When a bulk indexing or reindexing job processes many records, indexing reads Avoid per-record metadata queries during indexing, for example by batching the required metadata or reusing data already loaded for the record. Prompt for AI agentsIn `scripts/instance.cfg` at line 892:
**Indexing adds per-record database work**
When a bulk indexing or reindexing job processes many records, indexing reads `record.updated` in `_prepare_record`; with this setting enabled, that property queries record metadata and resolves its item-type mapping for each record. Bulk indexing therefore adds per-record database and mapping work, slowing reindexing and other indexing workloads.
Avoid per-record metadata queries during indexing, for example by batching the required metadata or reusing data already loaded for the record. |
||
| """Fix access rights for search indexes. True if fixing access rights.""" | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Medium · Harvest fails on timestamp dates
When a file’s
dateValueis present but is not exactlyYYYY-MM-DD, such as a valid date-time value,Record.updatedpasses the file’sdateValuedirectly todatetime.strptime(..., "%Y-%m-%d"), raisingValueError; OAI-PMH response generation then fails when it readsrecord.updated.Validate or safely parse
dateValuebefore callingstrptime, and skip values that cannot be parsed as dates.Prompt for AI agents