@article{OltmannsHaslerPetersKottigetal.2019, author = {Oltmanns, Elias and Hasler, Tim and Peters-Kottig, Wolfgang and Kuper, Heinz-G{\"u}nter}, title = {Different Preservation Levels: The Case of Scholarly Digital Editions}, volume = {18}, journal = {Data Science Journal}, number = {1(51)}, doi = {10.5334/dsj-2019-051}, pages = {9}, year = {2019}, abstract = {Ensuring the long-term availability of research data forms an integral part of data management services. Where OAIS compliant digital preservation has been established in recent years, in almost all cases the services aim at the preservation of file-based objects. In the Digital Humanities, research data is often represented in highly structured aggregations, such as Scholarly Digital Editions. Naturally, scholars would like their editions to remain functionally complete as long as possible. Besides standard components like webservers, the presentation typically relies on project specific code interacting with client software like webbrowsers. Especially the latter being subject to rapid change over time invariably makes such environments awkward to maintain once funding has ended. Pragmatic approaches have to be found in order to balance the curation effort and the maintainability of access to research data over time. A sketch of four potential service levels aiming at the long-term availability of research data in the humanities is outlined: (1) Continuous Maintenance, (2) Application Conservation, (3) Application Data Preservation, and (4) Bitstream Preservation. The first being too costly and the last hardly satisfactory in general, we suggest that the implementation of services by an infrastructure provider should concentrate on service levels 2 and 3. We explain their strengths and limitations considering the example of two Scholarly Digital Editions.}, language = {en} } @article{AnztBachDruskatetal.2020, author = {Anzt, H. and Bach, F. and Druskat, S. and L{\"o}ffler, F. and Loewe, A. and Renard, B. Y. and Seemann, G. and Struck, A. and Achhammer, E. and Appell, F. and Bader, M. and Brusch, L. and Busse, C. and Chourdakis, G. and Dabrowski, P. W. and Ebert, P. and Flemisch, B. and Friedl, S. and Fritzsch, B. and Funk, M. D. and Gast, V. and Goth, F. and Grad, J.-N. and Hermann, Sibylle and Hohmann, F. and Janosch, S. and Kutra, D. and Linxweiler, J. and Muth, T. and Peters-Kottig, Wolfgang and Rack, F. and Raters, F. H. C. and Rave, S. and Reina, G. and Reißig, M. and Ropinski, T. and Schaarschmidt, J. and Seibold, H. and Thiele, J. P. and Uekermann, B. and Unger, S. and Weeber, R.}, title = {An environment for sustainable research software in Germany and beyond: current state, open challenges, and call for action [version 1; peer review: 1 approved, 1 approved with reservations]}, journal = {F1000Research}, number = {9:295}, doi = {10.12688/f1000research.23224.1}, pages = {28}, year = {2020}, abstract = {Research software has become a central asset in academic research. It optimizes existing and enables new research methods, implements and embeds research knowledge, and constitutes an essential research product in itself. Research software must be sustainable in order to understand, replicate, reproduce, and build upon existing research or conduct new research effectively. In other words, software must be available, discoverable, usable, and adaptable to new needs, both now and in the future. Research software therefore requires an environment that supports sustainability. Hence, a change is needed in the way research software development and maintenance are currently motivated, incentivized, funded, structurally and infrastructurally supported, and legally treated. Failing to do so will threaten the quality and validity of research. In this paper, we identify challenges for research software sustainability in Germany and beyond, in terms of motivation, selection, research software engineering personnel, funding, infrastructure, and legal aspects. Besides researchers, we specifically address political and academic decision-makers to increase awareness of the importance and needs of sustainable research software practices. In particular, we recommend strategies and measures to create an environment for sustainable research software, with the ultimate goal to ensure that software-driven research is valid, reproducible and sustainable, and that software is recognized as a first class citizen in research. This paper is the outcome of two workshops run in Germany in 2019, at deRSE19 - the first International Conference of Research Software Engineers in Germany - and a dedicated DFG-supported follow-up workshop in Berlin.}, language = {en} } @inproceedings{WitzigBerthold2020, author = {Witzig, Jakob and Berthold, Timo}, title = {Conflict-Free Learning for Mixed Integer Programming}, booktitle = {Integration of AI and OR Techniques in Constraint Programming. CPAIOR 2020}, number = {12296}, publisher = {Springer, Cham.}, doi = {10.1007/978-3-030-58942-4_34}, pages = {521 -- 530}, year = {2020}, abstract = {Conflict learning plays an important role in solving mixed integer programs (MIPs) and is implemented in most major MIP solvers. A major step for MIP conflict learning is to aggregate the LP relaxation of an infeasible subproblem to a single globally valid constraint, the dual proof, that proves infeasibility within the local bounds. Among others, one way of learning is to add these constraints to the problem formulation for the remainder of the search. We suggest to not restrict this procedure to infeasible subproblems, but to also use global proof constraints from subproblems that are not (yet) infeasible, but can be expected to be pruned soon. As a special case, we also consider learning from integer feasible LP solutions. First experiments of this conflict-free learning strategy show promising results on the MIPLIB2017 benchmark set.}, language = {en} } @misc{Khorsandi2021, author = {Khorsandi, Ramin}, title = {Gitram 1.0.0}, doi = {10.12752/8527}, year = {2021}, abstract = {Gitram is a software that processes various metadata and data content from GIT and exports them in the format of an XML file. The software is specifically designed for the HPO-navi project. It is also compatible with Opus4 and any other software that can receive data through the sword interface. Gitram process the metadata and the repository content and sends it to Opus4 via the sword interface. The data is taken from a zip file that is stored in the "dataBackup" folder. Users also have an option of saving the data as a document file on Opus. Metadata can also be received from GitLab via a webhook. The entire project is programmed in Python 3.8+ and can be installed on Ubuntu 16 or above. It is open-source and its functionality can be modified to the users needs.}, language = {en} }