Document the meaning of `ontologies` and `preferredMappingOntologies` in project documentation

[tskir]

Project DTO mentions the ontologies and preferredMappingOntologies fields. I assume their meaning is exactly the same as for ZOOMA, that is:

• First try to map to preferredMappingOntologies, in that order by priority;
• Then try the remaining ontologies which are not in preferredMappingOntologies, in no particular order.

If I'm correct, then I think this needs to be documented on that page for complete clarify. (And if I'm not please do correct me!)

Additionally, a point for discussion: should we simplify the model and just have a single prioritised list of ontologies?

[tudorgroza]

Not quite - these 2 are an abstraction of the hardcoded values used in the prototype. ontologies is indeed used as spec for the Zooma calls, while preferredMappingOntologies is a replacement at project level for the hardcoded efo - and is used when querying OLS for terms during the matchmaking process.

[tskir]

Ah, I see, thanks! I think the ontologies to query ZOOMA and OLS will be pretty much always identical, so they could be merged into a single configuration variable. We can discuss this today

[tskir]

As discussed on the call 2021-03-23, the context configuration includes separately:

• A list of ZOOMA datasources
• A list of all acceptable ontologies (the terms which can be either be used directly or imported into target ontologies)
• A list of target ontologies (the ones the terms from which can be used directly).

It would be useful to update the docs to reflect this

[tudorgroza]

Done:

• https://github.com/EBISPOT/ontotools-curator/wiki/Project-DTO
• https://github.com/EBISPOT/ontotools-curator/wiki/Context-DTO