search

ykkunkels / ESIR_portal

Shiny app for the ESM Item Repository
2 stars 0 forks source link

Contribution workflow: make adaptations based on updated format of submission template #10

Open lauravanheck opened 8 months ago

lauravanheck commented 8 months ago

There are three changes to the submission template that need to be reflected in changes in the contribution workflow. This issue lists the proposed solutions.

  1. Additional row. This row should be deleted from the template because it contains instructions, not data to be added to the repository (similar to deleting the example rows). EASY
  2. Additional columns. The information of the additional columns should be added to existing columns (including an indication which column the value was added to originally), then the columns should be deleted; resulting in the same number of columns as the previous submission template format. EASY
  3. Different column order. The order of the columns in the new submission template reflect the order of the columns in the ESM item repository dataset; the previous submission template had a different column order. Adjust the code so the contribution workflow is independent of the order of the columns and depends on the column name instead. There should also be a warning if a certain column name cannot be found, possibly indicating the incorrect removal of a column during the submission process. EASY
ykkunkels commented 8 months ago

Perhaps good to first check whether this issue can be solved on the data-side of the project instead of the coding-side.

Also, we first have to agree on the format of the data and if the data-format of the data delivered from contributors matches that of the main dataset ("DATA_ESM_Item_Repository.csv")