Skip to content
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

Denormalize/parse MfN input sheet into Lycophron tempalte #25

Open
slint opened this issue Nov 1, 2023 · 5 comments
Open

Denormalize/parse MfN input sheet into Lycophron tempalte #25

slint opened this issue Nov 1, 2023 · 5 comments
Assignees

Comments

@slint
Copy link
Member

slint commented Nov 1, 2023

  • Define unique IDs for all the objects (speciments and photos)
  • Fill-in bi-directional links between specimen <-> photo
  • Map input data to DarwinCore/AudubunCore metadata fields

Depends on new input from MfA folks: plazi/arcadia-project#234

@CNaseband
Copy link

I think an automated solution could be reached, it would be written in Java though.
For possible future use I want to make the source code available here as well.

Where would you prefere the code to be placed? Maybe somewhere along:

/src/java/unnormaliser/*

@slint
Copy link
Member Author

slint commented Nov 1, 2023

Given that this will very likely be a one-off type of script (probably used twice, for the sample set and for the final data), maybe we put the code in a new branch inside a scripts/mfn-unnormalizer directory?

If we see that we need to run this a lot, then we'll probably merge into master and maintain. We should though push for them to eventually conform to the final Lycophron input format, rather than depending on us to convert their output everytime.

@CNaseband
Copy link

Agreed, I will create a "mfn" branch then, as the directory already contains that name

@CNaseband
Copy link

Here is a preview of the un-normalized data. Please respond if you spot mistakes
result.csv

@myrmoteras
Copy link

Given that this will very likely be a one-off type of script (probably used twice, for the sample set and for the final data), maybe we put the code in a new branch inside a scripts/mfn-unnormalizer directory?

If we see that we need to run this a lot, then we'll probably merge into master and maintain. We should though push for them to eventually conform to the final Lycophron input format, rather than depending on us to convert their output everytime.

not sure whether this is a one-off. The goal here is to demonstrate that we can do this at larger scale as a continuous process. It is even more complicated, that is to create a project that allows to create new species descriptions, which, when accomplished, would be uploaded as an articles with treatments with figures that reference to the images uploaded here.

The question then should be whether we make this a MfN/Plazi/Zenodo project or a project that would ultimately reside in Zenodo?

@slint slint changed the title Denormalize/parse MfA input sheet into Lycophron tempalte Denormalize/parse MfN input sheet into Lycophron tempalte Jun 25, 2024
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

No branches or pull requests

3 participants