* Form: If file is provide, save file to archive. Metadata will be stored and triggers a given workflow, should include feedback and email functionality.
#### User View
* Form:
* Open the website, fill in form with PI information and information describing the dataset or collection of dataset from TNA and/or campaign activities
* Feedback:
* User will recieve email confirmation and a link to the issue tracking system
* Issue tracking system:
* Workflows: Depending on the selected paramters and other relevant metadata from the "Homeless data portal" form, different workflows will be triggered.
* Storage: Possibility to store submitted metadata and files via forms to a archive for backup and tracebility.
* Open issue tracking system, see "tickets" associated to a users request for providing data
#### System View
* Form:
* Form information is stored and metadata from form selction is provided to the API of the issue tracking system
* Workflows: Depending on the selected paramters and other relevant metadata from the "Homeless data portal" form, different workflows will be triggered in the issue tracking system.
* Form will trigger storage of data in those cases where the data provider wants to provide examples or send the whole dataset together with the metadata.
* If file is provide, save file to archive. Metadata will be stored and triggers a given workflow, should include feedback and email functionality.
* Storage: Possibility to store submitted metadata and files via forms to a archive for backup and tracebility.
* Feedback
* Issuetracking system will be "in-charge" of sending feedback upon creation and update of a specific issue.
* Issue tracking system
* Functionality of issue tracking system should be treated like a black-box
#### Research Infrastructure (RI) View
* RI will look through the request for providing data and accept/decline in the issue tracking system
* RI will provide all feedback through the issue tracking system
