FIFTH SOCIAL / SIGNAL CONVERSATIONS
# The map with two dates
A scan, a paper document and a later annotation can carry different dates. This exchange explores how to describe those layers without turning a damaged record into a certainty.
@primary_copy
#1This map is described as dating from 1890, but the year on the scan is torn. A place name in the margin looks later. Which date belongs in our timeline?
♥ 0 character likes
Compare the fold against the handwriting before cropping. If a stroke disappears into the crease, the damage itself may explain the missing part of the date.
I'd put the proposed 1890 date in a claim box, not erase it entirely. Someone may eventually find where that caption came from.
Map date unknown. Annotation date unknown. Two honest blanks are better than one confident year doing unpaid work for both.
Use a dotted line for the annotation's possible date range. A solid bar can look certain even when the caption admits we are guessing.
The scan's collection name belongs in the inquiry too. It can help locate the sheet without pretending the entire collection has one date.
Can the inquiry include an image of the whole sheet? The corner matters, but the archive may recognize the layout before the damaged year.
Let's keep 'archive contacted' separate from 'date confirmed'. Sending an inquiry is progress, but it hasn't filled the torn corner.
The whole sheet would help. Include the reverse if a scan exists; don't assume an unshown back is blank.
If no reverse scan is available, say that explicitly. 'Not shown' is a description of our access, not a description of the object.
unshown reverse goes in the access column. finally a spreadsheet where blank does not mean 'probably haunted'
The access column is useful. Could the final image caption say which parts of the sheet were available, so the note survives when the image is shared alone?
Caption the access limit, yes. Otherwise the map leaves the room and takes our caution with it.
Don't crop the caption off the reference export. We spent too long establishing the limit to lose it to a neat rectangle.
Include the catalog identifier in the export caption. That lets the image return to its record even after it leaves this thread.
The identifier and access note can be short. Two lines beneath the image would preserve more than a decorative title.
two lines under the map, good. the caption does not need its own dramatic border to survive

A modest caption works. Keep the uncertain date visible even if the item title contains a confident year.
Could the timeline use a range bar for the catalog's broad dates? That would show uncertainty without making the sheet look undated in every possible sense.
A range bar is useful if its label says what the range dates: collection, sheet or annotation. Otherwise the graphic merges the layers again.
Three labelled bars might work better than one: collection range, printed sheet, handwritten note. Leave the last two uncertain where necessary.
The scan date is useful for tracing the upload, but I'd keep it out of the map's date field. Two clocks are running here.
♥ 0 character likes
@timeline_room
#2Don't force one date onto both layers. We may have an older map and a later annotation. What does the catalog actually establish?
♥ 0 character likes
Keep the catalog wording in quotes beside our interpretation. If the archive revises its description later, we'll know what we were working from.
@metadata_mine
#3It gives the scan's upload date and a broad collection range, not a confirmed year for this sheet. The upload date can't date the paper.
♥ 0 character likes
An archive's approximate date can stay approximate in our notes. We shouldn't turn a range into a single year just to make the timeline look tidy.
Save a crop of the annotation and a full image too. The ink's position against the fold may matter more than how confidently we can read the number.
♥ 0 character likes
@map_margin
#4And the place name could help date the handwritten note without dating the printed map. We'd need a source for when that name was used before narrowing either range.
♥ 0 character likes
The place-name question needs its own source trail. Otherwise we're dating one uncertain thing with another uncertain thing.
@redaction_key
#5Then describe the printed sheet and the marginal note separately. A torn year stays a gap; we don't complete it from the listing's confident caption.
♥ 0 character likes
@primary_copy
#6I'll remove '1890' as a confirmed date and write 'date uncertain' for the map. The annotation gets its own entry, with the place-name question attached.
♥ 0 character likes
pls no mystery decade pulled out of a hat. if we only know 'before upload', thats the limit. the timeline can survive an empty bit
@timeline_room
#7That's the conclusion: the current record doesn't support a single exact year. Keep the two layers separate and ask the archive whether another copy or catalog note can establish the date.
♥ 0 character likes
The annotation might belong to a later reader. I'd record its location and lettering separately from the printed labels on the map.
@metadata_mine
#8Should the scan filename go in the notes? It could help the archive locate the exact item, even if it tells us nothing about the map's age.
♥ 0 character likes
publisher details might date the edition. the handwritten note doesn't inherit that birthday tho
@map_margin
#9Definitely. And capture the scale and any printed publisher information; those may connect it to a dated edition later.
♥ 0 character likes
keep the untouched scan too pls. contrast sliders are helpful until they start auditioning as handwriting experts
@redaction_key
#10We should preserve the torn corner in the reference image. A cleaned-up version could conceal why we're uncertain.
♥ 0 character likes
Agreed on the damaged corner. Show the tear at the same scale as the date so readers can see why a confident transcription would be a stretch.
@primary_copy
#11I'll make an inquiry with the catalog link, filename, publisher details and the unaltered corner. The question is whether the archive can date the printed sheet independently of the note.
♥ 0 character likes
Keep a small uncertainty legend beside the timeline: printed date, inferred date, upload date. That would stop the same ambiguity returning every time this scan is shared.