About SEAD, this is an end-to-end infrastructure used to manage, share, curate, protect and publish data. SEAD offers safe Project Spaces in which both teams and individual researchers are able to develop data sets and submit their data for publication in repositories managed by SEAD. SEAD’s technology guides project teams via a publication process in which data collections from the team’s Project Space are curated and matched with a trusted repository. The SEAD standards and practices which are necessary are going to be presented in the following post.
Types of data
First and foremost, data can be uploaded to secure Project Spaces in SEAD and the annotated through the web interface of this provider. When it comes to projects with larger numbers of data files and complicated through processes, they will be uploaded and annotated through SEAD’s RESTful web service interface. The most prominent benefit of taking advantage of SEAD service is that its Project Spaces which are controlled by access will enable your team to upload and share any or all materials when you generate them so that you can use later for making decisions in the project.
In SEAD, groups are flexible enough to make decisions regarding which data and extra materials including experimental procedures, software, test suites as well as other types of formal and informal documentation in order to handle and protect the records of your project. SEAD is able to assist any decision you have made when it comes to what to keep in the project, how and when you should upload or annotate your data as well as what and when to publish and protect for the long-term use. SEAD motivates and allows project teams to both publish and preserve their data more than just the last results while making them consider raw data, control experiments, negative results, reports, notes and so on.
Data and metadata standards
SEAD allows for data publication in whatever format and for project teams to make use of any metadata vocabularies. As a standard, SEAD makes use of terms from the Dublin Core vocabulary and takes advantage of the W3C Provenance specification. With all of those things, a default option is provided to record the file, abstract, creator, creation data and contact. Project Space admins are able to add new terms about the project and connect to external community vocabularies in case there is a necessity. For instance, researchers can add more terms in order to describe the temporal or any other aspect of the data as well as data derivation relationships. SEAD software also enables teams to make a description for the data and document relationships between data files if necessary in order to make it more useful for others.
As data files in such common formats as images, movies, documents and slides are uploaded into SEAD, users can take a look at previews while metadata is stored in the file, which will be automatically extracted and become visible to promote your capability of learning the file contents. If your project makes use of other formats, you are highly recommended to contact SEAD to know whether to add more extractors or previewers to your Project Space.
With the aim of supporting your data publication process, SEAD offers a Staging Area in which you are able to review and make comparison for your data and metadata against the demands of particular repositories to define any problems you may come across when it comes to unsupported formats or missing required metadata. This process allows users to update their submission quickly to make sure that it adapts to the policies of the repository they opt.
Policies for approaching and sharing as well as provisions for suitable protection and privacy
SEAD offers users the needed mechanisms to have control over your data access. The SEAD team also works to make sure that your data is safe in its services. In case your data comes up with any particular access or privacy problem, it is highly recommended to contact the provider team in order to speak to them about your demands. Project Spaces of SEAD are controlled by access and make use of encrypted communications. Project Spaces are carried out by project teams in the project space and only users in that space are granted with privileges such as uploading and annotating data or just viewing only. You can manage who in your team has the right to handle SEAD, which means the ones who are able to view the data as well as edit or publish it.
Machines housing SEAD services are controlled by taking advantage of standard software or procedures adopted by SEAD’s parent companies.
Plans for Archiving and Preserving Access
SEAD’s design enables incremental upload and annotating data so that project teams can take better control over their data, with more metadata. By enabling this active use of data in the project, SEAD technology allows researchers to place an extra layer of quality guarantee that does not come when data is submitted for publication and annotated only at the end of the project. Moreover, RESTful API of SEAD can also be utilized to prevent manual transcription mistakes as well as many offerings from SEAD user interface like support for vocabularies are done to minimize input errors. Data in SEAD’s Project Spaces are saved on redundant disk arrays and backed up regularly on specific periods.
Policies and provisions for reuse and redistribution
SEAD motivates using open data licenses like the Creative Commons license for data publications. Teams can ask for a different license if it is assisted by the repository opted to publish and archive date. If it is not organized in advance, SEAD will make published data available using its open data license in a limited way and will not enforce approach control. Finally, SEAD encourages researchers and customers to discuss such particular issues with it in advance so that the upcoming collaboration goes smooth.