GenomicsStandardsConsortium
a top priority -- to reinstate the top level MIxS release folder with all of the v6.0 release files
With some recent updates to this directory, the MIxS release folder had been moved to a sub, sub,sub directory. Although the release is available in the releases directory (far right of the page), this is too obscure for our users, who have always had a top level release directory, to which they maintain links, to get the file(s), that they need.
The action to be taken, in the next week, is to recreate a top level MIxS release folder in this repository, so that when major releases are made and stored under 'releases' area as they are currently, that the releases, top level, folder is also populated with the latest release files. Also, that when we are in between major releases, the minor releases should have a folder there as well.
The direct to be reinstated at the top level of this repository: GenomicsStandardsConsortium/mixs should be: releases v6.0 release minor releases: v 6.1 release v 6.2 release
Yes, I recognize this replicates the 'releases' section, however, it is needed for our end users to make it easy to get to those files.
Cheers, Lynn
This should be discussed at both TWG and CIG. My view is that the current GitHub repo is not the correct place to be storing the old versions of the checklists (or anything else), but having the current version files (our products if you like) front and center in an obvious place would be a good thing.
Agreed, good point Chris. Make it easy for users to find the most recent release files.
On Wed, Nov 1, 2023 at 11:21 AM Chris Hunter @.***> wrote:
This should be discussed at both TWG and CIG. My view is that the current GitHub repo is not the correct place to be storing the old versions of the checklists (or anything else), but having the current version files (our products if you like) front and center in an obvious place would be a good thing.
— Reply to this email directly, view it on GitHub https://github.com/GenomicsStandardsConsortium/mixs/issues/692#issuecomment-1789146715, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBB4DIBRP5ARB3JY7ENE23YCJSGHAVCNFSM6AAAAAA6ZMHSMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBZGE2DMNZRGU . You are receiving this because you were mentioned.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 @.***
I'll make sure this is top of the agenda at the TWG call next week. With the linkml release, it should now be simple to find the latest release right on the home code page in github in the folder MIxS. Older releases are tagged and can be found that way. As for Chris, I agree that github should be where developers (who will understand github) should go to look for files, whereas most people will access it via our website and documentation. We need to make sure all of it is clear, including the readme on github. I also need to update the PURLs. Presumably the old ones still work as they should point to tags, but I need to check them.
I think this has been solved? As this exists: https://github.com/GenomicsStandardsConsortium/mixs/tree/main/mixs-templates
Is the next / final task to wrap this up documentation? @ramonawalls , @lschriml
We still need to indicate that these are Release 6, and to separate release docs from devel docs in the repository Sent from my iPhoneOn Jul 16, 2024, at 5:42 PM, Montana @.***> wrote: I think this has been solved? As this exists: https://github.com/GenomicsStandardsConsortium/mixs/tree/main/mixs-templates Is the next / final task to wrap this up documentation? @ramonawalls , @lschriml
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
@mslarae13 I don't believe this issue is about data collection templates. (Or at least not entirely about them). It's also about the TSV representations of the MIxS classes.
- This PR generates them. I beleive @lschriml has seen them and has informally approved them
- https://github.com/GenomicsStandardsConsortium/mixs/pull/812
- @sujaypatil96 is going to add code that organizes them better.
- as @lschriml mentioned, @pbuttigieg suggested that we have a clearer distinction between development drafts of release-able artifacts, vs the final release artifact location. I don' think we have worked that out yet.
Sounds good. Making great progress !!
On Thu, Jul 18, 2024 at 10:58 AM Mark Andrew Miller < @.***> wrote:
@mslarae13 https://github.com/mslarae13 I don't believe this issue is about data collection templates. (Or at least not entirely about them). It's also about the TSV representations of the MIxS classes.
- This PR generates them. I beleive @lschriml https://github.com/lschriml has seen them and has informally approved them
- @sujaypatil96 https://github.com/sujaypatil96 is going to add code that organizes them better.
- @pbuttigieg https://github.com/pbuttigieg suggested that we have a clearer distinction between development drafts of release-able artifacts, vs the final release artifact lcoation. I don' tthink we ahve worked that out yet.
— Reply to this email directly, view it on GitHub https://github.com/GenomicsStandardsConsortium/mixs/issues/692#issuecomment-2236795182, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBB4DLTYLOK6PLZ3R34RTTZM7JZHAVCNFSM6AAAAABK7MYE2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZWG44TKMJYGI . You are receiving this because you were mentioned.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 @.***
as @lschriml mentioned, @pbuttigieg suggested that we have a clearer distinction between development drafts of release-able artifacts, vs the final release artifact location. I don' think we have worked that out yet
This would be similar to what we do with OBO ontologies, where release artifacts are staged in a src directory before an official release triggers a copy to the top level or an approriate directory
Discussed at 2024-07-23 @lschriml approves the https://github.com/GenomicsStandardsConsortium/mixs/tree/main/mixs-templates
@jfy133 noticed there were some bugs with examples, and slot usage bugs see the PR#812 linked above
One final change to make. Make sure VERSION is obvious on https://github.com/GenomicsStandardsConsortium/mixs/tree/main/mixs-templates
- Current development version (6.2 right now)
- released / active version (6.0)
- Old version