-
Notifications
You must be signed in to change notification settings - Fork 0
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
don't add invenio-classifier keywords to records #554
Comments
Instructions to cleanup after inspirehep/inspire-next#4350 in deployed on prod: Exec into primary postgres node, run UPDATE records_metadata
SET json = (
SELECT jsonb_set(
json::jsonb,
'{keywords}',
(
SELECT jsonb_agg(elem)
FROM jsonb_array_elements(json::jsonb->'keywords') AS elem
WHERE elem->>'source' != 'classifier'
)
)
)
WHERE json::jsonb->'keywords' IS NOT NULL; |
@PascalEgn it's a very bad idea to modify records in the DB directly, as many things are done at the application level during the update (reindexing this record and dependent records if needed, storing a new version in the |
For the cleanup script, the following simple search can be used in the end: |
I opened a PR on the curation script repo, you can check if its fine @michamos :) |
Currently, we're adding keywords extracted by
invenio-classifier
in the article workflows to Literature records. These are only temporary, and are supposed to be later replaced by manually assigned keywords. However, DESY has stopped assigning those keywords manually, so we should stop putting the automated keywords in records too.This requires removing the
prepare_keywords
workflow step from thearticle
andcore_selection
workflows.Once that's implemented, we'll also need to clean up existing records.
The text was updated successfully, but these errors were encountered: