Museum Linked Data Browser: The Duchamp Research Portal

View Entities:

Getting Started

Orientation for cataloguers, field specialists, and DH researchers
Orientation for developers
Common language: integration and reconciliation
Reviewing your modeled data
The model's relationship to linked.art and other linked data models

Technologies Overview

Data sources
Data layers and transforms
Actions you can take
Technology stack
Data releases
Image management
Search
Language and localization

Data Models

Basic patterns from Linked.Art
Images
Museum data
Archives data
Person, Organization and Group data
Vocabularies

Data to Curate Relationships

Direct curated relationships
Faceted relationships
Indirect relationships

Actions you can take

Overview

Pipeline command overview

Pipeline command flow diagram from ppt

Changing source data

Change the data in your source system, export it, and commit the file to the collections-app github repo with the appropriate filename (eg, EDR_2.xml).

Changing reconciliation data

Reconciliation data is handled in two ways:

  • A CSV data file with inter-term reconciliation entries (eg, AAT terms, French classifiers, and possible equivalents)
  • A maker reconciliation data sheet with artist IDs, and their ISNI, ULAN, and LCNAF exact matches

If you need to change how a reconciled term appears in the site, you should change the CSV file. If you need to change the specific term being unified for an object in reconciliation (eg, aat:1234 to aat:6789), you should change the data in the source system.

Changing images

To change an image, make a change in the source repository (on the home network share) and re-run pipeline images compress.

Clearing the image cache

Requests to the image server pass first through an AWS CloudFront CDN that provides a basic cache of requested IIIF resources. While this provides some level of protection against high load events it can sometimes become out of sync with the compressed image repository, particularly after a series of updates, due to the length of time it takes for the CDN to execute the clear of the cache (ca 15min).

It can be helpful (and will not harm the service) to execute pipeline images cache-clear in these circumstances.

Rollout / rollback

The Duchamp Research Portal site uses Netlify for static site hosting based on a git repo. As a result site rollbacks are relatively straightforward:

  • Go to the Netlify site admin page
  • Click "Deploys"
  • You should see a list of previous site builds, with a Green / Yellow / Red status indicator.
  • Pick the deployment you'd like to possibly roll back to, then click "Preview deploy"
  • If the build matches what you'd like, click "Publish deploy." If you would like to lock this deployment in place during troubleshooting, use "Lock publishing to this deploy"

For more information on managing deployments, see Netlify's documentation on managing deploys

References

  • TBD