The document discusses the vision and goals of creating an open "Method Store" repository. The key points are: 1) The Method Store would be a repository that facilitates collaborative development of methodologies in archaeology to avoid redundant work and allow all sectors to participate. 2) It would allow methods, algorithms, and other research outputs to be deposited, shared, tagged, linked, and developed to draw connections between methodologies. 3) The long term goal is for the Method Store to only contain objects released under an open license like Creative Commons to make the research fully transparent and reusable.

1. Show us your working: an archaeology method store Anthony Beck & David Stott

2. Background During AARG 2010 a Method Store was discussed This went viral with support from a number of international institutions/people: Open Knowledge Foundation Council for British Archaeology English Heritage Antiquist 3d heritage This is its story..... sorry mainly text and a few pickies

5. The Big Society

8. Why

9. Why Open Methods provide transparent access to the process The user controls and understands the data processing and transformation From Black Box to White Box

10. What are Open Methods?

11. What is Open Science

12. What Open Science is NOT Just providing access to your data when a project has finished It's as much about engaging with the process as engaging with the science objects

13. Why Open Science?

14. Why Open Science?

15. Why not Open Science

16. The Method Store: VISION A repository that facilitates the collaborative development of methodologies and stops the community re-inventing the methodological wheel. A framework that is not intimidating for users, allowing all sectors of the domain to participate, but allows potentially rich data objects to be submitted (such as Taverna workflows). A system that allows links to be drawn between methodologies to indicate, for example, synergy, workflow or provenance. An environment which captures the cloud of discussion/narrative surrounding the development or forking of a method.

18. shared,

19. tagged,

20. linked,

21. chained,

24. The Website

25. The Future Workflows Better referencing Semantic tagging

26. The Future: Workflows

27. The Future There are other similar initiatives More will come Some will gain traction Others will wither and die All the content should be cross transferable

28. The Future

29. Thanks. Any Questions? http://methods.okfn.org/