Finding a rule scattered across years of issues

A reader remembers a rule about sacrificing a shield, but not the magazine issue that contained it. The contents page for Fight On! issue 2 identifies Shields Shall Be Splintered, credits J. Brian Murphy and gives page 28. Three pieces of information turn a vague recollection into a location that can be checked.

The example illustrates a retrieval problem, rather than reporting a patron enquiry I observed. A library can own the relevant issue and still have no effective route from the reader’s remembered subject to the page. Holdings and discoverability are separate parts of the service.

RPG zines make the problem particularly clear because an issue may combine adventures, variant rules, equipment, interviews and campaign reports. Each part can answer a different question. A record containing only the serial title and issue number leaves those answers hidden until someone opens the copy, even when the library has acquired every issue and preserved the complete publication in excellent condition.

Different memories need different routes

The Freelance Traveller magazine archive offers issue pages, a cover gallery and a consolidated listing. It explicitly directs readers who remember a cover but not a date toward the gallery. That is a thoughtful recognition that readers do not always arrive with bibliographic information.

A cover memory, an author’s name and a rule concept are different starting points. A visual gallery can serve the first reader, a contributor index can serve the second, and subject access or a well-written contents note can help the reader who remembers a concept but has forgotten its title. No single route makes the others unnecessary.

The publication’s PDF and website forms also create a useful distinction. An article page may make a text easy to find and read. The issue preserves the article’s position among other contributions. For a rules question, the article may be sufficient; for a study of editorial context, the surrounding issue may matter.

I would make the relationship visible when describing the two forms. A reader should be able to move from the article to its issue without assuming that the web page reproduces every physical or editorial feature of the magazine.

An index contains decisions about relationships

Shannon Appelcline’s Tales of the Reaching Moon index organises entries through subjects and records fields including title, system, author, issue and pages. Under skills, for example, it locates Greg Stafford’s Battle Skill in issue 6 on page 11 and identifies the associated system as RuneQuest third edition.

That combination is more useful than a bare keyword hit. It helps a reader distinguish a topic from a specific rules context and provides a location for inspection. The index’s declared coverage, issues 1–20, also tells the reader what the search is meant to include.

Geoffrey Bowker and Susan Leigh Star’s introduction to Sorting Things Out examines how classifications organise visibility and activity. An RPG index supplies a small, concrete setting for that argument. Its headings group some relationships together and leave others to be found through different routes.

A rule about a mounted character might be sought under combat, movement, animals or a specific game system. Choosing one heading does not make the other interpretations foolish. It creates a design question about additional access points and the vocabulary readers are likely to bring.

An index therefore deserves attribution and a scope statement of its own. It is intellectual work produced by someone with a particular method. Its categories should be understood as an aid to enquiry rather than an invisible, exhaustive map of the publication.

Start with a retrieval need that can be checked

For a library building access to RPG serials, I would choose a bounded set of issues and a small set of realistic questions. The questions could concern a named contributor, an adventure location, a particular rule or a remembered cover. Staff could then test which questions the current description answers.

Where a contents note solves the problem, there may be no need to build a larger database. Where the same subject crosses many issues, a maintained index may be worth the effort. The decision should follow the observed gap and the staff capacity to keep the new resource usable.

The test also needs an endpoint. Finding a promising entry is not the same as finding the required material. The reader must be able to identify the issue, reach a copy and confirm that the item answers the enquiry. A beautiful index to unavailable or ambiguously identified files leaves part of the job unfinished.

For academic research, version information can matter as much as the initial location. A rule may have appeared in a zine before being revised in a later book. The index should help identify the cited version rather than silently directing every enquiry to the newest text.

Maintain the index as a publication

A local index should name its coverage, last update and responsible contact. It should distinguish transcribed titles from supplied subject terms. If a page number has been inferred from a scan sequence rather than printed pagination, the distinction should be visible enough for another person to reproduce the lookup.

Corrections need a simple route. A reader may identify a misspelled contributor, a missing continuation or a link that now leads to a different edition. Recording the correction makes the index more useful while preserving a trace of why its description changed.

A public-library RPG group could contribute candidate terms from actual play enquiries. An academic course could compare those terms with a formal subject structure and examine what each approach makes easier to retrieve. Neither activity requires treating readers’ vocabulary as uniform or replacing professional judgement with a popularity count.

The useful collection is the one a reader can interrogate. A complete run gives the library material to work with. Contents, indexes and well-maintained relationships let a reader turn a half-remembered rule into an identifiable source.