This is done via #10.

• Use admin-index
• Style like Open Zaak
• Provide fixture to make the admin-index make sense

Based on the existing ZGW demo app, we can extend this demo app to show Objects and Objecttypes functionalitities.

The existing app can be found here: https://zgw-demo.vng.cloud/
And on Github: https://github.com/VNG-Realisatie/gemma-zaken-demo

We'll use the current JSON-schema definitions that we have: Boom and Melding. Geo-coordinates need to be present in the Objects API to make this work and Boom should have them.

1. Open data -- A map showing objects of selected (public) objecttypes (ie. Boom)

Similar to: https://zgw-demo.vng.cloud/apps/opendata/

Instead of "zaaktypen" it should say "objecttypen". Only public objecttypes should be shown, so in this case: Trees.
Later, I want to add "Lamppost" as public Objecttype to the API and it should then show up in the list of objecttypes in the demo app. We also need a testset for this.

• Add geocoordinates to objects api
• Add Boom schema and add a demo set of (like 10 on a specific geo area)
• Copy app to new app
• Retrieve public Objecttypes and show as checkbox on the side, instead of Zaaktypes
• Retrieve Objects (within geo-area?) of selected Objecttypes
• Create lamppost schema and 10 demo items or so (in the same geo area as trees)

2. Melding Openbare Ruimte -- Make a Melding about a Boom

Extension on: https://zgw-demo.vng.cloud/apps/mor/

Instead of selecting an address, you can select a public objecttype (tree) and select a specific tree on the map. On submission, a Zaak of Zaaktype "Melding Openbare Ruimte" is created, with related ZaakObjecten: Boom and Melding.

• Copy MOR app, to use for selecting objects
• Retrieve public Objecttypes and show as pulldown
• Retrieve Objects (within geo-area?) of selected Objecttype
• Allow user to pick shown object
• Submitting should create a zaak with related ZaakObject: Melding and Tree. The Melding should have some Melding specific values that are appropriate.
• Bonus: Make a radio button to switch between selecting an address and selecting an object in the same MOR app.

3. ZAC -- Show related objects

Extension on: https://zgw-demo.vng.cloud/apps/zaakbeheer/a6811688-be0e-4676-83d5-5ec8ae0d855f/

As part of the Zaak detail screen, we can show the related ZaakObjecten.

• Retrieve ZaakObjecten that are relelated to the Zaak, and show Objecttype name and maybe some generic data?
• Bonus: When clicking a ZaakObject, a detail screen will show, showing all key-values of that object.

Both are text fields, optional and part of the Objecttype meta data (outside the schema).

To document issues from #47

There should be a list of existing data sources that currently define and or manage information models.

This flag indicates whether this data is accessible without any specific authorizations. It's a boolean field in the meta data of the Objecttype API.

Note that an API-key might still be required to throttle requests.

The domain is a certain business department. I'm not sure if domain is the right field name. It's a textfield and can be optional for now.

It would be nice to have a compatibility matrix or score with existing models. For example, a tree is defined by 5 organizations and having an objecttype would be yet another. How much are these the same? Can they be used together, or are they interchangable?

Import test.

Mogelijke onderwerpen:

• bespreken initiele objecttypes

Mogelijke objecttypes:

• Inkomen (GBI)
• Vermogen (GBI)
• Vorderingen (GBI)
• Huishouden (Rotterdam)
• Meldingen (VNG/Amsterdam)
• Evenementenvergunningen (Utrecht)
• Activiteiten (sociaal domein) (Utrecht)
• Subsidies (Delft) [1]
• Bomen (Delft) [2]

[1] Verankerd in het Gemeentelijke Gegevens Model: https://gemeente-delft.github.io/Gemeentelijk-Gegevensmodel/domeinen/subsidies/https://gemeente-delft.github.io/Gemeentelijk-Gegevensmodel/domeinen/subsidies/
[2] IMBOR model: https://gemeente-delft.github.io/Gemeentelijk-Gegevensmodel/domeinen/image/IMGeoVSIMBOR.png

• verwijzingen naar buiten de Objects API
• verwijzingen binnen de Objects API
• verwijzingen heen en terug
• historie van objecten
• autorisatie op objecten
• autorisatie op objecttypen
• waar op filteren binnen objecten
• genestheid/gelaagdheid van JSON-schemas
• beheer gegevens / wie beheert
• verwijderen van objecten
• attributen onderverdelen in clusters/categorieen
• bulk opvoeren
• koppelen met registraties

Mogelijkheden:

• Direct aansluiten op de bron
• Direct bevragen via bestaande service
• Periodiek automatisch synchroniseren
• Periodiek handmatig uploaden

Documented here: https://docs.geostandaarden.nl/api/API-Strategie/
meaning this list here: https://docs.geostandaarden.nl/api/API-Designrules/