Hydra Newspapers Interest Group Call: 2017-02-02
Time: 1:00 PM EST / 10:00 AM PST
Call-In Info: 712-775-7035 (Access Code: 960009)
Moderator: Eben English (Boston Public Library)
Notetaker: TBD (Etherpad link: https://etherpad.wikimedia.org/p/Hydra_Newspapers_Interest_Group_Call__2017-02-02)
Attendees:
- Eben English (BPL)
- Joshua Allan Westgard (Maryland)
- sanderson (BPL)
- Betsy Post (Boston College)
- Jenn Colt (Cornell)
Agenda:
- BPL-Utah grant update
- submitted on january 13, thanks for looking at the draft and offering comments
- should hear something April-ish
- PCDM discussion continued
- Examples:
- U. of Maryland: https://wiki.duraspace.org/download/attachments/77447979/maryland2016hyrdraconnect.pdf
- Nat'l Library of Wales:
PCDM Mapping for Welsh Newspapers (NLW)
- U. of Maryland: https://wiki.duraspace.org/download/attachments/77447979/maryland2016hyrdraconnect.pdf
- memberOf vs. relatedObjectOf
- Discussion inclusive but heading towards memberOf for it sounds like
- POST-MEETING UPDATE 03 Feb 2017: U. Maryland has decided to go with what seems like the consensus view (pcdm:hasMember) of the best fit for relating articles to issues.
- Use Article object class to distinguish from Page
- UM: bibo:Article (http://purl.org/ontology/bibo/Article)
- could use pcdm:Range?
- Discussion inclusive but heading towards memberOf for it sounds like
- connecting Article objects to Pages
- NLW: mapping shows article object but not really a relationship to the page object, just to the issue
- IANA describedBy
- For locating specific articles, Maryland is planning to use search of OCR inside the issue as a secondary lookup
- Source data from vendor has article list, but does not include relationship of articles to image files
- Source data from vendor has article list, but does not include relationship of articles to image files
- NLW: mapping shows article object but not really a relationship to the page object, just to the issue
- use of Works extension models
- Not lots of replies from the pcdm group but no plans to get rid of works extension or range class
- pcdm:Range
- pcdm:Range is a section of the work corresponding to IIIF range
- pcdm:Range is a sub-class of object
- pcdm:Range can have member filesets, seems like we'd have member page object that then have member filesets? Discuss more.
- Page object relationship to article: would need to be ordered
- Would proxies be necessary here? May not be use case for alternate ordering of small sequence.
- IIIF Range/Sequence/Canvas
- http://iiif.io/api/presentation/2.0/#ranges
- Don't know if there's anything indicating canvas order
- Sequence of canvases but the canvases don't say anything about order
- Most people are generating IIIF dynamically. Maybe storing it you can have more relationships and modeling? Unsure.
- Shared canvas ontology does have sequence class
- pcdm:Range is a section of the work corresponding to IIIF range
- Eben will go back with more questions to the PCDM google group re: Article-Page relationship
- Examples:
- List of requirements:
Features & Requirements
- keep adding feature requests and indicating interest
- Eben will send to hydra lists to get more involvement
- Intel sharing from other groups
- IIIF Newspapers Interest Group
- starting a Text Granularity Technical Group to deal with searching for text within images
- https://docs.google.com/document/d/1wTxgcj-AlAE3KwcxP59mTZhOOQKkDEaqwVK_NHOIRvc/edit?usp=sharing
- talk about what type of text search results to return - paragraph, line or word level
- elminate need for API to ALTO data
- starting a Text Granularity Technical Group to deal with searching for text within images
- Hydra plugins group
- https://github.com/projecthydra-labs/hydra_plugins_wg
- current discussions in that repo
- IIIF Newspapers Interest Group
- Next meeting: Thursday March 2, 1 PM EST