There is no such content in this group
Posts
[CodeMeta] We need you! provide feedback for CodeMeta v3.0 before June 15
Dear all, Apologies for cross-posting. I'm writing to you today to get your feedback on a software metadata matter on the CodeMeta repository . If you haven't heard about the CodeMeta project and vocabulary, CodeMeta is a subset of schema.org classes SoftwareSourceCode and SoftwareApplications, providing additional properties for research software. CodeMeta vocabulary is in a json-ld format and developers can use a codemeta.json file to insert metadata in their repository. This metadata0 | Add new comment
Open Position: Research Associate in the field of Research Data Infrastructures at GESIS, Cologne
* Apologies for any cross-postings * GESIS - Leibniz Institute for the Social Sciences is an internationally active research institute, funded by federal and state governments and member of the Leibniz Association. For the next possible date, our Department Knowledge Technologies for the Social Sciences (WTS), Team FAIR Data and Human Information Interaction located in Cologne, is looking for a Research Associate in the field of Research Data Infrastructures (Salary group 13 TV-L, working time 75%, limited to September 2025)0 | Add new comment
Open position: Research Associate in the area of Research Data Management / FAIR Data at GESIS, Cologne
Dear RDA colleagues, we are looking for a Research Associate in the area of Research Data Management / FAIR Data to join KonsortSWD within the National Research Data Infrastructure (NFDI) in Germany. Find more information and how to apply (until June 1) under https://www.hidden-professionals.de/HPv3.Jobs/gesis/stellenangebot/18386.... Please feel free to forward the job ad to anyone interested.0 | Add new comment
Update: FAIR4RS RDA virtual plenary 17
The FAIR for Research Software (FAIR4RS) Working Group presented the structure of the first draft of the FAIR4RS principles at the Research Data Alliance (RDA) Plenary 17 on 21 April 2021:0 | Add new comment
[FAIR4RS][software-source-code-ig] VP17 software sessions
Dear all, We are having two interesting software sessions at VP17, tomorrow (Wednesday 21th) and Thursday 22nd. The FAIR4RS WG session is on Wednesday 21th at 12:45 - 14:15 UTC| *Breakout 4* : FAIR for Research Software (FAIR4RS) : Early Outcomes of the FAIR 4 Research Software: Definitions, Principles and Road Ahead The SSC IG session is on Thursday 22nd at 10:15 - 11:45 UTC| *Breakout 7:* Software Source Code : Scholarly Infrastructures and Quality Requirements of Software Source Code0 | Add new comment
RDA Plenary session FAIR4RS April 21st, 2020
Dear all, This is a gentle reminder of our RDA Plenary session "Early outcomes of the FAIR4RS WG: definitions principles and the road ahead". More information about the session see our events. Direct link to Juno for those registered (Click attending and add to your calendar).0 | Add new comment
BibLaTeX support for software (Was: Re: [rda-datacitation-wg] Data Citation - Participate in shaping BibLaTeX)
[cross-posting this message to other groups that may find this relevant, with some context for them, apologies to the Data Citation WG for repetitions] Dear all, there is an interesting thread in the Data Citation WG about extending the @dataset entry in biblatex, which is just treated as @misc in biblatex today, and falls quite short of fitting the bill [1]. A year ago, we had a similar situation for the @software entry type, which is also just an alias for the @misc entry. Today, the situation has changed a lot,0 | Add new comment
In the software citation rabbit hole (Was: Re: [fair4rs] Newly published - TU Delft Research Software Policy and...)
Dear Paula, dear all, software citation has been a hot topic for a few years now, and there are quite a few different takes on it in the growing literature that is becoming available. When one looks closely at it, though, it turns out that this issue is remarkably complex, and despite significant efforts and good will spent on it, we are still far from having resolved it satisfactorily. Let me try to summarise some of the key points I see. At first sight, a "*software citation*" seems a simple matter: one just0 | Add new comment