#depositmoInteractive Multi-Submission Deposit Workflows for Desktop Applications<br />David Tarrant<br />davetaz@ecs.soto...
In order to get more items into our repositories we need to get closer to the researchers workflow(and support this)<br />
Secondly, there needs to be an incentive for the researcher to use the service<br />
Preferred Environments<br />4<br />
Preferred Environments<br />5<br />
SWORD<br />Simple<br />A big success!<br />6<br />
Microsoft Author-Addin<br />SWORD advocated by Microsoft through their Author Add-In tool.<br />Beta 2 – Single repository...
The Problem with SWORD<br />Loads work onto the repository editors<br />Users are disconnected from their submissions.<br ...
Demand & Incentive<br />Many repositories want a copy<br />Green/Gold OA<br />Multi-submission is “even more” time consumi...
DepositMO<br />10<br />“Changing the culture, embedding deposit into the natural everyday workflow of researchers and lect...
11<br />
Office as a (client side) Service	<br />Fonts!<br />User “saves” to the repository<br />Repository requests a PDF version ...
Office as a (client side) Service	<br />Repository requires key words.<br />Repository asks for full text, does a key word...
SWORD + REST<br />Save first version to repository<br />When done, hit publish / submit.<br />Shows you on the desktop sta...
SWORD Receipt<br />Use the receipt as a URL for the publication from where you can obtain the following:<br />Status of pu...
Project Deliverables – Technical<br />Interaction Specification<br />Simple REST XML/RDF based<br />Extensible for new cli...
Project Deliverables – Training<br />Southampton and Edinburgh to build this into the campus workstations and provide desk...
The Team<br />18<br />
In order to get more items into our repositories we need to get closer to the researchers workflow(and support this)<br />
Secondly, there needs to be an incentive for the researcher to use the service<br /><ul><li>Closing the feedback loop
Extensible Opportunities</li></li></ul><li>#depositmohttp://blogs.ecs.soton.ac.uk/depositmo<br />David Tarrant<br />daveta...
Upcoming SlideShare
Loading in …5
×

Interactive Multi-Submission Deposit Workflows for Desktop Applications by Dave Tarrant

590 views
544 views

Published on

This first presentation on the JISC depositMO project was given at the Open Repositories 2010 conference in Madrid. The project is "embedding deposit into the natural everyday workflow" by connecting digital repositories - created with EPrints and DSpace - with common authoring tools such as Microsoft Office through the SWORD deposit protocol. Find out more at the project blog http://blogs.ecs.soton.ac.uk/depositmo/

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
590
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Interactive Multi-Submission Deposit Workflows for Desktop Applications by Dave Tarrant

  1. 1. #depositmoInteractive Multi-Submission Deposit Workflows for Desktop Applications<br />David Tarrant<br />davetaz@ecs.soton.ac.uk<br />Electronics and Computer Science<br />
  2. 2. In order to get more items into our repositories we need to get closer to the researchers workflow(and support this)<br />
  3. 3. Secondly, there needs to be an incentive for the researcher to use the service<br />
  4. 4. Preferred Environments<br />4<br />
  5. 5. Preferred Environments<br />5<br />
  6. 6. SWORD<br />Simple<br />A big success!<br />6<br />
  7. 7. Microsoft Author-Addin<br />SWORD advocated by Microsoft through their Author Add-In tool.<br />Beta 2 – Single repository SWORD deposit<br />Beta 3 – Multi-repository SWORD deposit<br />Works on Office 2007/2010<br />http://research.microsoft.com/authoring<br />7<br />
  8. 8. The Problem with SWORD<br />Loads work onto the repository editors<br />Users are disconnected from their submissions.<br />No feedback loop<br />No incentive<br />No guideline for what the receipt means.<br />8<br />
  9. 9. Demand & Incentive<br />Many repositories want a copy<br />Green/Gold OA<br />Multi-submission is “even more” time consuming<br />Each have different workflows and metadata schemas<br />9<br />
  10. 10. DepositMO<br />10<br />“Changing the culture, embedding deposit into the natural everyday workflow of researchers and lecturers”<br />
  11. 11. 11<br />
  12. 12. Office as a (client side) Service <br />Fonts!<br />User “saves” to the repository<br />Repository requests a PDF version (fonts embedded)<br />Client supplies the PDF (autonomously)<br />12<br />
  13. 13. Office as a (client side) Service <br />Repository requires key words.<br />Repository asks for full text, does a key word extraction<br />Repository client for keywords and sends the ones it has found<br />Client gets a dialogue to allow them to verify and enter more keywords <br />13<br />
  14. 14. SWORD + REST<br />Save first version to repository<br />When done, hit publish / submit.<br />Shows you on the desktop state of publication, e.g. open doc in word, author bar tells you state in all repositories.<br />14<br />
  15. 15. SWORD Receipt<br />Use the receipt as a URL for the publication from where you can obtain the following:<br />Status of publication<br />Number of downloads<br />Number of citations<br />Same URL for correction, deletion and other RESTFUL operations. <br />Fits well with work already in progress<br />15<br />
  16. 16. Project Deliverables – Technical<br />Interaction Specification<br />Simple REST XML/RDF based<br />Extensible for new clients (e.g. Open Office)<br />New Author Add-in supporting spec<br />Repository Integration<br />EPrints & DSpace<br />Desktop integration (extending existing tools where possible)<br />16<br />
  17. 17. Project Deliverables – Training<br />Southampton and Edinburgh to build this into the campus workstations and provide desktop training. <br />Project to train the trainers (17 currently)<br />17<br />
  18. 18. The Team<br />18<br />
  19. 19. In order to get more items into our repositories we need to get closer to the researchers workflow(and support this)<br />
  20. 20. Secondly, there needs to be an incentive for the researcher to use the service<br /><ul><li>Closing the feedback loop
  21. 21. Extensible Opportunities</li></li></ul><li>#depositmohttp://blogs.ecs.soton.ac.uk/depositmo<br />David Tarrant<br />davetaz@ecs.soton.ac.uk<br />Electronics and Computer Science<br />

×