Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Open-ONI
(Online Newspaper
Initiative)
Adapting chronam for State Use
Karen Estlund, OR/PA
Sheila Rabun, OR
Overview
● Who: 15 participants from 10
organizations
● What: Developers meeting to
tackle goals
● When: July 23-24, 2015
...
State-Based Fork for chronam
● New organization
open-oni (online
newspaper initiative)
created in Github and
forked chrona...
Community-managed Group
● Community-managed group and participants for state-based fork
○ Members added to https://github....
Slack: http://open-oni.slack.com
Features and Development Plan
● Feature-set agreement and development plan including timeline (e.g.
county browse, OCR edi...
Milestones 1. Minimum viable product (April 2016)
bug fixes, upgrades to libraries, current
state-based features from part...
Hosting Solution
● Plan and timeline for Amazon Machine Image
(AMI) for state-based projects who cannot
host locally
○ Uti...
Road Map for Compatibility
● Road map for compatibility with communities of practice (IIIF and DPLA)
○ Data model: https:/...
DPLA Data Model
Discarded Adaptation
Data Model
IIIF Mapping
Newspapers IIIF
Title Collection
Issue Manifest
Edition Manifest
Article Range
Page Canvas
Image Image
Alto A...
Minimally Conforming Metadata
{
"@id": "uri-for-title",
"@type": "Title",
"label": "Name of Newspaper",
"location": "Somew...
Next Steps
● Call in October 2015
● Tickets Assigned
● Sprint (schedule TBD at Oct. meeting)
Upcoming SlideShare
Loading in …5
×

Open-ONI: Online Newspaper Initiative

573 views

Published on

Review of Developers Meeting to fork chronam software for state based usage for serving digital newspapers. https://github.com/open-oni

Published in: Education
  • Be the first to comment

  • Be the first to like this

Open-ONI: Online Newspaper Initiative

  1. 1. Open-ONI (Online Newspaper Initiative) Adapting chronam for State Use Karen Estlund, OR/PA Sheila Rabun, OR
  2. 2. Overview ● Who: 15 participants from 10 organizations ● What: Developers meeting to tackle goals ● When: July 23-24, 2015 ● Where: University of Oregon Knight Library in Eugene, Oregon ● Why: To make chronam more accessible to states for NDNP content and beyond Goals: 1. Create a roadmap for extension of the LC Newspaper Viewer software (chronam) for state- based use 2. Plan for interoperability with communities of practice 3. Create a community development process 4. Engage the community
  3. 3. State-Based Fork for chronam ● New organization open-oni (online newspaper initiative) created in Github and forked chronam repository: https: //github.com/open- oni/open-oni
  4. 4. Community-managed Group ● Community-managed group and participants for state-based fork ○ Members added to https://github.com/open-oni/ and assigned issues ○ Community development guidelines adopted ○ Slack channel created: http://open-oni.slack.com ○ Continued use of chronam-users listserv to engage with wider community: http://listserv.loc.gov/archives/chronam-users.html ○ Quarterly gatherings to be set-up; notice to go out on chronam-users listserv - Sheila Rabun will set up first meeting for mid to late October 2015
  5. 5. Slack: http://open-oni.slack.com
  6. 6. Features and Development Plan ● Feature-set agreement and development plan including timeline (e.g. county browse, OCR editing, collaborator attribution tags) ○ Feature-set issues were added to Github issues with four milestones based on priority ○ All issues for initial milestone 1: minimum viable product were assigned ■ Minimum Viable Product deadline: April 1, 2016 ■ Prioritized in this milestone: bug fixes, upgrades to libraries, current state-based features from participants
  7. 7. Milestones 1. Minimum viable product (April 2016) bug fixes, upgrades to libraries, current state-based features from participants 2. Integration of existing features rights display, Common title display, ingest validation levels, etc. 3. Enhanced features enhance advanced search, remove dependency on marc record, etc. 4. Wishlist crowd source OCR correction, admin interface, etc.
  8. 8. Hosting Solution ● Plan and timeline for Amazon Machine Image (AMI) for state-based projects who cannot host locally ○ Utilize Docker for ready to install version: https://github.com/open-oni/docker-open- oni and https://registry.hub.docker. com/u/openoni/open-oni/ ○ AMI to be released after Minimum Viable Product is Ready: May 2016
  9. 9. Road Map for Compatibility ● Road map for compatibility with communities of practice (IIIF and DPLA) ○ Data model: https://github.com/open-oni/model ○ Issues for development added to https://github.com/open-oni/open- oni/issues ○ Recommendation for IIIF compatibility to serve DPLA
  10. 10. DPLA Data Model
  11. 11. Discarded Adaptation
  12. 12. Data Model
  13. 13. IIIF Mapping Newspapers IIIF Title Collection Issue Manifest Edition Manifest Article Range Page Canvas Image Image Alto Annotations
  14. 14. Minimally Conforming Metadata { "@id": "uri-for-title", "@type": "Title", "label": "Name of Newspaper", "location": "Somewhere, SW", "issues": [ { "@id": "uri-for-issue", "@type": "Issue", "label": "Name for Issue", "date": "1920-04-01" } ] }
  15. 15. Next Steps ● Call in October 2015 ● Tickets Assigned ● Sprint (schedule TBD at Oct. meeting)

×