...
| Table of Contents | ||
|---|---|---|
|
...
09-
...
12-18 (AGENDA)
Present: Joshua, Don, Autumn, Dao, Kay, Ranti, Lisa S., Lee, Lisa R., Brooke, Don T.
Regrets:
Agenda
- Edit and Approval of all previous minutes and publish
- Last look at Sierra Permissions document before checking with Terri Miller https://docs.google.com/document/d/1KDOBD_DCOE3qXdTqHJmglsQsnYtsqHVbzycWgUcZUBk/edit?usp=sharing
- Progress on "Who Does What" page?
Action items
- Action 1
- Action 2
- Action 3
Decisions
- Decision 1
- Decision 2
- Decision 3
TS Council 09-05-18
Present: Dao, Kay, Ranti (notes), Nicole, Lisa S., Lee, Lisa R., Brooke M. (Law Library)
Regrets: Joshua, Autumn, Tad, Don, Tim, Emily
Agenda
- III API. What can it do? (Dao)
- API: application programming interface, a web service that allows one to access "backdoor" of a system instead of using the public interface.
- Sierra API has been around for quite sometime.
- We don't have all possible endpoints yet. Innovative adding them for each Sierra update.
- Our library catalog already utilizing the API
- Google Book API: linking to Google Book limited preview or full text, depending on the availability on Google Books
- OCLC/Worldcat citation API. Showing the link to the Worldcat citation if available.
- Sierra API documentation: https://techdocs.iii.com/sierraapi/Content/titlePage.htm
- Sierra API access https://magic.msu.edu/iii/sierra-api/swagger/index.html (will need an API Key in order to access the data)
- Input/output format: the API is based on RESTful API, takes text queries or JSON in some cases
- API endpoints provide results in JSON and XML format
- Acquisition and Circulation have CRUD (Create, Read, Update, Delete) access
- Bib records only have Read access
- Sierra API is also accessible through browser plugins (Firefox RESTClient and Chrome Advanced REST Client)
- You will need to convert the key:secret into base64 strong by using the Based64 Encode and Decode online utility
- The API set up can be granular so only certain access can be granted.
- What III products have we purchased that we do not use? A reminder in case we see products differently now. (Dao)
- Metadata Builder: a program that helps build Dublin Core with OAI-PMH capability.
- We used to use it to harvest EAD from VVL finding aids (around 2003?) to create collection-level MARC records. These MARC records have been largely (but not entirely) replaced by item-level records, and most of the collection-level records are now suppressed or deleted.
- If we move to a different catalog system in the future, we should consider whether we still need the few remaining collection level records.
- Media Management: a product to add digital files to the catalog.
- We used to use it to store digital files on the catalog server and link those files to catalog records. The linked digital objects show up as thumbnails in OPAC catalog records.
- We used this program for a pilot project (around 2002?) to display digitized book covers. Lisa R. thinks these book cover links may have been removed from the catalog records. Now we use the Syndetic Solutions service to show book covers.
- The alternative to using Media Management is to supply a link to a digital object in the catalog record using the 856 field. This method does not provide a thumbnail preview of the image.
- There are several others, but these two products are the biggest.
- Metadata Builder: a program that helps build Dublin Core with OAI-PMH capability.
- TS Who Does What page
- Currently on the TS Drupal page: https://lib.msu.edu/tsarchive/techservices/whodoeswhat/
- Each unit will review their section and decide how they want the information to be displayed.
- Sierra server updates:
- Operating system upgrade: Dao is hoping to be done next week; still waiting for ITS on the exact date.
- After the upgrade, we will have the ability to add more material types.
- Test server: III is still working on loading the old data to populate the test server.
Action items
- Unit Heads will review their sections of the "Who Does What" page.
- Kay will ask for feedback from other Departments.
08-29-18
Present: Joshua, Don, Dao (notes), Kay, Ranti, Lisa S., Lee, Lisa R.
Regrets: Autumn
Agenda
- Review minutes from August 15, 2018 (Below this agenda)
- Last look at 2018/2019 Technical Services G & O's https://docs.google.com/document/d/1QlvpKLUH6J5OffeP8zs3isF2nLtrRRcMwUKqxUPbM2A/edit
- Sierra Permissions Document https://docs.google.com/document/d/1KDOBD_DCOE3qXdTqHJmglsQsnYtsqHVbzycWgUcZUBk/edit?usp=sharing
- Any issues for this Friday's football game from your area?
- TS Manager's time slot for this semester
Action items
- Action 1
- Action 2
- Action 3
Decisions
- Decision 1
- Decision 2
- Decision 3
- Ranti will created the Drupal page for the 2018/2019 TS Gs & Os
- Kay will contact Emily Sanford about fine tuning our process for publishing minutes in Confluence.
...
08-15-18
...
Present: Kay, Joshua, Don, Autumn,, Ranti, Lisa S., Lee
...
- Kay
- availability update
- will be meeting with John Straw soon from Ex Libris
- Joshua
- reindexing testing done; several issues identified that Innovate will need to address
- 490 still not indexing in title or series as planned
- Lucas discovered that portions of $0 and $1 URI character strings are searchable in the keyword (i.e., search for "authorities" gets lots of hits)
- reindexing testing done; several issues identified that Innovate will need to address
- Don
- project to update records for materials in Remote to circulate for 6 months instead of shorter loan periods
- mostly applies to serials records, since usually those only circulate for 21 days
- about 300k records
- project to update records for materials in Remote to circulate for 6 months instead of shorter loan periods
Action items
- Autumn – create separate drop-down for TS GOs on Drupal page & post finalized 18-19 GOs when prepared (edit: Ranti posted the finalized version)
- Various managers – edit Confluence procedures to replace names of retirees
...