Exclude sites assignment from "protection" of a catalogue

[Zack-83]

Rationale / Begründung

In multi-sites instances, managers may see all catalogs, and for that reason some are write-protected, to avoid accidental editing or deletion.

Yet this protection also hinders to pick up existing catalogs and give them free for the own instance without asking an admin.

Affected

Managers

Minimal functionality

The possibility of assigning catalogs (views, ...) to sites should bypass the writing protection.

From an information science point of view, the connection catalog <--> site belongs more to the site and should be accessible independently, also to avoid proliferation of clone catalogs (options, ...).

[MyPyDavid]

yes, think it's a good idea. To be precise, only the assignment of sites for the which the user is also an editor should editable..

[MyPyDavid]

from @jochenklar :
we could use a new endpoint that makes joinElement for sites,
and a button (with new icon) in the element panels that joins or remove the sites from the element (eg catalog)

[MyPyDavid]

I found these buttons as an option to add or remove the current site from an element.

• add https://fontawesome.com/v4/icon/calendar-plus-o
• remove https://fontawesome.com/v4/icon/calendar-minus-o

Would those fit or do you have other suggestions @jochenklar?

[jochenklar]

Mhm, it looks a bit to much like a calendar, maybe https://fontawesome.com/v4/icon/minus-square-o?

[MyPyDavid]

one technical question, does this mean that it needs to bypass the LockedValidator 🙈 as well?

[jochenklar]

Yes, but I don't think its a problem.

[MyPyDavid]

thanks, yes, it was already in the backend like that 👍 just had to remove it from the frontend