IDs when adding concepts in WebProtege VERSUS Comments in WebProtege

[matuskalas]

alpha02 collaborative dev

IDs had to be changed manually when merging to git, as the WebProtege project was set up unoptimally.

Problem: When afterwards merged back to WebProtege, would loose Comments for re-ID-ed concepts.

Thus are all comments kept in old, frozen "live" alpha02_dev at https://webprotege.stanford.edu/#projects/046821ee-2307-4d3f-b4a7-dececc665b92/edit/Classes

Was after alpha02

FOR EDITORS NB.: (CHANGE FROM PREVIOUS!) When adding a new concept, you MUST fill in an appropriate ID a.k.a. IRI a.k.a. URI of the new concept. In order to support future traceabilty, it MUST have the following form:

http://edamontology.org/<sub-ontology>___<underscored-label>

where <sub-ontology> is one of data, format, operation, topic

and <underscored-label> is the first short label you give to the concept, with spaces replaced by underscores ('_').

The 3 underscores ('___') are necessary in this temporary agile setting, to mark the next 3rd alpha version alpha03.

Example:
http://edamontology.org/topic___New_ultra_super_nanoscopy

Sorry for a complication and thank you for understanding!!!

That didn't really work well

Still problems:

• Had to change some IDs manually while merging into git version
• When afterwards merged back to WebProtege, lost Comments for re-ID-ed concepts

From alpha03

IDs should be automatically assigned as http://edamontology.org/znew____<underscored-label>. Number of 'N' underscores corresponds to the alpha'N'_dev version.

N.B. !!DANGEROUS!!: Thus Comments would be kept only for:

• older concepts, or
• ONES THAT HAVE BEEN MERGED TO GIT & BACK TO WEBPROTEGE, or
• ONES THAT ARE ADDED WHILE TEMPORARILY CHANGING THE ID SETTINGS. !!DANGEROUS!!