Do we need any components related to mappings?

[stefandesu]

Right now, we only have components related to concepts and schemes, and some general purpose things. But there is literally nothing about mappings and concordances, even though they play an important part in project coli-conc.

Question: Do we need any components related to mappings and concordances? If yes, which components could that be?

[nichtich]

We want to show mappings in BARTOC as well. I'd postpone this feature or we should discuss the general way mappings should be shown (some of them could be combined in one component)::

1. Mapping Details (the modal used in Cocoda)
2. Mapping List with targets a concept is mapped to
3. Mapping List with sources a concept is mapped from
4. Mapping List or graphical view what a concept is mapped from and to (requires to include direction)
5. Table of arbitrary mappings with several details

I think the full mapping table is too complex but a MappingDetails (1) and MappingList (2-4) could be part of jskos-vue.

[stefandesu]

Sounds good. I'd suggest to postpone as well until we were able to integrate jskos-vue into Cocoda and BARTOC, and then we can start with this one. If we try to do it all at the same time, we'll never finish. 🙈

[nichtich]

jskos-web implements a mapping view based on jskos-vue. This might be moved as component to jskos-vue to also to be used by jskos-proxy (see gbv/jskos-proxy#4) and later by Cocoda as Mapping Details. jskos-proxy, however, also requires a component to list mappings from or to a given concept (to be shown as additional tab in concept details).