2015-06-18

Agenda items for DRS Pilot discussion:

1. Archives Exhibit Builder: Discussion Items
   1. Re-visit WP spec, more specifics on "exhibit" piece: layout, user stories, any other information Eli needs. Samples from Archives: Bouve, Desegregation, Northeastern at War.
   2. Will use two collections as base, which still need DRS ingest: Roxbury Oral Histories (40 items), Desegregation by student assistant (200 items, image and doc). Comments: Development of bulk uploader independent of DRS, but are planning on using Desegregation collection as test.
   3. These collections could also be good tests for bulk uploader: is there an ETA on that? Could we ask for higher priority for bulk uploader and ingest of those two collections?
   4. How do we handle exhibits where users want to include non-owned items? Metadata records in DRS? If including metadata records for non-owned items, has implications for automated workflows (Digital Commonwealth, WP connector). (Comment from Jim: I think our projects can basically do what they like with their WordPress instances, and that our terrain is the DRS w/r/t regulating copyright and ownership; I'd be curious about how much exhibits will necessarily impact our workflow in the instances specified, as it seems like updates and additional content will only circulate within the purview of individual project sites. We'll need to have regular check-ins to see if content projects are adding to their sites should also be added to the DRS, but I think we've anticipated that already. I do think it's worth considering how the DSG makes distinctions between DRS and non-DRS content and what both projects and audiences might think about these distinctions).
   5. For Archives items, would like metadata to include originating collection and credits information. Does the WP connector currently pull in that info?
   6. Static vs. dynamic content: currently browse and search results pages are dynamically generated. Exhibit builder (and any WP plugins) call on WP media library, which is not necessarily updated dynamically. This could happen periodically, with users able to choose whether metadata updates overwrite their local text. Needs discussion.
   7. Functional requests
      1. Permissions agreements that are attached to object/collection but kept private. Answer: 100% doable, and encouraged!
      2. Ability to import just one item within a complex digital object, e.g. when 153-page document and want to highlight just one page of that document for an exhibit, what is the workflow for importing only that one page, rather than all 153? In exhibit builder, can you see all subcomponents, and only choose the relevant ones? Answer: May be possible if document stored as complex object, but if document stored as single PDF, importing a single page from that PDF much more difficult and perhaps out of scope.
      3. Ability to clone exhibits -- special template for Archives exhibits, with pre-loaded About Us, rights statement, Archives banner images and branding. Also credits page that could be filled in for each project. Could this be an include, so that if Archives changed their boilerplate, it would change on all sites?
      4. Recommended citation like IRis, Simmons exhibit, Harvard; are automated citations possible, or is this something for a later update to the Toolkit?
2. Latin American Jewish Artists: Items are top priority for ingest, currently looking to schedule time with PI for update on functional requests. Suggested list from AD:
   1. Simple bookshelf with cover images, on-click call to Issuu.
   2. Video playlist like NIEC -- code for this already exists.
   3. Pan-and-zoom viewer: being built for Arader? If so, would be nice addition to this project.
3. Intellectual Property: what is the DSG's stance? What do we suggest are good practices to our projects? Do we have boilerplate rights statements?
4. Coordination w/ WEB group: When do we want to run branding by WEB?