Date: Thu, 28 Mar 2024 20:03:31 +0100 (CET) Message-ID: <1896623183.3160.1711652611585@confluencesrv1.awi.de> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3159_636484605.1711652611585" ------=_Part_3159_636484605.1711652611585 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Items can be created by: (1) manuall= y editing EPIC's submission form: this option is ideal for items&= nbsp;which have not been published yet (e.g. an article in press) or do not= have a DOI (e.g. talks, posters, field reports). In case you have en= tered an article which has not been published yet, you should keep it in yo= ur "User Workarea" until the article has a DOI and thus ready for rev= ision by editors (use the "Save for later" option instead of "Deposit"; see= "Understanding the Workflow" below). (2) importing from resolvabl= e DOIs : this option is ideal for articles for which an official = DOI is available as it automatically imports all the exsiting bibliographic= metadata as available direclty from CrossRef. In this case users wil= l only have to additionally enter the AWI-specific metadata (e.g. user= name/email for AWI authors, research platforms, grant ID, etc). (3) importing from BibTex: this option is ideal for items whi= ch are already in a BibTex formatted reference document. |
Items created in EPIC are automatically store= d in the "User Workarea" when the option "Save for later" is selected. = ; In the context of Helmholtz revision process, it is particula= r important that the following metadata fields for all articles, theses, bo= oks and chapters in books, are correclty entered: (1) official DOI= for articles: the DOI allow us to automatically tag your item to= a PANGAEA dataset, if applied. The official DOIs are also use= d to find out the impact of your articles in various social media along wit= h citation information as provided by the alternative metrics "Altmet= rics" badge in the landing pages. (2) authors: all= AWI authors must be assigned AWI email, username and ORCID (if available).= Use the auto-completion functionality to avoid typos. Only ite= ms for which the AWI username is available and in "Live archive" will be fo= und in AWI personal homepages. (3) divisions/work packages= u>: the organizational units of all AWI authors must be entered accor= dingly. Items which do not allign with Helmholtz research must be tag= ged with "Helmholt Inependent research" option. (4) platform= s/campaigns: research platforms operated by AWI (and respective c= ampaigns) used to acquire the data used in publications, presentations, the= sis and field reports must be tagged accordingly. This enables the as= signment of EPIC items to expeditions/campaigns in the framework of the&nbs= p; DATA portal (see "Re-using the metadata" below) |
Users are only allowed to edit items in their= own "User Workspace". Once the metadata is complete and the PDF has = been uploaded, users may click on the "Deposit" option. This wi= ll automatically move the item you created from workflow status = "User Workarea" to "Under review" and an email notification is then sent t= o editors. Items will then be reviewed by editors for metadata correc= tness and placed in "Live archive" as soon as possible. Once in= live archive, items are then automatically displayed in AWI personal homep= ages and an individual persistent unique identifier is created (type handle= ; example: hdl:10013/epic.8a437225-08fc-4e53-99e3-cd67dbfe1424). Once = in "Live archive", items of type article, book, chapter in book and theses,= relevant for the Helmholtz metrics, will be bibliographically revised by l= ibrarians. Please note that items in "Live archive" can only be edite= d by the respective divison/section editors (see internal list) or librarians (request to pub-bib at awi.de= ). Only items in "Live Archive" are displayed in AWI personal homepag= es. Items in "Live archive" have a handle and thus should not be dele= tetd. However, in exceptional cases in which an item should no longer= be shown, it can be hidden from the public by placing it under status "Ret= ired". Email to epic at&n= bsp;awi.de or pub-bib at a= wi. de should be sent in case you need to hide an item. |
Following the Guidelines for Safeguarding Good Scienti= fic Practices, you are advised to archive all data related to pub= lications in a certified and cite-enabled repository. For AWI data, in part= icular for the data acquired using AWI research platforms, the recommended = information system is PANGAEA which is a CoreTrustSeal c= ertified repository . We strongly advise you to submit your data usin= g https://pangaea.de/submit/ as soon as possible so that you= can examplary insert the dataset DOI in the article's reference list = in time. Data archival in PANGAEA follows the FAIR Guiding Principles for scientific data management an= d stewardship. The exte= nsive curational and editorial services often require processing time= s ranging from several days to several weeks, depending on the data volume = and complexity. To prevent data to be publicly available before = the related manuscript is published, PANGAEA offers the "in review" dataset= status which supports, upon demand, the provision of an access= token for the data peer-revision process. PANGAEA additonally = provides password protection for datasets under moratorium if wished (for o= ngoing projects, as example). As depicted in the = example , datasets archived in PANGAEA will be automatically shown using a = PANGAEA icon in EPIC landing/abstract pages for all articles in which an of= ficial DOI has been provided as "Supplement" for a dataset archived in PANG= AEA. |
EPIC enables tag= ging to an EU grant number (FB7 and H2020). Make sure you exactly fol= low the syntax rules as displayed in the help text. By tagging your items t= o the corresponding EU grant, you are susporting openAIRE to create statist= ics of various funding agencies and projects. The grant number is automatically displayed in the individual landing= page of articles, if provided. Example: |
EPIC supports the export of the metadata asso= ciated with an individual item as well as the listing of items resulting in= a given search criteria (e.g. all ISI articles from A. Boetius= ). Items can be exported in various formats individually or by making= a bulk export using the advanced search interface. The metadat= a in EPIC is also being used in the framework of the AWI DATA portal. = In this case EPIC's metadata is being harvested on a daily basis and displ= ayed in the context of expedition/campaigns and in the facetted search.&nbs= p; Examples are:
EPIC can also be used to archive key resources related to dev= ices and sensors described in https://sensor.awi.de (e.g. da= ta processing reports, calibration documents, factsheets; use type "M= iscellaneous"). |