-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃拰 Files from Debian 馃悶 #57
Comments
excellent summary @matuskalas , thanks. Now, regarding the problem of multiple packages related to one bio.tools entry, I would strongly argue that: |
Just to chip in here with a reminder of bio.tools scope vis-脿-vis tools and packages - bio.tools aims to be a registry of unique tool functionality, which means the default is for different interfaces providing essentially the same functionality to go in one entry (see the guidelines written for IFB recently). cc @hansioan |
Exactly @joncison 馃憤 Therefore, as examples:
|
In the awesome YAMLs from Debian - despite of the highly appreciated perfectionism - we found a couple of 馃悶馃悰. @smoe if/when you'll have a bit of time for hacking the "yamlDump" again, it'd be super lovely if you could test the following records/phenomena with the edam.sh and edamJson2biotools.py? e^6 thanks!! 馃殌馃檹馃徑
Note 1: In these 2 cases, there is probably a reason to maintain both major versions in Debian (or isn't it?), and therefore we should consider that in bio.tools too: consider whether they should have different descriptions, and maybe also EDAM annotation (if not, keep just 1 record), plus credits, pubs, ...
Are there any more pairs of src pkgs that point to the same bio.tools record? What should be the general solution, or options, here? Any additional ideas on this issue @hmenager @bgruening ? (e.g. having 2 debian.yaml files in 1 bio-tools/content directory for the start? )
dnacopy: some YAML validators are happy, but some dislike the colon+space in
R package: DNA copy number data analysis
bowtie: funny "punctuation" of function Genome indexing (Burrow-Wheeler). Ok in bowtie2. It looks like the only occurence of this phenomenon.
Note 2: Btw., @hmenager @bgruening @OlegZharkov have the best experiences with using the ruamel.yaml python lib for creating pretty YAML files.
The text was updated successfully, but these errors were encountered: