Guide the user to the metadata creator on the OEP website within the upload/review process.

[jh-RLI]

At the moment we have the very helpful upload feature. Here you can create tables, create OEMeta data and upload data from csv files. However, it is often necessary to create only the OE metadata, e.g. to initiate and complete the data review/publication process. Therefore, I would like to separate the metadata creator function and offer it as a stand-alone feature in addition to the upload tool on the OEP website.

This is what I mean by "upload feature/tool":

Since you developed the upload function @wingechr (True? :D ), could you provide me with some links to the scripts/function/class here? If that takes too long, I'm sure I'll find them myself. :)

[wingechr]

The meta data editor is already an independent module.

If you go to any table that where you havw writing permissions, click on Edit in the metadata section:

[jh-RLI]

Thanks! I never had permission on a table to test that :) Now I have 👍 . I'll talk to @christian-rli, but it seems to me that this will work, we just want an easy way to get the oemetadata.json file, since every user has to submit it when initiating the github-based review process.

[jh-RLI]

Maybe we should also list a raw json file upload there. As the result of the review process is the file, therefore it would be good to enable the user to update the metadata straightforward without looking up the changes in the file manually. OFC we have oem2orm and the oep-client to do so as developers, but why not enable the user to do the job.

Or we move the review to the OEP (no version control :( )

@christian-rli
Additionally, we need to update the review process. The user would need to create a table using the OEP-Website (table can be empty, EDIT: metadata can also be created when creating the table). If the table exists the user can use the oep metadata tool (see Edit button) to create the metadata. Then he can download the file and submit it in the review process.

[christian-rli]

Let's discuss this in an OEP developer meeting.