Skip to content

Feat: add extracted once in the metadata extraction - #224

Merged
imadbourouche merged 2 commits into
developmentfrom
feat/metadata-extract-once
Sep 18, 2025
Merged

Feat: add extracted once in the metadata extraction#224
imadbourouche merged 2 commits into
developmentfrom
feat/metadata-extract-once

Conversation

@imadbourouche

@imadbourouche imadbourouche commented Aug 28, 2025

Copy link
Copy Markdown
Collaborator

Context

related issues

Now we introduce the extracted once in the metadata extraction process. This means that if a metadata has the extracted: once we will proceed in these steps:

  1. we will check if the latest submission of the ontology contains this metadata
  2. if so we will not extracted again and the value will be the same
  3. else we will continue in the process of extraction

Why ?
To avoid the duplication of some metadata after curation (ex: Agents)

TO-DO

  • Check the complete process (UI, API, model) when deploy it

@imadbourouche imadbourouche changed the title Feat: Add extracted once in the metadata extraction Feat: add extracted once in the metadata extraction Aug 28, 2025
@imadbourouche
imadbourouche merged commit 471a9f1 into development Sep 18, 2025
8 checks passed
@jonquet

jonquet commented Sep 23, 2025

Copy link
Copy Markdown

For reference: metadata properties descriptions are available at:
https://data.stageportal.lirmm.fr/submission_metadata => for submission
https://data.stageportal.lirmm.fr/ontology_metadata => for ontology

@imadbourouche I can't see the change inside these links right now (no mention of extracted: once).
Might be because StagePortal is currently down?

@imadbourouche

Copy link
Copy Markdown
Collaborator Author

@jonquet yes it'w weird it's not showing it in the api response. in the file it's changed but in the api it's not showing i'll see what's wrong

@imadbourouche

Copy link
Copy Markdown
Collaborator Author

@jonquet fixed
image

@jonquet

jonquet commented Sep 23, 2025

Copy link
Copy Markdown

OK I see it now (just changed the name in the text of this PR).
Right now its "once" for all the agents properties.
But it also needs to be "once" for:

In addition I will suggest it also for:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants