Make it even easier for large scale consumers to get the version updates of GSC MIxS

[Woolly-at-EBI]

Make it even easier for large scale consumers to get the version updates. Similar may be useful for people/groups just needing one or two MIxS checklists.
Current enablers include:

• The information is being maintained in a more structured LINKML form rather than XLSX.
• Git is being further utilised e.g. versions

use cases include:

• what new checklists/packages/extension have been added or removed? (between 2 releases)
• what terms have been added or removed? (between 2 releases)
• what terms have been updated, e.g. structured_name, title_name, definition, pattern etc. (between 2 releases)

Suggestion is to start simple:

• brief documentation on typical use cases and what parts of the linkml are relevant.
• some example python code to meet those use cases
• an automated structured report of differences between versions? (would supplement any manual docs)

It is possible that it may necessitate changes to the linkml.(I can't envision anything yet)

[lschriml]

Great suggestions Peter !!

…

On Tue, Jan 7, 2025 at 3:49 AM Peter Woollard ***@***.***> wrote: Make it even easier for large scale consumers to get the version updates. Similar may be useful for people/groups just needing one or two MIxS checklists. Current enablers include: - The information is being maintained in a more structured LINKML form rather than XLSX. - Git is being further utilised e.g. versions use cases include: - what new checklists/packages/extension have been added or removed? (between 2 releases) - what terms have been added or removed? (between 2 releases) - what terms have been updated, e.g. structured_name, title_name, definition, pattern etc. (between 2 releases) Suggestion is to start simple: - brief documentation on typical use cases and what parts of the linkml are relevant. - some example python code to meet those use cases - an automated structured report of differences between versions? (would supplement any manual docs) It is possible that it may necessitate changes to the linkml.(I can't envision anything yet) — Reply to this email directly, view it on GitHub <#882>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBB4DL5ZQ42RY2RIXVYEWL2JOII7AVCNFSM6AAAAABUXHLU4GVHI2DSMVQWIX3LMV43ASLTON2WKOZSG43TEMRUGQZDMNA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Lynn M. Schriml, Ph.D. Associate Professor Institute for Genome Sciences University of Maryland School of Medicine Department of Epidemiology and Public Health 670 W. Baltimore St., HSFIII, Room 3061 Baltimore, MD 21201 P: 410-706-6776 | F: 410-706-6756 ***@***.***