🛈 Wiki Tips

(1) Is your name in Wiki displaying only your last name? Or is your name in Wiki displaying as you user account id? Need to update your name in Wiki so colleagues can find you? Want to upload a photo? See Personal Settings in the updated FAQ in Wiki Help.
(2) Can't find a user to add to your wiki space? See what you can do when User cannot be found via search .
Child pages
  • January 23, 2019: Calisphere/DAMS/OAC Update

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

TopicIn briefAction items
Harvesting Updates
  • UC San Diego--Research Data Curation & Digital Library Development collections, UC Davis--Sherry Lehmann Wine Catalogs, UCSB--Art, Design & Architecture Museum (Albert Frey, Rudolf Schindler); non-UC harvesting updates: LAPL photo collection update (~1500 new objects), coming soon--History San Jose, USC
  • A number of collections digitized through the LSTA-funded California Revealed program are also in-progress of being harvested. Some UC campus libraries may have nominated collections for digitizing through California Revealed – and we'll highlight those at our upcoming monthly updates, when published.

  • Roadmaps are managed in Trello, and linked from our OAC/Calisphere Help Center. 3 different roadmaps available: OAC, Calisphere, and Collection Management Tools (CDL-hosted ArchivesSpace and Nuxeo)
  • We can do a deep dive into the roadmaps, as part of our monthly updates
  • How to share suggestions and feature requests:
    • You can “Watch” a card (need a Trello account)
    • If there’s a roadmap item or particular problem or feature you think should factor into the roadmap, we want to build out the Community Forum area in the Help Center. – we can thumbs up; comment; essentially vote and help gauge collective interest.
    • Could use monthly updates to chat about things that are added here. A way to do this collectively as a group
    • Help Center community forum can be a way to surface new discussions, while Trello is a way to track current progress

National Finding Aid Network planning process
  • OAC Roadmap: https://trello.com/b/nLKuGoAd/oac-roadmap
  • We've been working on convening a planning conversation with statewide and regional finding aid aggregators, to explore the idea of developing shared infrastructure and services for hosting finding aids at a more national level
  • We have a project website that summarizes the planning work – will be announcing this soon: https://confluence.ucop.edu/display/NAFAN
  • Plan to convene a planning meeting to discuss an action plan for the very initial planning phase.

OAC map view reimplementation
  • Google changed their terms of service and require a payment method for utilizing their maps API.
  • Working on migrating to Mapbox, to supercede the map-based views in OAC.
  • Preview available on http://oac-dev.cdlib.org/

Calisphere web accessibility audit
  • We've been making some updates to front-end code (to make the site more accessible), drawing heavily on an audit conducted with the help of UCOP:
    • The audit is significantly thorough. Lots of recommendations; currently picking through the easiest ones. Examples include:
    • Hovers – to make it more accessible for keyboard only users
    • Colors, the orange will probably be a smidge darker to meet color contrast accessibility darker
    • Some of the grays need to go a little darker
    • Adding skip links to skip through more easily, rather than having to tab down very far
    • Also picking up on some larger design changes – haven’t fully mapped them out yet. But on the object page views, we are considering adding a design element so users can more immediately report accessibility issues to us
  • Related to web accessibility: heads up that the Digitization & Preservation CKG is launching a task force to "reboot" shared systemwide recommendations for digitizing content – and those recommendations will include guidance on digitizing with web accessibility compliance in mind
    • The CDL has maintained a set of recommendations for a number of years, which largely point to federal agency specifications (e.g., creating high-res TIFFs). But these specs are are mostly silent on web accessibility
    • Task force will draft up current recommendations/best practices for digitizing audio, video, images, and text. Will likely continue to references the federal agency guidelines, but adding in web accessibility guidelines. E.g. when creating an audio file, include a transcription. When creating PDFs, ensure there is full text embedded.
  • Will share more info on the audit. Rachael Hu is probably the best contact here

Calisphere object viewer
  • Will be working on changing how we expose Nuxeo objects for harvesting, to use IIIF v3 manifest. Also looking more closely at Mirador, as a potential new object viewer that could be adapted for Calisphere
  • Have been tracking the work of a couple development projects – Universal Viewer; Mirador.
  • Mirador object viewer and development community is refactoring Mirador; it could potentially be more adaptable for Calisphere complex object 2.0 specs we came up with a few years ago. (E.g., will need to support different type of file formats; needs to be very adaptable for very complex object types)
  • So we’re currently tracking Mirador and tracking Mirador community calls. We really want to do a review of where Mirador is at. Now that they have some wireframes and design ideas, we want to compare them with the Calisphere object 2.0 to see how they match, see what the gaps are.
  • Other aspect is changing out how we’re harvesting objects out of Nuxeo to use a standard that also underlines Mirador. Also may involve refactoring how we pull content out of Nuxeo.

  • Possibly need to increase storage capacity. Could be because the new releases are larger?
  • Next release is imminent. Currently running v2.5.1
  • Late last year transitioned UC Riverside Librar from local to CDL-hosted instance.