This is a follow-on from #912 -- thank you for that!
Currently, the only way to get some project information (analyzer_spec, vocab_spec, transform_spec, backend.params and backend.DEFAULT_PARAMETERS) is directly from an AnnifProject object. In cannif, I import the annif module directly to read them, and I would prefer to not have to.
It would be very helpful to have these exposed within the REST interface instead. I'm mindful of overloading the /projects response object, and the fact there are backend and vocab dicts already. However, at a minimum the *_spec fields would go a long way, and backend_params gives enough information to recreate or update a project.
I would even support a /backends endpoint for the information provided in backend.DEFAULT_PARAMETERS, especially if it provides a list / dict of configured / installed backends eg. somehow identify or omit those without external dependencies installed.
This is a follow-on from #912 -- thank you for that!
Currently, the only way to get some project information (
analyzer_spec,vocab_spec,transform_spec,backend.paramsandbackend.DEFAULT_PARAMETERS) is directly from an AnnifProject object. In cannif, I import the annif module directly to read them, and I would prefer to not have to.It would be very helpful to have these exposed within the REST interface instead. I'm mindful of overloading the
/projectsresponse object, and the fact there arebackendandvocabdicts already. However, at a minimum the*_specfields would go a long way, andbackend_paramsgives enough information to recreate or update a project.I would even support a
/backendsendpoint for the information provided inbackend.DEFAULT_PARAMETERS, especially if it provides a list / dict of configured / installed backends eg. somehow identify or omit those without external dependencies installed.