BHL
Archive
This is a read-only archive of the BHL Staff Wiki as it appeared on Sept 21, 2018. This archive is searchable using the search box on the left, but the search may be limited in the results it can provide.

TechCall_01may2017

Agenda
Dial: 1-877-820-7829
Enter the passcode: 407326

1. Articles and PDFs: revisit if this is a task for BHL Egypt http://biodiversitylibrary.countersoft.net/workspace/828/item/59005
Less of a standalone project, more integrated into overall website.
Martin - fine with moving back to Mike, especially if can move it forward.
Storing metadata from downloads - are we doing this? We retain it but we don't use it to define segments
Stored in a table, in PDF table.
Currently tied to a range of volume and issue numbers, not single volumes or issues
A long time ago Bianca did an analysis of that and quality was mixed; Trish, we viewed it as good enough to help find the articles.
We changed interface to ask people to add that metadata
If they're going to take the time to do it, they would probably do it right.
But they don't have a box for volume, or for issue. They're not instructed to invert author name.
If we aren't going to use it, we should remove the message that says we'll use it to help others.
We'll revisit at a later time.

Article stuff confirmed to go to Mike.

2. KBART check-in
Have started work on 1 or 2 Gemini issues related to KBART. Overall, proposed timeline still makes sense.

3. Implementing BioStor-like article definition in BHL
Started documentation on EABL process. Mike's concern that too many partners might be getting on board with a process that was never meant to be scalable. So we started discussing what the requirements would be for defining at batch level. Related to some work that Joel and Kristina were doing. But the focus for this is on existing content, rather than new.
Discussed having TSV files with a list of fields that we've identified that we think will be needed; Susan is working on the documentation.
Also discussed whether there were chunks of Rod Page's code that could be incorporated. Investigation was needed.
Trade offs would need to be made; asking user for start page vs time and effort into programming/development
Need to coordinate with whatever Joel is doing with Macaw so that it matches same terminology as in Admin Dash
Joel does not yet have documentation for the work he and Kristina are doing; once ready that can inform how to display in Admin Dash

Joel is reviewing fields that Trish collated to determine which to send over to IA
Susan reviewed that documentation and realized that we really will need volume and issue number in cases where container is for a range. container = BHL item

Nicole Kearney will be sending a TSV file for Susan to add to BHL; will give a sense of how well EABL process would work for Nicole

Where does this fall on levels of priority?
For EABL it's not a priority. We're working successfully with Rod. Though he's been away a few weeks now and it is dependent on him.

Martin - let's move to a fairly higher priority for Mike.
Mike knows where the code is and understands the process which involves a bit of manual processing

If we asked people to provide page info etc, would that cut back on manual work?
Yes.
If page info could be supplied, it would help.

Is what we create, can he then harvest what we generate?
Mike just completed adding ability to spit out RIS files, we're really close to using BHL APIs to generate what Rod needs
We'll want to be careful not to duplicate harvesting from BioStor things that we already have.

4. Full-Text Search - Should we allow wildcards and basic AND/OR searches?
Yes, why not.
Multiple ways to build queries so just wanted to confirm what we wanted users to do.
Martin says yes let's do that.

On the notes from the Singapore meeting, BHL Egypt would join for some tech calls.
Once we get the work package proposal from them and it's all signed off, Ahmed may join us once a month or as needed.

Full text search -- order has been sent to Dell
8-11 days for construction and delivery
Then tagged, inventoried, configured and installed at OCIO