from chronam to oni: the path to self-sufficiency in
TRANSCRIPT
Portland State University Portland State University
PDXScholar PDXScholar
Online Northwest Online Northwest 2018
Mar 30th, 2:15 PM - 3:00 PM
From Chronam to ONI: The Path to Self-Sufficiency From Chronam to ONI: The Path to Self-Sufficiency
in Newspaper Digitization in Newspaper Digitization
Sarah Seymore University of Oregon, [email protected]
Follow this and additional works at: https://pdxscholar.library.pdx.edu/onlinenorthwest
Let us know how access to this document benefits you.
Seymore, Sarah, "From Chronam to ONI: The Path to Self-Sufficiency in Newspaper Digitization" (2018). Online Northwest. 17. https://pdxscholar.library.pdx.edu/onlinenorthwest/2018/presentations/17
This Presentation is brought to you for free and open access. It has been accepted for inclusion in Online Northwest by an authorized administrator of PDXScholar. Please contact us if we can make this document more accessible: [email protected].
From Chronam to ONI: The Path to Self-
Sufficiency in Newspaper Digitization
Sarah Seymore
Digital Collections Metadata Librarian
Program Manager, ODNP
March 30, 2018
https://oregonnews.uoregon.edu/
Timeline and page counts
● Over 900,000 pages since 2009
● Over 80,000 pages of current newspapers
https://github.com/open-oni/open-oni
What’s
different?
What are the
benefits?
● More flexibility with theming/better
customization, and static pages and
plugins for website features
● The out-of-the-box ONI template is
modern, clean, and already
bootstrapped.
● RAIS image server
● IIIF presentation API in place
● Nearly turn-key
● Batching is nearly the same as
Chronam
● Better cost of upkeep and ability to
have integrated code with the core
code.
https://oregonnews.uoregon.edu/
Old website design
https://oregonnews.uoregon.edu/
https://oregonnews.uoregon.edu/
https://oregonnews.uoregon.edu/
https://oregonnews.uoregon.edu/map
https://oregonnews.uoregon.edu/titles_by_location
https://oregonnews.uoregon.edu/issues/
https://oregonnews.uoregon.edu/
Suggestions and Lessons Learned
Suggestions
● Have good, clear, relevant
ROI
● Don’t forget to build in
research time!
● Have an internal and external
communication plan in place
● Do not disrespect the
timebox of the sprint!
Lessons
Learned
● Thoroughly compare the
template and UX needs
● Prepare for debugging and
troubleshooting period
● Did you lose anything?
● How far are you looking
ahead?
https://github.com/uoregon-libraries/newspaper-curation-app
Publishers
Automation
Student/manual work
Newspaper Curation Application
SFTP reports
Metadata Entry and Review Queues
Metadata Entry
Metadata Entry
Metadata Review
Users and Permissions
Titles List
MARC org codes
An issue live on the website!
What’s next?
● UX testing
● More user stories and
promotion!
● Fundraising how-to-guide
● More current publishers
● Public survey
● Diverse and inclusive
content
● Continue to refine systems,
workflows, and decrease
errors
https://odnp.uoregon.edu/
https://odnp.uoregon.edu/fundraising-and-grant-writing-how-to-guide/
What’s next?
● UX testing
● More user stories and
promotion!
● Fundraising how-to-guide
● More current publishers
● Public survey
● Diverse and inclusive
content
● Continue to refine systems,
workflows, and decrease
errors
● ONI community sprint?
Other
takeaways
● Everything costs money
● Get used to admins asking
for user stories and
demonstrable cases of reuse
● Have a lot of transparency
and get used to it
● ROI is important
● There is never too much
promotion
● Remind people that you are
still figuring it out, and
remember that that is OK
