Software has been a crucial contributor to scientific progress in astronomy for decades, but practices that enable machine-actionable citations have not been consistently applied to software itself. Instead, software citation behaviors developed independently from standard publication mechanisms and policies, resulting in human-readable citations that remain hidden over time and that cannot represent the influence software has had in the field. These historical software citation behaviors need to be understood in order to improve software citation guidance and develop relevant publishing practices that fully support the astronomy community. To this end, a 23 year retrospective analysis of software citation practices in astronomy was developed. Astronomy publications were mined for 410 aliases associated with nine software packages and analyzed to identify past practices and trends that prevent software citations from benefiting software authors.

Software is a copyrightable creative work that is foundationally important to the future of scholarly research, yet software citation is not ubiquitous. Despite increasing acceptance of general software citation principles (Smith et al. 2016), challenges exist that make their implementation difficult. As a result, metadata to facilitate software citation goes unrecorded, software goes uncited (Bouquin et al. 2020), and software authors continue to be divorced from their contributions to science and human cultural heritage. If this status quo persists, uncited software will become increasingly difficult to find, access, and build upon, which will prevent software from being a “Findable, Accessible, Interoperable, and Reusable” (FAIR) Digital Object in the future. Addressing the challenges that currently impact software citation implementation requires action from the scholarly communication ecosystem and digital preservation landscape, along with cooperation from software authors and users. This situation presents an opportunity to enable a future for FAIR software through software citation by leveraging intersections between digital challenges in libraries and archives, and the work of experts in other disciplines to advance theory and practice. To achieve this end, the Harvard-Smithsonian Center for Astrophysics (CfA) has partnered with the Institute of Museum and Library Services (IMLS) to bring together stakeholders and experts representing the many forms of labor and expertise to address specific questions about software citation that have so far gone unresolved, such as: How can we enable software citation when the software is part of a larger deposit of content in an archival repository? How can we enable the adoption of metadata standards that support software citation in repositories? How can we enable software citation when the software is part of a larger deposit of content in an archival repository? How can we enable the adoption of metadata standards that support software citation in repositories? To address the above questions, the Software Citation Workshop (SCW) was created. Although the meeting organizers originally planned for a fully in-person meeting, the constantly shifting pandemic landscape necessitated a new approach. Instead of one large meeting, SCW ‘22 started with a series of three online focus groups. These groups were held online from June 28th to June 30th, 2022. The goal of the focus groups was to help meeting organizers better understand how various stakeholders view problems associated with software citation metadata availability in repositories and perceived barriers to implementing software citation metadata standards. The focus groups also helped to identify how these people think software citation problems should be prioritized by addressing specific challenges, such as: What is the status of software citation adoption in your domain? What barriers and incentives influence the availability of software citation metadata in repositories? (e.g., policies, curatorial practices, user-generated information) From your perspective, how should people cite software that is part of a larger deposit? (e.g., Jupyter notebooks deposited with a paper) What could we do to make software citation metadata available in these larger deposits? What influences the adoption of metadata standards that support software citation in repositories? Are curators aware of the differences between the specific software citation metadata formats? (i.e., Citation File Format (CFF) (Druskat 2022) vs. CodeMeta (Jones et al. 2020)) Are software authors aware of the different formats and when/how to use them? What have your experiences been with either? Should we be encouraging one over the other? What is the status of software citation adoption in your domain? What barriers and incentives influence the availability of software citation metadata in repositories? (e.g., policies, curatorial practices, user-generated information) From your perspective, how should people cite software that is part of a larger deposit? (e.g., Jupyter notebooks deposited with a paper) What could we do to make software citation metadata available in these larger deposits? What influences the adoption of metadata standards that support software citation in repositories? Are curators aware of the differences between the specific software citation metadata formats? (i.e., Citation File Format (CFF) (Druskat 2022) vs. CodeMeta (Jones et al. 2020)) Are software authors aware of the different formats and when/how to use them? What have your experiences been with either? Should we be encouraging one over the other? In August 2022, an in-person workshop will summarize the answers to these challenges given by the online focus groups into an expanded and revised version of the Software Citation Implementation Challenges (Katz et al. 2019) document. In-person meeting attendees will be encouraged to brainstorm interventions to tackle and prioritize these newly defined software citation problems, and to lay out a series of mutually supporting approaches to address them. Attendees will also be given the opportunity to synthesize plans of action and other deliverables that can be shared widely. This presentation aims to promote these yet to be determined plans of action by introducing attendees to the lessons learned and outputs produced by the SCW ‘22 meetings. Through open collaboration and feedback, this presentation will also introduce attendees to ways they can help ensure the future of software as a FAIR Digital Object.

No abstract

No abstract