rubbish, great idea!

experiment with https://pypi.org/project/django-partial-date/ for storing partial dates?

https://django-autocomplete-light.readthedocs.io/en/master/

when organities have multiple roles in a production, show the production only once

It would be good practice to provide an image (scan) or pdf of the playbill in which the shows and credits are listed. So, this needs to be uploaded.

• so that they can either be merged
• or that their difference can be made more explicit, e.g.
  -- by a clearly diverging disambiguation line
  -- by relating the two entities with a relation that explains their relationship (e.g. A is a festival by B, or explicitly a relationship "A B")

Next to fields that are mappable on wikidate or musicbrainz, there should be an indication if it is the same value as in wikidata or musicbrainz

for classes, add verbose_name and verbose_name_plural to class Meta
for fields, add verbose_name and verbose_name_plural as parameter

has as member > member of

get credentials via heroku website

So that you can view the main organities for a production in the production_listView.

they should e.g. all have a name, sort name and disambiguation

they all have a name

e.g. an event on facebook is published as a schema.org event, so we can read relatively structured metadata via a browser plugin. The event gets stored as a show in stagebrainz, and it can get picked up via the QA list of shows without connected production. That last step is manual work.

The structure of all the RelationXYType entries is identical. Let's avoid duplicate code.

Perhaps something like this?

• superusers: obvious
• admins: add, delete, update, merge > for all entities
• quality assurance: access to QA screens, add, update, merge > for core entities
• editors: add, update > for core entities
• contributors: add > for core entities

e,g, a person is related to a character in the context of a production

it's all the same code anyway, so let's reuse code!

A generic merge functionality to merge Entities, EntityTypes, Relations and RelationTypes.

E.g. a list of urls without any related entities.

Collections of entities of the same model, e.g. a collection of productions
e.g. "Kunstenpunt collection of Flemish subsidized productions", "Kunstenpunt collection of Flemish/Dutch theatre text authors 2019", ...

When there are 15 organities connected to a production, some organities are highlighted in the announcements, e.g. the director or an important actor. This could be captured with a simple boolean box in the RelationXY model.

https://pypi.org/project/django-bootstrap-modal-forms/

https://docs.djangoproject.com/en/dev/howto/initial-data/#providing-initial-data-for-models

with an overview of the basic fields, the related organities, and a show

The Organisations, People and Venues tables are identical, so could be simplified to a single table, in which the Type helps to distinguish between the different entities.

These relations are typically semantic in nature, so the type should provide a field in which a wikidata P-number can be stored (or something else semantically)

Generated html should contain a json-ld or something like that.

to disambiguate between different productions, the season or start/end date should be listed

Let's take structured data urls away from urls, and provide a (semantic) identifier field for organisations people and venues