Should creating/editing services/software in the admin dashboard be disallowed?

[vronk]

Currently, it is possible to add/edit Service Software via default Admin dashboard means.
Should this be diasllowed?

[stefanprobst]

in report edit forms creating/editing software and services in not allowed, but links to sshoc marketplace as source of truth.

[laureD19]

admin need to keep creating/editing rights for software and services (for metadata fields that are not populated by the MP) as the admin dashboard is where we manage the DARIAH portfolio (vs. catalogue coming from the sshoc marketplace). There is more information in the KB than in the MP.

This is one of the reasons we need to clarify #182

[stefanprobst]

"creating" means adding new software/service entries via admin dashboard. i think we should not allow this, because the source of truth for all software/services should be the marketplace.

as for "editing": yes, some fields on software/service only exist in the dariah knowledge base, and these need to be editable by admins. however, fields which are populated by ingesting data from marketplace should probably be readonly, because any local changes will be overwritten when running the sshoc ingest anyway.

fields populated by ingest are "name", "url", "countries", "marketplaceId".

[laureD19]

The problem is that we have services (maybe software too, I would need to check) that are listed in the KB that are not in the marketplace (all the "internal services" for ex.). We want to keep track of them internally but there is no point listing them in the marketplace

[stefanprobst]

there is no point listing them in the marketplace

why not? can you give an example?

we should try to avoid a two-sources-of-truth scenario if possible

[laureD19]

The portfolio is a superset of the catalogue.
Under internal services, we track all commercial services DARIAH uses for ex. (zoom, google...)
Then, we also have services under development, deprecated... So these ones, there were once in the MP, but are not anymore, or will be one day.
So, read-only for fields coming from the MP and items coming from the MP, ok. But for others cases, admin need to be able to edit

[vronk]

in other words knowledge base should serve as a service portfolio, which is a superset of information in a catalogue (MP).

So I am afraid "two-sources-of-truth" scenario is unavoidable.

[vronk]

where do you see potential conflict?