-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ODRC: documenthandelingen op documenten #76
Milestone
Comments
This was referenced Oct 16, 2024
Discussed: set up a default for "vaststelling", so that the ODPC can drop the edit interface if needed. Date of the action is the date of publication/upload |
bart-maykin
added a commit
that referenced
this issue
Nov 13, 2024
…l. This is because we only allow one action as per now, and migrating this in the future to its own model when we allow multiple instances is very easy to do. Also for now we can just use the publications 'verantwoordelijke' field as the 'wasAssciatedWith' because for now these two won't differ from eachother.
bart-maykin
added a commit
that referenced
this issue
Nov 13, 2024
… fake documenthandelingen field with setter to help populate and save the api data.
bart-maykin
added a commit
that referenced
this issue
Nov 13, 2024
… fake documenthandelingen field with setter to help populate and save the api data.
Merged
bart-maykin
added a commit
that referenced
this issue
Nov 13, 2024
…registratiedatum which will be filed in by the model save method
bart-maykin
added a commit
that referenced
this issue
Nov 13, 2024
…registratiedatum which will be filed in by the model save method
bart-maykin
added a commit
that referenced
this issue
Nov 13, 2024
…registratiedatum which will be filed in by the model save method
bart-maykin
added a commit
that referenced
this issue
Nov 13, 2024
bart-maykin
added a commit
that referenced
this issue
Nov 13, 2024
…l. This is because we only allow one action as per now, and migrating this in the future to its own model when we allow multiple instances is very easy to do. Also for now we can just use the publications 'verantwoordelijke' field as the 'wasAssciatedWith' because for now these two won't differ from eachother.
bart-maykin
added a commit
that referenced
this issue
Nov 13, 2024
… fake documenthandelingen field with setter to help populate and save the api data.
bart-maykin
added a commit
that referenced
this issue
Nov 13, 2024
…registratiedatum which will be filed in by the model save method
bart-maykin
added a commit
that referenced
this issue
Nov 13, 2024
bart-maykin
added a commit
that referenced
this issue
Nov 13, 2024
bart-maykin
added a commit
that referenced
this issue
Nov 14, 2024
bart-maykin
added a commit
that referenced
this issue
Nov 14, 2024
…l. This is because we only allow one action as per now, and migrating this in the future to its own model when we allow multiple instances is very easy to do. Also for now we can just use the publications 'verantwoordelijke' field as the 'wasAssciatedWith' because for now these two won't differ from eachother.
bart-maykin
added a commit
that referenced
this issue
Nov 14, 2024
bart-maykin
added a commit
that referenced
this issue
Nov 14, 2024
bart-maykin
added a commit
that referenced
this issue
Nov 14, 2024
…, added model property and setting to retrieve and populate the documenthandeling fields when using the api.
bart-maykin
added a commit
that referenced
this issue
Nov 14, 2024
sergei-maertens
added a commit
that referenced
this issue
Nov 14, 2024
sergei-maertens
pushed a commit
that referenced
this issue
Nov 14, 2024
…l. This is because we only allow one action as per now, and migrating this in the future to its own model when we allow multiple instances is very easy to do. Also for now we can just use the publications 'verantwoordelijke' field as the 'wasAssciatedWith' because for now these two won't differ from eachother.
sergei-maertens
pushed a commit
that referenced
this issue
Nov 14, 2024
sergei-maertens
pushed a commit
that referenced
this issue
Nov 14, 2024
sergei-maertens
pushed a commit
that referenced
this issue
Nov 14, 2024
…, added model property and setting to retrieve and populate the documenthandeling fields when using the api.
sergei-maertens
pushed a commit
that referenced
this issue
Nov 14, 2024
sergei-maertens
added a commit
that referenced
this issue
Nov 14, 2024
Documenthandelingen staat nu live op de testomgeving & zit in de latest docker image |
@felixcicatt Wat mij betreft kan deze op Done. Wat vind jij? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Als medewerker wil ik bij ieder document documenthandelingen kunnen vastleggen, zodat de burger dit kan raadplegen.
Toelichting
Helaas is dit verplicht vanuit DiWoo: link.
N.a.v. discussie bij ODPC #26 ondersteunen we vooralsnog maar één documenthandeling per document, ook al kan volgens DiWoo een document ook meer dan één documenthandelingen kennen.
Acceptatie criteria
soortHandeling
(verplicht, enumeratie)atTime
(verplicht, dateTime)wasAssciatedWith
(optioneel, referentie naar 'organisatie' ODCR: Organisatie datamodel + API resource #26)Taken
documenthandelingen
array in the (detail and list) responsesThe text was updated successfully, but these errors were encountered: