baton slides from open repositories 2016

25
Baton Lightweight, Service- Oriented Workflow Management John P. Bell | @nmdjohn Jen W. Green | @greenjenn Dartmouth College June 15, 2016 – Open Repositories 2016

Upload: nmdjohn

Post on 11-Apr-2017

156 views

Category:

Technology


1 download

TRANSCRIPT

Page 1: Baton slides from Open Repositories 2016

BatonLightweight, Service-Oriented Workflow ManagementJohn P. Bell | @nmdjohnJen W. Green | @greenjennDartmouth College

June 15, 2016 – Open Repositories 2016

Page 2: Baton slides from Open Repositories 2016

Dartmouth’s Repository

Harvester Metadata Repository

Page 3: Baton slides from Open Repositories 2016

Dartmouth’s Repository

Page 4: Baton slides from Open Repositories 2016

Dartmouth’s Repository

PIDs Metrics

Page 5: Baton slides from Open Repositories 2016

Dartmouth’s Repository

HRMS

Banne

r

OBIE?

SHARE?

EVERY

DATABASE

FOREVER Faculty

OA Repos

Librarians

Page 6: Baton slides from Open Repositories 2016

Dartmouth’s Repository

Data is…not consistent across sourcesbeing reused from different contextssometimes completely missingtracked across different systems for the same object (Linked Data!)

Page 7: Baton slides from Open Repositories 2016

Good News!

Humans: Still Necessary

Page 8: Baton slides from Open Repositories 2016

Dartmouth OA

The Council on Libraries, in conjunction with the Dartmouth Library and others, will develop and monitor a plan for a service or mechanism that would render implementation of the policy as part of the Open Digital Repository for Dartmouth Scholarship as convenient for the faculty as possible. - Dartmouth Open Access Policy, pg. 2

Page 9: Baton slides from Open Repositories 2016

Article Workflow

Page 10: Baton slides from Open Repositories 2016

Elements

Page 11: Baton slides from Open Repositories 2016

Metadata

Page 12: Baton slides from Open Repositories 2016

Licensing

Page 13: Baton slides from Open Repositories 2016

Baton

Page 14: Baton slides from Open Repositories 2016

Baton

Page 15: Baton slides from Open Repositories 2016

Design Principles

Assistive not automatedSoftware coordinates, humans executeTrust the humans

Integrated–sometimesHumans want workflow, but in contextNeed backstop for third party systems

Workflow as a serviceSeparated concerns

Page 16: Baton slides from Open Repositories 2016

Architecture

Page 17: Baton slides from Open Repositories 2016

Architecture

Page 18: Baton slides from Open Repositories 2016

Architecture

Page 19: Baton slides from Open Repositories 2016

API

API ClientsWhitelisted systems/keysEnd-user agnostic (johnbell@dac, johnbell@lna)

API ActionsTrust the request

Object IDsReference URIApplication URL

Page 20: Baton slides from Open Repositories 2016

Workflows

Page 21: Baton slides from Open Repositories 2016

Workflow Rules

Workflows are linear…but they have logic to trigger other workflows…and can be initiated at arbitrary steps

Workflows are tied to systems…but require a Reference URI to pass between them

Workflows are instantiated …so receipts are kept and notes passed

Page 22: Baton slides from Open Repositories 2016

User Interface

Page 23: Baton slides from Open Repositories 2016

Admin Interface

Page 24: Baton slides from Open Repositories 2016

Where’s the code?

HRMS

Banne

r

OBIE?

SHARE?

EVERY

DATABASE

FOREVER Faculty

OA Repos

Librarians

Page 25: Baton slides from Open Repositories 2016

Thanks!

Thanks to Carla Galarza and Eric Bivona (Dartmouth Library Technology Group) for all their work on LNA.

Thanks to Jeremy Friesen (Notre Dame), whose HydraConnect 2015 presentation on their Sipity tool helped inspire parts of Baton’s design.

Questions?

John P. Bell | @nmdjohn | [email protected] W. Green | @greenjenn | [email protected]

Github: https://github.com/DartmouthDSC/ …soon!