[Conception] Archiving - obsolete

Information added to the Featur Passport

What - is - Archiving?

  • Data that is not viewable anymore in the front-end

  • Has a characteristic in the back-end, which makes it clear for API consumers of OP that the data should not be taken into account

  • If we run a query on the SPARQL endpoint, we need an attribute (or something else) to be able to include and exclude that it is archived (and can be filtered out in the query or afterwards manually)

Common use cases (based on user feedback)

  1. Archiving a Bestuurseenheid

Cause: Accidently creating a double

Frequency : Low - As maturity in use increases, I would estimate this would happen once every month. Current cases: at least 4

Combinatorial effects of archiving it (Very High!):

  • It is related to a Bestuursorgaan, which is/can be related to mandates, which is linked to a person. (All the Bestuursorganen, Mandates would need to be archived too)

  • It is related to a Site (All the sites would need to be archived too)

  • It is related to a Bedienaar (for a worship service only): (All the Mandates would need to be archived too)

  • It is related to a Betrokken Lokale Bestuur (this needs to be unlinked so that this relationship doesn’t need to be archived)

  • It - can be – related to a central worship service and representative organ (this needs to be unlinked so that this relationship doesn’t need to be archived)

2. Archiving a Bedienaar

Cause: Accidently adding the wrong person as a bedienaar

Frequency : Low - As maturity in use increases, I would estimate this would happen once every month. Current cases: at least 1

Combinatorial effects of archiving it (Medium):

  • The Minister position details data needs to be archived

  • It is related to a Person. (The position that is being archived needs to be unlinked from the Person)

  • It is related to a Bestuurseenheid (The position needs to be unlinked from the Bestuurseenheid)

3. Archiving a Bestuurslid/Mandataris

Cause: Accidently adding the wrong person as a mandate/bestuurslid

Frequency : Low - As maturity in use increases, I would estimate this would happen once every month. Current cases: at least 1

Combinatorial effects of archiving it (Medium):

  • The Mandataris/Bestuurslid position details data needs to be archived

  • It is related to a Person. (The position that is being archived needs to be unlinked from the Person)

  • It is related to a Bestuursorgaan (The position needs to be unlinked from the Bestuursorgaan)

Less common but theoretically possible

4. Archiving a site

Cause: Accidently adding the wrong site

For an organization it can occur that a vestiging (or a type vestiging) is no longer in use after date xx-xx-xxxx. This problem should best be covered with start- and end-dates.

Combinatorial effects of archiving it (Medium):

  • The Site details data needs to be archived

  • It is related to a Bestuurseenheid (The site needs to be unlinked from the Bestuurseenheid)

5. Archiving a Betrokken Lokale Bestuur

Cause: Accidently adding the wrong Betrokken Lokale Bestuur

After a change event it can occur that a gemeente or provincie is no longer a Betrokken Lokale Bestuur after date xx-xx-xxxx. This problem should best be covered with start- and end-dates.

Combinatorial effects of archiving it (Medium):

  • The Betrokken Lokale Bestuur details data (percentage, type) needs to be archived

  • It is related to a Bestuurseenheid (The Betrokken Lokale Bestuur with its relationship data needs to be unlinked from the Bestuurseenheid)

6. Archiving a Person

Cause: Accidently adding a person that is not linked to a position or bestuurseenheid, or an end-user adding person for testing purposes in Production

Frequency : Low - As maturity in use increases, I would estimate this would happen once every quarter.

Combinatorial effects of archiving it (Medium):

  • The Mandataris/Bestuurslid position needs to be archived

  • The Bedienaar position needs to be archived

  • It is related to a Bestuurseenheid (The Betrokken Lokale Bestuur with its relationship data needs to be unlinked from the Bestuurseenheid)

  • It is related to a Bestuursorgaan (The position needs to be unlinked from the Bestuursorgaan)

Last updated