Closed mdoering closed 5 years ago
@thomasstjerne do you foresee troubles with the UI? I would think it gets simpler if you do not have to deal with colsource for basic sector mappings and decisions
for the changed sector/colSource its not much of an API change, but it might effect how you manage sectors and colsource in the frontend: https://github.com/Sp2000/colplus-frontend/issues/108
Sectors and are editorial decisions are tight to a ColSource which is part of a Dataset. ColSource is only needed for the CoL, not the pCat. Very often this is 1:1 anyways and just added complexity.
Suggest to relate all decisions and sectors directly to a dataset and offer an optional colSourceKey on sectors to group them.