MVP LPDC
Principles
IPDC collects flemish products/services and local products/services. As such, IPDC wants to collect new LPDC products as instances of a concept.
If a concept doesn't yet exist in IPDC (LPDC). A local authority (LA) can make it's instance based on a vierge product fiche concept template. It will be used as a new concept for other local authorities when syncing the LA-LPDC with IPDC.
For SDG concerned services, a translation is provided within the concept, but each local authority may differ from it.
Some products and services are mandatory to provide for a local authority, some are optional. e.g. Issueing an e-id card is mandatory, having a LEZ is not.
An instance has several statusses, as a "besluit", i.e. draft, geaggendeerd, published. We should re-think the Gelinkt Notuleren wording of "concept" in order not to spread fog on the "concept" word (as draft is concept in gelinkt notuleren).
An instance will need versioning. Basically the versioning concerns a published version, while a preperation is made for a new published version, being a draft. Alternative: none or cloning an existing instance and rename it. (Though the URI will differ)
Concept as defined by IPDC / The translation of DRAFT should be "Ontwerp"link with role?
Action | Page | main goal | Page features, buttons, views | MVP 80% | MVP 100% |
inloggen | ACM/IDM - gebruikersbeheer | standard inlog via Loket | module button available (what place?) | yes similar to others |
|
-home page of the module | LD-LPDC - overview | overview LD-LPDC :selection of instances allocated to the local government by the local government | list with : name | yes |
|
|
|
| status | yes |
|
|
|
| click through (edit/view) | yes |
|
|
|
| link to besluit | no |
|
|
|
| last modified date | yes |
|
|
|
| add instance | yes |
|
|
|
| view concepts | yes |
|
|
|
| link to IPDC | yes (if provided) |
|
-add instance button-view available concepts | view LPDC - Concepts - overview | Overview of the concepts available from IPDC, ranking & filtering possible based on columns (see next) | name | yes |
|
|
|
| status | not clear for template |
|
|
|
| date | if clear |
|
|
|
| mandatory (j/n) | underspecified |
|
|
|
| theme | if provided |
|
|
|
| selection field that refers to action buttons (e.g. add to LD-LPDC-overview", "add to "Pakket", archive | no |
|
|
|
| click through (view) | no |
|
|
|
| multiselect in list / action buttons impact selected items | no |
|
|
| this is a specific list, linked to the user logged in (preferred) or linked to the entity (e.g. local government) | add to favorites (most use) | no |
|
click through (view) | LPDC - Concept | Content of the concept + metadatafields - need to to view original text and a translation on the same page. One should be able to select what translation to view next to the original; | button "add to LD-LPDC"(action adds an instance of the concept to the overview of the local government) | no |
|
|
|
| button "make instance"(action opens the new instance of the concept . | under specified? |
|
|
|
| feature: linked Concepts based on theme | no |
|
|
|
| feature: export to .csv? | no |
|
|
|
| feature: link to instances other LB? | no |
|
via overview (homepage) - click through edit/view | LD-LPDC - instance | Content of the instance + metadatafields - need to to view original text and a translation on the same page. One should be able to select what translation to edit next to the original; | -instance has standard the relevant content of the concept | no |
|
|
|
| -visible what "text box" was changed compared to the concept | no |
|
|
|
| -visible what local translation to provide (e.g. translation not editable if concept text was used / editable if change occured) | under specified |
|
|
|
| -button "BEWAAR" vs. -AUTO-SAVE | yes (bewaar) |
|
|
|
| -undo possibility | no |
|
|
|
| STATUS - manually adaptable | no (published should be published) |
|
|
|
| STATUS - feature: based on besluit status) / link to besluit and besluit status | no |
|
Instance (in a certain status) | instance of a service/product | edit instance |
| yes |
|
|
| edit instance if not published yet. In the MVP we don't mind if the instance already exists and is published. Once we are live, we have to foresee this feature (e.g. clone a published instance and make a new ontwerp - add version number to both instances, when last one is published, the former one is archived automatically.) |
| no |
|
|
| versioning |
| no |
|
filter / rank | all overview pages + instance / concept | being able to filter and rank on columns |
| filter yes (what is rank) |
|
|
| within instance/concept only show the "need2adapt local" fields (trigger?) |
| no |
|
new concept |
| instance based on empty concept. A concept should be generated in IPDC to link this. |
| under specified |
|
|
|
|
|
|
|
? uri logic |
| tbd |
| yes |
|
Last updated