VineSum hackathon - Githubissues

openminted / Open-Call-Discussions

A central place for participants in the open calls to ask questions

2 stars 1 forks source link

VineSum hackathon #19

Closed AlexJoom closed 6 years ago

AlexJoom commented 6 years ago

We don't need technical support

galanisd commented 6 years ago

Actually I had a workflow for your app. I replaced Vine component with the latest...saved an app to the Registry etc.

vine

Then I fed the app with a corpus I found in the Registry...and the execution finished. So I think we are OK.

vinesuccess

Unfortunately I was not able to make the workflow/app public so I can share it with you.

pennyl67 commented 6 years ago

@AlexJoom You can now proceed to the uploading of the final version at services.openminted.eu, which has been cleaned from all previous resources, so that we know that everything is updated. Should you run into any problems, please let us know. Thanks!

pennyl67 commented 6 years ago

@AlexJoom My mistake, please refrain from uploading at services.openminted.eu until further notice.

gkirtzou commented 6 years ago

Dear @AlexJoom you can now proceed to the uploading of your component at https://services.openminted.eu/home

Just, some final suggestions, not obligatory but recommended, for the metadata record are

Add in both input and output resource info the language(s) that your component can handle.
Add the resourceCreator with contact yourself, for citation reasons.
Add documentation to either user manuals or publication for citation reasons.

Please, when you upload your component, create the appropriate workflow so that someone could run your component using the workflow editor. For more info see https://openminted.github.io/releases/workflow-editor/ Please also let me know when you have uploaded the your component to the production site. If you encounter any problems, please let us know. Thanks

gkirtzou commented 6 years ago

Note that when you create an application, you wiil be asked to fill in a metadata record. Some tips for filling it in - so that they are discoverable by the users but also that users can cite you and your resource.

Give the application a unique name that humans can read and short enough
Give an explanatory description; remember you can re-use the description of the component(s) in the workflow accumulatively
Add in the inputProcessingResourceInfo the information of the first component used in the workflow (the one after omtdImpoter), and in the outputResourceInfo the information of the last component; if the annotations from previous components are retained in the final output, please add those as well
(optionally) You can use the relations set with the relation "hasPart" to document the components used in the workflow - it can be repeated multiple times.

snikolakis commented 6 years ago

Hi @gkirtzou , we have uploaded our component here: https://services.openminted.eu/landingPage/component/24d68cdd-1e24-47a6-8006-5f6d08718dc3

All the recommended fields for the metadata record have been filled and we created a new workflow here: https://services.openminted.eu/landingPage/application/7cc09c26-d310-43be-b753-ede278589fd6

Thank you.

gkirtzou commented 6 years ago

@spyninja I can see the application but no the component (it is private). COuld you send me the metadata record in xml?

gkirtzou commented 6 years ago

@spyninja sorry the reverse. I can see the component but not the application.

snikolakis commented 6 years ago

I'm sorry for the inconvenience, I have made the application public, as well.

pennyl67 commented 6 years ago

Closing the issue: application public in services and tested with Chebi corpus