For CRDL: Add CRUD logic to support People Browse
This is also known as the "Names Index", which is currently a legacy Ultimate database. This development will need to be done to support the People browse interface for CRDL. @mcalists and @nlawrence will be adding more requirements here, such as fields required for the Names table, etc, as we get closer to redesigning CRDL.
From the DLG Priorities Document:
Suggested courses of action: Design and develop a Blacklight-based front end for the CRDL portal, displaying information already present, indexed and managed by the DLG Admin back end. Implement bespoke Event and People browse functionality by adding on CRUD functionality for those entities in DLG Admin. Working with GALILEO designer, build front-end elements for People and Event browsing.
From 5/20 DLG Notes:
- Names Index
- Want a feature like the People Browse from CRDL
- Be able to find a name and see all of the things associated with it
- MOST USED THING ON CRDL
- Minimum fields needed
- Name Key -> ID or slug
- Type: person or corporate entity
- Authoritative Name - person
- Authoritative Name - corporate entity
- Alternate Names -> multivalue
- Related Names -> multivalue
- Bio/History -> multivalue, text blocks
- Authoritative Name Source -> originating DB name
- Source uri
- Public
- Want to be able to import from sources like LCNAF and SNAC - not necessarily in their native format but we need to be able to bulk load
- Maybe eventually use data these other sources provide instead of extract/import?
- Eventually link/publish our data? We’ve got lots of Names and bios not in the above references
- Bulk import from Names Index to create the initial data set
- Any entries that exist in current dlg_subject_personal that DON'T exist after Names Index import need to get added
- Food for thought going forward, it looks like the "People" route is in wide use on Wikipedia: