You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently parsing and releasing the BCIO upper level consists of several steps, including that we parse the BCIO Upper Defs spreadsheet and merge the content with the spreadsheet of extracted relations from LucidChart to create the BCIO Upper Level Merged spreadsheet. However, there is a bug in this process in that the merged file does not contain the correct status flags as are specified the original Upper Defs spreadsheet. In addition, the LucidChart upper levle visualisation is not editable by all team members. Thus, to simplify the release workflow, suggest that the Upper Level Merged file be corrected and then the Upper Defs file be removed. Thereafter, users can edit the Upper Level Merged file directly including maintaining status and relationships.
The text was updated successfully, but these errors were encountered:
Currently, the fields included in the BCIO Upper level Merged spreadsheet are hardcoded to BCIO_ID, Name, Parent, Definition, Synonyms, Examples - plus relations. Therefore, all of the following fields defined in BCIO_Upper_Defs.xlsx are not included:
Logical definition, Definition source, Curator note, Comment, Curation status
@jannahastings Are the others expected to be missing or should they be included as well?
Currently parsing and releasing the BCIO upper level consists of several steps, including that we parse the BCIO Upper Defs spreadsheet and merge the content with the spreadsheet of extracted relations from LucidChart to create the BCIO Upper Level Merged spreadsheet. However, there is a bug in this process in that the merged file does not contain the correct status flags as are specified the original Upper Defs spreadsheet. In addition, the LucidChart upper levle visualisation is not editable by all team members. Thus, to simplify the release workflow, suggest that the Upper Level Merged file be corrected and then the Upper Defs file be removed. Thereafter, users can edit the Upper Level Merged file directly including maintaining status and relationships.
The text was updated successfully, but these errors were encountered: