SaaS product design for Delhi collection platforms

Give collection teams a reliable way to revise an object record, approve its public description and see what visitors will find before the change goes live.

See the catalogue review example
Light line illustration of India Gate and the stepped galleries of Agrasen ki Baoli in Delhi.

Design one review from edit to release

A sample object record for a Delhi collection product

The National Museum in New Delhi digitises collection objects for public discovery. In this fictional product exercise, a small archive wants to correct a catalogue caption while a rights reviewer checks a replacement photograph. GreyBath provides SaaS product design remotely.

Keep the approved page visible during review

Record A214 currently has an approved caption and an approved photograph. A registrar corrects the date in the caption and attaches a new photograph for review. Record both changes as a revision of A214, with the earlier approved version still available to visitors.

Let reviewers see what they are approving

The editor checks the wording while the image reviewer checks the proposed photograph and its public credit. Show the previously approved values beside the proposed values and identify which person still has a decision to make.

Show how a partial release works

The revised caption is approved and the replacement photograph remains under review. In the pilot, the publisher previews a release with the new caption and the existing photograph. The change history records the values used and identifies the photo that is still waiting.

Give collection teams clear roles

Review the preview with the staff who edit the records and the people who decide what can appear in the public catalogue.

Collection software product teams

Design one review pattern that can be reused across collection types with organisation-specific approval rules.

Registrars and catalogue editors

See which values are public and which are being reviewed before editing a record.

Rights reviewers

Review the requested image use and the credit with enough context to return an incomplete decision.

Engineering teams

Use the approved field and state model to specify preview, release and revision history.

Test a revision with one record

  1. Choose one sample revision

    Sketch A214 and agree which fields are public before any changes are made.

  2. Prototype a split decision

    Approve only the caption change. Ask the publisher to identify the held photo and preview the exact public record.

  3. Review the result with engineering

    Check that the release has one approved caption, one approved image and a history of decisions. Document how the live catalogue would receive it.

Agree which decisions the pilot covers

Start with one record type, two kinds of edits and the roles that approve them. Your team defines who can authorise publication and what rights information it needs.

Discuss your project
Fields and asset history

Choose the identifiers, descriptions and attachments involved. Agree which values can go live independently.

Permissions and preview

Map who can view private notes, open the public preview, make decisions and release a change.

Integration boundary

Agree how the catalogue receives an approved revision and what happens when a sync fails.

Questions about collection platforms

Ask us something else
Can we keep our current collection database?

We can design against a representative extract or the existing API. Check whether the source can preserve stable identifiers and revision states before agreeing an integration.

Can draft records stay private?

Yes. Define which roles can view draft metadata and images, then include direct-link and shared-preview access in the acceptance criteria.

Can two fields follow different approval paths?

Yes, when the collection owner allows that release rule. The prototype should show the exact approved combination before a publisher confirms it.

Can we review Hindi and English descriptions separately?

We can scope language-specific drafts and approvals. Agree how a visitor will see available languages when one translation is still in review.

What do we need for a first session?

Bring one sample record, a public view, one example of a returned change and the roles involved in release. Remove private details.

Test how a record becomes public