Currently there is example tprm.zip file under upload form which user have to download and upload manually. Make clicking zip file not download but upload as an example and open schema list.

Allow user to calculate hashlink for local file:
Simple input where user can choose the file. Browser locally would read the file calculate hashlink for him and display it below. File should not be uploaded anywhere.

ODCA does not include information about presentation layer. Will be nice to have some basic layout configuration which can be easily portable.

We need to think about adding that to the specification.

The idea is to keep there information like:

• required fields
• hidden fields
• layout of the form
• etc.

Some overlays like label, information have support for language means that use can decided which language they are meant for.

We need to figure out as well how to add support for multiple overlays with different language e.g. have lable overlay in PL, EN and DE in same time. Or upload OCA into the system and add new translation overlay.

if the file is corrupted or something fail while trying to convert csv to oca there is no error message nor indication that something happen.

Base on existing schema base reviewer could generate by hit of the button a new schema base and overlays allowing him to review existing data set and capture only review information.

Deploy tool under one of the existing domain and link it in the readme

Currently Attribute Type is set to Array[Text] if control is "select option" but it should be Array[Text] only if there is multiple select option enabled

Allow user to import existing schema by providing ipfs link or uploading the file directly.

Since schema is compose from multiple files we need to think how to handle that case.
Maybe we could have one big JSON LD file which could be uploaded.

While user finish process of creating objects, there should be a way to publish the objects directly on IPFS which automatically will provide DRI (decentralized resources identifier) which can be used to link objects (check how this would be compatible with Hashlinks)

Prepare classes for all objects in ODCA which can be used later during import/export feature

Current generator seems to force to have a section to actually host fields.

Since section correspond to category in ODCA it should be optional.

Steps to reproduce:

• Create new schema (name + description)
• add one text input, fill attr name, and control label and information
• save
• export

Expected: zip file with ODCA
Current state:

TypeError: "value is undefined"
printQuoted kotlinx-serialization-kotlinx-serialization-runtime.js:5502
printQuoted_61zpoe$ kotlinx-serialization-kotlinx-serialization-runtime.js:5476
encodeString_61zpoe$ kotlinx-serialization-kotlinx-serialization-runtime.js:5401
encodeStringElement_bgm7zs$ kotlinx-serialization-kotlinx-serialization-runtime.js:1862
serialize_awe97i$ odca.js:2897
encodeSerializableValue_tf03ej$ kotlinx-serialization-kotlinx-serialization-runtime.js:5255
encode_0 kotlinx-serialization-kotlinx-serialization-runtime.js:1395
stringify_tf03ej$ kotlinx-serialization-kotlinx-serialization-runtime.js:6236
stringify_tf03ej$ kotlinx-serialization-kotlinx-serialization-runtime.js:6287
toDto odca.js:854
serialize odca.js:195
initOdcaCommunication odcaCommunication.js:34
VueJS 2
download FormBuilderTemplate.vue:51
download SectionComponent.vue:67
VueJS 3
vue.runtime.esm.js:1888
[Vue warn]: Error in event handler for "export_form": "TypeError: value is undefined"
(found in ) vue.runtime.esm.js:619
TypeError: "value is undefined"
printQuoted kotlinx-serialization-kotlinx-serialization-runtime.js:5502
printQuoted_61zpoe$ kotlinx-serialization-kotlinx-serialization-runtime.js:5476
encodeString_61zpoe$ kotlinx-serialization-kotlinx-serialization-runtime.js:5401
encodeStringElement_bgm7zs$ kotlinx-serialization-kotlinx-serialization-runtime.js:1862
serialize_awe97i$ odca.js:2897
encodeSerializableValue_tf03ej$ kotlinx-serialization-kotlinx-serialization-runtime.js:5255
encode_0 kotlinx-serialization-kotlinx-serialization-runtime.js:1395
stringify_tf03ej$ kotlinx-serialization-kotlinx-serialization-runtime.js:6236
stringify_tf03ej$ kotlinx-serialization-kotlinx-serialization-runtime.js:6287
toDto odca.js:854
serialize odca.js:195
initOdcaCommunication odcaCommunication.js:34
VueJS 2
download FormBuilderTemplate.vue:51
download SectionComponent.vue:67
VueJS 3

Control options partially cover supported controls without covering Reset and Save button which confuse user what for they are.

We should decide if we want to show options below supported controls or hide them while options are shown

After placing control user needs to visit options to define basic properties.

Those options will generate proper overlays at the end.

Label -> Label Overlay
Control Type -> Schema base -> attr type
Name -> Schema base -> attr name
Default Value -> Entry Overlay
PII (checkbox) -> Schema base -> pii_attributes
language -> Apply language for all overlays create for that attribute
Information -> Information Overlay
Format -> Format Overlay
Encode -> Encode Overlay
Review (checkbox) -> Review Overlay
Source (checkbox) -> Source Overlay

All other properties available in the tool are not relevant for the ODCA and should be remove (see presentation layer for more details #12 )

It is not obvious for the user that double click on the control gives options.

We need to make sure that user would be guided over the process and that it will be smooth for him.

To improve the process we could:

• change double click on one click to select control and display options
• after start dragging the input some bin should be showed so user can understand how to remove it (or just display delete on side of apply and cancel)
• after dropping control options could be opened automatically

After building data capture form user should have possibility to generate JSON LD file out of that form which would follow ODCA

For reference take a look on odca-ruby implementation

Publish docker image on the public hub
Encapsulate everything what is needed to run tool locally or in own server environment.

Add PDP / Consent life cycle to the schema base as a linked object.

I'm super interested in ODCA and would love to help contribute to this tool. What are some issues I could tackle to help move this project forward?

on side of export add publish button which would popup modal asking to which repository (default one add repository.odca.online - but allow to specify any link) and give all the hashes.