Open slint opened 10 months ago
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/*
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.
Agreed, I will create a "mfn" branch then, as the directory already contains that name
Here is a preview of the un-normalized data. Please respond if you spot mistakes result.csv
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?
Depends on new input from MfA folks: https://github.com/plazi/arcadia-project/issues/234