Difference between revisions of "CURATEcamp iPRES 2012 Discussion Ideas"
Mark Jordan (talk | contribs) |
Mark Jordan (talk | contribs) |
||
| Line 8: | Line 8: | ||
'''Micro service requirements''' (Paul Wheatley): How do we design micro services to maximise their re-use and simplify their orchestration? What are our requirements for the generic aspects of their design (and most importantly their interfaces)? Can we come up with micro services that can easily be shared between orchestration systems? (See this discussion about FITS and characterisation tool wrapping http://openplanetsfoundation.org/blogs/2012-07-27-fits-or-not-fits) | '''Micro service requirements''' (Paul Wheatley): How do we design micro services to maximise their re-use and simplify their orchestration? What are our requirements for the generic aspects of their design (and most importantly their interfaces)? Can we come up with micro services that can easily be shared between orchestration systems? (See this discussion about FITS and characterisation tool wrapping http://openplanetsfoundation.org/blogs/2012-07-27-fits-or-not-fits) | ||
| − | '''Service-oriented architecture for digital preservation''' (Mark Jordan) Some work started by JISC (http://www.ahds.ac.uk/about/projects/soapi/index.htm) but current status is unknown. | + | '''Service-oriented architecture for digital preservation''' (Mark Jordan) Some work started by JISC (http://www.ahds.ac.uk/about/projects/soapi/index.htm) but current status is unknown. This topic is relevant to integrating digital preservation activities not only within an organization but also to allow cross-organization collaboration and tool-sharing. The RESTful BagIt Server (https://github.com/acdha/restful-bag-server) is an example of a such a service. |
'''Re-use and collaboration''' (Paul Wheatley): There seems to be a lot of repetition and reinvention in DP community tool development, despite limited resources and a small pool of contributing parties. How can we avoid these problems, maximise collaboration, increase re-use of existing solutions, and improve sharing of knowledge about where they can be used effectively? | '''Re-use and collaboration''' (Paul Wheatley): There seems to be a lot of repetition and reinvention in DP community tool development, despite limited resources and a small pool of contributing parties. How can we avoid these problems, maximise collaboration, increase re-use of existing solutions, and improve sharing of knowledge about where they can be used effectively? | ||
'''Requirements on file format registries''' (Paul Wheatley): File format initiatives are suddenly all the rage (http://openplanetsfoundation.org/blogs/2012-07-06-biodiversity-and-registry-ecosystem). I have previously suggested (controversial) that we haven't always clearly articulated what our requirements and use cases are for these systems (http://openplanetsfoundation.org/blogs/2012-07-05-dont-panic-what-we-might-need-format-registries). So what requirements do preservation tool developers (and users of their tools) have on file format registries? | '''Requirements on file format registries''' (Paul Wheatley): File format initiatives are suddenly all the rage (http://openplanetsfoundation.org/blogs/2012-07-06-biodiversity-and-registry-ecosystem). I have previously suggested (controversial) that we haven't always clearly articulated what our requirements and use cases are for these systems (http://openplanetsfoundation.org/blogs/2012-07-05-dont-panic-what-we-might-need-format-registries). So what requirements do preservation tool developers (and users of their tools) have on file format registries? | ||
Revision as of 15:53, 13 September 2012
Feel free to use this space to share ideas for discussion at CURATEcamp 2012 iPRES.
Topic you are interested in (Your name): A sentence or three about your topic.
Micro service requirements (Paul Wheatley): How do we design micro services to maximise their re-use and simplify their orchestration? What are our requirements for the generic aspects of their design (and most importantly their interfaces)? Can we come up with micro services that can easily be shared between orchestration systems? (See this discussion about FITS and characterisation tool wrapping http://openplanetsfoundation.org/blogs/2012-07-27-fits-or-not-fits)
Service-oriented architecture for digital preservation (Mark Jordan) Some work started by JISC (http://www.ahds.ac.uk/about/projects/soapi/index.htm) but current status is unknown. This topic is relevant to integrating digital preservation activities not only within an organization but also to allow cross-organization collaboration and tool-sharing. The RESTful BagIt Server (https://github.com/acdha/restful-bag-server) is an example of a such a service.
Re-use and collaboration (Paul Wheatley): There seems to be a lot of repetition and reinvention in DP community tool development, despite limited resources and a small pool of contributing parties. How can we avoid these problems, maximise collaboration, increase re-use of existing solutions, and improve sharing of knowledge about where they can be used effectively?
Requirements on file format registries (Paul Wheatley): File format initiatives are suddenly all the rage (http://openplanetsfoundation.org/blogs/2012-07-06-biodiversity-and-registry-ecosystem). I have previously suggested (controversial) that we haven't always clearly articulated what our requirements and use cases are for these systems (http://openplanetsfoundation.org/blogs/2012-07-05-dont-panic-what-we-might-need-format-registries). So what requirements do preservation tool developers (and users of their tools) have on file format registries?
