Skip to content

Categories:

Improving deposit: an open digital repositories thunderbolt

JIF: Thunderbolts session - graphicThe following is a slightly extended and embellished version of a rapid-fire talk given in one of the Thunderbolts and Lightning (#2) sessions at the JISC Innovation Forum 2010. “What are the big thunderbolts in institutions today that you know about and you think your colleagues, including those from JISC, should also be aware of?”

Strictly this is not is not about the DepositMO project, but it refers to the project, which prompted my theme here. I’ve been involved in a lot of JISC projects, and while we have produced many successes, perhaps few have produced thunderbolts. Maybe this one will.

Speakers had a maximum of 5 mins, and absolutely no extra seconds. Any unused time was thrown open for immediate responses. Across the whole session there were 12 volunteer speakers, and a panel of speakers was convened after each four. All presentations were simultaneously represented in a graphic, as shown, the whole session being represented on a single large sheet. Overall, a brilliant format.

JIF: Thunderbolts, open digital repositories - graphicMy interest is open digital repositories. Looking at the graphic from the first session, and after the opening speakers in this session, I know, this is so last year. But I contend we are doing repositories wrong.

So what are we doing wrong? Many things probably, but here I want to focus on just one. In an age of austerity we should be planning, digitally, for an age of abundance. Our entry filters for repositories are set for print rather than digital – the filter is on the output side now, not on the input. So we make it harder for researchers to contribute content, to participate.

We are so stuck on quality control we learned with print. By seeking to eliminate the bad we are making it harder for people to find the good. In digital the bad is invisible, but the good can only be found if it is accessible and widely indexed all over the Web.

Take two simple repository examples: editorial buffers and mediated deposit. These delay the appearance of content in a repository. To what purpose? According to a recent poster, a survey found only 7% of deposit to repositories is author self-deposit. How will mediated deposit scale?

My own ‘institutional’ or School repository at Southampton, yet which was recently ranked 10 in the world – rather than the whole University of Southampton repository – some time ago made two important decisions.

First, the editorial buffer for light moderation of deposits had reached a backlog of days. So it was removed, with no discernible loss of quality, but the submitted content appeared on the Web instantly. The author is in control.

Second, a colleague deposited a paper which had me as a co-author. I spotted a couple of minor errors in the eprint record, as you do, and asked him to make corrections. You can edit it yourself, he said. Yes, I was an authorized repository editor, but I so rarely used that privilege that I could barely remember my password, I admitted. No, my colleague said, anyone eligible to submit to the repository can edit any record in the repository. Could this be true? Open spam season! Yes, it was true, and no, it has not ruined the repository.

These are simple examples of progressing from print to digital thinking, but print thinking is embedded in our decisions everywhere, and we are too wedded to old practices to recognize this.

How can we improve both deposit rates and speed of deposit to repositories? One approach is the new JISC project, Modus Operandi for Repository Deposit (DepositMO). The clue is in the title: deposit. The basic idea is we embed the facility for repository deposit in the workspace that most people use: Microsoft Office documents.

Alfred Hitchcock by Pieter Musterd (tempo doeloe) Here’s the twist. It may be that deposit is a MacGuffin. A MacGuffin is a device famously used by my namesake, Alfred Hitchcock, and is essentially a plot driver that may turn out not to have been integral to the plot. That is, a distraction.

It may turn out that DepositMO is not primarily about deposit, but about opening a dialogue with the researcher. Already we can see new possibilities, providing new services mediated in the cloud, for example, all opened via this new deposit interface.

In another current JISC project, KeepIt, we have been developing cloud services for repositories, and we have helped repository managers plan for an abundance of digital content by showing them how to discover the scope of that content. We have seen that in our institutions digital content is all around.

We have to re-program our digital filters, those within ourselves first, to allow our repositories to emerge and flourish. And we have to plan for digital abundance. If we do not, unsuccessful repositories will die, and successful repositories will be submerged under a flood of content.

Posted in Uncategorized.

Tagged with , , , .


DepositMO opens at OR2010 in Madrid

“Changing the culture, embedding deposit into the natural everyday workflow”

“#depositMO looks like a really exciting project”

DepositMO made its debut on the international stage at the Open Repositories 2010 conference in Madrid, from 6-9 July. Below is the slideshow and the Twitter commentary that accompanied the presentation.

A copy of the related short paper is available from the conference site. Original source materials are collected in our own digital repository, ECS EPrints at the University of Southampton.

[slideshare id=4743218&doc=or2010-pres-100713040238-phpapp01]

Twitterstream for this presentation

The following edited Twitterstream from Wed. 7th July 2010 is taken from the conference record on Twapper Keeper (hashtag #or10)

@stevehit Dave Tarrant about to talk on DepositMO #or10 (main auditorium). What’s that? A new JISC project. I’m involved! Oops, off to work @depositmo

@ianthe88 Looking forward to hearing about DepositMO – we’re (Edinburgh Uni) involved too 🙂

@gmcmahon #or10 Interactive Multi-Submission Deposit Workflows for Desktop Applications – paper… http://ff.im/-nkSie

@neilstewart #or10 Dave Tarrant, first on Tweet trends, then on desktop apps for deposit

@mjgiarlo Now at #or10: Dave Tarrant asked us all to tweet.

@neilstewart #or10 DepositMO, a new JISC project on incentivising deposit of researc in IRs

@dfflanders BitTarrant skewing his tweego results with a plug at the start of his#depositmo talk

@ianthe88 @davetaz: You have to provide the researchers with the tools they want or get what you need into the tools they’re already using

@neilstewart #or10 SWORD available in Word 2010, but SWORD a “fire and forget” tool with no feedback loop

@swordapp Dave Tarrant speaking now on the success of SWORD and the MS Word add-on

@clopezpe DepositMO “Changing the culture, embedding deposit into the natural everyday workflow”

@swordapp We’re looking at that for SWORD v2. See http://bit.ly/aPPraX RT @neilstewart: #or10 SWORD avail in Word, but SWORD a “fire and forget” tool

@depositMO Looks like SWORD is a key word for DepositMO project

@crisvaquer Tarrant: Office as a (client side) service

@depositMO Looks like Dave’s call for more tweets @ #or10 worked. Busy feed while he talks

@ptsefton Looks like we could use #depositmo approach/APIs in our desktop web work

@swordapp SWORD is always the key – RT @depositMO: Looks like SWORD is a key word for DepositMO project

@depositMO Not sure if this talk is the problem or solution spec for the project. Knowing Dave, that will be both

@neilstewart #depositMO looks like a really exciting project, will be keeping tabs on it

@clopezpe http:///blog.soton.ac.uk/depositmo

@ianthe88 Nicely done @davetaz on #depositmo – looking forward to seeing the result!

Posted in Uncategorized.

Tagged with , .


Project plan 7: budget

Note. Revised project dates – 1 July 2010 to 30 June 2011 – will affect the phasing of the costs between Y1 and Y2, but will not affect the totals.

Jun.10‐Mar.11

Yr1

Apr.11‐May.11

Yr2

Total FEC

£

Staff

89,373

18,478

107,851

Travel & subsistence

5,000

5,000

10,000

Other (Including Edinburgh
share £94,741)

19,795

81,946

101,741

Total incurred

114,168

105,424

219,592

Directly allocated costs

Personnel

20,359

4,207

24,566

Institutional estate

28,599

5,892

34,491

Total allocated

48,958

10,099

59,057

Indirect costs

General
services

74,721

15,393

90,114

Total FEC

237,847

130,916

368,763

JISC contribution

190,278

104,733

295,011

Institutional contribution

47,569

26,183

73,752

JISC contribution

80.0%

80.0%

80.0%

Posted in Uncategorized.

Tagged with , , , , , .


Project plan 6: timeline, workplan and workpackages

Timeframe: 2010-2011
DepositMO_Gantt

Deliverables

The following software deliverables are proposed:

D0. Interaction Specification: At the core of the project as required by all subsequent development, this deliverable will define the method for interaction between the client and server components required to build deposit directly into authors’ everyday workflows. Here clients are those defined by D1 (MS Office) and D4 (Operating Systems) and the servers are those consuming the content defined in D2 (EPrints and DSpace). A common and extensible specification is required to allow all of these softwares to interoperate. The development of this specification will be a beta after 4 months followed by an enhanced specification towards the end of the project.

D1. Office – Repository Conversation Addin: Allowing extended metadata, document components and multiple formats to be packaged into a single SWORD deposit. This is the desktop client side of the protocol. Three phases consist of scoping, developing and enhancing. See deliverable D2 for the matching repository server component.

D2(a/b). Repository Conversation Plugin: the repository software components that allow additional metadata and file formats to be requested for a SWORD package to interface with D1.

D3. Office Media Licensing Addin: similar to “Insert Picture”, except it takes CC images from Flickr / Google or purchased images directly from iStockPhoto. Also annotates all media (e.g. images pasted from Web Browser) with explicit provenance/rights management metadata.

D4. Desktop integration. This deliverable is similar to D1 except that the interaction is done directly with the operating system rather than office. Full interactivity should be available without the limitation of the office platform. Windows, MAC and Linux (Ubuntu) operating systems are in scope

D5. Repository Virtual File System: this deliverable has been dropped from the workplan.

The following training deliverables are proposed:

D6. Deskside coaching kit (DSC) consisting of technical training resources, academic how‐to materials and support and problem-solving documentation.

D7. Virtual kit (VDSC) consisting of web tutorials, short video walkthroughs, wiki supported by project team.

The following community activities are proposed:

D8. Researcher community workshops for archaeology, chemistry, materials science and educators.

D9. OfficeSWORD community building via Codeplex and DepositMO websites, and dev8D Code Dojo and Developer Challenge (2011).

The following reports are proposed, that include evaluation results:

D10. Analysis of culture change at Southampton / Edinburgh

D11. Analysis of culture change for discipline researchers

Deliverables D1, D3 and D4 are independent of the repository platform and will assume a primarily Windows/Office desktop environment due to the time restrictions of the project. Deliverable D2 is dependent on repository platform, and will be coded for both DSpace and EPrints.

Deliverable D9 will focus on building sustainable community of OfficeSWORD developers, in collaboration with Microsoft.

Posted in Uncategorized.

Tagged with , , , , , , .


Project plan 5: Team and end-user engagement

depositMO project team chart

Engagement with the Researcher Community: Effecting Culture Change

The aim of DepositMO is to effect culture change among researchers to use repositories in their everyday workflows. The key to the success of the DepositMO project will be the negotiation of a new relationship between researchers and the repository, including using the developed technology solutions. This project will seek to form deep engagements with researchers from a number of disciplines, a number of existing repository projects and a number of institutions.

The DepositMO user community will initially be drawn from researchers from across the Universities of Southampton and Edinburgh, with focus on disciplines which have investments in current JISC repository activities and multi‐institutional research user communities – in the areas of archaeology, chemistry, materials scienceand that are principal users of Microsoft Office. We are working with these user communities already as part of the JISC Institutional Data Management Blueprint (IDMB) project.

Teaching activities, across the disciplines, will be represented by the team responsible for the Southampton EdShare repository,  and the Humbox project.

Edinburgh University will represent a different repository infrastructure (DSpace).

The principal stakeholders are researchers and lecturers, and this project will aim at trainee and early‐career researchers, such as postgraduate students, postdoctoral research assistants and junior lecturers, who by definition have more time for engagement and who offer a greater chance of developing new practice. Our secondary stakeholders are librarians and repository staff (repository liaison officers and repository managers) who mediate, manage and offer leadership on repository engagement.

The major mechanism of researcher engagement undertaken by this project will be deskside coaching, i.e. face to face, one‐on‐one training and consultation. This is the recently established mechanism of the University of Southampton’s Library Repository Team and has also been adopted by the University of Edinburgh’s Research Publications Service.

Engagement methodology

i. Develop training resources (presentations, videos, web resources) in conjunction with the initial set of focus communities (Archaelogy, Chemistry, Materials Science, EdShare)

a. The resources will comprise a Deskside Coaching Kit (DSC) for use in one‐to‐one training and a Virtual DSC (VDSC) as a supplementary support resource that can be used by trainees and end users after their deskside sessions, that can be shared with colleagues, and that will be used in Graduate School research training modules.
b. The resources will focus on the extended repository capabilities developed by this project, and on those capabilities developed by other projects in the Deposit programme.

ii. Train the trainers (Southampton and Edinburgh library liaison officers)
iii. Run an in‐depth program of deskside training to whole University staff
iv. Monitor the effects of the training program, both qualitatively in terms of change of attitudes and behaviour and quantitatively in terms of the use of the repository
v. Roll out the program to the disciplinary research and teaching users.
vi. The developer community will be targeted through JISC mechanisms (e.g. dev8D), Microsoft Research, EPrints, and the researcher communities. We will take leadership of the OfficeSWORD open source project.

Close working relationships should exist between the 3 layers of the team (shown in the figure) with quarterly (or more) meetings involving all partners. The core investigators and project manager will interface discussion between developers and training/user team.

Posted in Uncategorized.

Tagged with , , , , , , .


Project plan 4: IPR

At the start of the project a detailed specification and description will be produced of all background intellectual property on software tools already developed and therefore owned by the University of Southampton and other partners and made available for use by the project.

Foreground IP emerging from the project will be identified and the ownership of the IP agreed. Typically, foreground IP is freely available to all parties to the project and for a predetermined period from the conclusion of the project.

The project will also publish guidelines on the commercial exploitation of the IP generated by the project and the benefactors thereof.

Software produced as part of the project will be based on open standards and released as open source. All software components will be distributed under the open source licenses favoured by their respective communities.

Office addins will be distributed through the Microsoft Research site for Scholarly Communications.

Software from the project will be added to the EPrints Services portfolio and maintained and developed by them.

Since it is open source, software will also be offered to other repository developers (e.g. DuraSpace and @mire) via an end‐of‐project workshop.

Licences

  • Code: multiple licences, GPL v3 where possible
  • Presentations and documentation: Creative Commons Attribution UK 2.0: England and Wales
  • Project content: Open Data Commons Attribution License

Posted in Uncategorized.

Tagged with , , , , , , , .


Project plan 3: risks and handling success

Risk Probability
(1-5)
Severity
(1-5)
Score
(P x S)
Actions
to Prevent/Manage Risk
Staffing 2 5 10 All project staff identified and available. Project Management from its existing staff. Strong project team culture already exists.
Organisational 1 3 3 Project Plan to clarify relationships and expectations between partners. Particular emphasis is being placed on advocacy and researcher
engagement.
Financial 1 5 5 Project Team has extensive experience with similar projects.
Technical 2 5 10 High level of expertise proven over several projects; most of technical
infrastructure is already in place to allow further workflow development to proceed effectively.
Legal 2 1 2 Institution has access to good legal support.

Evaluation

The project will employ a number of quantitative and qualitative evaluation metrics to ensure that we can judge the outcomes of the project:

i. Downloads and deployment of Office add‐ins.
ii. Number of deposits in repositories at Southampton University and Edinburgh University
iii. Number of deskside coaching sessions held.
iv. Downloads/views of virtual deskside coaching kits.
v. Pre‐ and post‐ DepositMO project interviews. In‐depth qualitative analysis of project impact amongst focus discipline researchers.
vi. Embedding of training in Graduate School (post‐Roberts funding), number of participants.
vii. DepositMO workshop for all stakeholders – participants and workshop feedback.

Sustainability will be supported through building developer community around the open source software outputs to this project. Microsoft Research has committed to working with us to ensure that the Office components continue to be disseminated through their channels. Server‐side functionality will be rolled into EPrints and DSpace as standard functionality. Deskside coaching will be embedded within our library service, and training material delivered through our Graduate School as part of compulsory courses. By working with key researcher communities directly we aim to drive culture change so that widespread usage will drive forwards further development and deployment.

Expansion: It is anticipated that a successful project should see an update similar to that of SWORD with a similar community wanting to get involved. All specifications with accompanying examples for the protocol developed will be published in an easy-to-read form such that others (both producers and consumers) can adopt the emerging technologies. Many relationships with others in a similar area (such as Peter Sefton), are already in place for the consideration and implementation of appropriate technologies from the start of the project to allow interested parties an easier implementation route from day one.

Posted in Uncategorized.

Tagged with , , , , , , .


Project plan 2: local and wider community benefits

Deposit MO extends the widely used Microsoft Office suite to enable seamless interaction with repositories to improve deposit usage. It therefore extends to all users of this in the UK and worldwide. Extending the Windows desktop impacts many users, with the back‐end services compatible with other operating systems. By targetting two repository architectures, EPrints and DSpace, and using SWORD and ORE protocols we ensure interoperability and sustainability in the long‐term.

Stakeholder analysis

A range of stakeholders in the research, repository and developer communities will be positively impacted by this project.

i. Researchers. By bringing the repository on to the desktop we can bridge the gap between everyday tools and web‐based services. By using deskside coaching we will try to effect culture change one person at a time, and providing Web‐based virtual coaching support will enable wider rollout.
ii. Repository support staff. Librarians and information workers will be involved in developing training materials, and deploying them at Southampton University and Edinburgh University. By collaborating across institutions we aim to make these training materials generic for widespread adoption across the higher education sector.
iii. Developers. Our software outputs will be open source, and we expect to increase usage by explicitly supporting the developer community around OfficeSWORD. Microsoft Research will actively disseminate our work. Will work with JISC, at events such as dev8D Code Dojo and Challenges, and within the EPrints and DSpace communities to raise awareness.
iv. IT Services. University of Southampton IT service, iSolutions, has committed to deploy DepositMO add‐ins campus‐wide as part of its standard software deployment on all University workstations.

Posted in Uncategorized.

Tagged with , , , , , , .


Project plan 1: aim, objective and outputs

DepositMO riangle schematicThe DepositMO project aims to develop an effective culture change mechanism that will embed a deposit culture into the everyday work of researchers and lecturers. The proposal will extend the capabilities of repositories to exploit the familiar desktop and authoring environments of its users. The objective is to turn the repository into an invaluable extension to the researcher’s desktop in which the deposit of research outputs becomes an everyday activity. The target desktop software suite is Microsoft Office, which is widely used across many disciplines, to maximise impact and benefit. Targeting both EPrints and DSpace, leveraging SWORD and ORE protocols, DepositMO outputs will support a large number of organisations. The ultimate goal is to change the Modus Operandi of researchers so that repository deposit becomes standard practice across a wide number of disciplines using familiar desktop tools.

Aim and objectiv

The aim of this proposal is to develop an effective culture change mechanism that will succeed in embedding a deposit culture into the everyday work of researchers and lecturers. To make this possible, our objective is to extend the capabilities of repositories to exploit desktop and authoring environments and to turn the repository into an invaluable extension to the researcher’s desktop to address apparent repository weaknesses.

The universal model of repository engagement serves the research community poorly. Emerging from post‐publication library acquisition models (e.g. OAIS), all the work, research and creative effort happens beyond the borders of the repository. It is the finalized research outputs that are currently accommodated in our systems. Only when the research and writing have finished can an individual item be individually uploaded and tagged. To address this situation, the repository needs to provide services that are relevant for researchers.

The typical researcher uses ‘office’ applications to create and edit papers, reports, presentations, posters and teaching materials on their computer desktop. Consequently, the repository must provide better services for the desktop and for office documents. These services should not just be inward looking to make the repository better accommodate office documents, but make the repository a useful source of novel functionality that assists researchers in their daily tasks, including collaboration.

Outputs

A new high‐bandwidth bridge that connects the users’ desktop environment to the repository will be constructed to overcome the specific deficiencies described above that are seen as key barriers to repository deposit, consisting of three parts:

i. a set of components for the Microsoft Office authoring environments and the underlying operating system, such as the Windows Explorer or Mac OS Finder
ii. a suite of enhanced services provided by the repository that work with the desktop/office enhancements and an enhanced SWORD interaction
iii. a bulk upload utility that matches material on the desktop with records in the repository to support away‐from‐office scenarios (e.g. extended archaeological digs) and end‐of-project deposit.

Technology is only part of the solution: An equally important part of this proposal is to help to change the Modus Operandi of the researcher using the following approaches:

i. coaching them to make use of (and hopefully to depend on) the repository for their daily activities. This will be achieved by an expert team, working closely with groups of researchers and library/repository staff to introduce new software and negotiate new working practices.
ii. raising awareness of what is possible in target user communities in archaeology, chemistry, materials science and humanities through existing researcher networks with whom the project team is already working closely.

Posted in Uncategorized.

Tagged with , , , , , , , .