Reusability: Software Publication
This is a modal window.
Das Video konnte nicht geladen werden, da entweder ein Server- oder Netzwerkfehler auftrat oder das Format nicht unterstützt wird.
Formale Metadaten
| Titel |
| |
| Serientitel | ||
| Teil | 8 | |
| Anzahl der Teile | 9 | |
| Autor | ||
| Lizenz | CC-Namensnennung 3.0 Deutschland: Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen. | |
| Identifikatoren | 10.5446/37830 (DOI) | |
| Herausgeber | ||
| Erscheinungsjahr | ||
| Sprache |
Inhaltliche Metadaten
| Fachgebiet | |
| Genre |
6
7
00:00
SoftwarePhysikalisches SystemDifferentePerfekte GruppeXMLUMLVorlesung/Konferenz
00:55
SoftwareDistributionenraumSoftwareProdukt <Mathematik>MereologieVererbungshierarchieComputeranimation
01:19
SoftwareProdukt <Mathematik>MathematikVorlesung/KonferenzBesprechung/Interview
01:52
SoftwareDistributionenraumQuellcodeProzess <Informatik>VerschlingungOffene MengeGebäude <Mathematik>p-BlockMetrisches SystemSoftware EngineeringProgrammverifikationPhysikalisches SystemWiderspruchsfreiheitSpeicherabzugDesintegration <Mathematik>Kontextbezogenes SystemSoftwarePhysikalisches SystemWiderspruchsfreiheitProdukt <Mathematik>Offene MengeProgrammverifikationMathematikGebäude <Mathematik>Differentep-BlockAutorisierungSchlüsselverwaltungOpen SourceMereologieVorzeichen <Mathematik>Kartesische KoordinatenBitQuellcodeVerschlingungComputeranimation
03:15
HauptidealPeer-to-Peer-NetzQuellcodeSoftwareDigitalsignalFundamentalsatz der AlgebraMathematikDatensatzMereologieFokalpunktHauptidealSoftwareDokumentenserverComputeranimation
03:40
QuellcodeSoftwareDokumentenserverDigitalsignalZenonische ParadoxienKollaboration <Informatik>ProgrammierumgebungCodeDigital Rights ManagementProzess <Informatik>HauptidealErwartungswertEreignishorizontDatenparallelitätOpen SourceGarbentheorieLokales MinimumNeuroinformatikMathematikStatistikBildverarbeitungTransaktionEnergiedichteSimulationGeradeNumerisches VerfahrenMaschinelles LernenMultiplikationMaßstabVorgehensmodellAlgebraisches ModellSystemprogrammierungProgrammierungAlgorithmusPeer-to-Peer-NetzDatenverarbeitungssystemAggregatzustandNatürliche SpracheLemma <Logik>DokumentenserverMailing-ListeVererbungshierarchieBildverarbeitungSoftwareNeuroinformatikSuite <Programmpaket>RelativitätstheorieBildgebendes VerfahrenComputerspielPhysikalismusComputeranimationXML
04:20
Algebraisches ModellSoftwareStatistikSystemprogrammierungMathematikProgrammierungAlgorithmusPeer-to-Peer-NetzDatenverarbeitungssystemAggregatzustandComputerspielEreignishorizontDatenparallelitätOffene MengeOpen SourceGarbentheorieHauptidealDigitalsignalNormierter RaumSolitärspielDokumentenserverQuellcodeZenonische ParadoxienKollaboration <Informatik>ProgrammierumgebungCodeDigital Rights ManagementProzess <Informatik>SoftwareDokumentenserverQuellcodeDigital Object IdentifierCodeProjektive EbeneDigital Rights ManagementSoftwareentwicklerUmwandlungsenthalpieQuick-SortCMM <Software Engineering>ComputeranimationXML
05:06
DokumentenserverQuellcodeSoftwareDigitalsignalZenonische ParadoxienKollaboration <Informatik>ProgrammierumgebungCodeDigital Rights ManagementProzess <Informatik>SoftwareFreewareOpen SourceProgrammierumgebungProjektive EbeneElektronische BibliothekKonfiguration <Informatik>CodeDokumentenserverPhysikalisches SystemComputeranimationXML
05:37
Zenonische ParadoxienSoftwareDrucksondierungTypentheorieZeitabhängigkeitSampler <Musikinstrument>Registrierung <Bildverarbeitung>SoftwareWort <Informatik>TypentheorieMailing-ListeRechter WinkelMultiplikationsoperatorRechenschieberXMLComputeranimation
06:18
SoftwareZenonische ParadoxienGammafunktionVariationsprinzipTypentheorieDissipationFatou-MengeRegistrierung <Bildverarbeitung>Elektronische BibliothekSoftwareRechenzentrumMailing-ListeWort <Informatik>TypentheorieOrdnung <Mathematik>WiderspruchsfreiheitComputeranimation
06:57
SoftwareZenonische ParadoxienSoftwareResultanteWiderspruchsfreiheitComputeranimation
07:20
SoftwareTypentheorieMereologieXMLFlussdiagrammVorlesung/Konferenz
07:45
Lesen <Datenverarbeitung>Manufacturing Execution SystemVersionsverwaltungROM <Informatik>SynchronisierungSoftwareInhalt <Mathematik>FlächeninhaltVersionsverwaltungResultanteInformationMereologieMailing-ListeXMLFlussdiagrammComputeranimation
08:48
SoftwareTouchscreenDigital Object IdentifierKontextbezogenes SystemKraftInformationDatenverarbeitungssystemMetrisches SystemÄhnlichkeitsgeometrieDesktop-PublishingAuswahlaxiomSoftwareWeb SiteOffice-PaketXML
09:17
Digital Object IdentifierTouchscreenSoftwareKontextbezogenes SystemKraftÄhnlichkeitsgeometrieMetrisches SystemDatenverarbeitungssystemInformationTopologieRegistrierung <Bildverarbeitung>Regulator <Mathematik>Zenonische ParadoxienZeitabhängigkeitFatou-MengeVersionsverwaltungTypentheorieTreiber <Programm>ResultanteWeb SiteMailing-ListeSoftwareComputeranimationXML
09:54
DatenverarbeitungssystemTopologieSoftwareTouchscreenDigital Object IdentifierKontextbezogenes SystemKraftZeitabhängigkeitVorzeichen <Mathematik>Zenonische ParadoxienTypentheorieLeistungsbewertungSLAM-VerfahrenSoftwareFlächeninhaltXMLProgramm/QuellcodeFlussdiagramm
10:21
SoftwareTouchscreenDigital Object IdentifierKontextbezogenes SystemKraftDatenverarbeitungssystemInformationÄhnlichkeitsgeometrieMetrisches SystemGruppenoperationSoftwareForcingTouchscreenAdditionInformationXMLComputeranimation
10:49
SoftwareWiderspruchsfreiheitBefehl <Informatik>Notepad-ComputerInformationForcingBefehl <Informatik>MereologieGruppenoperationMathematikSchnittmengeSoftwareComputeranimation
11:11
SoftwareProdukt <Mathematik>Basis <Mathematik>MetadatenSoftwareSystemaufrufMailing-ListeMathematische LogikCASE <Informatik>Produkt <Mathematik>Basis <Mathematik>Funktion <Mathematik>XML
11:40
SoftwareSystemidentifikationEindeutigkeitVirtuelle MaschineMechanismus-Design-TheoriePublic-domain-SoftwareMetadatenVersionsverwaltungZahlenbereichSystemplattformSoftwareAttributierte GrammatikMultifunktionExpertensystemIdentifizierbarkeitVersionsverwaltungEindeutigkeitSystemidentifikationPublic-domain-SoftwareMetadatenUmwandlungsenthalpieVorlesung/KonferenzBesprechung/InterviewXML
12:46
MarketinginformationssystemVerzeichnisdienstCodeElektronische PublikationDateiformatInformationSoftwareVirtuelle MaschineFormale GrammatikSoftwareVersionsverwaltungVerschlingungElektronische PublikationWurzel <Mathematik>VerzeichnisdienstCodeVorlesung/KonferenzBesprechung/InterviewXML
13:15
Vorzeichen <Mathematik>Hill-DifferentialgleichungLogarithmusMRP <CAE>Interface <Schaltung>MenütechnikDigital Object IdentifierPhysikalisches SystemPlastikkarteSummierbarkeitElektronische PublikationInformationBitURLZeichenketteSoftwareMinimumWeb SiteComputeranimation
13:53
BenutzerfreundlichkeitSoftwareWurzel <Mathematik>VerzeichnisdienstCodeElektronische PublikationDateiformatVirtuelle MaschineSerielle SchnittstelleSpieltheorieViereckQuarkmodellForcingXML
14:15
Vorzeichen <Mathematik>MaximalfolgeElektronische PublikationDifferenteProjektive EbeneVorlesung/KonferenzXMLComputeranimation
14:39
Wurzel <Mathematik>VerzeichnisdienstCodeElektronische PublikationDateiformatVirtuelle MaschineSerielle SchnittstelleSpieltheorieSinusfunktionElektronische PublikationOffene MengePerfekte GruppeMailing-ListeXMLComputeranimation
15:12
Vorzeichen <Mathematik>MaximalfolgePROMCodeGeradeMarketinginformationssystemNormierter RaumMailing-ListeElektronische PublikationTopologieComputeranimationXML
15:37
Wurzel <Mathematik>VerzeichnisdienstCodeElektronische PublikationDateiformatInformationSoftwareAnalog-Digital-UmsetzerDateiformatBitInformationElektronische PublikationAuszeichnungsspracheVirtuelle MaschineComputeranimation
16:03
SoftwareVerzeichnisdienstWurzel <Mathematik>CodeDateiformatElektronische PublikationSerielle SchnittstelleVirtuelle MaschineSpieltheorieComputermusikRechenwerkChatten <Kommunikation>Formale SpracheUmwandlungsenthalpieUmsetzung <Informatik>Elektronische PublikationAutorisierungMessage-PassingTypentheorieVersionsverwaltungDateiformatSchlüsselverwaltungWort <Informatik>XMLComputeranimation
16:51
SoftwareCodeWurzel <Mathematik>VerzeichnisdienstDateiformatElektronische PublikationSerielle SchnittstelleVirtuelle MaschineMeta-TagAnalog-Digital-UmsetzerDigital Object IdentifierVerschlingungTVD-VerfahrenInklusion <Mathematik>TermKontextbezogenes SystemInformationElektronische PublikationCodeMeterBitMultiplikationsoperatorXML
17:12
Analog-Digital-UmsetzerCodeMeta-TagDigital Object IdentifierVerschlingungTVD-VerfahrenKontextbezogenes SystemVirtuelle MaschineInformationInklusion <Mathematik>Spitze <Mathematik>Formale SemantikElektronische PublikationInformationVirtuelle MaschineKontextbezogenes SystemCodeMeta-TagCASE <Informatik>SoftwarewartungSoftwareentwicklerKontinuierliche IntegrationMailing-ListeOffice-PaketDifferentialAdressraumBitrateMetadatenE-MailAutorisierungXMLComputeranimation
18:05
Meta-TagCodeInformationVirtuelle MaschineDigital Object IdentifierKondensation <Mathematik>VerschlingungTVD-VerfahrenKontextbezogenes SystemTermInklusion <Mathematik>Analog-Digital-UmsetzerRechenwerkWeb SiteGarbentheorieElektronische PublikationStapeldateiXMLComputeranimation
18:42
Meta-TagCodeVirtuelle MaschineInformationGerichteter GraphDigital Object IdentifierTermMathematikPhysikalisches SystemMereologieElektronische PublikationEntscheidungstheorieCodeMeta-TagXML
19:25
Dämon <Informatik>TopologieVersionsverwaltungCAN-BusFormale SpracheInformationGarbentheorieMinimumWeb SiteVerschlingungService providerPhysikalisches SystemElektronische BibliothekDifferenteComputeranimation
19:53
SoftwareSoftwareentwicklerPhysikalisches SystemLuenberger-BeobachterElektronische BibliothekMetadatenInformationSystemplattformCodeDokumentenserverXML
20:38
Elektronische PublikationBitMereologieInformationVorlesung/Konferenz
21:12
SoftwareGoogolCAN-BusRippen <Informatik>MetadatenSystemplattformXMLComputeranimation
21:45
CAN-BusGoogolBildschirmfensterRippen <Informatik>GasströmungBildschirmmaskeOrdnungsreduktionZyklische RedundanzprüfungBitrateAdressraumElektronische PublikationDeskriptive StatistikInformationSystemaufrufDateiformatXMLComputeranimation
22:09
CAN-BusGoogolRechenwerkMenütechnikElektronische PublikationDeskriptive StatistikDifferenteInformationWeb SitePunktComputeranimationXML
22:32
FlächeninhaltAdressraumStrom <Mathematik>OrdnungsreduktionZyklische RedundanzprüfungGasströmungPi <Zahl>SoftwareGoogolRechenwerkPunktTopologieInformationGoogolComputeranimationXML
22:58
StatistikGasströmungExplosion <Stochastik>VersionsverwaltungDatenflussIndexberechnungHoaxSoftwareSpezialrechnerSoftwareMailing-ListeBitMetadatenComputeranimation
23:22
InformationDigital Object IdentifierMetadatenZenonische ParadoxienBenutzeroberflächeSoftwareData MiningKontrollstrukturSurjektivitätCodeMeta-TagKonfiguration <Informatik>Mailing-ListeMetadatenElektronische PublikationTypentheorieÄußere Algebra eines ModulsSoftwareInformationIdentifizierbarkeitStatistische HypotheseXMLProgramm/Quellcode
24:00
MetadatenSoftwareDigital Object IdentifierInformationZenonische ParadoxienBenutzeroberflächeKontrollstrukturVersionsverwaltungUmwandlungsenthalpieDefaultElektronische PublikationDefaultMultiplikationsoperatorDatensatzLesen <Datenverarbeitung>SystemplattformKonfiguration <Informatik>Quick-SortVersionsverwaltungMetadatenUmwandlungsenthalpieTheoretische PhysikLastRichtungOrdnung <Mathematik>Vorlesung/KonferenzXML
25:10
Zenonische ParadoxienDigital Object IdentifierVersionsverwaltungDefaultManagementinformationssystemStandardabweichungLanding PageBildverstehenDialektVersionsverwaltungWeb SiteWeb-SeiteBildschirmmaskeUmwandlungsenthalpieRechter WinkelCodeComputeranimation
26:03
Digital Object IdentifierZenonische ParadoxienVersionsverwaltungUmwandlungsenthalpieSoftwareMetadatenVirtuelle MaschineSystemidentifikationURLProdukt <Mathematik>Repository <Informatik>Landing PageInklusion <Mathematik>InformationSoftwareUmwandlungsenthalpieElektronische PublikationGraphische BenutzeroberflächeGüte der AnpassungMailing-ListeCodeURLXML
26:58
DistributionenraumDatenstrukturFaserbündelSoftwareDigital Object IdentifierVersionsverwaltungDualitätstheorieVariableAusnahmebehandlungNotepad-ComputerAttributierte GrammatikChecklisteCodeDatenstrukturProjektive EbeneAdditionCASE <Informatik>SoftwareAttributierte GrammatikXML
27:35
DistributionenraumSoftwareDatenstrukturFaserbündelDigital Object IdentifierVersionsverwaltungDualitätstheorieVariableAusnahmebehandlungNotepad-ComputerAttributierte GrammatikChecklisteZahlenbereichVersionsverwaltungMultiplikationsoperatorVorlesung/Konferenz
28:00
ChecklisteDistributionenraumSoftwareDatenstrukturFaserbündelDigital Object IdentifierVersionsverwaltungDualitätstheorieVariableAusnahmebehandlungNotepad-ComputerAttributierte GrammatikMultiplikationsoperatorMathematikKartesische KoordinatenPhysikalisches SystemXMLUML
Transkript: Englisch(automatisch erzeugt)
00:00
Does anyone know what a software publication is? You make it publicly available for others, you can name this a publication. You open the software in some way. If you look at the research system, a publication is a bit different. We can see how we can improve it so that your interests as the researchers are met. So is there anyone who has published software before? So what? The last days, perfect.
00:30
Okay, so on GitHub. Bioconductor, okay. Ah, okay, yes. Okay, so why do software publications matter?
00:56
Well, we are researchers, it's part of, it's a research product and we should handle it like
01:01
publications, like a paper or like the data. Software is a research product and we should make sure that it's open enough so that others can reproduce our findings, modify it and create new findings with that. And who benefits from software publications? The users and in future you. In future you, there's a lot of change right now in Europe
01:27
and in the world. It's understood that research software is a research product and it's already possible to cite software, not a publication or a paper about software, the software itself.
01:41
Like you can cite data, you can also start citing software and this is why it's important for you because in a few years possibly there will be some analysis, how impactful your software might have been and if others have started using it and are able to cite it,
02:01
then it's your credit somehow and you can show that you have maybe written less papers than others but your software has been quite influential and has been used in other papers that others have written. So there is a change in the system and you should start applying it as soon as possible so you have another research product which is of value for you.
02:26
Okay, we have been talking about that why opening software and source code matters. Sustainability, verifiability of research software, improve the perception of the role of software. So if you start doing software publications it means software will be understood in a different way,
02:42
for example by funding authorities. You open up research software as a key building block in open science or we have open access papers, we have open data and now we have open source which is part of open science. You can link software publications to the scientific reputation
03:03
system through consistent application of DUIs for example and you can do a bit more there and this is part of the aims of the DERSE movement in Germany and Neil Schohang once said until there is a radical change in the way that academic credit is given the principal record of
03:23
scientific research is still the peer-reviewed publication. Given that software is a fundamental part of doing science we agree with that in the digital age the question we are often asked is where can I publish papers which are primarily focused on my research on my scientific
03:40
software. So what we have is we have software journals and repositories. Software journals use their individual policies and you can have a comprehensive list for example which is provided by the Software Sustainability Institute. We can have a look at it and I've read it.
04:01
Which journals should I publish my software? We are not talking about a software publication it's more a workaround but if you like to do the work around you find many journals, general journals, engineering, humanities, social science, image processing, informatics, life sciences, physical sciences, geosciences. So you will definitely find a journal which helps you to write something
04:25
about your software. This is the one thing and of course the other thing is that there are repositories which you can use to mint a DOI for source code copies so far like Zenodo. It's just minting a DOI on a copy or software release packages. We have software and source code
04:46
repositories. Most likely you won't have a DOI there but you have code there and software project management where the software development really happens. It's GitHub or GitLab for example. You have some sort of foundations so if you have reached a specific majority then it's an
05:08
environment for free and open source software projects for example the Apigee Foundation or the Eclipse Foundation and of course you have your institutes. Some institutes already offer the option that software or code repositories can use or digital repositories
05:23
minting duis to software itself can be used as well. So there are many channels where you can start providing your software in a way that it's also that you get the acknowledgement in the scientific reputation system. This is something I will skip. We can dive into
05:42
the software publications. When we go to the data size search we will find that there are software publications. They list approximately 60 000 there. As you can see it's more than 60 000 words that are if you look on the right it's the the filter you can see we have selected
06:01
software as a resource type so others are doing it already. So data side shows a long list of 60 000 software publications which is quite a lot but I also have to say when we go to Zenodo which basically is the digital repository which is having or is hosting
06:27
or is listing or minting duis for software we can trigger the same search here. It's listing 50 000 words just the software resource type and also
06:49
just for the data center Zenodo but if you go to Zenodo yourself you will find an inconsistency for example when we go to Zenodo and use the search there they are just saying that there
07:03
are 20 000 here 20 found 20 000 results which are software so there's an inconsistency between data side and Zenodo which basically results from that a few people for example assign
07:23
the resource type software to data which is accompanied to software so they make a publication for the software and say it's resource type software and then they provide the data and say it's also resource type software because it's a part of the software and can be used with the software but in fact it's data so if you are using that Zenodo and
07:44
publishing your software yourself or the data for software be careful what you select because you have all things in your own hands however summarized that means Zenodo currently has the biggest amount of software publications available which have a dui for example we can check that
08:03
one click on it and for example we see that there's a dui you can even see that this piece of software is a supplement to another publication you can see the content of it what's in there
08:24
and you can see that there are different versions of the piece of software and they even provide you information how to cite that stuff cite s and you can start using that by copy and paste and put it if you use the software in a paper to produce results you can
08:43
use that part in the citations in the reference list of your paper okay and as you can see Zenodo itself has 20 000 and the next one is figshare or bioconductor with five or three thousand so Zenodo currently is the choice the place to publish software okay software citation so data
09:11
site offers citation snippets for copy and paste after the ui minting we have seen a similar thing just right now
09:21
what did we say data site for example yeah we can click this is data site the the search result again we can use site as well here and you can use the apa harvard mla vancouver and you just need to copy and paste and you can put it in your reference list and you should start doing
09:41
that as well if you publish your software and you get a dui you have a copy and paste snippet you can put in the paper that you have written where you are using your own software pardon uh the bibtage is uh was that one no it's just telling you okay um but software
10:25
citation starts at your screen before or without minting a dui so when you start to package there's the force 11 and the specific group who have defined a few principles and
10:41
you can also think about what is software what is data but we don't need to talk about that in respect to citations it's just additional information but force 11 i think you have been talking about that as a community to help facilitate change toward improved knowledge create and sharing software as part of that and there's a software citation group which produced
11:02
a consolidated set of citation principles and the citation principles um i think these are six and not only which are general statements we will have a look at them and there are use cases and discussions how to make use of them so principle one is the importance software should be considered a legitimate and citable product it's a research output accorded the same importance
11:24
as citations of other research other research products so in the reference list of a journal article and should not be omitted or separated should be cited on the same basis as any other research product so this basically means if you're writing a piece of paper which is based on data
11:41
and which is based on software you will end up with three publications already and in your paper you can cite the data and you can cite the software you have used then credit and attribution it's important in research software citations should facilitate given credit and attribution to all contributors unique identification is identification as principle
12:04
three a software citation should include a method for identification recognized at least by the community of the corresponding domain experts but it would be better if it's also recognized by a general public researchers then we have three other principles persistence so unique
12:24
identifiers and metadata describing the software and its disposition should persist accessibility software citations should facilitate access to the software itself and specificity software citations should facilitate identification of and access to the
12:41
specific version of software that was used so not just the general hint to the software here's my github link no please don't do it that way please use the specific version that has been used in your paper you can use citation files or citation cff files the first one is a
13:01
plain text file named citation i think you have been talking about that yesterday as well so you just like the license file you put a citation file in the root directory of your code we have an example and since there is no real standard how to handle it when we go to this example where's the citation file oh you can you have the citation file we
13:25
click it and you can see that this citation file is a bit more extensive possibly than you have seen yesterday but the most important thing is that there's the biptash entry and there's much more information there where this belongs to a bit of a url and information then to cite
13:42
the piece of software and publication please use and they provide a copy and paste string they even say that this string might be modified in the citation style of your publication and so on and so on and at the bottom they say why they are doing that and they refer to the force 11 document referring to the principles and how to implement them
14:04
do we have another example yes we have more examples which is very important for you because this is a practice which is just being adopted by many researchers who are writing software and if you want to become such a researcher as well then you of course would like to look how are others doing that and we can make a search on a file named citation well that's
14:26
interesting okay and then you would see all the different citations files which are in other projects and you can click on them and check how others are doing that get some experience with
14:41
it get ideas how to design your own citation file what shall i do yeah at the end or plus
15:03
colon r open size that way okay perfect and then you have a list of right then you have a list of
15:27
citations file and you just can look how others are doing that and you can see this one only contains the biptash entry okay so it's the first entry for you how to work with citation files and then we have the the citation file format because this one is a human readable
15:47
information normally that's that's i mean it's a biptash entry so it could also be machine readable but mainly it's mainly meant for being human readable and the citation file format is human and machine readable to because it uses the yaml the yet another markup language
16:05
and we have an example here as well for the for a specific python converter and as you can see now we don't have a citation file now we have a citation cff file and when we look into that
16:22
we have a specific syntax and it tells us something about the authors uh the date released toy some keywords uh license is also in the a message title and a version so it's a different type of how to do things basically that means for you things are just changing so you should if you don't know no one knows which of these formats
16:47
or which of these approaches may survive over the next years you should start using both of them to support future future use what else
17:03
next one is that there are also other attempts i think you also have been talking about code meter a bit and json ld files this provides a way of describing describing machine readable information with semantic context again there are examples there's a code meta json file here and as you can see there's much more information in here but basically it
17:25
says also different persons are involved with their names with an email address and also with orchid these are the country authors and contributors so there's a different differentiation and it's a long list in that case of contributors it's even also differentiating
17:45
that there's a maintainer and there's also some some information on continuous integration development starters funding so it's a really expressive file where you can put much more metadata in which are then not only mainly machine readable but for developers is also human
18:05
readable what else the next thing is that you have a readme md for example which is displayed in at first in github and other like github hosting websites and there you can also
18:23
include a small section how to cite or to cite in publications please use and you provide a copy and paste snippet and if possible you can even add a dui batch you have copy and paste possibilities for example in sonodo how to apply a dui batch in a readme file on github
18:41
and there might things coming up over the next years as well so currently the the reputation system in science and research changes and you are part of that change and you should be aware of what happens and if you want to be flexible and address the the final decision maybe
19:05
you should consider a citation file you should consider a cff file if you like you can play around with this code meta json use the readme file because this is the first thing people see and you should stay up to date because there might be new attempts new approaches over the next
19:24
one two or three years they are also used somehow wait wait wait wait for example this you remember this is sonodo and you have this site as information and you also have this xbox section at the bottom and you already have a link which is listing jsonld and you can see that they
19:43
already integrate this information somehow so basically it's it's something that just occurs and the different providers of publication systems or digital repositories and also code repositories and they're just figuring out how it can be used by us by the developers by humans
20:04
but also how it can be used by the systems itself to to to communicate these metadata information in a way that they are findable on different platforms so there's no real solution right now and everyone is start playing around with that so please start playing with it as well
20:23
yeah yeah they are experimental definitely they are integrated it's quite progressive that you can find jsonld on sonodo so it's experimental and no one knows where this will end maybe they drop this in a year and say it it it it isn't something that is applied by the community
20:42
as you said biptash is something you have to experiment with it and if you like to support a future use which might be dropped you should consider all these i mean it's a bit of effort but it's not so much it's a citation file you can if you like it's the biptash stuff and some human readable part if you like you can really put the cff file in it so it's a bit more information
21:06
you have the jsonld that's a bit more work i would say or you use because this one is automatically generated from your metadata so you can use sonodo as your publication platform and then you have the jsonld stuff and can take that out and you have of course
21:23
something like a readme where you just put the copy and paste very prominent for the batch that that it has been published of course this was a generic approach i think uh yesterday and the days before you have been using r and cron for example and you have addressed probably also the citation uh citing r and r packages and publications so you can use citation and citation
21:50
is reading for example we have a citation file we have a description file for example for nitta we can look at nitta and nitta has this information in cron and you get
22:04
some biptash information and this is a comment and copy and paste information and this one is generated by the citation file and by the description file as you can see this is the citation file in r it's a different citation file than we have seen before and it's integrating
22:22
a site entry which is a manual which is a book and which is a collection obviously and when you look at the manual then this is the information which is shown also at the first point here and with the information as biptash entry so there are community practices and you should really
22:44
consider these community practices for example if you are practices if you are for example using r and cron because they have been or they are still supported in google schooler so for example when we look at google schooler for this person we can find
23:03
that there are tons of publications paper publications and just in between there's a piece of software that's basically the idea that you have also a publication list and that you are not just listing your papers and a bit of your data you have published but also the software that is
23:20
published okay next thing metadata for publications if you use synodo there's a long list where you can start adding your files you can say which communities are involved upload type would be software then you have basic information like information about you the license the funding
23:41
related alternative identifiers contributors references a journal where this might have been mentioned a conference or something like that a book a thesis or a different or you can select subjects so there are tons of metadata you can select you should make use of it as as good as possible and it's basically up to you it's also connected to github i i don't know if you have
24:06
shown it perfect and there's also further reading how you can apply metadata but basically if you go with synodo this is from from my knowledge the most advanced platform because it's all in your hands and they provide you a lot of options to add metadata then you have some
24:23
sort of doi versioning in synodo which is pretty cool as well what i would say because doi versioning allows you to cite all versions and a specific version of a record and allows to edit and update the records files after the initial publication so when you publish an upload on synodo for the first time you get two duis the first one is a specific version of the record
24:46
and the other one is a doi representing all versions of the record again which doi should i use in citations to ensure that other researchers can access the exact research artifact for reproducibility you should use the the the specific doi for a specific version
25:06
and by default also synodo generates this citation for the for the for the latest so we can have a look at an example now you can see this is the standard example from synodo
25:22
on the left is the code on the right you have the versions and you can see that been all nine versions cite all versions this is the one catches all doi which is 5.9 2020 and then you have specific um specific uh duis for these for this version for the latest
25:43
version 2.2 and you have a different doi here um so it's quite flexible but it's one entry it's landing page and if you select one of these duis and the duis resolve to the landing page you end up in a page where you get all versions which is excellent this is exactly what you want
26:05
okay so best practices for software citations is publish it if it's on github then follow specific steps there otherwise submit it to synodo or somewhere else with appropriate metadata and get a dui for it create a citation file before that update your readme file
26:26
a secondary workaround might be that you write a paper about it and you should also consider what you do when you cite someone else's software in a paper which has not a dui and a code or just a snippet a citation snippet you just can copy and paste then you should do it on your own to
26:43
have a good practice check who are the contributors what is the name is the url for this piece of software and then build your own citation snippet and put it in the reference list of your publication where you use a software of someone else so wrap up is um if we look at
27:03
all of this stuff is select a proven and strong license check the compatibility for the license use additional license provisions if required for example in the case that you would allow that others can follow modifications if they are published somewhere else so that the code is
27:21
available without redistribution then structure the software project bundle a release put a specific documentation on the dependencies and licenses we have been talking about this doc folder attribute others work enable citation publish get a dui and don't be shy a dui really is just a number so use it and publish whenever you want and ensure that all versions or releases
27:47
can be referred at all and individually so this is the versioning start and the most important thing is start somehow with the recommendations given spend time to make your own experiences and talk with others about that and then over the time things will evolve it's i wouldn't say
28:04
it's fairly new but it's new enough so that everyone helps to apply the current change in the scientific reputation system