![UKOLN is supported by: Monica Duke Project Manager/Researcher 29 th March 2011 Aston Business School SageCite Project http://blogs.ukoln.ac.uk/sagecite/ #sagecite [email_address]](https://image.slidesharecdn.com/mduke-sagecite-jisc-march11-110405021353-phpapp01/85/mduke-sagecitejiscmarch11-1-320.jpg)
![[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Semelhante a Mduke sagecite-jisc-march11
Semelhante a Mduke sagecite-jisc-march11 (20)
Último
Último (20)
Mduke sagecite-jisc-march11
- 1. UKOLN is supported by: Monica Duke Project Manager/Researcher 29 th March 2011 Aston Business School SageCite Project http://blogs.ukoln.ac.uk/sagecite/ #sagecite [email_address]
- 3. Data Process Publication Research Object Citation Chains Credit and Attribution
- 12. DataCite sagecitedemorepository Citable data Produces Register, submit metadata Generate landing page for data and store DOIs Mint DataCite API Google API Resolve to landing page Taverna workflow The relationships between data via DataCite DOIs with tools are captured by the provenance (OPM) produced by Taverna 1 2 3 4 5 6 Workflow metadata For referring to data reported in the provenance
- 13. Additional steps for citing data
- 16. Workflow Provenance Gene URI myExperiment URI Data sets in GEO database Register Submit Open Provenance Model W3C Provenance Incubator RDF Data creator ORCID DOI, Pubmed Id Scientific publication Publication? Sage bionetwork model (Co-expn, Bayesian) DataCite Workflow user ORCID
- 17. Identity Workshop prep-meeting, Helsinki, January 27 2011 Publishing a journal article Publishing a dataset G. A. Thorisson, University of Leicester
- 20. Identity Workshop prep-meeting, Helsinki, January 27 2011 Centrally-managed informatics infrastructure: i) for researchers to manage & use profile ii) for tracking author-to-publication attribution links iii) interaction with other systems (e.g. publishers, digital libraries ORCID ID: G-1442-2009 J. Smith, Univ. North Pole ORCID ID: D-2400-2010 J. Smith, Luthor Corporation ORCID ID: B-1242-2010 G. Thorisson, Univ. Leicester G. A. Thorisson, Univ. Leicester G. A. Thorisson, Cold Spring Harbor Lab. G. A. Thorisson, University of Leicester
Notas do Editor
- One of the CLIP group of projects funded by JISC Focus of talk is on the domain as some of the citation issues will be common with other projects. Concentrating on Sage and its data and some of the implications. Not covering everything done in the project.
- Holy Trinity as written up in the proposal.
- There is something missing from the triangle Cuts across the 3 areas of data, process, publicaton Central to issues of attribution and credit That’s the contributors! Will come back to them later.
- This is an overview of a more complex process (simplified view). Does not show original sources which enter the process. Each part can be looked at in more detail – example coming up. Different people involved as each stage is specialized.
- This is just one of the stages from the previous diagram. We have a version of this for each of the stages, not enough time to go into each of the stages. Each stage has input and ouput, tools employed e.g. r scripts
- Previous slide was a simplified view, actual process is broken down into a workflow, with configuration details, actual scripts, input and output.
- Main contribution has been to capture this process, document it better via Taverna, makeit more understandable and re-usable. Understanding the domain before we can ask the questions about citation. Lessons Learned. Publications have many gaps, perl scripts not very user friendly, working from a document shared by SageBionetworks. Based on a visit to Sage Bionetworks, funded by Sage, built relationships and dialogue leading to data sharing
- Moving on to a slightly diffferent perspective from the domain to the general citation question that we start to address. Started to think about how citation happens. Scenarios on the blog. For each of these stages we will think about the questions that our example throws. I cite others – input data is derived from somewhere I make my work citable – main work of the project (Taverna) Credit – motivation – least addressed so far in the project.
- Identifying the contributor is an issue e.g. the geographicla area of work, may need to identify the organisation that funded. Does the modification change the original, how do I preserve the link.
- This has been the main area of work for Sagecite – next slide show the role of taverna.
- Assign DataCite DOIs Generate metadata – open question; linked data approach Store is temporary for the purposes of demonstrator
- Extra steps have been added to the workflow, within Taverna
- More slides on the last question…
- This was a diagram we had early on in the project - What about other types of publication?
- I presented this at SOLO earlier this month, .. [eda segja annarstadard, i recent & ongoing ORCID activities] I reach for Geoff Bilder’s slides again and nick a few things what I want to do here is replace Geoff’s silly little dude with glasses with my much much cooler ‘academic dude’, as we call him in the office. ### SKIPTA ### I want to show you in the next few slides a hypothetical scenario involving this dude, representing me, submitting a dataset to this digital repository which is a companion to Geoff’s Psychoceramics Review journal this will demonstrate some of the practicalities of how we might actually use ORCID in data publication.
- Coming back to those people….. ORCID addressed by a presentation later on, focussed effort on discussions, bulding scenarios.
- Have started disussions, no service yet – how tools like myExperiment and Taverna which are on the desktop and manage identity (not global) work with a service like ORCID to exchange information including for validation.
- Finally, an advert……..
- Collaborators on some of the projects, provided some of the slides, Sage funded the visit, shared data and documentation.