Software Reuse - Revision history

PRWheatley at 17:25, 15 January 2016

2016-01-15T17:25:17Z

← Older revision		Revision as of 17:25, 15 January 2016
Line 9:		Line 9:
	'''From [https://docs.google.com/document/d/1hE3IXKbR78bIO4fHeGh4ugC8fxO-23koov3wnLHpqBw Spotlight Data: Jisc RDS Software Projects]'''		'''From [https://docs.google.com/document/d/1hE3IXKbR78bIO4fHeGh4ugC8fxO-23koov3wnLHpqBw Spotlight Data: Jisc RDS Software Projects]'''
	:"Key project outputs:		:"Key project outputs:
	#Report: Guidelines for persistently identifying software using DataCite		:#Report: Guidelines for persistently identifying software using DataCite
	#Report: Phase II Report on Technical Progress and Case Study		:#Report: Phase II Report on Technical Progress and Case Study
	#Landing page system and ‘Play it’ button demonstrations"		:#Landing page system and ‘Play it’ button demonstrations"

	'''From a [http://digital-archiving.blogspot.co.uk/2015/12/the-research-data-spring-projects.html synthesis of the projects in the context of the OAIS model], by Jen Mitcham of the Filling the Digital Preservation Gap project'''		'''From a [http://digital-archiving.blogspot.co.uk/2015/12/the-research-data-spring-projects.html synthesis of the projects in the context of the OAIS model], by Jen Mitcham of the Filling the Digital Preservation Gap project'''

PRWheatley at 17:06, 15 January 2016

2016-01-15T17:06:27Z

← Older revision		Revision as of 17:06, 15 January 2016
Line 23:		Line 23:
	*[https://www.jisc.ac.uk/podcasts/research-data-springsoftware-reuse-repurposing-and-reproducibility-22-sep-2015 Jisc Project Podcast]		*[https://www.jisc.ac.uk/podcasts/research-data-springsoftware-reuse-repurposing-and-reproducibility-22-sep-2015 Jisc Project Podcast]
	*[https://github.com/cjw-charleswu/Recompute Recompute on Github]		*[https://github.com/cjw-charleswu/Recompute Recompute on Github]
			*[http://www.recomputation.org/ Recomputation.org]

	==Potential to enhance==		==Potential to enhance==

PRWheatley at 17:05, 15 January 2016

2016-01-15T17:05:54Z

← Older revision		Revision as of 17:05, 15 January 2016
Line 22:		Line 22:
	*[http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/12/SoftwareRRR-Report-Dec151.pdf Phase 2 report, detailing work done as of December 2015]		*[http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/12/SoftwareRRR-Report-Dec151.pdf Phase 2 report, detailing work done as of December 2015]
	*[https://www.jisc.ac.uk/podcasts/research-data-springsoftware-reuse-repurposing-and-reproducibility-22-sep-2015 Jisc Project Podcast]		*[https://www.jisc.ac.uk/podcasts/research-data-springsoftware-reuse-repurposing-and-reproducibility-22-sep-2015 Jisc Project Podcast]
			*[https://github.com/cjw-charleswu/Recompute Recompute on Github]

	==Potential to enhance==		==Potential to enhance==

PRWheatley at 17:04, 15 January 2016

2016-01-15T17:04:52Z

← Older revision		Revision as of 17:04, 15 January 2016
Line 44:		Line 44:

	Further dissemination of the outputs of this project, including simple, straightforward demonstrations at relevant events will help establish the assignment of PIDs to research software in future. Broader applicability of core project developments offers potential to open up new sources of funding from other sectors.		Further dissemination of the outputs of this project, including simple, straightforward demonstrations at relevant events will help establish the assignment of PIDs to research software in future. Broader applicability of core project developments offers potential to open up new sources of funding from other sectors.

			[http://coptr.digipres.org/Recompute Entry for Recompute added to the COPTR registry].

	==Project website sustainability checklist==		==Project website sustainability checklist==

PRWheatley: /* Potential to enhance */

2016-01-15T16:54:14Z

Potential to enhance

← Older revision		Revision as of 16:54, 15 January 2016
Line 28:		Line 28:
	This project already aims to develop preservation capabilities--long-term preservation through assigning persistent identifiers, maintaining the relationship between content and software, and breaking down the components of ‘software’ to ensure a broad range of objects can be cited. To further the preservation capabilities developed through this project, the researchers might aim to produce an outcome that generalises the processes developed for assigning DataCite DOIs to this type of bespoke research software so that the processes could be applied to other types of software, such as commercial software. These processes could benefit heritage and government sector organisations looking to perform similar versioning and PID assignments on their own software.		This project already aims to develop preservation capabilities--long-term preservation through assigning persistent identifiers, maintaining the relationship between content and software, and breaking down the components of ‘software’ to ensure a broad range of objects can be cited. To further the preservation capabilities developed through this project, the researchers might aim to produce an outcome that generalises the processes developed for assigning DataCite DOIs to this type of bespoke research software so that the processes could be applied to other types of software, such as commercial software. These processes could benefit heritage and government sector organisations looking to perform similar versioning and PID assignments on their own software.

	It's worth noting that David Rosenthal, in his 2015 Andrew Mellon Foundation report, identified one of the two remaining barriers to deployment of emulation as a preservation strategy as [https://mellon.org/media/filer_public/0c/3e/0c3eee7d-4166-4ba6-a767-6b42e6a1c2a7/rosenthal-emulation-2015.pdf "the tools for creating preserved system images are inadequate"], a challenge that this work attempts to solve and indeed automate. The process of generating the "playable" image has a useful side-effect of ~~validating~~ that the source code is easily built. In effect this gives Software Reuse an impressive double pronged approach to the long term preservation of software.		It's worth noting that David Rosenthal, in his 2015 Andrew Mellon Foundation report, identified one of the two remaining barriers to deployment of emulation as a preservation strategy as [https://mellon.org/media/filer_public/0c/3e/0c3eee7d-4166-4ba6-a767-6b42e6a1c2a7/rosenthal-emulation-2015.pdf "the tools for creating preserved system images are inadequate"], a challenge that this work attempts to solve and indeed automate. The process of generating the "playable" image has a useful side-effect of ensuring that the source code is easily built. In effect this gives Software Reuse an impressive double pronged approach to the long term preservation of software.

	==Collaboration==		==Collaboration==

PRWheatley: /* Potential to enhance */

2016-01-15T16:35:47Z

Potential to enhance

← Older revision		Revision as of 16:35, 15 January 2016
Line 26:		Line 26:
	''Is there potential to leverage non-preservation focused developments to enhance preservation capabilities?''		''Is there potential to leverage non-preservation focused developments to enhance preservation capabilities?''

	This project already aims to develop preservation capabilities--long-term preservation through assigning persistent identifiers, maintaining the relationship between content and software, and breaking down the components of ‘software’ to ensure a broad range of objects can be cited. To further the preservation capabilities developed through this project, the researchers might aim to produce an outcome that generalises the processes developed for assigning DataCite DOIs to this type of bespoke research software so that the processes could be applied to other types of software, such as commercial software. These processes could benefit heritage and government sector organisations looking to perform similar versioning and PID assignments on their own software. It's worth noting that David Rosenthal, in his 2015 Andrew Mellon Foundation report, identified one of the two remaining barriers to deployment of emulation as a preservation strategy as [https://mellon.org/media/filer_public/0c/3e/0c3eee7d-4166-4ba6-a767-6b42e6a1c2a7/rosenthal-emulation-2015.pdf "the tools for creating preserved system images are inadequate"], a challenge that this work attempts to solve and indeed automate.		This project already aims to develop preservation capabilities--long-term preservation through assigning persistent identifiers, maintaining the relationship between content and software, and breaking down the components of ‘software’ to ensure a broad range of objects can be cited. To further the preservation capabilities developed through this project, the researchers might aim to produce an outcome that generalises the processes developed for assigning DataCite DOIs to this type of bespoke research software so that the processes could be applied to other types of software, such as commercial software. These processes could benefit heritage and government sector organisations looking to perform similar versioning and PID assignments on their own software.

			It's worth noting that David Rosenthal, in his 2015 Andrew Mellon Foundation report, identified one of the two remaining barriers to deployment of emulation as a preservation strategy as [https://mellon.org/media/filer_public/0c/3e/0c3eee7d-4166-4ba6-a767-6b42e6a1c2a7/rosenthal-emulation-2015.pdf "the tools for creating preserved system images are inadequate"], a challenge that this work attempts to solve and indeed automate. The process of generating the "playable" image has a useful side-effect of validating that the source code is easily built. In effect this gives Software Reuse an impressive double pronged approach to the long term preservation of software.

	==Collaboration==		==Collaboration==

PRWheatley at 13:54, 12 January 2016

2016-01-12T13:54:50Z

← Older revision		Revision as of 13:54, 12 January 2016
Line 69:		Line 69:
	*Potential: Wide applicability of underlying developments could benefit broad preservation sector (and beyond), and potentially open up further sources of funding		*Potential: Wide applicability of underlying developments could benefit broad preservation sector (and beyond), and potentially open up further sources of funding
	*Would benefit from further dissemination in the broader digital preservation community		*Would benefit from further dissemination in the broader digital preservation community
	*Suggest adding key details to the project website, including start/end dates, ~~licencing~~ details and references to source code on Github.		*Suggest adding key details to the project website, including start/end dates, licensing details and references to source code on Github.

	{{:LTPARfooter}}		{{:LTPARfooter}}

PRWheatley at 13:53, 12 January 2016

2016-01-12T13:53:22Z

← Older revision		Revision as of 13:53, 12 January 2016
Line 26:		Line 26:
	''Is there potential to leverage non-preservation focused developments to enhance preservation capabilities?''		''Is there potential to leverage non-preservation focused developments to enhance preservation capabilities?''

	This project already aims to develop preservation capabilities--long-term preservation through assigning persistent identifiers, maintaining the relationship between content and software, and breaking down the components of ‘software’ to ensure a broad range of objects can be cited. To further the preservation capabilities developed through this project, the researchers might aim to produce an outcome that generalises the processes developed for assigning DataCite DOIs to this type of bespoke research software so that the processes could be applied to other types of software, such as commercial software. These processes could benefit heritage and government sector organisations looking to perform similar versioning and PID assignments on their own software. It's worth noting that David Rosenthal, in his 2015 Andrew Mellon Foundation report, identified one of the two remaining barriers to deployment of emulation as a preservation strategy as "the tools for creating preserved system images are inadequate", a challenge that this work attempts to solve and indeed automate.		This project already aims to develop preservation capabilities--long-term preservation through assigning persistent identifiers, maintaining the relationship between content and software, and breaking down the components of ‘software’ to ensure a broad range of objects can be cited. To further the preservation capabilities developed through this project, the researchers might aim to produce an outcome that generalises the processes developed for assigning DataCite DOIs to this type of bespoke research software so that the processes could be applied to other types of software, such as commercial software. These processes could benefit heritage and government sector organisations looking to perform similar versioning and PID assignments on their own software. It's worth noting that David Rosenthal, in his 2015 Andrew Mellon Foundation report, identified one of the two remaining barriers to deployment of emulation as a preservation strategy as [https://mellon.org/media/filer_public/0c/3e/0c3eee7d-4166-4ba6-a767-6b42e6a1c2a7/rosenthal-emulation-2015.pdf "the tools for creating preserved system images are inadequate"], a challenge that this work attempts to solve and indeed automate.

	==Collaboration==		==Collaboration==
	''Is there potential for collaboration and/or exploiting existing/parallel work beyond the project consortiums?''		''Is there potential for collaboration and/or exploiting existing/parallel work beyond the project consortiums?''

	The development of processes and methods for assigning PIDs to software could be aligned with the software preservation activities of the Open Preservation Foundation who support a broader range of sectors. The work could also be aligned with that of the Software Sustainability Institute. The range of contact points detailed in the [http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/12/SoftwareRRR-Report-Dec151.pdf phase 2 report] is very encouraging. Additions to the list would be at the access end of image encapsulation delivery with the [https://olivearchive.org/about/ Olive Archive] and the [http://bw-fla.uni-freiburg.de/wordpress/ bwFLA]. The work of both is summarised well in the previously mentioned [https://mellon.org/media/filer_public/0c/3e/0c3eee7d-4166-4ba6-a767-6b42e6a1c2a7/rosenthal-emulation-2015.pdf Rosenthal report].		The development of processes and methods for assigning PIDs to software could be aligned with the software preservation activities of the Open Preservation Foundation who support a broader range of sectors. The work could also be aligned with that of the Software Sustainability Institute. The range of contact points detailed in the [http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/12/SoftwareRRR-Report-Dec151.pdf phase 2 report] is very encouraging. Additions to the list would be at the access end of image encapsulation delivery with the [https://olivearchive.org/about/ Olive Archive] and the [http://bw-fla.uni-freiburg.de/wordpress/ bwFLA]. The work of both is summarised well in the previously mentioned [https://mellon.org/media/filer_public/0c/3e/0c3eee7d-4166-4ba6-a767-6b42e6a1c2a7/rosenthal-emulation-2015.pdf Rosenthal report] (page 6+).

	==Considerations going forward==		==Considerations going forward==

PRWheatley at 13:38, 12 January 2016

2016-01-12T13:38:12Z

← Older revision		Revision as of 13:38, 12 January 2016
Line 26:		Line 26:
	''Is there potential to leverage non-preservation focused developments to enhance preservation capabilities?''		''Is there potential to leverage non-preservation focused developments to enhance preservation capabilities?''

	This project already aims to develop preservation capabilities--long-term preservation through assigning persistent identifiers, maintaining the relationship between content and software, and breaking down the components of ‘software’ to ensure a broad range of objects can be cited. To further the preservation capabilities developed through this project, the researchers might aim to produce an outcome that generalises the processes developed for assigning DataCite DOIs to this type of bespoke research software so that the processes could be applied to other types of software, such as commercial software. These processes could benefit heritage and government sector organisations looking to perform similar versioning and PID assignments on their own software.		This project already aims to develop preservation capabilities--long-term preservation through assigning persistent identifiers, maintaining the relationship between content and software, and breaking down the components of ‘software’ to ensure a broad range of objects can be cited. To further the preservation capabilities developed through this project, the researchers might aim to produce an outcome that generalises the processes developed for assigning DataCite DOIs to this type of bespoke research software so that the processes could be applied to other types of software, such as commercial software. These processes could benefit heritage and government sector organisations looking to perform similar versioning and PID assignments on their own software. It's worth noting that David Rosenthal, in his 2015 Andrew Mellon Foundation report, identified one of the two remaining barriers to deployment of emulation as a preservation strategy as "the tools for creating preserved system images are inadequate", a challenge that this work attempts to solve and indeed automate.

	==Collaboration==		==Collaboration==
	''Is there potential for collaboration and/or exploiting existing/parallel work beyond the project consortiums?''		''Is there potential for collaboration and/or exploiting existing/parallel work beyond the project consortiums?''

	The development of processes and methods for assigning PIDs to software could be aligned with the software preservation activities of the Open Preservation Foundation who support a broader range of sectors. The work could also be aligned with that of the Software Sustainability Institute. The range of contact points detailed in the [http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/12/SoftwareRRR-Report-Dec151.pdf phase 2 report] is very encouraging. ~~An addition~~ to the list would be the [https://olivearchive.org/about/ Olive Archive].		The development of processes and methods for assigning PIDs to software could be aligned with the software preservation activities of the Open Preservation Foundation who support a broader range of sectors. The work could also be aligned with that of the Software Sustainability Institute. The range of contact points detailed in the [http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/12/SoftwareRRR-Report-Dec151.pdf phase 2 report] is very encouraging. Additions to the list would be at the access end of image encapsulation delivery with the [https://olivearchive.org/about/ Olive Archive] and the [http://bw-fla.uni-freiburg.de/wordpress/ bwFLA]. The work of both is summarised well in the previously mentioned [https://mellon.org/media/filer_public/0c/3e/0c3eee7d-4166-4ba6-a767-6b42e6a1c2a7/rosenthal-emulation-2015.pdf Rosenthal report].

	==Considerations going forward==		==Considerations going forward==

PRWheatley: /* Collaboration */

2016-01-12T13:14:40Z

Collaboration

← Older revision		Revision as of 13:14, 12 January 2016
Line 31:		Line 31:
	''Is there potential for collaboration and/or exploiting existing/parallel work beyond the project consortiums?''		''Is there potential for collaboration and/or exploiting existing/parallel work beyond the project consortiums?''

	The development of processes and methods for assigning PIDs to software could be aligned with the software preservation activities of the Open Preservation Foundation who support a broader range of sectors. The work could also be aligned with that of the Software Sustainability Institute. The range of contact points detailed in the [http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/12/SoftwareRRR-Report-Dec151.pdf phase 2 report] is very encouraging.		The development of processes and methods for assigning PIDs to software could be aligned with the software preservation activities of the Open Preservation Foundation who support a broader range of sectors. The work could also be aligned with that of the Software Sustainability Institute. The range of contact points detailed in the [http://rrr.cs.st-andrews.ac.uk/wp-content/uploads/2015/12/SoftwareRRR-Report-Dec151.pdf phase 2 report] is very encouraging. An addition to the list would be the [https://olivearchive.org/about/ Olive Archive].

	==Considerations going forward==		==Considerations going forward==