sword & resourcesync - stuart lewis

13
Stuart Lewis Library & University Collections Information Services, University of Edinburgh * SWORD & ResourceSync @swordapp / #swordapp #resourcesync

Upload: repository-fringe

Post on 26-Jan-2015

108 views

Category:

Education


4 download

DESCRIPTION

Stuart Lewis, University of Edinburgh's presentation on SWORD & ResourceSync. This was presented on Thursday 1st August 2013 at Repository Fringe 2013

TRANSCRIPT

Page 1: SWORD & ResourceSync - Stuart Lewis

Stuart Lewis

Library & University Collections

Information Services, University of Edinburgh

*SWORD & ResourceSync

@swordapp / #swordapp

#resourcesync

Page 2: SWORD & ResourceSync - Stuart Lewis

*Opposites

*Technical introduction

*SWORDv2

*ResourceSync introduction

*Comparison

*Demo?

*Purpose: introduce ResourceSync, understand the key functions of SWORD and ResourceSync, and how they can work together

Page 3: SWORD & ResourceSync - Stuart Lewis

*Technical Introduction

*It’s useful to know about CRUD!

*Create

*Read

*Update

*Delete

Page 4: SWORD & ResourceSync - Stuart Lewis

*Technical Introduction

*Also useful to know about HTTP verbs

*GET – retrieve information

*POST – create new content

*PUT – update or create new named content

*DELETE – delete existing content

*…others (HEAD, TRACE, OPTIONS, CONNECT, PATCH)

Page 5: SWORD & ResourceSync - Stuart Lewis

*Technical Introduction

*Also useful to know about HTTP response codes

*404 Not Found

*200 OK

*201 CREATED

*202 ACCEPTED

*200s = good, 300s = further actin required, 400s = client error, 500 = server errors

Page 6: SWORD & ResourceSync - Stuart Lewis

*SWORD

* SWORD

*Simple Web-service Offering Repository Deposit

*Create objects in repositories

*Interoperability

*A protocol, not a piece of software!

Page 7: SWORD & ResourceSync - Stuart Lewis

*SWORDv1 and v2

*SWORDv1

*Create

*Read

*SWORDv2

*Create

*Read

*Update

*Delete

Page 8: SWORD & ResourceSync - Stuart Lewis

*ResourceSync

*Synchronising web resources

*Generic web problem

*Applicable to repositories

*Can be used as OAI-PMH replacement

*Find changes items:

*Files or metadata or both

*Lots of use cases:

*Archiving, mirroring, statistics gathering

*NISO / OAI initiative + Sloan funding

*JISC input + funding (implementations)

*Interoperability

*Not a piece of software!

Page 9: SWORD & ResourceSync - Stuart Lewis

*ResourceSync

*Layers of the protocol:

*Discovery

*Capability description

*Baseline sync

*Changelists

*Dumps

Page 10: SWORD & ResourceSync - Stuart Lewis

*ResourceSync

*Based on sitemaps:<url>

<loc>http://example.com/res2_dublin-core_metadata.xml</loc>

<lastmod>2013-01-02T19:00:00Z</lastmod>

<rs:md change="updated"

type="application/xml"/>

<rs:ln rel="describes"

href="http://example.com/res2.pdf"

modified="2013-01-02T19:00:00Z"

hash="md5:1584abdf8ebdc9802ac0c6a7402c03b6"

length="8876"

type="application/pdf"/>

</url>

Page 11: SWORD & ResourceSync - Stuart Lewis

*SWORD & ResourceSync

*SWORD

*Putting things INTO a repository

*POST / PUT / DELETE

*ResourceSync

*Discovering what is in a repository and what has changed

*GET

Page 12: SWORD & ResourceSync - Stuart Lewis

*Feeling brave?

*Example:

*arXiv ReosurceSync feed:

*http://resync.library.cornell.edu/

*Mirror into local DSpace using SWORD:

*Spare time + brave enough for demo?

Page 13: SWORD & ResourceSync - Stuart Lewis

*Further information

*SWORD: swordapp.org

*ResourceSync: www.niso.org/workrooms/resourcesync/

*OAI-PMH using ResourceSync: cottagelabs.com

*ResourceSync use cases: Ariadne Issue 70

*SWORD & ResourceSync: blog.stuartlewis.com