Before you approve a change to a read-only collectibles catalogue, choose one record and write down what a visitor should see at each stage of publication. Then compare those expectations with the changed code and the results from a test catalogue. This gives the developer and the curator a common way to judge an alert, especially when a small change to a credit line affects what appears in search.
Define what a visitor can read
Start with the fields and actions that matter to the collection. A public item might show its title, an approved maker credit, an image, and a short provenance note. The curator’s preview might also show a proposed credit, a note about the source, and a reminder to check permission for an image. Put the intended destination beside each field in the review notes.
- Draft. The curator can preview the proposed record. For this catalogue, a visitor should find no listing for a draft that has never been published.
- Published. The public item page and search result should agree on the title and approved credit. The curator may still have a newer revision in progress.
- Withdrawn. Agree on whether a visitor should see a withdrawal notice or no public listing. Write down what should happen to the search result as well.
The OWASP authorization guide recommends validating permissions on every request. Ask the maintainer to show where the application applies the catalogue’s publication rules for each public view. Give the record a stable test ID so the review follows the same item when its title, credit, or image changes.
Follow Signal Card through a release candidate
Suppose a curator is preparing a fictional item called Signal Card. Its first credit is “Workshop A.” The curator gets better documentation and enters “Studio B” as the proposed credit. In this example the approved item should stay public under its old credit until the correction is approved. The curator’s evidence note belongs in the private preview throughout.
On the test catalogue, the preview shows Studio B as expected. The public item page still shows Workshop A, but the search card already says Studio B. The reviewer records both results against the same test item and build. The curator leaves the correction unpublished, and the maintainer holds the release candidate because the ordinary search view disagrees with the approved record.
The developer reviews the change that builds search cards and finds that it selects the newest saved credit. The fix makes the search card use the approved credit. On the revised build, the maintainer records three results. Before approval, both public views show Workshop A. After approval, both show Studio B. The source note stays in the curator’s preview. The curator accepts the correction and the maintainer clears the release hold for this change.
Match the finding to the revision
A source finding is easiest to interpret when you have the change it refers to in front of you. Copy the revision and file reference into the review ticket. Give the affected behavior a name the curator will recognize, such as “credit shown in the search card,” and ask the developer to say which publication rule is at issue.
For a code review with a code vulnerability scanner, check which repository revision the finding describes. Topscan SAST offers scans on repository commits. If the report predates the change under review, ask the maintainer for evidence tied to the current candidate before using the finding to make a release decision.
Record the result in terms of the catalogue. For Signal Card, “the search card used the pending credit before approval” tells the next reviewer what the team found and which behavior the fix has to preserve. If the alert concerns a file used only for sample data, record that explanation and who checked it. If the reviewer is still unsure which public view uses the code, give someone the task of tracing the change and keep the finding open.
Record the evidence that clears the change
Keep enough information for another maintainer to understand the decision after the release. The OWASP authorization guide recommends unit and integration tests for authorization logic. For a credit change like Signal Card’s, ask the developer to preserve the rule for selecting an approved credit in a test and keep an acceptance result for the visitor and curator views.
Use this checklist when the change is ready for sign-off.
- Save the candidate revision, the test record ID, and the finding or review reference.
- Write the expected public fields for the changed search and item views, including what a visitor should see while an edit awaits approval.
- Confirm that a curator can save a correction in preview and approve it through the ordinary editorial workflow.
- Keep the results before and after approval. Use synthetic records in examples that may circulate outside the maintenance team.
- Name the maintainer responsible for any affected component outside this review, such as the collection’s separate import service. Give that owner a follow-up task and make clear whether the current release depends on it.
Use the evidence from the same candidate when you sign off. A ticket with the right screen capture and the wrong revision still leaves the maintainer with a release question to answer.
Frequently asked questions
What if a finding refers to a file that was renamed? Ask the developer to match the finding to the current implementation and leave both references in the ticket. Keep the original finding ID so someone can follow the history without guessing from a filename.
Should an imported credit go straight to the public item card? Decide which fields your collection expects a curator to approve. In a collection that imports provisional credits, keep those values in preview until a curator approves the public version. Include the search card in that decision.
What should we save when nothing visibly changes in the catalogue? Keep the expected output, the candidate revision, and the result on the sample record. For a review of an internal refactor, the existing approved credit and the curator’s ability to edit it may be the very things you wanted to preserve.
Does this review verify who owns a collectible? Use the collection’s provenance records to evaluate an ownership claim. The code review helps establish whether the catalogue shows the fields that the curator approved.