Decide what to put in offering publication wizard step 1: asset definition

[xamcost]

Hi there! The goal of this issue is to finalize the content of the first step of the offering publication wizard, which consists of a form describing, at a very high level, the asset to be published.

This form should contain (please give feedback!):

• asset name
• short description: this is a one sentence description to put as a highlight when browsing the catalogue. We suggest making it a required entry.
• a version number ? For users to manually version
• description: a longer description of the asset, optional but strongly recommended.
• a picture for the asset, optional. This is not a file, just a URL pointing towards a picture. No storage needed.
• some keywords for the asset, optional
• the license of the dataset (MIT, ...) ?

The current version looks like this:

[xamcost]

Pinging @psotres and @telsaleh for their feedback! Feel free to suggest any change.

[psotres]

Asset description is part of the offering generation phase, so not really part of MVM stream, which will be consuming, validating, and exposing them to be discovered.

As the integration process is still ongoing, there might be some extra (minor) requirements in the future, but let's see. Personally, I'd prefer not to be involved on every step so I'll leave this to Tarek and INRIA (you should probably include them as well).

[xamcost]

Thank you for you answer @psotres !

Personally, I'd prefer not to be involved on every step so I'll leave this to Tarek and INRIA (you should probably include them as well).

No pb, I won't include you in things related to offering creation.

Asset description is part of the offering generation phase, so not really part of MVM stream, which will be consuming, validating, and exposing them to be discovered.

I am sorry but I do not really get why this is not part of the MVM stream... Do you mean that for Sedimark v0, we do not intend to have a UI in the marketplace to create offerings, but only to browse them in the catalogue ? That won't make marketplace usage very smooth if offerings has to be created separately...

[psotres]

Asset description is part of the offering generation phase, so not really part of MVM stream, which will be consuming, validating, and exposing them to be discovered.

I am sorry but I do not really get why this is not part of the MVM stream... Do you mean that for Sedimark v0, we do not intend to have a UI in the marketplace to create offerings, but only to browse them in the catalogue ? That won't make marketplace usage very smooth if offerings has to be created separately...

No no, what I was trying to say is that, strictly speaking, according to the 4 different streams Panos proposed in last WP5, the offering generation part is a task from a different stream. Of course it needs to be generated, but MVM does not cover such functionality, it just processes them.

[xamcost]

Closing since it is now covered by #8 and the fields to show in this form will be dictated by the ontology.