https://binnenland.atlassian.net/browse/DL-3488
https://dev.loket.lblod.info/mock-login (needs to be deployed, target friday)
- stories: actionable enough for devs to start on (but not fully written out) OR link to existing stories
- needs refinement: too vague to start on
- what does it mean to publish?
- can these be updated once published?
- nieuwe versie aanmaken: what does it mean?
- "origineel" is not trivial to implement
- wait for the final details from IPDC model before moving on
- supporting evidence, e.g. id-card, also a copy?
- we wait for a converted dataset from organisatieregsiter (boris/OP should be busy with that)
- hierarchical dataset gemeente - regio - provincie - gewest - land (for field location) needs extension https://github.com/lblod/app-organization-portal/blob/poc/add-gemeenten/config/migrations/2022/20220614112713-referentieregios.ttl This is relevant for the geografisch toepssingsgebied (very likely boris/OP will do) https://binnenland.atlassian.net/browse/OP-1512
- adresmodel voor contactpunt (compatible with stuff of wegwijs) (very likely boris/OP will do)
- logica uitvoerende overheid: get info from session id.
- make a specific code list for general organisations: general organisations + add the creator of the service in the list
- vertaald/niet-vertaald calculation https://binnenland.atlassian.net/browse/DL-3766
- validations in the backend
- extended validations
- note: new extra validations components might be needed
- filter on uitvoerende overheid: the owner of the service will be the uitvoerende overheid. This filter should be made in the frontend. Very similar to subsidies
- tags component: https://binnenland.atlassian.net/browse/DL-3797
- trigger validation flow (on publish)
- voeg 'product toe' from no template
- validation when publishing: all forms need validation before publishing
- go over the implemented designs with Dieter after POC has been deployed (and user feedback gathered?)
- how to deal with related products? (UIX wise)
- UIX wise -> how to use the editor for legal references
- quid collapsable fields? https://binnenland.atlassian.net/browse/DL-3767
- bug can add https://github.com/lblod/ember-submission-form-fields/blob/feature/updated-form-model/addon/components/listing.js#L36-L40
- cleanup maintain etc: https://binnenland.atlassian.net/browse/DL-3790
- language strings support (new story): for a minimal set of components https://binnenland.atlassian.net/browse/DL-3791
- use the experiment from the editor to make a clean component: rich-text
- custom-component: where translation can be compared with the original
- augment generator: this means: make sure there is a least one resource in the data satisfying model x/y/z https://binnenland.atlassian.net/browse/DL-3792 Note: the backend could do this too, but then it wouldn't be re-usable
- how data-wise deal with ember-RDFa editor. A whole new set of problems come from that. (first, wait for UIX wise see if this is realistic)
- maintenance rdflib: bump package
- forking store improvements:
- is a dirty state, i.e. detect real changes so the pop-flow works better
- performance: try to notifiy observers only when real changes are persisted, so not too many re-renders
- the core poc has been delivered, but needs cleanup/robustness improvement
- integrate the components so loket starts spitting data.
- refinment: not clear how we pull the data back.