Review a reading

A reading made by a model is a draft. Reviewing it means going through its mentions beside the source's text, confirming what is right, rejecting or correcting what is wrong, and adding what the model missed. Your corrections are kept separately from the reading and applied again whenever the source is read again, so the work survives a re-reading. Readings, mentions and entities are explained in How analysis works.

In an organisation's project, reviewing needs the editor or owner role. Viewers can open the review desk's material but cannot change it.

The review deskCopy Anchor Link

The review desk shows one source's reading: its units in order, the text of the current unit with the findings underlined, and an inspector for the mention you select. You can reach it from the item's Analysis tab with Review this reading, from a corpus's Sources view by choosing the link beside a source that says how many mentions "want a look" (the desk then opens at the first of them), or from a corpus's views by opening a source's reading from its evidence.

On the desk, Back to investigation returns to the corpus, Previous source and Next source move through the corpus's sources, and Open in the library opens the item.

If the source is still being read, the desk says so. If the source's text has changed since it was read, the inspector tells you to read the source again before working on it.

Mentions that want a lookCopy Anchor Link

Pangur marks a mention as wanting a look when nobody has confirmed it and either its quoted words were not found in the document or the model said it was unsure of it. The inspector gives the reason in each case. The desk counts these mentions ("6 want a look"), and Previous that wants a look and Next that wants a look jump between them. A unit dated outside the years you gave in the corpus's guidance is also marked, as outside the dates you gave.

Correcting a mentionCopy Anchor Link

Select an underlined passage in the text, or a mention in the inspector, to work on it. Confirm marks the mention as right, after which it no longer wants a look. Reject marks it as wrong, and rejected mentions are left out of the corpus views and exports; Restore brings a rejected mention back. Change role sets its Role in this record, for example from "mentioned" to "recipient". Move this mention to… files the mention under another entity: search for the entity under Move to another entity, or choose "A new entity named" the text you typed to create one.

Each action is confirmed briefly on screen.

Adding a missed mention or relationCopy Anchor Link

To add a mention the model missed, select the words in the text. The inspector offers Add a mention at the selected words. Choose its kind (person, place, organisation, work, event, concept, object or other), fill in who or what it is (or leave the field empty to use the selected words), choose the role, and choose Add the mention. Mentions you add are labelled "added by hand".

Each unit's relations are listed under Relations in this unit. To add one, choose Add a relation, pick the entity it runs from, describe the relation (for example "kinship" or "patronage"), pick the entity it runs to, and choose Add the relation. Strike out removes a relation from the views, and Restore brings it back.

Correcting an eventCopy Anchor Link

An event can be corrected from the review desk or from the evidence beside the corpus views. Not an event strikes it out and Restore brings it back. Correct the date or place opens two fields: the date as the source gives it (for example "12 June 1709"; leave it empty to use the record's date) and the place, or no place. An event whose quoted words are not in the text is left off the timeline and the map until it is corrected.

A reading made before Pangur extracted events says so and invites you to read the source again to find them.

Undo, redo and keysCopy Anchor Link

Undo and Redo step back and forward through your corrections on the desk. The keyboard shortcuts are:

Marking a reading as reviewedCopy Anchor Link

Each source has a review state that every member of the project sees: nobody has been through the reading yet, you have started on it, you reviewed it on a given date, or it has been read again since your review, in which case the corrections carried over and the additions are unreviewed.

Choose Mark as reviewed when you have finished. You can attach a note with Add a note, for example "Checked against the facsimile to f. 40.", and Reopen the review returns the reading to "in review". A reviewed source is skipped when you choose Read everything again on its corpus, unless you choose to include reviewed sources (analysing the corpus).

Corrections that outlive a readingCopy Anchor Link

Pangur records each correction against the passage it concerns rather than against the reading it was made on. When a source is read again, Pangur applies your corrections to the new reading by finding the same passages.

If the new reading has no passage for a correction, for example because the source was divided differently, the correction is listed on the item's Analysis tab under Corrections without a place. Each one describes what you did, such as rejecting a mention of a particular person, and Pangur tries it again on each new reading. Withdraw discards a correction you no longer need.

Deciding which names are one personCopy Anchor Link

The same person often appears under several spellings, and a place under its old and new names. A corpus's Review view lists the decisions about identity in three groups.

Possible pairs are two entities that may be one, shown with their quotations. Choose Keep with the name you want to keep, which merges the other into it, or Keep apart; a pair you keep apart is not offered again. The pairs are drawn from the whole project, so a corpus entity may be paired with a spelling found in another source.

Identified as read lists mentions the model filed under a name your project already held, such as "J. Keith" filed under "John Keith". Choose Looks right or Not this person.

Merged by Analysis lists merges made by Pangur's automatic identity pass, with Looks right or Undo. In this pass a model reads the project's entity lists and merges those it judges to be one. It is off by default and is run by an administrator where it is used, so most projects will not see this group at all. Where it does run, it does not override a decision a person has made, and it does not merge two entities linked to different authority records.

Merges are reversible. Pangur keeps the merged entity and points it at the one you kept. Immediately after a merge Pangur tells you which name is now part of which, with Undo; later, the entity's evidence shows what it was merged with and offers Separate again.

Merging entities changes nothing in the source texts. It changes only how the corpus views and exports group the mentions.

Linking an entity to an authorityCopy Anchor Link

An authority is a record in your project's catalogue for a person, place, organisation or repository (Descriptions, authorities and linked records). Linking an entity to one ties the analysis to the catalogue and, for a place, gives it coordinates for the map.

Open the entity's evidence from a corpus view. Link to an authority in your catalogue searches your catalogue's authorities by name, and Create an authority from this entity makes a new authority record from the entity. For a place, Look the place up proposes matches from Wikidata, and nothing is linked until you accept a proposal. Unlink removes the link, and Manage authorities opens the authorities list.

In the web client a person always makes the link; Pangur does not link an entity to an authority on its own. A place takes its coordinates from the authority it is linked to, which is why a place without coordinates does not appear on the map. An assistant connected over MCP can resolve a whole corpus's places at once, as described under places, concepts and context.