Presenter: Peter Burnhill, Director, EDINA national academic data centre, University of Edinburgh, Scotland UK
Presentation given at Beyond Books: What STM & Social Science publishing should learn from each other Marriott Hotel/Kensington, London, 22 April 2010
Doing data in the social sciences and humanities: links to and from published work
1. Doing data in the social sciences and humanities: links to and from published work Peter Burnhill Director, EDINA national academic data centre, University of Edinburgh, Scotland UK Beyond Books: What STM & Social Science publishing should learn from each other Marriott Hotel/Kensington , London, 22 April 2010
8. Researchers’ viewpoint: a cultural shift? Preserve or Perish “ You are not finished until you have done the research, published the results, and published the data, receiving formal credit for everything.” Mark A. Parsons (2006) International Polar Year “ A scholar’s positive contribution is measured by the sum of the original data that he contributes. Hypotheses come and go but data remain.” in Advice to a Young Investigator (1897) Santiago Ramón y Cajal (Nobel Prize winner, 1906)
9.
10.
11.
12.
13.
14.
15.
16.
17. Research publications as research data DISC-UK DataShare Project Edinburgh, LSE, Oxford, Southampton from informal storage and sharing to formal institutional arrangement Robin Rice, Data Librarian, University of Edinburgh
18.
19.
20.
21.
22.
23.
24.
25.
26.
27. search on bibliography and hyperlink to data Myron Gutmann, Inter-university Consortium for Political & Social Research
28. From data to (subsequent & known) published literature
29. Works with supplemental files from “Dissertations, Data Sets and ProQuest UMI”, Austin McLean, IASSIST, May 2008
40. Research publications as research data DataShare2 from formal institutional arrangement to formal publishing into (linked) data infrastructure
41.
42. Research publications as research data DISC-UK DataShare Project (Edinburgh, LSE, Oxford, Southampton) From informal storage and sharing To formal publishing into data infrastructure
Notes de l'éditeur
EDINA may be less familiar, at least to all of you. It is a national academic data centre, established in 1995 following the success of the University of Edinburgh putting forward its Data Library in an open competition to set up three datacentres capable of hosting and providing access to bibliographic datasets and numeric research data. The other two were BIDS, which subsequently moved into the private sector as Ingenta, and MIDAS, the data centre at the University of Manchester - its now renamed as Mimas. The mission of EDINA, which incidentally is the older poetic name for Edinburgh, is to enhance productivity of research, learning and teaching in the UK. It used to host a range of key A&T databaes like BIOSIS ~Previews, Compendex, Inspec, Art Abstracts etc, but now the services on journal …. As you can see, EDINA is a funded by JISC … <click>
Commitment to openness for primary data Expect to
Type A: if its part of the published work then should we look to the preservation agencies, the national deposit libraries and CLOCKSS, LOCKSS and Portico, for access over the longer term? And do publishers see these as costly files to maintain in the short to medium term? Or do publishers want to hand the responsibility to subject and institutional data repositories? Type B: and with knowledge of UKDA, ADS but also the (growing but problematic ??) call for data to be held in institutional repositories, some recommendations on what is the 'right thing' to do, and how that can be done with ease - a Repository Junction task! For Type C, I intend to propose what editors should require by way of citation and URL link. I am on the hunt for such editorial practice.
Type A: if its part of the published work then should we look to the preservation agencies, the national deposit libraries and CLOCKSS, LOCKSS and Portico, for access over the longer term? And do publishers see these as costly files to maintain in the short to medium term? Or do publishers want to hand the responsibility to subject and institutional data repositories? Type B: and with knowledge of UKDA, ADS but also the (growing but problematic ??) call for data to be held in institutional repositories, some recommendations on what is the 'right thing' to do, and how that can be done with ease - a Repository Junction task! For Type C, I intend to propose what editors should require by way of citation and URL link. I am on the hunt for such editorial practice.
The OA-RJ broker design is based on the following simple model (shown above): 1. Data object or API query is received at the Broker URI 2. For API queries, the broker is passed user information (IP address, hostname or organisation name) and will return repository details 3. For data objects, the broker will initially receive a package, unpack it, then determines where it belongs following certain deduction criteria. 4. In certain situations a notification step (not shown) may be desirable, where the broker informs target repositories that material will be sent to them/is available 5. The data object is repackage and sent to the target repository, either via PUSH or PULL mechanisms.