search

rism-digital / muscat

🗂️ A Rails application for the inventory of handwritten and printed music scores
http://muscat-project.org
34 stars 16 forks source link

Visibility of cataloging projects #1340

Closed HirschSt closed 1 year ago

HirschSt commented 1 year ago

We should provide more visibility for grouping sources/sources for research projects / cataloguing projects, etc. Because a project-source/holding relation can be considered as a metadata information, linking could be done in Marc 980. Attribution to a project should be provided afterwards in special cases by maintenance.

For now we have the following options:

I. A dedicated Project authority

This would need a dedicated migration and a redesign of many parts in Muscat, probably the most expensive way to introduce projects.

II. Project as Institution (aka “Corporate Entity”)

We can use existing institution auth, but then we probably have to extend the model. Also projects can be managed by institutions, but not exist without any relation to institutions or people. Less expensive, but not totally appropriate.

III. Project as Publication entity

We can use existing publication auth, but then we also probably have to extend the model. A project can release publications, but it looks like that a project is no publication. Less expensive, but not totally appropriate.

IV. Project as Workgroup

Since every Muscat user is a member of a workgroup, it should be somehow possible to use this workgroup as a metadata for a source/holding etc. In this case also any source update can be triggered. Workgroup model should be improved substantially then.

Any opinions or additions?

HirschSt commented 1 year ago

PS: should we convert this issue to a github discussion? Unfortunately I am not allowed to do this ...