diff --git a/dmp-backend/web/src/main/java/eu/eudat/controllers/AboutController.java b/dmp-backend/web/src/main/java/eu/eudat/controllers/AboutController.java new file mode 100644 index 000000000..b0bf85aea --- /dev/null +++ b/dmp-backend/web/src/main/java/eu/eudat/controllers/AboutController.java @@ -0,0 +1,46 @@ +package eu.eudat.controllers; + +import eu.eudat.logic.managers.MaterialManager; +import eu.eudat.logic.managers.MetricsManager; +import eu.eudat.types.MetricNames; +import org.springframework.beans.factory.annotation.Autowired; +import org.springframework.core.env.Environment; +import org.springframework.http.ResponseEntity; +import org.springframework.web.bind.annotation.*; + +import java.io.IOException; +import java.nio.file.Files; +import java.nio.file.Path; +import java.nio.file.Paths; +import java.util.Objects; +import java.util.stream.Stream; + +@RestController +@CrossOrigin +@RequestMapping(value = {"/api/material/about/"}) +public class AboutController { + + private Environment environment; + private MaterialManager materialManager; + private final MetricsManager metricsManager; + + @Autowired + public AboutController(Environment environment, MaterialManager materialManager, MetricsManager metricsManager) { + this.environment = environment; + this.materialManager = materialManager; + this.metricsManager = metricsManager; + } + + @RequestMapping(path = "{lang}", method = RequestMethod.GET ) + public ResponseEntity getAbout(@PathVariable(name = "lang") String lang) throws IOException { +// long files = 0; +// try (Stream paths = Files.list(Paths.get(Objects.requireNonNull(this.environment.getProperty("about.path"))))) { +// files = paths.count(); +// } +// metricsManager.calculateValue(MetricNames.LANGUAGES, (int) files, null); + try (Stream paths = Files.walk(Paths.get(Objects.requireNonNull(this.environment.getProperty("about.path"))))) { + return this.materialManager.getResponseEntity(lang, paths); + } + } + +} diff --git a/dmp-backend/web/src/main/java/eu/eudat/controllers/FaqController.java b/dmp-backend/web/src/main/java/eu/eudat/controllers/FaqController.java new file mode 100644 index 000000000..0aa9ff078 --- /dev/null +++ b/dmp-backend/web/src/main/java/eu/eudat/controllers/FaqController.java @@ -0,0 +1,45 @@ +package eu.eudat.controllers; + +import eu.eudat.logic.managers.MaterialManager; +import eu.eudat.logic.managers.MetricsManager; +import org.springframework.beans.factory.annotation.Autowired; +import org.springframework.core.env.Environment; +import org.springframework.http.ResponseEntity; +import org.springframework.web.bind.annotation.*; + +import java.io.IOException; +import java.nio.file.Files; +import java.nio.file.Path; +import java.nio.file.Paths; +import java.util.Objects; +import java.util.stream.Stream; + +@RestController +@CrossOrigin +@RequestMapping(value = {"/api/material/faq/"}) +public class FaqController { + + private Environment environment; + private MaterialManager materialManager; + private final MetricsManager metricsManager; + + @Autowired + public FaqController(Environment environment, MaterialManager materialManager, MetricsManager metricsManager) { + this.environment = environment; + this.materialManager = materialManager; + this.metricsManager = metricsManager; + } + + @RequestMapping(path = "{lang}", method = RequestMethod.GET ) + public ResponseEntity getFaq(@PathVariable(name = "lang") String lang) throws IOException { +// long files = 0; +// try (Stream paths = Files.list(Paths.get(Objects.requireNonNull(this.environment.getProperty("faq.path"))))) { +// files = paths.count(); +// } +// metricsManager.calculateValue(MetricNames.LANGUAGES, (int) files, null); + try (Stream paths = Files.walk(Paths.get(Objects.requireNonNull(this.environment.getProperty("faq.path"))))) { + return this.materialManager.getResponseEntity(lang, paths); + } + } + +} diff --git a/dmp-backend/web/src/main/java/eu/eudat/controllers/GlossaryController.java b/dmp-backend/web/src/main/java/eu/eudat/controllers/GlossaryController.java new file mode 100644 index 000000000..f46e0f4f0 --- /dev/null +++ b/dmp-backend/web/src/main/java/eu/eudat/controllers/GlossaryController.java @@ -0,0 +1,45 @@ +package eu.eudat.controllers; + +import eu.eudat.logic.managers.MaterialManager; +import eu.eudat.logic.managers.MetricsManager; +import org.springframework.beans.factory.annotation.Autowired; +import org.springframework.core.env.Environment; +import org.springframework.http.ResponseEntity; +import org.springframework.web.bind.annotation.*; + +import java.io.IOException; +import java.nio.file.Files; +import java.nio.file.Path; +import java.nio.file.Paths; +import java.util.Objects; +import java.util.stream.Stream; + +@RestController +@CrossOrigin +@RequestMapping(value = {"/api/material/glossary/"}) +public class GlossaryController { + + private Environment environment; + private MaterialManager materialManager; + private final MetricsManager metricsManager; + + @Autowired + public GlossaryController(Environment environment, MaterialManager materialManager, MetricsManager metricsManager) { + this.environment = environment; + this.materialManager = materialManager; + this.metricsManager = metricsManager; + } + + @RequestMapping(path = "{lang}", method = RequestMethod.GET ) + public ResponseEntity getGlossary(@PathVariable(name = "lang") String lang) throws IOException { +// long files = 0; +// try (Stream paths = Files.list(Paths.get(Objects.requireNonNull(this.environment.getProperty("glossary.path"))))) { +// files = paths.count(); +// } +// metricsManager.calculateValue(MetricNames.LANGUAGES, (int) files, null); + try (Stream paths = Files.walk(Paths.get(Objects.requireNonNull(this.environment.getProperty("glossary.path"))))) { + return this.materialManager.getResponseEntity(lang, paths); + } + } + +} diff --git a/dmp-backend/web/src/main/java/eu/eudat/controllers/TermsOfServiceController.java b/dmp-backend/web/src/main/java/eu/eudat/controllers/TermsOfServiceController.java new file mode 100644 index 000000000..d9d015193 --- /dev/null +++ b/dmp-backend/web/src/main/java/eu/eudat/controllers/TermsOfServiceController.java @@ -0,0 +1,45 @@ +package eu.eudat.controllers; + +import eu.eudat.logic.managers.MaterialManager; +import eu.eudat.logic.managers.MetricsManager; +import org.springframework.beans.factory.annotation.Autowired; +import org.springframework.core.env.Environment; +import org.springframework.http.ResponseEntity; +import org.springframework.web.bind.annotation.*; + +import java.io.IOException; +import java.nio.file.Files; +import java.nio.file.Path; +import java.nio.file.Paths; +import java.util.Objects; +import java.util.stream.Stream; + +@RestController +@CrossOrigin +@RequestMapping(value = {"/api/material/termsofservice/"}) +public class TermsOfServiceController { + + private Environment environment; + private MaterialManager materialManager; + private final MetricsManager metricsManager; + + @Autowired + public TermsOfServiceController(Environment environment, MaterialManager materialManager, MetricsManager metricsManager) { + this.environment = environment; + this.materialManager = materialManager; + this.metricsManager = metricsManager; + } + + @RequestMapping(path = "{lang}", method = RequestMethod.GET ) + public ResponseEntity getTermsOfService(@PathVariable(name = "lang") String lang) throws IOException { +// long files = 0; +// try (Stream paths = Files.list(Paths.get(Objects.requireNonNull(this.environment.getProperty("termsofservice.path"))))) { +// files = paths.count(); +// } +// metricsManager.calculateValue(MetricNames.LANGUAGES, (int) files, null); + try (Stream paths = Files.walk(Paths.get(Objects.requireNonNull(this.environment.getProperty("termsofservice.path"))))) { + return this.materialManager.getResponseEntity(lang, paths); + } + } + +} diff --git a/dmp-backend/web/src/main/java/eu/eudat/controllers/UserGuideController.java b/dmp-backend/web/src/main/java/eu/eudat/controllers/UserGuideController.java index 9e26cf92a..f513238cf 100644 --- a/dmp-backend/web/src/main/java/eu/eudat/controllers/UserGuideController.java +++ b/dmp-backend/web/src/main/java/eu/eudat/controllers/UserGuideController.java @@ -1,5 +1,6 @@ package eu.eudat.controllers; +import eu.eudat.logic.managers.MaterialManager; import eu.eudat.logic.managers.MetricsManager; import eu.eudat.logic.security.claims.ClaimedAuthorities; import eu.eudat.models.data.helpers.responses.ResponseItem; @@ -32,47 +33,26 @@ import static eu.eudat.types.Authorities.ADMIN; public class UserGuideController { private Environment environment; + private MaterialManager materialManager; private final MetricsManager metricsManager; @Autowired - public UserGuideController(Environment environment, MetricsManager metricsManager) { + public UserGuideController(Environment environment, MaterialManager materialManager, MetricsManager metricsManager) { this.environment = environment; + this.materialManager = materialManager; this.metricsManager = metricsManager; } @RequestMapping(path = "{lang}", method = RequestMethod.GET ) - public ResponseEntity getUserGuide(@PathVariable(name = "lang") String lang) throws IOException { + public ResponseEntity getUserGuide(@PathVariable(name = "lang") String lang) throws IOException { long files = 0; try (Stream paths = Files.list(Paths.get(Objects.requireNonNull(this.environment.getProperty("userguide.path"))))) { files = paths.count(); } - metricsManager.calculateValue(MetricNames.LANGUAGES, (int) files, null); + metricsManager.calculateValue(MetricNames.LANGUAGES, (int) files, null); try (Stream paths = Files.walk(Paths.get(Objects.requireNonNull(this.environment.getProperty("userguide.path"))))) { - List result = paths.filter(Files::isRegularFile) - .map(Path::toString).collect(Collectors.toList()); - - String fileName = result.stream().filter(guide -> guide.contains("_" + lang)).findFirst().orElse(null); - if (fileName == null) { - fileName = result.stream().filter(guide -> guide.contains("_en")).findFirst().get(); - } - InputStream is = new FileInputStream(fileName); - - Path path = Paths.get(fileName); - - HttpHeaders responseHeaders = new HttpHeaders(); - responseHeaders.setContentLength(is.available()); - responseHeaders.setContentType(MediaType.TEXT_HTML); - responseHeaders.set("Content-Disposition", "attachment;filename=" + path.getFileName().toString()); - responseHeaders.set("Access-Control-Expose-Headers", "Content-Disposition"); - responseHeaders.get("Access-Control-Expose-Headers").add("Content-Type"); - - byte[] content = new byte[is.available()]; - is.read(content); - is.close(); - - return new ResponseEntity<>(content, responseHeaders, HttpStatus.OK); + return this.materialManager.getResponseEntity(lang, paths); } - } @RequestMapping(value = "current", method = RequestMethod.POST) diff --git a/dmp-backend/web/src/main/java/eu/eudat/logic/managers/MaterialManager.java b/dmp-backend/web/src/main/java/eu/eudat/logic/managers/MaterialManager.java new file mode 100644 index 000000000..344fe24b3 --- /dev/null +++ b/dmp-backend/web/src/main/java/eu/eudat/logic/managers/MaterialManager.java @@ -0,0 +1,51 @@ +package eu.eudat.logic.managers; + +import org.springframework.beans.factory.annotation.Autowired; +import org.springframework.http.HttpHeaders; +import org.springframework.http.HttpStatus; +import org.springframework.http.MediaType; +import org.springframework.http.ResponseEntity; +import org.springframework.stereotype.Component; + +import java.io.FileInputStream; +import java.io.IOException; +import java.io.InputStream; +import java.nio.file.Files; +import java.nio.file.Path; +import java.nio.file.Paths; +import java.util.List; +import java.util.stream.Collectors; +import java.util.stream.Stream; + +@Component +public class MaterialManager { + + @Autowired + public MaterialManager(){} + + public ResponseEntity getResponseEntity(String lang, Stream paths) throws IOException { + List result = paths.filter(Files::isRegularFile) + .map(Path::toString).collect(Collectors.toList()); + + String fileName = result.stream().filter(about -> about.contains("_" + lang)).findFirst().orElse(null); + if (fileName == null) { + fileName = result.stream().filter(about -> about.contains("_en")).findFirst().get(); + } + InputStream is = new FileInputStream(fileName); + + Path path = Paths.get(fileName); + + HttpHeaders responseHeaders = new HttpHeaders(); + responseHeaders.setContentLength(is.available()); + responseHeaders.setContentType(MediaType.TEXT_HTML); + responseHeaders.set("Content-Disposition", "attachment;filename=" + path.getFileName().toString()); + responseHeaders.set("Access-Control-Expose-Headers", "Content-Disposition"); + responseHeaders.get("Access-Control-Expose-Headers").add("Content-Type"); + + byte[] content = new byte[is.available()]; + is.read(content); + is.close(); + + return new ResponseEntity<>(content, responseHeaders, HttpStatus.OK); + } +} diff --git a/dmp-backend/web/src/main/resources/config/application.properties b/dmp-backend/web/src/main/resources/config/application.properties index 36a28a8bb..ab20c2856 100644 --- a/dmp-backend/web/src/main/resources/config/application.properties +++ b/dmp-backend/web/src/main/resources/config/application.properties @@ -110,7 +110,19 @@ database.lock-fail-interval=120000 ##########################MISC########################################## #############USER GUIDE######### -userguide.path=user-guide/ +userguide.path=dmp-backend/web/src/main/resources/material/user-guide + +#############ABOUT######### +about.path=dmp-backend/web/src/main/resources/material/about + +#############TERMS OF SERVICE######### +termsofservice.path=dmp-backend/web/src/main/resources/material/terms-of-service + +#############GLOSSARY######### +glossary.path=dmp-backend/web/src/main/resources/material/glossary + +#############FAQ######### +faq.path=dmp-backend/web/src/main/resources/material/faq #############NOTIFICATION######### notification.rateInterval=30000 diff --git a/dmp-backend/web/src/main/resources/material/about/About_en.html b/dmp-backend/web/src/main/resources/material/about/About_en.html new file mode 100644 index 000000000..2f0fc37ac --- /dev/null +++ b/dmp-backend/web/src/main/resources/material/about/About_en.html @@ -0,0 +1,76 @@ + + + + + + + + + + + + + + + + + +
+
+
+

About

+
+
+
+
+

ARGOS is an online tool in support of automated processes to creating, managing, sharing and linking DMPs with research artifacts they correspond to. It is the joint effort of OpenAIRE and EUDAT to deliver an open platform for Data Management Planning that addresses FAIR and Open best practices and assumes no barriers for its use and adoption. It does so by applying common standards for machine-actionable DMPs as defined by the global research data community of RDA and by communicating and consulting with researchers, research communities and funders to better reflect on their needs. +

ARGOS provides a flexible environment and an easy interface for users to navigate and use.

+
+
+
+ + + diff --git a/dmp-backend/web/src/main/resources/material/faq/Faq_en.html b/dmp-backend/web/src/main/resources/material/faq/Faq_en.html new file mode 100644 index 000000000..82600bf1d --- /dev/null +++ b/dmp-backend/web/src/main/resources/material/faq/Faq_en.html @@ -0,0 +1,749 @@ + + + + + + + + + + + + + + + + + +
+
+
+

About ARGOS

+

What is ARGOS?

+

Argos is an open and collaborative platform developed by OpenAIRE to facilitate + Research Data Management (RDM) activities concerning the implementation of Data + Management Plans. It uses OpenAIRE guides created by the RDM Task Force to + familiarize users with basic RDM concepts and guide them throughout the process of + writing DMPs. It also utilises the OpenAIRE pool of services and inferred sources to + make DMPs more dynamic in use and easier to be completed and published. Argos is + based on the OpenDMP open source software and is available through the OpenAIRE + Service catalogue and the EOSC.

+ +
+

Is Argos designed for one specific funder, e.g. the EC/Horizon Europe?

+

+ Argos is a flexible tool, designed to accommodate all research performing + and research funding organisations’ policies and Research Data Management (RDM) needs. + It already supports templates for different authorities. + These templates are created by Admin users in Argos. + In addition, we currently work to provide non-administrative users with the capability + to modify templates according to their own needs. +

+
+

Why use Argos?

+

Argos is easy to use and navigate around. It familiarises users with the DMP process + and provides guidance on basic RDM concepts so that users find useful resources to + learn from without having to leave the Argos environment. Users can invite their + colleagues and collaboratively work on completing a DMP. Moreover, Argos is an + integral part of the OpeAIRE ecosystem and the Research + Graph. Argos integrates + other services of the ecosystem to enable contextualisation of information, which is + especially useful when data are re-used, for example to understand how/ if they can + be repurposed.

+
+

Who is Argos for?

+

Argos is designed as a tool for inclusive use by researchers, students, funders, + research communities and institutions. It can be used in the context of research + projects’ conduct to comply with funders’ RDM requirements, as a tool in support of + literacy programmes in academia or can be independently deployed to meet given + stakeholder demands. Also, it is available in native languages, thanks to the help + of OpenAIRE NOADs, which strengthens common understanding of all researchers + involved in the DMP writing process. + By using Argos, researchers and students are able to create their DMPs in + collaboration with other colleagues, learn basic RDM concepts throughout the process + and publish DMPs as outputs in an open and FAIR manner, among other things by + assigning DOIs and licenses and by maintaining DMPs as living documents through + versioning. + At the same time, Argos can be configured and deployed by funders, institutions and + research communities. They can plug in their own services and/ or make use of + OpenAIRE underlying services that Argos is built with ad-hoc.

+
+

Using Argos

+

+ Argos consists of two main functionalities: DMPs and Datasets. + Argos can be used for: +

+ A. Viewing/ consulting publicly released DMPs and Datasets or Projects + corresponding to + DMPs +

+ Argos offers options for publishing DMPs in two modes, private or public. To view + public DMPs and Datasets, there is no need for login to the platform. +

+ B. Writing and publishing a DMP +

+ Argos helps researchers comply with mandates that may be attached to their grant + proposal/ project funding. They can therefore choose from the most suitable to their + needs template from the Datasets collection and proceed with answering the + corresponding questions. Once finalized, researchers can assign a DOI to their DMP, + publish and eventually cite it. +

+ C. Practicing on writing DMPs and Dataset Descriptions +

+ Argos may be used for educational purposes. The process of Data Management Planning + reflects the data management lifecycle, hence the tool can be used in response to + global RDM training demands. Examples may refer to embedding DMPs and DMP tools in + specific curricula or be embedded in library instructions’ sessions to familiarize + researchers and students the processes of RDM and DMP. +

+
+

Can I exploit ARGOS DMPs?

+

+ Of course. If you want to compare DMPs or analyse DMP data, then we advise you to export the records in .xml. + This schema is the most complete as it includes all information held in a DMP: information provided by the Admin + when structuring the template and input provided by researchers when completing their DMPs. +

+
+

Manage Account

+

Log in and out of Argos

+

+ You can log in Argos by selecting one of the providers from the Login page. Argos + does not require Sign Up. +

+
+

Create an administrator account

+

+ If you are interested in becoming an administrator in Argos and benefit from extra + features relevant to creating tailored templates, please email argos@openaire.eu . +

+ +
+

+ Switch from administrator account +

+

+ There is no need to switch from your administrator account to use Argos. The only + difference between regular users and administrators profiles in Argos is an extra + set of tools at the bottom of the main tool bar that is positioned on the left + handside. +

+
+

+ Change your email +

+

+ Argos does not have Sign Up. To change email, please see “Switch between accounts”. + Alternatevily, you can add more email addresses to your user account by selecting + the “Add alternative email” from your profile. +

+
+

+ Switch between accounts +

+

+ You can switch between email accounts by loging in with different providers from the + Login page. The change depends on whether you have used different email addresses to + sign up with those providers. On the occassion that only one email address is used + for all providers offered by Argos, then no change is expected. You can always add + new email accounts in your profile from the “Add alternative email” in your profile + page. +

+
+

+ Delete your account +

+

+ If you want to delete your Argos profile, please email argos@openaire.eu . +

+
+

+ Accounts access and safety +

+

+ How can I access my account and edit my profile? +

+

+ You can access your profile page and make desired edits from clicking on the avatar + at the very top of the toolbar located on the right handside. +

+
+

+ Can’t login to ARGOS +

+

+ Please try using a different provider from the Login page and contact us at: + argos@openaire.eu . +

+
+

+ Accessing Argos +

+

+ If you are reading this right now, you probably know the answer already! One way to + access Argos is through the OpenAIRE Service + catalogue. Another way is through the + EOSC + Catalogue. But, you can always find Argos at + argos.openaire.eu . + To access Argos software, please visit + https://code-repo.d4science.org/MaDgiK-CITE/argos/src/branch/master + . +

+
+

Argos User Roles

+

+ Who is the author of a DMP? +

+

+ Author of the DMP is everyone contributing to writing the DMP. Both Argos owners and + Argos members are DMP authors. Researchers, however, are not DMP authors. +

+
+

+ What is the difference between owners and + members? +

+

+ Argos DMP owner is the person initiating the DMP. People who are invited to join the + DMP process are members who contribute to writing the DMP. DMP owners have extra + editing rights and they are the ones to finalize the DMP process. Members can view + and edit DMPs and Datasets, but can not perform further actions for its validation + or finalization. +

+
+

+ What is the role of a researcher in Argos? +

+

+ Researchers in Argos are project contributors and usually those who own or have + managed data described in respective DMPs. +

+
+

+ Can a researcher be a DMP author? +

+

+ Of course! This depends on whether the researcher has also been involved in the DMP + writing process. +

+
+

+ What does an Admin user do? +

+

+ Not everyone can become an Admin user in Argos. This happens upon request at + argos@openaire.eu. Admin users are able to create + their own tailored templates from + a specialised editor, configure their own APIs and integrate services with Argos in + collaboration with and support of the Argos development team. Fees may apply + according to the type of requests. +

+
+

Creating DMPs

+

+ I can’t find my project in the list. What should + I do? +

+

+ DMPs that are created as part of the project proposal are not included in Argos. + Only accepted project proposals are listed in the platform. If you can’t find your + project in the list (drop-down menu), please use the “Insert manually” + functionality. +

+
+

+ I can’t find my grant in the list. What should I + do? +

+

+ If you can’t find your grant in the list (drop-down menu), please use the “Insert + manually” functionality. +

+
+

+ How do I edit and design my own DMP + template? +

+

+ You have to be an Admin user to design your own template in Argos. To learn more + about Admin users, check “What does an Admin user do?”. +

+
+

+ Can I create my own templates in Argos? +

+

+ Yes, you can, provided that you are an Admin user. To learn more about Admin users, + check “What does an Admin user do?”. +

+
+

+ What is the difference between “Save”, “Save & + Close”, “Save & Add New”? +

+
+

They all perform the same action, but the difference lies in where you are directed + after you have saved your DMP or Dataset.

+
    +
  • + When choosing Save, information that you have added in the editor is kept + and you + can continue adding more from the same page you were working on. +
    • +
  • + When choosing Save & Close, information that you have added is kept, but the + editor’s window closes and you are redirected to your dashboard. +
    • +
  • + [only for datasets] When choosing Save & Add New, information that you have + added is + kept, and you are redirected to another editor to start a new dataset. +
    • +
+
+
+

+ Can I modify things once I have finalized + them? +

+

+ Yes, you can, as long as you haven’t assigned a DOI to your DMP. You just select + “Undo Finalization”. +

+
+

+ How do I invite collaborators? +

+

+ You may use the “Invite” button to share DMPs with your colleagues and start working + on them together. +

+
+

+ Can scientists collaborate on the same DMP even though they may belong to different institutions (e.g. a hospital, a University, etc, collaborating on a project) and the dataset also "belongs" to different institutions? +

+

+ Of course. Argos supports collaborations across diverse teams. There are two most frequent ways that can address this question: +

+ A. Everyone works on the same DMP, but on different dataset descriptions +

+ In this case, each organisation makes its own dataset description(s) in a single DMP. + That means that the manager (i.e. person responsible for the DMP activity) creates a DMP in ARGOS + and shares it with everyone. If the DMP is shared with co-ownership rights, + then the people will be able to edit it and add their dataset descriptions at any time during the project. + If there is the need to control editing rights of people writing the DMPs, then the manager can create the dataset description(s) + and share these each time with the team members that are responsible for adding input for the specified datasets. +

+ B. Everyone works on their own DMP and content is later merged into one single DMP +

+ In this case, each organisation might work on their own DMP for the same project. + At one point, you need to decide which DMP is going to be the core for the work you perform, share co-ownership + between managers of all DMPs so they can copy all dataset descriptions of their DMPs in this single DMP document. +

+
+

+ How do I create an identical DMP or Dataset as a + copy? +

+

+ DMPs and Datasets can be cloned and used in different research contexts. + Existing DMPs presenting similarities with new ones, can be cloned, changed name and + then edited according to the new project data requirements. + Existing Datasets can be cloned and used in new DMPs that are reusing data described + in their context. +

+
+

+ What is the DMP version? How is it set? +

+

+ Versioning in Argos is both an internal and an external process. That means that + versioning happens both in the Argos environment when editing the DMP, and outside + of Argos when a DMP output is published in Zenodo. At every stage of the DMP + lifecycle, users have the option of keeping versions of the DMPs they are editing. + In Argos, users can create new versions of their DMPs by selecting the “Start New + Version” option to keep track of the evolution of their DMP throughout the writing + process. When published, versioning is associated with a DOI. Published DMPs are + automatically versioned every time a newer version of the same output is uploaded in + Zenodo. +

+
+

+ DMPs and Datasets +

+

+ What is the DMP? +

+

+ A DMP in Argos consists of vital information about the research project on behalf of + which the DMP is created and of more in depth information about the management, + handling and curation of datasets collected, produced or reused during the research + lifetime. A DMP in Argos accommodates documentation of more than one datasets. That + way datasets are provided with the flexibility to be described separately, following + different templates per type of dataset or research community concerned each time, + also possible to be copied and used in multiple DMPs. Datasets are then bundled up + in a DMP and can be shared more broadly. Special attention is given to the handling + of data that are being re-used via OpenAIRE APIs. +

+
+

+ How do I find which Dataset template to use? +

+

+ This depends on the reason why you are creating a DMP in the first place. If it is + for compliance matters with funders, institutions or research communities RDM + policies, then you may select the dataset template of that particular stakeholder. + If you are creating a DMP for training purposes, you may select and work on any + template from the Argos collection. +

+
+

+ How do I create my own Dataset template? +

+

+ Currently, it is not possible for all Argos users to create dataset templates of + their own, so they have to work on predefined templates. Additional rights for + editing Dataset templates according to tailored needs have Admin users. This is + expected to change in the near future. To learn more about Admin users, check “What + does an Admin user do?”. +

+
+

+ Can I create smaller versions of a template for project proposals? +

+

+ Yes, it is possible in Argos to create short versions of templates that can be used + for grant proposals, such as for Horizon Europe. + If you are interested in working with us to create this short version of any ARGOS template, + please contact us: argos@openaire.eu. +

+
+

+ Can I customise an existing template (e.g. for a specific institution)? +

+

+ Yes, you can. In the current version, this is possible for Admin users who have their own deployment on-premises or cloud. + Please note that this subject to change in the near future as we are working on a feature that will allow all users + to customise (remove/add/extend) specific questions on the template they are working on. +

+
+

+ What is a Dataset? +

+

+ A Dataset in Argos is an editor with set up questions that support the creation of + descriptions of how data are / have been handled, managed and curated throughout the + research data lifecycle. The editor holds a collection of Dataset templates each one + with different sets of predefined questions as per funders, institutions, research + communities RDM policy requirements. Researchers and students can choose the + template that corresponds to their RDM needs in order to get funding or get their + degree, respectively. A DMP in Argos may consist of one or more datasets. +

+
+

+ Why do I need more than one Dataset? +

+

+ You don’t necessarily need to have many Datasets in a DMP. However, you might be + producing a plethora of data during your research that are diverse in type and/ or + scope of collection/ re-use, thus presenting diverse management needs. Argos gives + you the flexibility to describe all data produced and/ or re-used in your research + separately. That way it is easy to perform the mapping of information provided in a + DMP to the respective data types or data collections they correspond to. Equally, + reuse of particular datasets in different DMPs is easier. For the latter, please + check “How do I create an identical DMP or Dataset as a copy?”. +

+
+

+ It is not very clear to me when one should choose to add a dataset or to describe several "data products" in the same description. +

+

+ This is something that has to be tackled conceptually, from the author of the DMP. + If those "products" have their own lifetime and rules (IPR, Access rights, etc), they should be described as different datasets. + Alternative formats should not be treated as different datasets, unless they have other differences due to the format, too. + But, for instance, if you have datasets in CSV and JSON formats and under the same terms, they could be seen as one dataset description in the DMP. +

+
+

+ Can I add to my DMP information about datasets published on Zenodo? +

+

+ Argos offers a search to Zenodo for prefilling the DMP you are working with dataset metadata. + This search has been developed according to the rules set by Zenodo + and therefore has the same behaviour as when you are using the search bar on the Zenodo interface. + However, we understand the need to be able to find records with their PID, + hence we introduced some changes and now support searching DOIs from the Argos interface. +

+
+

+ Is it possible to describe a dataset that is not yet in a repository? +

+

+ Of course! You can choose to manually describe your dataset, e.g. for a dataset you are planning to produce, + instead of pre-filling the template with available metadata from a dataset that has already been shared and preserved in a repository. +

+
+

+ What are public DMPs and Datasets? +

+

+ Public DMPs and Public Datasets are collections of openly available Argos outputs. + That means that DMP owners and members are making their DMP and/or Dataset outputs + available to all Argos and non-Argos users who might want to consult or re-use them + under the framework provided by the assigned DMP license. Please also check “Is all + the information I create visible by default?”. +

+
+

+ Is all information I create visible by + default? +

+

+ No, it is not. You can choose how your DMP is displayed in Argos from the + “Visibility” option. Choosing Public will immediately locate your DMP in the “Public + DMPs” collection and make it available to all Argos and non-Argos users. + Choosing Private will keep the DMP visible only to you and to the people invited to + edit the DMP in collaboration with you. Private DMPs are not publicly displayed to + other users. +

+
+

+ What is the difference between the DMP and the dataset export? +

+

+ DMP export contains all vital information for a DMP, including funding and dataset details, + while dataset export is a subset of the DMP export containing information only about a dataset described in the DMP. + Both DMP and Dataset exports are available in .pdf, .docx, .xml. + In addition, DMP export is available in the RDA .json format + to increase interoperability of ARGOS exchanged DMPs. +

+
+

+ Is there a storage allowance limitation for the + DMPs and Dataset files? +

+

+ No, there is no storage limit or fee for either files stored in Argos. +

+
+

+ Publishing DMPs +

+

+ Is it possible to publish DMPs in different repositories (so not Zenodo)? +

+

+ Yes, it is possible. + But, to have different repositories attached to the system, you will need your own on-premises or cloud deployment. + We are already working on that for DSpace and Dataverse repositories. +

+
+

+ Do you know that Zenodo has empty DMPs from ARGOS? +

+

+ Yes, we are aware of that. + Argos has no control over the DMPs that you generate and publish and thus can not be held accountable for empty DMPs. + Please remember that, as on all other occasions where you publish content, you should do so responsinbly. + If you have any questions regarding publishing DMPs, don’t hesitate to contact us at argos@openaire.eu. +

+
+

+ Once I upload a final version of a DMP to Zenodo, do I need to update this first final version from Zenodo or from Argos? +

+

+ Both options are possible according to how you have deposited the DMP in the first place. + If you have deposited your DMP with a token (i.e. from the ARGOS account on Zenodo), + then you won’t have editing rights on the Zenodo record, but you will still be able to make changes + on ARGOS by starting and depositing a new version of the published DMP. + However, if you have deposited your DMP using your own account on Zenodo (i.e. login to Zenodo with your own credentials), + then you are able to also make minor changes, e.g. on the title of the DMP, directly from the Zenodo interface. +

+
+

Troubleshooting

+

+ Can’t finalize a DMP +

+

+ You might be experiencing this problem because there are incomplete mandatory fields + in your DMP. Please check for those fields, fill in with appropriate information and + try again. Should the problem persists, please contact argos@openaire.eu . +

+
+

+ Can’t co-edit a DMP +

+

+ DMPs can be shared with many colleagues in support of collaborative writing, but + DMPs should be worked by one person at a time. Argos will inform you if another + colleague has the DMP you are trying to edit open, so that your team avoids + information loss. +

+
+

+ Deposit is not working +

+

+ You need to have a Zenodo login to perform a deposit. Please sign up in Zenodo or + use the token option to publish your DMPs and get a DOI. +

+
+

Legal and privacy

+

+ Is Argos open source? +

+

+ Yes, it is. The OpenDMP software that Argos has deployed upon is open source code + available under Apache 2.0 license. You may find more information about the software + here. +

+
+

+ Can I contribute to Argos development? +

+

+ Of course! Please feel free to suggest new features and to actively contribute to + Argos development via pull requests in Gitea. +

+
+

+ Is Argos GDPR compliant? +

+

+ Argos takes all necessary steps in handling and protecting personal and sensitive + information. Please check the Argos Terms of Service and Privacy Policy. +

+
+

+ Which is the Argos data policy? +

+

+ Please find all information about Argos Terms of Service and Privacy, here. + Additionally, you may find Argos Cookies policy, here. +

+
+

+ What is the work ownership of information + created in Argos? +

+

+ Unless there are any contractual or institutional agreements stating ownership of + outputs produced in the context of a project/ collaboration, owners of Argos outputs + are DMP contributors, i.e. DMP owners and DMP members, who have been involved with + writing the DMP. +

+
+

+ Which are the terms and policies of Argos? +

+

+ Please find all information about Argos Terms of Service and Privacy, here. + Additionally, you may find Argos Cookies policy, here. +

+ + +
+
+
+ + + diff --git a/dmp-backend/web/src/main/resources/material/glossary/Glossary_en.html b/dmp-backend/web/src/main/resources/material/glossary/Glossary_en.html new file mode 100644 index 000000000..e1ee6253c --- /dev/null +++ b/dmp-backend/web/src/main/resources/material/glossary/Glossary_en.html @@ -0,0 +1,94 @@ + + + + + + + + + + + + + + + + + +
+
+
+

Glossary

+
+
+
+
+

DMP

+

A DMP - short for Data Management Plan - is a document describing the processes that the data have undergone and the tools used for their handling and storage during a research lifecycle. Most importantly, DMPs secure provenance and enable re-use of data by appointing data managers and by including information on how data can be re-used by others in the future. Therefore, a DMP is a living document which is modified according to the data developments of a project before it’s completed and handed over at the end of the project. + Public funders increasingly contain DMPs in their grant proposals or policy funding requirements. A good paradigm is the European Commission demands for the production and delivery of DMPs for projects funded under the Horizon 2020 Funding Programme. On that note, and to encourage good data management practices uptake, many European institutions include DMPs in post-graduate researchers policies and offer relevant support to staff and students. +

+ +

DMP template

+

DMP template contains general but vital information about the name and the duration of the project that the DMP corresponds to, the contributing organisations and individuals as well as the datasets that are under the Dataset Description section. It also offers the possibility of describing datasets other than primary data generated, under “External References” section. A DMP template can have many Dataset Descriptions. +

+ +

Dataset Description

+

Dataset Description documents the management processes of datasets following funder’s or institution’s requirements. A dataset description is essentially a questionnaire template with underlying added value services for interoperability and machine readability of information which is developed based on the given requirements. Management requirements differ from funder to funder and from institution to institution, hence the growing collection of Dataset Descriptions to select from. + Moreover, a Dataset Description links to the documentation of one dataset, hence a DMP template may contain more than one dataset descriptions on the occasion when multiple datasets were used during the project. When documentation of some of the project’s datasets falls under additional requirements (e.g. projects receiving multiple grants from different sources), there is the possibility of describing datasets with more than one Dataset Description template. +

+
+
+
+ + + diff --git a/dmp-backend/web/src/main/resources/material/terms-of-service/TermsOfService_en.html b/dmp-backend/web/src/main/resources/material/terms-of-service/TermsOfService_en.html new file mode 100644 index 000000000..2bcaaeb33 --- /dev/null +++ b/dmp-backend/web/src/main/resources/material/terms-of-service/TermsOfService_en.html @@ -0,0 +1,115 @@ + + + + + + + + + + + + + + + + + +
+
+
+

Terms of Service

+
+
+
+
+

The OpenDMP service was developed to provide a more flexible, collaborative environment with machine actionable solutions in writing, sharing and publishing Data Management Plans (DMPs). It is a product of cooperation between OpenAIRE AMKE and EUDAT CDI and is offered both as a software “OpenDMP '' and as an online service under the name “ARGOS”.

+

+
    +
  1. OpenDMP software is offered under the Free Open Source Software license  Apache 2.0, for further development and use by institutions and interested parties.
    2. +
  2. ARGOS service is offered by OpenAIRE as part of its mission to support Open Science in the European Research Area, focusing on information linking and contextualisation that enriches its Research Graph. Use of ARGOS denotes agreement with the following terms: +
      +
    1. ARGOS is a software interface and a database with no storage capacity to store or preserve research data. The DMPs created are hosted in the OpenAIRE production environment for the sole purpose of exposing the DMP records once finalised (“published”). If assigned a DOI, the DMP records are linked to and preserved in Zenodo, the OpenAIRE’s repository service. The ARGOS service is made available for use free-of-charge for research, educational and informational purposes.
      2. +
    2. Login to ARGOS is possible through a variety of external providers, among which Google, Facebook, Twitter, B2Access and OpenAIRE Login, that share information of their user profiles with ARGOS, according to the rights that have been granted to the given provider by the user. External email addresses that are used in invitations for collaborations are held in ARGOS database that stores information about only the name, surname and email address of the DMP creator and collaborator.  Personal data is collected via the login option and via email invitations sent to external DMP contributors. This personal information as well as the activity of ARGOS users is used only for deriving usage metrics and assessing the service quality. They are stored in ARGOS database for as long as the account is active and they are accessible only from people in the team in charge of quality and risk assessment. They will not be used for other purposes other than the ones stated in this document and they can be deleted at any time should the user claim a relevant request. The aforementioned processes are also facilitated by the use of cookies (see below the “Cookie policy”).
      3. +
    3. Data concerning DMP information will be used by OpenAIRE for research and development purposes, such as identifying DMP models, and for ensuring compliance with policy requirements and monitoring of DMPs uptake linked to OpenAIRE’s Monitoring Dashboards and the Open Science Observatory.
      4. +
    4. The DMP Manager, i.e. the person who creates and manages a DMP, and/ or the contributor, i.e. the person who is invited to collaborate on a DMP, shall ensure that content is accurate and presented in a way that adheres to these Terms of Service and applicable laws, including, but not limited to, privacy, data protection and intellectual property rights.
      5. +
    5. ARGOS service is provided by OpenAIRE “as is”. Although OpenAIRE and its partners take measures for the availability, dependability, and accuracy of the service, access to ARGOS, utilisation of its features and preservation of the data deposited or produced by the service are not guaranteed. OpenAIRE cannot be held responsible for any data loss regarding DMPs, ethical or financial damage or any other direct or indirect impact that any failure of ARGOS service may have on its users.  
      6. +
    6. ARGOS users are exclusively responsible for their use of content, and shall hold OpenAIRE free and harmless in connection with their download and/or use.
      7. +
    7. OpenAIRE may not be held responsible for the content provided or statements made in Data Management Plans created and managed by its users.
      8. +
    8. All content is provided “as-is”. Users of content (“Users”) shall respect applicable license conditions. Download and use of content from ARGOS does not transfer any intellectual property rights in the content to the User.
      9. +
    9. In the case any content is reported as violating third party rights or other legal provisions, ARGOS reserves the right to remove the content from the service until the dispute is legally settled. Any such incidents should be reported at noticeandtakedown@openaire.eu 
      10. +
    10. ARGOS users are held responsible for the data and information they provide in the service. Users may not add information, data or any other type of artifact that may be malicious, intentionally erroneous and potentially harmful for other ARGOS users, IPR owners and/or the general public.
      11. +
    11. In case a user of ARGOS identifies a potential infringement of copyright, harmful or malicious operation, function, code, information or data, shall inform OpenAIRE providing sufficient evidence for the identification of the case and the information and/or data challenged.
      12. +
    12. OpenAIRE reserves the right, without notice, at its sole discretion and without liability, (i) to alter or delete inappropriate content, and (ii) to restrict or remove User access where it considers that use of ARGOS interferes with its operations or violates these Terms of Service or applicable laws.
      13. +
    13. These Terms of Service are subject to change by OpenAIRE at any time and without notice, other than through posting the updated Terms of Service on the OpenAIRE website and indicating the version and date of last update.
      14. +
    +
    3. +
+

For any questions or comments you may have about the current Terms of Service, please contact us: argos@openaire.eu 

+
+
+
+ + + diff --git a/user-guide/UserGuide_de.html b/dmp-backend/web/src/main/resources/material/user-guide/UserGuide_de.html similarity index 100% rename from user-guide/UserGuide_de.html rename to dmp-backend/web/src/main/resources/material/user-guide/UserGuide_de.html diff --git a/user-guide/UserGuide_en.html b/dmp-backend/web/src/main/resources/material/user-guide/UserGuide_en.html similarity index 100% rename from user-guide/UserGuide_en.html rename to dmp-backend/web/src/main/resources/material/user-guide/UserGuide_en.html diff --git a/user-guide/UserGuide_es.html b/dmp-backend/web/src/main/resources/material/user-guide/UserGuide_es.html similarity index 100% rename from user-guide/UserGuide_es.html rename to dmp-backend/web/src/main/resources/material/user-guide/UserGuide_es.html diff --git a/user-guide/UserGuide_gr.html b/dmp-backend/web/src/main/resources/material/user-guide/UserGuide_gr.html similarity index 100% rename from user-guide/UserGuide_gr.html rename to dmp-backend/web/src/main/resources/material/user-guide/UserGuide_gr.html diff --git a/user-guide/UserGuide_pt.html b/dmp-backend/web/src/main/resources/material/user-guide/UserGuide_pt.html similarity index 100% rename from user-guide/UserGuide_pt.html rename to dmp-backend/web/src/main/resources/material/user-guide/UserGuide_pt.html diff --git a/user-guide/UserGuide_sk.html b/dmp-backend/web/src/main/resources/material/user-guide/UserGuide_sk.html similarity index 100% rename from user-guide/UserGuide_sk.html rename to dmp-backend/web/src/main/resources/material/user-guide/UserGuide_sk.html diff --git a/user-guide/UserGuide_sr.html b/dmp-backend/web/src/main/resources/material/user-guide/UserGuide_sr.html similarity index 100% rename from user-guide/UserGuide_sr.html rename to dmp-backend/web/src/main/resources/material/user-guide/UserGuide_sr.html diff --git a/user-guide/UserGuide_tr.html b/dmp-backend/web/src/main/resources/material/user-guide/UserGuide_tr.html similarity index 100% rename from user-guide/UserGuide_tr.html rename to dmp-backend/web/src/main/resources/material/user-guide/UserGuide_tr.html diff --git a/dmp-frontend/src/app/core/core-service.module.ts b/dmp-frontend/src/app/core/core-service.module.ts index b36cf42f8..af0f85591 100644 --- a/dmp-frontend/src/app/core/core-service.module.ts +++ b/dmp-frontend/src/app/core/core-service.module.ts @@ -47,6 +47,10 @@ import { TypeUtils } from './services/utilities/type-utils.service'; import { SpecialAuthGuard } from './special-auth-guard.service'; import {PrefillingService} from "@app/core/services/prefilling.service"; import { DepositRepositoriesService } from './services/deposit-repositories/deposit-repositories.service'; +import { AboutService } from './services/about/about.service'; +import { FaqService } from './services/faq/faq.service'; +import { GlossaryService } from './services/glossary/glossary.service'; +import { TermsOfServiceService } from './services/terms-of-service/terms-of-service.service'; // // // This is shared module that provides all the services. Its imported only once on the AppModule. @@ -112,6 +116,10 @@ export class CoreServiceModule { LanguageService, LockService, UserGuideService, + AboutService, + FaqService, + GlossaryService, + TermsOfServiceService, CurrencyService, MergeEmailConfirmationService, ConfigurationService, diff --git a/dmp-frontend/src/app/core/services/about/about.service.ts b/dmp-frontend/src/app/core/services/about/about.service.ts new file mode 100644 index 000000000..404563c3e --- /dev/null +++ b/dmp-frontend/src/app/core/services/about/about.service.ts @@ -0,0 +1,23 @@ +import { Injectable } from "@angular/core"; +import { ConfigurationService } from "../configuration/configuration.service"; +import { HttpClient, HttpResponse } from "@angular/common/http"; +import { Observable } from "rxjs"; + +@Injectable() +export class AboutService { + private aboutUrl : string; + + constructor( + private http: HttpClient, + private configurationService: ConfigurationService + ) { + this.aboutUrl = `${configurationService.server}material/about`; + } + + public getAbout(lang: string): Observable> { + return this.http.get(`${this.aboutUrl}/${lang}`, { responseType: 'blob', observe: 'response', headers: {'Content-type': 'text/html', + 'Accept': 'text/html', + 'Access-Control-Allow-Origin': this.configurationService.app, + 'Access-Control-Allow-Credentials': 'true'} }); + } +} \ No newline at end of file diff --git a/dmp-frontend/src/app/core/services/faq/faq.service.ts b/dmp-frontend/src/app/core/services/faq/faq.service.ts new file mode 100644 index 000000000..c59cfe9cd --- /dev/null +++ b/dmp-frontend/src/app/core/services/faq/faq.service.ts @@ -0,0 +1,23 @@ +import { Injectable } from "@angular/core"; +import { ConfigurationService } from "../configuration/configuration.service"; +import { HttpClient, HttpResponse } from "@angular/common/http"; +import { Observable } from "rxjs"; + +@Injectable() +export class FaqService { + private faqUrl : string; + + constructor( + private http: HttpClient, + private configurationService: ConfigurationService + ) { + this.faqUrl = `${configurationService.server}material/faq`; + } + + public getFaq(lang: string): Observable> { + return this.http.get(`${this.faqUrl}/${lang}`, { responseType: 'blob', observe: 'response', headers: {'Content-type': 'text/html', + 'Accept': 'text/html', + 'Access-Control-Allow-Origin': this.configurationService.app, + 'Access-Control-Allow-Credentials': 'true'} }); + } +} \ No newline at end of file diff --git a/dmp-frontend/src/app/core/services/glossary/glossary.service.ts b/dmp-frontend/src/app/core/services/glossary/glossary.service.ts new file mode 100644 index 000000000..c346074bd --- /dev/null +++ b/dmp-frontend/src/app/core/services/glossary/glossary.service.ts @@ -0,0 +1,23 @@ +import { Injectable } from "@angular/core"; +import { ConfigurationService } from "../configuration/configuration.service"; +import { HttpClient, HttpResponse } from "@angular/common/http"; +import { Observable } from "rxjs"; + +@Injectable() +export class GlossaryService { + private glossaryUrl : string; + + constructor( + private http: HttpClient, + private configurationService: ConfigurationService + ) { + this.glossaryUrl = `${configurationService.server}material/glossary`; + } + + public getGlossary(lang: string): Observable> { + return this.http.get(`${this.glossaryUrl}/${lang}`, { responseType: 'blob', observe: 'response', headers: {'Content-type': 'text/html', + 'Accept': 'text/html', + 'Access-Control-Allow-Origin': this.configurationService.app, + 'Access-Control-Allow-Credentials': 'true'} }); + } +} \ No newline at end of file diff --git a/dmp-frontend/src/app/core/services/terms-of-service/terms-of-service.service.ts b/dmp-frontend/src/app/core/services/terms-of-service/terms-of-service.service.ts new file mode 100644 index 000000000..5ebe6a573 --- /dev/null +++ b/dmp-frontend/src/app/core/services/terms-of-service/terms-of-service.service.ts @@ -0,0 +1,23 @@ +import { Injectable } from "@angular/core"; +import { ConfigurationService } from "../configuration/configuration.service"; +import { HttpClient, HttpResponse } from "@angular/common/http"; +import { Observable } from "rxjs"; + +@Injectable() +export class TermsOfServiceService { + private termsOfServiceUrl : string; + + constructor( + private http: HttpClient, + private configurationService: ConfigurationService + ) { + this.termsOfServiceUrl = `${configurationService.server}material/termsofservice`; + } + + public getTermsOfService(lang: string): Observable> { + return this.http.get(`${this.termsOfServiceUrl}/${lang}`, { responseType: 'blob', observe: 'response', headers: {'Content-type': 'text/html', + 'Accept': 'text/html', + 'Access-Control-Allow-Origin': this.configurationService.app, + 'Access-Control-Allow-Credentials': 'true'} }); + } +} \ No newline at end of file diff --git a/dmp-frontend/src/app/ui/about/about.component.html b/dmp-frontend/src/app/ui/about/about.component.html index 16d8dfe91..f51042fc1 100644 --- a/dmp-frontend/src/app/ui/about/about.component.html +++ b/dmp-frontend/src/app/ui/about/about.component.html @@ -1,33 +1,5 @@ -
+
-
-

{{ 'ABOUT.TITLE' | translate}}

-
+
-
-
-

ARGOS is an online tool in support of automated processes to creating, managing, sharing and linking DMPs with research artifacts they correspond to. It is the joint effort of OpenAIRE and EUDAT to deliver an open platform for Data Management Planning that addresses FAIR and Open best practices and assumes no barriers for its use and adoption. It does so by applying common standards for machine-actionable DMPs as defined by the global research data community of RDA and by communicating and consulting with researchers, research communities and funders to better reflect on their needs. -

ARGOS provides a flexible environment and an easy interface for users to navigate and use.

-
-
- - - -
+
\ No newline at end of file diff --git a/dmp-frontend/src/app/ui/about/about.component.scss b/dmp-frontend/src/app/ui/about/about.component.scss index 38187f826..30a2f8b8b 100644 --- a/dmp-frontend/src/app/ui/about/about.component.scss +++ b/dmp-frontend/src/app/ui/about/about.component.scss @@ -8,6 +8,9 @@ img { width: 100%; } -// .about-component { -// margin-top: 80px; -// } +.iframe { + width: 100%; + height: calc(100vh - 80px); + margin: 0px; + border: none; +} diff --git a/dmp-frontend/src/app/ui/about/about.component.ts b/dmp-frontend/src/app/ui/about/about.component.ts index 4bc1ca7b6..5d0640053 100644 --- a/dmp-frontend/src/app/ui/about/about.component.ts +++ b/dmp-frontend/src/app/ui/about/about.component.ts @@ -1,21 +1,36 @@ -import { HttpClient } from '@angular/common/http'; import { Component, OnInit } from '@angular/core'; +import { DomSanitizer, SafeResourceUrl } from '@angular/platform-browser'; +import { AboutService } from '@app/core/services/about/about.service'; +import { LanguageService } from '@app/core/services/language/language.service'; import { MatomoService } from '@app/core/services/matomo/matomo-service'; +import { BaseComponent } from '@common/base/base.component'; +import { takeUntil } from 'rxjs/operators'; @Component({ selector: 'app-about-componet', templateUrl: './about.component.html', styleUrls: ['./about.component.scss'] }) -export class AboutComponent implements OnInit { +export class AboutComponent extends BaseComponent implements OnInit { + + aboutHTMLUrl: SafeResourceUrl; + sanitizedGuideUrl: any; constructor( - private httpClient: HttpClient, - private matomoService: MatomoService) { - } + private aboutService: AboutService, + private sanitizer: DomSanitizer, + private languageService: LanguageService, + private matomoService: MatomoService + ) { super(); } ngOnInit() { this.matomoService.trackPageView('About'); + this.aboutService.getAbout(this.languageService.getCurrentLanguage()) + .pipe(takeUntil(this._destroyed)) + .subscribe(response => { + const blob = new Blob([response.body], { type: 'text/html' }); + this.aboutHTMLUrl = this.sanitizer.bypassSecurityTrustResourceUrl((window.URL ? URL : webkitURL).createObjectURL(blob)); + }); } } diff --git a/dmp-frontend/src/app/ui/faq/dialog/faq-dialog.component.html b/dmp-frontend/src/app/ui/faq/dialog/faq-dialog.component.html index 526d13413..30f2126a1 100644 --- a/dmp-frontend/src/app/ui/faq/dialog/faq-dialog.component.html +++ b/dmp-frontend/src/app/ui/faq/dialog/faq-dialog.component.html @@ -7,7 +7,7 @@ close -
+
diff --git a/dmp-frontend/src/app/ui/faq/faq-content/faq-content.component.html b/dmp-frontend/src/app/ui/faq/faq-content/faq-content.component.html index 28ff25f85..e87b95039 100644 --- a/dmp-frontend/src/app/ui/faq/faq-content/faq-content.component.html +++ b/dmp-frontend/src/app/ui/faq/faq-content/faq-content.component.html @@ -1,678 +1,5 @@ -
-
-
-

{{ 'FAQ.TITLE-DASHED' | translate}}

-
-
+
-
-

About ARGOS

-

What is ARGOS?

-

Argos is an open and collaborative platform developed by OpenAIRE to facilitate - Research Data Management (RDM) activities concerning the implementation of Data - Management Plans. It uses OpenAIRE guides created by the RDM Task Force to - familiarize users with basic RDM concepts and guide them throughout the process of - writing DMPs. It also utilises the OpenAIRE pool of services and inferred sources to - make DMPs more dynamic in use and easier to be completed and published. Argos is - based on the OpenDMP open source software and is available through the OpenAIRE - Service catalogue and the EOSC.

- -
-

Is Argos designed for one specific funder, e.g. the EC/Horizon Europe?

-

- Argos is a flexible tool, designed to accommodate all research performing - and research funding organisations’ policies and Research Data Management (RDM) needs. - It already supports templates for different authorities. - These templates are created by Admin users in Argos. - In addition, we currently work to provide non-administrative users with the capability - to modify templates according to their own needs. -

-
-

Why use Argos?

-

Argos is easy to use and navigate around. It familiarises users with the DMP process - and provides guidance on basic RDM concepts so that users find useful resources to - learn from without having to leave the Argos environment. Users can invite their - colleagues and collaboratively work on completing a DMP. Moreover, Argos is an - integral part of the OpeAIRE ecosystem and the Research - Graph. Argos integrates - other services of the ecosystem to enable contextualisation of information, which is - especially useful when data are re-used, for example to understand how/ if they can - be repurposed.

-
-

Who is Argos for?

-

Argos is designed as a tool for inclusive use by researchers, students, funders, - research communities and institutions. It can be used in the context of research - projects’ conduct to comply with funders’ RDM requirements, as a tool in support of - literacy programmes in academia or can be independently deployed to meet given - stakeholder demands. Also, it is available in native languages, thanks to the help - of OpenAIRE NOADs, which strengthens common understanding of all researchers - involved in the DMP writing process. - By using Argos, researchers and students are able to create their DMPs in - collaboration with other colleagues, learn basic RDM concepts throughout the process - and publish DMPs as outputs in an open and FAIR manner, among other things by - assigning DOIs and licenses and by maintaining DMPs as living documents through - versioning. - At the same time, Argos can be configured and deployed by funders, institutions and - research communities. They can plug in their own services and/ or make use of - OpenAIRE underlying services that Argos is built with ad-hoc.

-
-

Using Argos

-

- Argos consists of two main functionalities: DMPs and Datasets. - Argos can be used for: -

- A. Viewing/ consulting publicly released DMPs and Datasets or Projects - corresponding to - DMPs -

- Argos offers options for publishing DMPs in two modes, private or public. To view - public DMPs and Datasets, there is no need for login to the platform. -

- B. Writing and publishing a DMP -

- Argos helps researchers comply with mandates that may be attached to their grant - proposal/ project funding. They can therefore choose from the most suitable to their - needs template from the Datasets collection and proceed with answering the - corresponding questions. Once finalized, researchers can assign a DOI to their DMP, - publish and eventually cite it. -

- C. Practicing on writing DMPs and Dataset Descriptions -

- Argos may be used for educational purposes. The process of Data Management Planning - reflects the data management lifecycle, hence the tool can be used in response to - global RDM training demands. Examples may refer to embedding DMPs and DMP tools in - specific curricula or be embedded in library instructions’ sessions to familiarize - researchers and students the processes of RDM and DMP. -

-
-

Can I exploit ARGOS DMPs?

-

- Of course. If you want to compare DMPs or analyse DMP data, then we advise you to export the records in .xml. - This schema is the most complete as it includes all information held in a DMP: information provided by the Admin - when structuring the template and input provided by researchers when completing their DMPs. -

-
-

Manage Account

-

Log in and out of Argos

-

- You can log in Argos by selecting one of the providers from the Login page. Argos - does not require Sign Up. -

-
-

Create an administrator account

-

- If you are interested in becoming an administrator in Argos and benefit from extra - features relevant to creating tailored templates, please email argos@openaire.eu . -

- -
-

- Switch from administrator account -

-

- There is no need to switch from your administrator account to use Argos. The only - difference between regular users and administrators profiles in Argos is an extra - set of tools at the bottom of the main tool bar that is positioned on the left - handside. -

-
-

- Change your email -

-

- Argos does not have Sign Up. To change email, please see “Switch between accounts”. - Alternatevily, you can add more email addresses to your user account by selecting - the “Add alternative email” from your profile. -

-
-

- Switch between accounts -

-

- You can switch between email accounts by loging in with different providers from the - Login page. The change depends on whether you have used different email addresses to - sign up with those providers. On the occassion that only one email address is used - for all providers offered by Argos, then no change is expected. You can always add - new email accounts in your profile from the “Add alternative email” in your profile - page. -

-
-

- Delete your account -

-

- If you want to delete your Argos profile, please email argos@openaire.eu . -

-
-

- Accounts access and safety -

-

- How can I access my account and edit my profile? -

-

- You can access your profile page and make desired edits from clicking on the avatar - at the very top of the toolbar located on the right handside. -

-
-

- Can’t login to ARGOS -

-

- Please try using a different provider from the Login page and contact us at: - argos@openaire.eu . -

-
-

- Accessing Argos -

-

- If you are reading this right now, you probably know the answer already! One way to - access Argos is through the OpenAIRE Service - catalogue. Another way is through the - EOSC - Catalogue. But, you can always find Argos at - argos.openaire.eu . - To access Argos software, please visit - https://code-repo.d4science.org/MaDgiK-CITE/argos/src/branch/master - . -

-
-

Argos User Roles

-

- Who is the author of a DMP? -

-

- Author of the DMP is everyone contributing to writing the DMP. Both Argos owners and - Argos members are DMP authors. Researchers, however, are not DMP authors. -

-
-

- What is the difference between owners and - members? -

-

- Argos DMP owner is the person initiating the DMP. People who are invited to join the - DMP process are members who contribute to writing the DMP. DMP owners have extra - editing rights and they are the ones to finalize the DMP process. Members can view - and edit DMPs and Datasets, but can not perform further actions for its validation - or finalization. -

-
-

- What is the role of a researcher in Argos? -

-

- Researchers in Argos are project contributors and usually those who own or have - managed data described in respective DMPs. -

-
-

- Can a researcher be a DMP author? -

-

- Of course! This depends on whether the researcher has also been involved in the DMP - writing process. -

-
-

- What does an Admin user do? -

-

- Not everyone can become an Admin user in Argos. This happens upon request at - argos@openaire.eu. Admin users are able to create - their own tailored templates from - a specialised editor, configure their own APIs and integrate services with Argos in - collaboration with and support of the Argos development team. Fees may apply - according to the type of requests. -

-
-

Creating DMPs

-

- I can’t find my project in the list. What should - I do? -

-

- DMPs that are created as part of the project proposal are not included in Argos. - Only accepted project proposals are listed in the platform. If you can’t find your - project in the list (drop-down menu), please use the “Insert manually” - functionality. -

-
-

- I can’t find my grant in the list. What should I - do? -

-

- If you can’t find your grant in the list (drop-down menu), please use the “Insert - manually” functionality. -

-
-

- How do I edit and design my own DMP - template? -

-

- You have to be an Admin user to design your own template in Argos. To learn more - about Admin users, check “What does an Admin user do?”. -

-
-

- Can I create my own templates in Argos? -

-

- Yes, you can, provided that you are an Admin user. To learn more about Admin users, - check “What does an Admin user do?”. -

-
-

- What is the difference between “Save”, “Save & - Close”, “Save & Add New”? -

-
-

They all perform the same action, but the difference lies in where you are directed - after you have saved your DMP or Dataset.

-
    -
  • - When choosing Save, information that you have added in the editor is kept - and you - can continue adding more from the same page you were working on. -
    • -
  • - When choosing Save & Close, information that you have added is kept, but the - editor’s window closes and you are redirected to your dashboard. -
    • -
  • - [only for datasets] When choosing Save & Add New, information that you have - added is - kept, and you are redirected to another editor to start a new dataset. -
    • -
-
-
-

- Can I modify things once I have finalized - them? -

-

- Yes, you can, as long as you haven’t assigned a DOI to your DMP. You just select - “Undo Finalization”. -

-
-

- How do I invite collaborators? -

-

- You may use the “Invite” button to share DMPs with your colleagues and start working - on them together. -

-
-

- Can scientists collaborate on the same DMP even though they may belong to different institutions (e.g. a hospital, a University, etc, collaborating on a project) and the dataset also "belongs" to different institutions? -

-

- Of course. Argos supports collaborations across diverse teams. There are two most frequent ways that can address this question: -

- A. Everyone works on the same DMP, but on different dataset descriptions -

- In this case, each organisation makes its own dataset description(s) in a single DMP. - That means that the manager (i.e. person responsible for the DMP activity) creates a DMP in ARGOS - and shares it with everyone. If the DMP is shared with co-ownership rights, - then the people will be able to edit it and add their dataset descriptions at any time during the project. - If there is the need to control editing rights of people writing the DMPs, then the manager can create the dataset description(s) - and share these each time with the team members that are responsible for adding input for the specified datasets. -

- B. Everyone works on their own DMP and content is later merged into one single DMP -

- In this case, each organisation might work on their own DMP for the same project. - At one point, you need to decide which DMP is going to be the core for the work you perform, share co-ownership - between managers of all DMPs so they can copy all dataset descriptions of their DMPs in this single DMP document. -

-
-

- How do I create an identical DMP or Dataset as a - copy? -

-

- DMPs and Datasets can be cloned and used in different research contexts. - Existing DMPs presenting similarities with new ones, can be cloned, changed name and - then edited according to the new project data requirements. - Existing Datasets can be cloned and used in new DMPs that are reusing data described - in their context. -

-
-

- What is the DMP version? How is it set? -

-

- Versioning in Argos is both an internal and an external process. That means that - versioning happens both in the Argos environment when editing the DMP, and outside - of Argos when a DMP output is published in Zenodo. At every stage of the DMP - lifecycle, users have the option of keeping versions of the DMPs they are editing. - In Argos, users can create new versions of their DMPs by selecting the “Start New - Version” option to keep track of the evolution of their DMP throughout the writing - process. When published, versioning is associated with a DOI. Published DMPs are - automatically versioned every time a newer version of the same output is uploaded in - Zenodo. -

-
-

- DMPs and Datasets -

-

- What is the DMP? -

-

- A DMP in Argos consists of vital information about the research project on behalf of - which the DMP is created and of more in depth information about the management, - handling and curation of datasets collected, produced or reused during the research - lifetime. A DMP in Argos accommodates documentation of more than one datasets. That - way datasets are provided with the flexibility to be described separately, following - different templates per type of dataset or research community concerned each time, - also possible to be copied and used in multiple DMPs. Datasets are then bundled up - in a DMP and can be shared more broadly. Special attention is given to the handling - of data that are being re-used via OpenAIRE APIs. -

-
-

- How do I find which Dataset template to use? -

-

- This depends on the reason why you are creating a DMP in the first place. If it is - for compliance matters with funders, institutions or research communities RDM - policies, then you may select the dataset template of that particular stakeholder. - If you are creating a DMP for training purposes, you may select and work on any - template from the Argos collection. -

-
-

- How do I create my own Dataset template? -

-

- Currently, it is not possible for all Argos users to create dataset templates of - their own, so they have to work on predefined templates. Additional rights for - editing Dataset templates according to tailored needs have Admin users. This is - expected to change in the near future. To learn more about Admin users, check “What - does an Admin user do?”. -

-
-

- Can I create smaller versions of a template for project proposals? -

-

- Yes, it is possible in Argos to create short versions of templates that can be used - for grant proposals, such as for Horizon Europe. - If you are interested in working with us to create this short version of any ARGOS template, - please contact us: argos@openaire.eu. -

-
-

- Can I customise an existing template (e.g. for a specific institution)? -

-

- Yes, you can. In the current version, this is possible for Admin users who have their own deployment on-premises or cloud. - Please note that this subject to change in the near future as we are working on a feature that will allow all users - to customise (remove/add/extend) specific questions on the template they are working on. -

-
-

- What is a Dataset? -

-

- A Dataset in Argos is an editor with set up questions that support the creation of - descriptions of how data are / have been handled, managed and curated throughout the - research data lifecycle. The editor holds a collection of Dataset templates each one - with different sets of predefined questions as per funders, institutions, research - communities RDM policy requirements. Researchers and students can choose the - template that corresponds to their RDM needs in order to get funding or get their - degree, respectively. A DMP in Argos may consist of one or more datasets. -

-
-

- Why do I need more than one Dataset? -

-

- You don’t necessarily need to have many Datasets in a DMP. However, you might be - producing a plethora of data during your research that are diverse in type and/ or - scope of collection/ re-use, thus presenting diverse management needs. Argos gives - you the flexibility to describe all data produced and/ or re-used in your research - separately. That way it is easy to perform the mapping of information provided in a - DMP to the respective data types or data collections they correspond to. Equally, - reuse of particular datasets in different DMPs is easier. For the latter, please - check “How do I create an identical DMP or Dataset as a copy?”. -

-
-

- It is not very clear to me when one should choose to add a dataset or to describe several "data products" in the same description. -

-

- This is something that has to be tackled conceptually, from the author of the DMP. - If those "products" have their own lifetime and rules (IPR, Access rights, etc), they should be described as different datasets. - Alternative formats should not be treated as different datasets, unless they have other differences due to the format, too. - But, for instance, if you have datasets in CSV and JSON formats and under the same terms, they could be seen as one dataset description in the DMP. -

-
-

- Can I add to my DMP information about datasets published on Zenodo? -

-

- Argos offers a search to Zenodo for prefilling the DMP you are working with dataset metadata. - This search has been developed according to the rules set by Zenodo - and therefore has the same behaviour as when you are using the search bar on the Zenodo interface. - However, we understand the need to be able to find records with their PID, - hence we introduced some changes and now support searching DOIs from the Argos interface. -

-
-

- Is it possible to describe a dataset that is not yet in a repository? -

-

- Of course! You can choose to manually describe your dataset, e.g. for a dataset you are planning to produce, - instead of pre-filling the template with available metadata from a dataset that has already been shared and preserved in a repository. -

-
-

- What are public DMPs and Datasets? -

-

- Public DMPs and Public Datasets are collections of openly available Argos outputs. - That means that DMP owners and members are making their DMP and/or Dataset outputs - available to all Argos and non-Argos users who might want to consult or re-use them - under the framework provided by the assigned DMP license. Please also check “Is all - the information I create visible by default?”. -

-
-

- Is all information I create visible by - default? -

-

- No, it is not. You can choose how your DMP is displayed in Argos from the - “Visibility” option. Choosing Public will immediately locate your DMP in the “Public - DMPs” collection and make it available to all Argos and non-Argos users. - Choosing Private will keep the DMP visible only to you and to the people invited to - edit the DMP in collaboration with you. Private DMPs are not publicly displayed to - other users. -

-
-

- What is the difference between the DMP and the dataset export? -

-

- DMP export contains all vital information for a DMP, including funding and dataset details, - while dataset export is a subset of the DMP export containing information only about a dataset described in the DMP. - Both DMP and Dataset exports are available in .pdf, .docx, .xml. - In addition, DMP export is available in the RDA .json format - to increase interoperability of ARGOS exchanged DMPs. -

-
-

- Is there a storage allowance limitation for the - DMPs and Dataset files? -

-

- No, there is no storage limit or fee for either files stored in Argos. -

-
-

- Publishing DMPs -

-

- Is it possible to publish DMPs in different repositories (so not Zenodo)? -

-

- Yes, it is possible. - But, to have different repositories attached to the system, you will need your own on-premises or cloud deployment. - We are already working on that for DSpace and Dataverse repositories. -

-
-

- Do you know that Zenodo has empty DMPs from ARGOS? -

-

- Yes, we are aware of that. - Argos has no control over the DMPs that you generate and publish and thus can not be held accountable for empty DMPs. - Please remember that, as on all other occasions where you publish content, you should do so responsinbly. - If you have any questions regarding publishing DMPs, don’t hesitate to contact us at argos@openaire.eu. -

-
-

- Once I upload a final version of a DMP to Zenodo, do I need to update this first final version from Zenodo or from Argos? -

-

- Both options are possible according to how you have deposited the DMP in the first place. - If you have deposited your DMP with a token (i.e. from the ARGOS account on Zenodo), - then you won’t have editing rights on the Zenodo record, but you will still be able to make changes - on ARGOS by starting and depositing a new version of the published DMP. - However, if you have deposited your DMP using your own account on Zenodo (i.e. login to Zenodo with your own credentials), - then you are able to also make minor changes, e.g. on the title of the DMP, directly from the Zenodo interface. -

-
-

Troubleshooting

-

- Can’t finalize a DMP -

-

- You might be experiencing this problem because there are incomplete mandatory fields - in your DMP. Please check for those fields, fill in with appropriate information and - try again. Should the problem persists, please contact argos@openaire.eu . -

-
-

- Can’t co-edit a DMP -

-

- DMPs can be shared with many colleagues in support of collaborative writing, but - DMPs should be worked by one person at a time. Argos will inform you if another - colleague has the DMP you are trying to edit open, so that your team avoids - information loss. -

-
-

- Deposit is not working -

-

- You need to have a Zenodo login to perform a deposit. Please sign up in Zenodo or - use the token option to publish your DMPs and get a DOI. -

-
-

Legal and privacy

-

- Is Argos open source? -

-

- Yes, it is. The OpenDMP software that Argos has deployed upon is open source code - available under Apache 2.0 license. You may find more information about the software - here. -

-
-

- Can I contribute to Argos development? -

-

- Of course! Please feel free to suggest new features and to actively contribute to - Argos development via pull requests in Gitea. -

-
-

- Is Argos GDPR compliant? -

-

- Argos takes all necessary steps in handling and protecting personal and sensitive - information. Please check the Argos Terms of Service and Privacy Policy. -

-
-

- Which is the Argos data policy? -

-

- Please find all information about Argos Terms of Service and Privacy, here. - Additionally, you may find Argos Cookies policy, here. -

-
-

- What is the work ownership of information - created in Argos? -

-

- Unless there are any contractual or institutional agreements stating ownership of - outputs produced in the context of a project/ collaboration, owners of Argos outputs - are DMP contributors, i.e. DMP owners and DMP members, who have been involved with - writing the DMP. -

-
-

- Which are the terms and policies of Argos? -

-

- Please find all information about Argos Terms of Service and Privacy, here. - Additionally, you may find Argos Cookies policy, here. -

- - -
+
-
+
\ No newline at end of file diff --git a/dmp-frontend/src/app/ui/faq/faq-content/faq-content.component.scss b/dmp-frontend/src/app/ui/faq/faq-content/faq-content.component.scss index 91beac1bf..f6c049328 100644 --- a/dmp-frontend/src/app/ui/faq/faq-content/faq-content.component.scss +++ b/dmp-frontend/src/app/ui/faq/faq-content/faq-content.component.scss @@ -7,6 +7,10 @@ img { width: 100%; } -.faq-component { - //margin-top: 80px; +.iframe { + width: 100%; + height: 65vh; + margin: 0px; + border: none; + max-width: 100%; } diff --git a/dmp-frontend/src/app/ui/faq/faq-content/faq-content.component.ts b/dmp-frontend/src/app/ui/faq/faq-content/faq-content.component.ts index 179cbc410..2fae67a4d 100644 --- a/dmp-frontend/src/app/ui/faq/faq-content/faq-content.component.ts +++ b/dmp-frontend/src/app/ui/faq/faq-content/faq-content.component.ts @@ -1,17 +1,38 @@ import { Component, OnInit, Input } from '@angular/core'; +import { SafeResourceUrl, DomSanitizer } from '@angular/platform-browser'; +import { FaqService } from '@app/core/services/faq/faq.service'; +import { LanguageService } from '@app/core/services/language/language.service'; +import { MatomoService } from '@app/core/services/matomo/matomo-service'; +import { BaseComponent } from '@common/base/base.component'; +import { takeUntil } from 'rxjs/operators'; @Component({ selector: 'app-faq-content', templateUrl: './faq-content.component.html', styleUrls: ['./faq-content.component.scss'] }) -export class FaqContentComponent implements OnInit { +export class FaqContentComponent extends BaseComponent implements OnInit { @Input() isDialog: boolean; - constructor() { } + faqHTMLUrl: SafeResourceUrl; + sanitizedGuideUrl: any; + + constructor( + private faqService: FaqService, + private sanitizer: DomSanitizer, + private languageService: LanguageService, + private matomoService: MatomoService + ) { super(); } ngOnInit() { + this.matomoService.trackPageView('Terms of Service'); + this.faqService.getFaq(this.languageService.getCurrentLanguage()) + .pipe(takeUntil(this._destroyed)) + .subscribe(response => { + const blob = new Blob([response.body], { type: 'text/html' }); + this.faqHTMLUrl = this.sanitizer.bypassSecurityTrustResourceUrl((window.URL ? URL : webkitURL).createObjectURL(blob)); + }); } } diff --git a/dmp-frontend/src/app/ui/glossary/glossary-content/glossary-content.component.html b/dmp-frontend/src/app/ui/glossary/glossary-content/glossary-content.component.html index 953bb8298..0d965191d 100644 --- a/dmp-frontend/src/app/ui/glossary/glossary-content/glossary-content.component.html +++ b/dmp-frontend/src/app/ui/glossary/glossary-content/glossary-content.component.html @@ -1,24 +1,5 @@ -
-
-
-

{{ 'GLOSSARY.TITLE' | translate}}

-
-
+
-
-

DMP

-

A DMP - short for Data Management Plan - is a document describing the processes that the data have undergone and the tools used for their handling and storage during a research lifecycle. Most importantly, DMPs secure provenance and enable re-use of data by appointing data managers and by including information on how data can be re-used by others in the future. Therefore, a DMP is a living document which is modified according to the data developments of a project before it’s completed and handed over at the end of the project. - Public funders increasingly contain DMPs in their grant proposals or policy funding requirements. A good paradigm is the European Commission demands for the production and delivery of DMPs for projects funded under the Horizon 2020 Funding Programme. On that note, and to encourage good data management practices uptake, many European institutions include DMPs in post-graduate researchers policies and offer relevant support to staff and students. -

- -

DMP template

-

DMP template contains general but vital information about the name and the duration of the project that the DMP corresponds to, the contributing organisations and individuals as well as the datasets that are under the Dataset Description section. It also offers the possibility of describing datasets other than primary data generated, under “External References” section. A DMP template can have many Dataset Descriptions. -

- -

Dataset Description

-

Dataset Description documents the management processes of datasets following funder’s or institution’s requirements. A dataset description is essentially a questionnaire template with underlying added value services for interoperability and machine readability of information which is developed based on the given requirements. Management requirements differ from funder to funder and from institution to institution, hence the growing collection of Dataset Descriptions to select from. - Moreover, a Dataset Description links to the documentation of one dataset, hence a DMP template may contain more than one dataset descriptions on the occasion when multiple datasets were used during the project. When documentation of some of the project’s datasets falls under additional requirements (e.g. projects receiving multiple grants from different sources), there is the possibility of describing datasets with more than one Dataset Description template. -

-
+
-
+
\ No newline at end of file diff --git a/dmp-frontend/src/app/ui/glossary/glossary-content/glossary-content.component.scss b/dmp-frontend/src/app/ui/glossary/glossary-content/glossary-content.component.scss index 2d066c10e..30a2f8b8b 100644 --- a/dmp-frontend/src/app/ui/glossary/glossary-content/glossary-content.component.scss +++ b/dmp-frontend/src/app/ui/glossary/glossary-content/glossary-content.component.scss @@ -8,6 +8,9 @@ img { width: 100%; } -.glossary-component { - //margin-top: 80px; +.iframe { + width: 100%; + height: calc(100vh - 80px); + margin: 0px; + border: none; } diff --git a/dmp-frontend/src/app/ui/glossary/glossary-content/glossary-content.component.ts b/dmp-frontend/src/app/ui/glossary/glossary-content/glossary-content.component.ts index 83696d3e5..a5cb277b8 100644 --- a/dmp-frontend/src/app/ui/glossary/glossary-content/glossary-content.component.ts +++ b/dmp-frontend/src/app/ui/glossary/glossary-content/glossary-content.component.ts @@ -1,23 +1,38 @@ -import { HttpClient } from '@angular/common/http'; import { Component, OnInit, Input } from '@angular/core'; +import { DomSanitizer, SafeResourceUrl } from '@angular/platform-browser'; +import { GlossaryService } from '@app/core/services/glossary/glossary.service'; +import { LanguageService } from '@app/core/services/language/language.service'; import { MatomoService } from '@app/core/services/matomo/matomo-service'; +import { BaseComponent } from '@common/base/base.component'; +import { takeUntil } from 'rxjs/operators'; @Component({ selector: 'app-glossary-content', templateUrl: './glossary-content.component.html', styleUrls: ['./glossary-content.component.scss'] }) -export class GlossaryContentComponent implements OnInit { +export class GlossaryContentComponent extends BaseComponent implements OnInit { @Input() isDialog: boolean; + glossaryHTMLUrl: SafeResourceUrl; + sanitizedGuideUrl: any; + constructor( - private httpClient: HttpClient, + private glossaryService: GlossaryService, + private sanitizer: DomSanitizer, + private languageService: LanguageService, private matomoService: MatomoService - ) { } + ) { super(); } ngOnInit() { this.matomoService.trackPageView('Glossary'); + this.glossaryService.getGlossary(this.languageService.getCurrentLanguage()) + .pipe(takeUntil(this._destroyed)) + .subscribe(response => { + const blob = new Blob([response.body], { type: 'text/html' }); + this.glossaryHTMLUrl = this.sanitizer.bypassSecurityTrustResourceUrl((window.URL ? URL : webkitURL).createObjectURL(blob)); + }); } } diff --git a/dmp-frontend/src/app/ui/navbar/navbar.component.ts b/dmp-frontend/src/app/ui/navbar/navbar.component.ts index dc208f73a..c701ab0ce 100644 --- a/dmp-frontend/src/app/ui/navbar/navbar.component.ts +++ b/dmp-frontend/src/app/ui/navbar/navbar.component.ts @@ -244,7 +244,8 @@ export class NavbarComponent extends BaseComponent implements OnInit { disableClose: true, data: { isDialog: true - } + }, + width: '100%' }); } } diff --git a/dmp-frontend/src/app/ui/sidebar/sidebar-footer/sidebar-footer.component.ts b/dmp-frontend/src/app/ui/sidebar/sidebar-footer/sidebar-footer.component.ts index 387890390..20cefa854 100644 --- a/dmp-frontend/src/app/ui/sidebar/sidebar-footer/sidebar-footer.component.ts +++ b/dmp-frontend/src/app/ui/sidebar/sidebar-footer/sidebar-footer.component.ts @@ -98,7 +98,8 @@ export class SidebarFooterComponent extends BaseComponent implements OnInit { disableClose: true, data: { isDialog: true - } + }, + width: '100%' }); } } diff --git a/dmp-frontend/src/app/ui/sidebar/sidebar-footer/terms/terms.component.html b/dmp-frontend/src/app/ui/sidebar/sidebar-footer/terms/terms.component.html index 63ae0b084..45cef287f 100644 --- a/dmp-frontend/src/app/ui/sidebar/sidebar-footer/terms/terms.component.html +++ b/dmp-frontend/src/app/ui/sidebar/sidebar-footer/terms/terms.component.html @@ -1,34 +1,5 @@ -
+
-
-

{{ 'TERMS-OF-SERVICE.TITLE' | translate}}

-
+
-
-
-

The OpenDMP service was developed to provide a more flexible, collaborative environment with machine actionable solutions in writing, sharing and publishing Data Management Plans (DMPs). It is a product of cooperation between OpenAIRE AMKE and EUDAT CDI and is offered both as a software “OpenDMP '' and as an online service under the name “ARGOS”.

-

-
    -
  1. OpenDMP software is offered under the Free Open Source Software license  Apache 2.0, for further development and use by institutions and interested parties.
    2. -
  2. ARGOS service is offered by OpenAIRE as part of its mission to support Open Science in the European Research Area, focusing on information linking and contextualisation that enriches its Research Graph. Use of ARGOS denotes agreement with the following terms: -
      -
    1. ARGOS is a software interface and a database with no storage capacity to store or preserve research data. The DMPs created are hosted in the OpenAIRE production environment for the sole purpose of exposing the DMP records once finalised (“published”). If assigned a DOI, the DMP records are linked to and preserved in Zenodo, the OpenAIRE’s repository service. The ARGOS service is made available for use free-of-charge for research, educational and informational purposes.
      2. -
    2. Login to ARGOS is possible through a variety of external providers, among which Google, Facebook, Twitter, B2Access and OpenAIRE Login, that share information of their user profiles with ARGOS, according to the rights that have been granted to the given provider by the user. External email addresses that are used in invitations for collaborations are held in ARGOS database that stores information about only the name, surname and email address of the DMP creator and collaborator.  Personal data is collected via the login option and via email invitations sent to external DMP contributors. This personal information as well as the activity of ARGOS users is used only for deriving usage metrics and assessing the service quality. They are stored in ARGOS database for as long as the account is active and they are accessible only from people in the team in charge of quality and risk assessment. They will not be used for other purposes other than the ones stated in this document and they can be deleted at any time should the user claim a relevant request. The aforementioned processes are also facilitated by the use of cookies (see below the “Cookie policy”).
      3. -
    3. Data concerning DMP information will be used by OpenAIRE for research and development purposes, such as identifying DMP models, and for ensuring compliance with policy requirements and monitoring of DMPs uptake linked to OpenAIRE’s Monitoring Dashboards and the Open Science Observatory.
      4. -
    4. The DMP Manager, i.e. the person who creates and manages a DMP, and/ or the contributor, i.e. the person who is invited to collaborate on a DMP, shall ensure that content is accurate and presented in a way that adheres to these Terms of Service and applicable laws, including, but not limited to, privacy, data protection and intellectual property rights.
      5. -
    5. ARGOS service is provided by OpenAIRE “as is”. Although OpenAIRE and its partners take measures for the availability, dependability, and accuracy of the service, access to ARGOS, utilisation of its features and preservation of the data deposited or produced by the service are not guaranteed. OpenAIRE cannot be held responsible for any data loss regarding DMPs, ethical or financial damage or any other direct or indirect impact that any failure of ARGOS service may have on its users.  
      6. -
    6. ARGOS users are exclusively responsible for their use of content, and shall hold OpenAIRE free and harmless in connection with their download and/or use.
      7. -
    7. OpenAIRE may not be held responsible for the content provided or statements made in Data Management Plans created and managed by its users.
      8. -
    8. All content is provided “as-is”. Users of content (“Users”) shall respect applicable license conditions. Download and use of content from ARGOS does not transfer any intellectual property rights in the content to the User.
      9. -
    9. In the case any content is reported as violating third party rights or other legal provisions, ARGOS reserves the right to remove the content from the service until the dispute is legally settled. Any such incidents should be reported at noticeandtakedown@openaire.eu 
      10. -
    10. ARGOS users are held responsible for the data and information they provide in the service. Users may not add information, data or any other type of artifact that may be malicious, intentionally erroneous and potentially harmful for other ARGOS users, IPR owners and/or the general public.
      11. -
    11. In case a user of ARGOS identifies a potential infringement of copyright, harmful or malicious operation, function, code, information or data, shall inform OpenAIRE providing sufficient evidence for the identification of the case and the information and/or data challenged.
      12. -
    12. OpenAIRE reserves the right, without notice, at its sole discretion and without liability, (i) to alter or delete inappropriate content, and (ii) to restrict or remove User access where it considers that use of ARGOS interferes with its operations or violates these Terms of Service or applicable laws.
      13. -
    13. These Terms of Service are subject to change by OpenAIRE at any time and without notice, other than through posting the updated Terms of Service on the OpenAIRE website and indicating the version and date of last update.
      14. -
    -
    3. -
-

For any questions or comments you may have about the current Terms of Service, please contact us: argos@openaire.eu 

-
-
-
+
\ No newline at end of file diff --git a/dmp-frontend/src/app/ui/sidebar/sidebar-footer/terms/terms.component.scss b/dmp-frontend/src/app/ui/sidebar/sidebar-footer/terms/terms.component.scss index ae3eb886e..30a2f8b8b 100644 --- a/dmp-frontend/src/app/ui/sidebar/sidebar-footer/terms/terms.component.scss +++ b/dmp-frontend/src/app/ui/sidebar/sidebar-footer/terms/terms.component.scss @@ -8,6 +8,9 @@ img { width: 100%; } -.terms-component { - //margin-top: 80px; +.iframe { + width: 100%; + height: calc(100vh - 80px); + margin: 0px; + border: none; } diff --git a/dmp-frontend/src/app/ui/sidebar/sidebar-footer/terms/terms.component.ts b/dmp-frontend/src/app/ui/sidebar/sidebar-footer/terms/terms.component.ts index 6e8cdb08a..4a3bddc6a 100644 --- a/dmp-frontend/src/app/ui/sidebar/sidebar-footer/terms/terms.component.ts +++ b/dmp-frontend/src/app/ui/sidebar/sidebar-footer/terms/terms.component.ts @@ -1,21 +1,36 @@ -import { HttpClient } from '@angular/common/http'; import { Component, OnInit } from '@angular/core'; +import { SafeResourceUrl, DomSanitizer } from '@angular/platform-browser'; +import { LanguageService } from '@app/core/services/language/language.service'; import { MatomoService } from '@app/core/services/matomo/matomo-service'; +import { TermsOfServiceService } from '@app/core/services/terms-of-service/terms-of-service.service'; +import { BaseComponent } from '@common/base/base.component'; +import { takeUntil } from 'rxjs/operators'; @Component({ selector: 'app-terms', templateUrl: './terms.component.html', styleUrls: ['./terms.component.scss'] }) -export class TermsComponent implements OnInit { +export class TermsComponent extends BaseComponent implements OnInit { - constructor( - private httpClient: HttpClient, - private matomoService: MatomoService - ) { } + termsHTMLUrl: SafeResourceUrl; + sanitizedGuideUrl: any; - ngOnInit() { - this.matomoService.trackPageView('Terms of Service'); - } + constructor( + private termsService: TermsOfServiceService, + private sanitizer: DomSanitizer, + private languageService: LanguageService, + private matomoService: MatomoService + ) { super(); } + + ngOnInit() { + this.matomoService.trackPageView('Terms of Service'); + this.termsService.getTermsOfService(this.languageService.getCurrentLanguage()) + .pipe(takeUntil(this._destroyed)) + .subscribe(response => { + const blob = new Blob([response.body], { type: 'text/html' }); + this.termsHTMLUrl = this.sanitizer.bypassSecurityTrustResourceUrl((window.URL ? URL : webkitURL).createObjectURL(blob)); + }); + } }