TechCall_18jun2018
Agenda
Update on API v.3
Re-worked a bit. Search methods still have a little uncertainty. API should be parallel. Will be dependent on completion of the full text advanced search functionality and UI.
Recent feedback on full text search
Debrief on Joel and Carolyn's discussion with Martin
Summary:
- Advanced search bug where results are not limited to exact string matches within quotes, or limited to the field that is being searched. (79381, 79358; 79400, 79375).
Decision: To be worked on the next opportunity Mike has between work on priority tasks (e.g., API v3 and transcriptions; and before work on DOI assignments)- Example: within Publication tab, enter in Title field "memoirs of the geological survey of south africa" (including quotes). Returns results with "memoirs of the geological survey of india" in title and in Details. The portion that matches is bolded. But it does not limit results only to those with the full string as a match as it should. To confirm, searched inside 3 volumes of “… india” and no matches for the full string including south Africa. South Africa on it’s own is found inside some of them. Looked at volumes 8 (no match for south Africa inside), 10 (no match for South Africa inside), 3 (South Africa mentioned on page 199).
- Susan: Supports the Hathi Trust approach.
- Sort results - 79402 - won't address in short term.
- Export results - 79402 and 79369 - Joel proposed using an API call to download results in a new window. What format is useful to people? APIs support JSON, XML, and SOAP. JSON may be useful to non-techie. Most users might be looking for csv. Would just use API to transform results to whatever we want to present to user.
- Link to old interface - August 7; look into how frequently old interface is still being other used.
Transcriptions
Estimating launch date so Grace can plan announcements
Announcing tool to staff and presence of transcriptions to public.
Moving Walls (
58083) - links to content on publisher/rights holder website that is more recent than what would be available in BHL
Decision: (from discussion with Martin) To be worked on after Transcriptions, before DOI assignments.
Follow up on action items from prior calls
- All review comments added to Transcription Requirements and respond as needed.
- Susan will talk to Diane Rielinger about using page prefix to add MM-DD info (aiming for 3pm on 6/11).
- Page prefix is not the issue. Diane is using batch definition tool very heavily; happen to be individual archival letters. She can't upload via the tool if it doesn't have conventional year and some are undated. If I went into Admin Dash - can i put word 'Undated' in the year field? Is the tool consistent with the validation used in Admin Dash? Needs more investigation. Carolyn add the Gemini number back in.
- Carolyn to loop Bianca back into the Gemini ticket on date issues with MODS exports.
- Carolyn to follow up with Bianca on Supplement.
- Carolyn to update Gemini tickets to indicate these will be on hold for the time being.
- 60989 and 60752: Carolyn will clarify with Bianca what is needed for resequencing. Fairly complicated to implement.
- 60922 : Mike will create an indicator at the item level in the admin dash to prevent ingest of article metadata from external sources such as BioStor. Involves database changes, changes to Admin site, and BioStory processes.
- For June 25 or later: Susan will consult with Cataloging Group on status of author name work. (They have a call in about two weeks from now; Tech Team will revisit after that call)
Action Item
Susan will look for a Gemini issue and verify this is still a problem (See transcription document)
