2017-08-24 Re-Imagining Collection - ID, Ingest, UI, and other Implications

Date

Attendees

Goals

  • Explore short and long term needs to accommodate "Digital Collections" that are born digital and/or do not conform to DPC output. 
  • See:  DC-174 - Getting issue details... STATUS  for context

Discussion items

TimeItemWhoNotes
Background


  • Conversations that overlap between born digital and digital collections programs.
  • A group led by Val, met on 8/11 to talk through ideal scenarios for accessing collections w/ born digital / digitized aspects.
    • Spoiler alert: we are more interested in making the collection context clear to end users and not ask them to understand the administrative differences between digitized and born digital.
  • ReImagining
 Questions 


  • What DC features (ingest, modeling, and UI configuration) are triggered by DPC / RL IDs? DDR expects an ID that behaves like an RLID and a DPC ID
    • Ingest: folder ingest is built around DPC ID - standard ingest worked in this case .
      • Ingesting the captions files and transcripts - they all match the local IDs.
        • We can look at changing the way things match.
    • Portal Customizations: Some of these are triggered by the Local ID
      • We can assign a local ID that is different than the file name
      • We do want to present the file name for RL born digital items, as many of those items do not have a title.
      • Local ID is used in the URL in DC. If there is no local ID, the UI will default to the PID
    • UI: no highlight or showcase items w/out local ids. We could eventually use ARKs instead of local IDs
      • No thumbnail items
    • If we were ingesting this collection in to the RLBD set, would there be a different outcome?
      • No would be dealing with a lot of the same questions.
      • The RLBD admin set is not able to take a configuration file.
  • What kinds of cases do we want to accommodate?
    • We need a flexible way to ingest things regardless of their filenames - in other words - map all the parts outside of DDR
  • File tree in Born digital - could be made available in DC if we want it to, but will require some development to determine integration.
  • Featured items in DC - could be made available in born digital w/ a little development.

Options
  • Assign a local ID based on the RL ID to each file
    • Use the folder's RL ID that Craig assigned at the root

Possible Development
  • Ingest captions and derivatives from csv so curators can associate components w/ items outside of DDR.

Action Items
None for now - Revisit following RLBD and DC meeting report.

Action items

  •