Key to me here is not whether the product is open source or not, but if the data is readily available in a decent format, which I think is what Eric is saying as well.
In that spirit, happy to add whatever kind of export function for the discussions in CKM, via the REST API in some form or more likely via a csv, xml, or json file available to CKAs/admins or whatever does the trick…
I agree with the advantages and disadvantages mentioned above.
If as a consequence of assessing these advantages and disadvantages, a CKM instance such as the int’l openEHR CKM doesn’t want to use the internal CKM discussion space, we could look into adding links from these CKM discussion spaces to the appropriate place in Discourse - assuming there is a clear convention on where to find the appropriate topic(s) on Discourse based on the base url of the openEHR Discourse site.
In that regard, it is a bit unfortunate if there can only be one Discourse topic per archetype (and template, project, general discussion?) as I think Erik was suggesting. One topic may be a bit too limited to work well for different discussions about each archetype - or is this something you feel comfortable with?
However, the alternative of having one Discourse category per archetype may be overkill - especially if a user needs to subscribe to each category individually as at least used to be the case.
Using Discourse Tags with the archetype-id or CKM’s citeable identifier (which never changes) may be another option, but this requires that someone manages the tags on discourse so that CKM can link to the appropriate search results page. Not ideal either, but that in my limited understanding of Discourse are the three available options - unless some one has others?
Either way, it won’t be as convenient if you are in CKM as it is now and there are things that cannot be done like creating an editor task based on a discussion, being notified of new discussions in CKM as per your notification settings and subscriptions to archetypes, editors inviting reviewers based on their participation in discussions about that archetype.
There are some other details to be solved like
- how to handle any discussions occuring for archetypes/templates in private incubators in CKM;
- what to do with project discussions and general discussions;
- what identifier to use for templates.
Also note that archetype-ids can and do regularly change in CKM as part of the editorial process - the most common one is probably from v0 to v1, but anything can happen before the archetype’s initial publication.