Metadata in Socioplastics is not a neutral descriptive layer added after knowledge has been produced. It is one of the places where theoretical distinctions are made operational. At eleven thousand nodes, the field depends on node numbers, titles, dates, URLs, series positions, marker identities, bibliographic records, DOI identities, versions, channels, archive months and publication interfaces. Each field answers a theoretical question: what is the object, when does it belong, which manifestation is being described, what counts as recurrence, what constitutes continuity, what is the relation between source and version, and which distinctions should remain stable across time? This paper develops two arguments. First, identity is not ontology: assigning a stable identifier to an object does not exhaust what that object is. Second, date semantics must remain explicit because production date, publication date, archive date, deposit date and revision date are not interchangeable. Metadata becomes theory when it makes such distinctions visible and reproducible.
ESSAY
Metadata is often treated as administrative residue.
A title.
A date.
An identifier.
A filename.
A tag.
A URL.
A field completed after the important intellectual work has already happened.
Socioplastics takes the opposite position.
Metadata is one of the places where the field decides what kind of thing it thinks it is dealing with.
This is why metadata is theory.
At eleven thousand nodes, the claim becomes practical rather than rhetorical. A field of this scale cannot rely on memory alone. It needs stable distinctions among node identity, source identity, manifestation identity, version, date, series position, bibliographic work, marker, channel and archival state. Every distinction carries assumptions about what counts as sameness, change, continuity and relation.
The architecture described in Node 11000 depends on these distinctions. Tome, Book, Chapter and Node organise ordinal position. Series organise recurrence. Markers organise conceptual relation. Bibliography organises intellectual provenance. DOI records create persistent scholarly identities. Channels create distinct publication environments. Monthly archives create temporal entrances.
Metadata is what allows these structures to remain coordinated.
The first principle is that identity is not ontology.
A node number gives an object a stable address within Socioplastics.
It does not define everything the object is.
Node 10997 may refer to an essay on art, but the number itself does not explain artistic research. A DOI can identify a scholarly manifestation, but it does not define the truth or value of the argument. A URL can locate a source, but the URL does not exhaust the source’s historical meaning. A series number can position an item within recurrence, but it does not determine the object’s complete interpretation.
Identifiers stabilise relation.
They do not finish meaning.
This distinction matters because knowledge infrastructures often make a category look more ontologically secure than it really is. Once an object has a field, a code or an identifier, the temptation is to imagine that its nature has been settled.
Socioplastics should resist that temptation.
Metadata should provide precision without false closure.
The Node is the clearest example.
A node creates an internal coordinate.
That coordinate remains stable even when the represented object has other identities.
A paper may have a node number, a title, a source URL, a repository record, a DOI and a local filename.
These are not competing names for one flat thing.
They describe different relational roles.
The node locates the object within the corpus.
The URL locates one source or manifestation on the web.
The DOI provides a persistent scholarly identifier.
The filename supports local or computational handling.
The title provides semantic recognition.
The metadata architecture becomes strong when these identities are connected without being collapsed.
This is precisely why manifestation relations matter.
One intellectual object can have several manifestations.
A text can exist as a blog post, TXT file, repository PDF and machine-readable dataset record.
These manifestations may differ in layout, persistence, version state and interface.
The metadata must therefore answer a difficult but fundamental question:
When are two records the same work?
And when are they distinct objects?
This is not clerical housekeeping.
It is an epistemic decision.
Bibliographic deduplication makes the problem visible at scale.
A single book or article can appear in several records because punctuation, edition information, author format, subtitle or publisher field varies.
If every variant is counted as distinct, the bibliography overstates intellectual multiplicity.
If genuinely different editions are merged carelessly, historical difference disappears.
Deduplication therefore requires a theory of identity.
The move from a raw bibliographic predecessor of 2,386 records to the V11 CLEAN master of 2,202 unique references is meaningful because the field had to decide which variations represented duplicate records and which represented distinct works.
The result is not simply a smaller list.
It is a more explicit ontology of bibliographic identity.
Node 10991 develops the broader logic of Subir Bajando. Here the point is narrower: cleaning metadata requires theoretical judgment.
Dates reveal the same problem even more clearly.
A date appears simple until the field asks what the date actually means.
The date an artwork was made.
The date it was first exhibited.
The date a photograph was taken.
The date a blog post was published.
The date a source was recovered.
The date a DOI was deposited.
The date a file was revised.
The date a Book was closed.
These are different temporal events.
A single generic DATE field can therefore create false certainty.
Socioplastics needs date semantics.
A production date should not silently become a publication date.
A publication date should not be confused with an archive-recovery date.
A DOI deposit date should not replace the historical date of the underlying work.
A revision date should not erase the original publication date.
This distinction becomes especially important in a field that combines recent scholarship with historical archives.
Temporal precision is theoretical precision.
The field asks not only when an object exists, but what kind of temporal relation is being recorded.
This is one reason monthly archives are so important.
A monthly archive is a temporal interface.
It groups materials by publication chronology within a channel.
That chronology may differ from the date on which the underlying work was produced.
An old project can be republished in a recent month.
The archive month then records the temporal history of publication, not necessarily the temporal origin of the object.
Both dates can matter.
Neither should replace the other.
This is a general rule.
Metadata should preserve multiple temporalities when multiple temporalities are analytically relevant.
The same principle applies to versioning.
A file revised in 2026 may contain a text first written in 2024.
A DOI record may stabilise a version after earlier public circulation.
A dataset snapshot may represent the state of a corpus at one threshold while the underlying field continues to grow.
Version metadata therefore gives time a structural form.
A version says: this object existed in this configuration at this moment.
That proposition is essential for a field that grows continuously.
Without versioning, later readers cannot distinguish historical states.
This is particularly important at 11K.
The first ten thousand nodes constitute a sealed collection.
Tome XI extends the field to eleven thousand.
A later 12K snapshot may change many transversal elements while leaving the first collection historically fixed.
The metadata must preserve both continuity and closure.
This is why STATUS is not trivial.
OPEN.
CLOSED.
SEALED.
DRAFT.
FINAL.
CURRENT.
ARCHIVED.
These words affect interpretation.
A draft can change.
A sealed Book should not.
A current bibliography can accept new references.
A historical snapshot should preserve the state it records.
Status metadata therefore governs expectations about change.
It is a small field with large consequences.
Series metadata does something similar for recurrence.
COPOS 615 and MEAT 970 are not merely counts.
They are frontier statements.
A series position says that an item belongs inside an ordered recurrence.
This can make a missing number meaningful.
It can establish cut lines for future maintenance.
It can allow the field to distinguish continuity from a loose thematic cluster.
Node 10993 develops seriality in detail. The metadata point is that the existence of a SERIES field transforms recurrence into inspectable structure.
The same happens with markers.
A marker is not merely a keyword.
Its lexical form belongs to a controlled conceptual system.
Unique roots, two-word construction and canonical naming prevent uncontrolled synonym proliferation.
Metadata discipline allows the conceptual vocabulary to remain stable enough for recurrence to become visible.
A marker can therefore be understood as metadata with theoretical ambition.
It both labels and proposes.
The distinction between KEYWORDS and MARKERS should remain clear.
Keywords are descriptive access terms.
Markers are controlled field operators.
Conflating them would weaken both.
The field gains strength by allowing several descriptive systems to coexist while preserving their different functions.
This extends to platform tags and labels.
A Blogger label belongs to the source platform’s navigation system.
A keyword belongs to a paper or record.
A marker belongs to Socioplastics’ conceptual infrastructure.
A series name belongs to recurrence.
An adjacent field belongs to disciplinary positioning.
All can appear near the same object.
They are not interchangeable.
This is why maximal metadata is not the goal.
More fields can produce more confusion if their semantics overlap.
Good metadata is selective.
Every field should answer a distinct question.
NODE: where is the object in the corpus?
SERIES: does it belong to a recurrent structure?
SLUG: what stable textual identifier supports publication and files?
STATUS: what is its current version state?
DATE: which temporal event is being recorded?
SOURCE URL: where is the source manifestation?
DOI: what persistent scholarly identity exists?
INTERFACE: through which publication surface is this manifestation accessed?
CITATION: how should this object be referenced?
AUTHOR and AFFILIATION: who is responsible for it and from which institutional position?
These fields create a small relational grammar.
Their value lies in semantic separation.
This is where Jeffrey Pomerantz’s formulation of metadata as a subject in its own right becomes relevant. Metadata systems are never simply transparent descriptions of pre-existing reality. They are constructed frameworks that determine what can be retrieved, grouped and compared.
Socioplastics radicalises this insight through scale and heterogeneity.
Its metadata must operate across texts, videos, artistic traces, bibliography, series, archives and scholarly publications.
A flat template cannot describe every object equally well.
The system therefore needs a stable core plus media-specific extensions.
This is an important design principle.
A paper may need CITATION and DOI.
A video may need duration and channel.
A bibliography record needs publication fields.
A monthly archive needs month and channel.
A marker needs canonical term and lexical status.
A built project may need location, date and project relation.
Common metadata should support interoperability.
Specific metadata should preserve medium.
This balance prevents one universal schema from flattening the field.
The architecture can therefore be described as layered metadata.
Core fields create common address.
Object-specific fields preserve difference.
The distinction is analogous to the wider double geometry of Socioplastics.
Common structure gives coherence.
Transversal and media-specific structures preserve heterogeneity.
Metadata also determines what machines can see.
A script can check node continuity only if node numbers are explicit.
It can detect duplicate URLs only if source URLs occupy consistent fields.
It can identify series gaps only if series positions are machine-readable.
It can compare bibliographic records only if authors and titles are sufficiently structured.
It can build date distributions only if date semantics remain consistent.
Machine readability therefore depends on metadata discipline.
But metadata discipline should not be confused with total formalisation.
Not every meaningful relation can or should become a field.
Interpretation exceeds schema.
An artwork may contain ambiguity that no metadata field should resolve.
A city may be described through several contradictory experiences.
A theoretical concept may shift subtly across contexts.
A video may contain relationships that only become visible through viewing.
The metadata should support access to those meanings, not pretend to replace them.
This is the same distinction as identity versus ontology.
Metadata stabilises handles.
It does not exhaust objects.
The design of a field therefore requires deciding where formalisation should stop.
This is a theoretical decision.
Too little metadata produces opacity.
Too much metadata produces administrative overreach and false precision.
The appropriate level depends on what relations the field needs to preserve.
Socioplastics has gradually learned this through practice.
Some metadata became necessary only when scale increased.
At one hundred nodes, a loose naming system can survive.
At eleven thousand, small inconsistencies propagate.
A missing zero in an identifier.
A repeated URL.
An unstable marker spelling.
A title variant.
An ambiguous date.
A broken series number.
Each error becomes costly because it weakens automated comparison and human trust.
Scale changes the epistemic weight of metadata.
This is why maintenance and metadata are inseparable.
Node 10991 develops maintenance as growth.
Metadata maintenance consists of resolving identity, standardising where useful, preserving historical distinctions, fixing broken relations and freezing stable states.
This work is often invisible because it produces fewer new objects.
Its epistemic effect is substantial.
A field with clean identifiers becomes more searchable.
A field with stable dates becomes more historically interpretable.
A field with consistent series metadata becomes auditable.
A field with explicit versions becomes reproducible.
A field with manifestation relations becomes citable without confusion.
Maintenance therefore converts metadata from clutter into infrastructure.
Metadata also shapes reading order.
The Field Paper series demonstrates this clearly.
The node numbers increase from 10991 to 11000.
The intended reading order is 11000 → 10991.
These two orders coexist.
One is ordinal.
One is conceptual.
The metadata must preserve both.
If the reading order were left implicit, a future reader might assume ascending numerical sequence.
A single field solves the ambiguity.
READING ORDER is therefore not decorative.
It encodes a local epistemic instruction.
This example demonstrates how metadata can describe relations not visible in the identifier itself.
The node tells us where the paper is.
The reading-order field tells us how the local sequence should be traversed.
Again, identity is not ontology.
The same principle applies to INTERFACE.
A paper may be available through several interfaces.
Blog.
Repository.
GitHub.
Hugging Face.
Local TXT.
PDF.
The interface does not define the intellectual object.
It defines a mode of encounter.
Recording interface therefore helps future readers interpret what they are seeing.
A blog manifestation may include images and links absent from a TXT file.
A PDF may stabilise page layout.
A dataset record may remove design but increase computational access.
The metadata can preserve those differences.
This becomes crucial for provenance.
A future researcher may need to know which manifestation was used for a quotation or analysis.
The source relation matters.
Node 10992 develops provenance in detail. Metadata provides the infrastructure through which provenance becomes recoverable.
CITATION fields are similarly important because they translate an internal object into an external scholarly form.
An internal node may be easy to locate inside Socioplastics but difficult to cite elsewhere.
A canonical citation creates portability.
This is especially useful for essays and markers intended to circulate beyond the immediate archive.
The metadata block should therefore function as a bridge between internal architecture and external scholarship.
This is one reason the Field Papers themselves should carry explicit metadata.
If the papers argue that metadata is epistemically important, they should embody that claim.
NODE.
SERIES.
TOME.
BOOK.
SLUG.
STATUS.
READING ORDER.
AUTHOR.
AFFILIATION.
YEAR.
Later, when they genuinely exist:
DOI.
NODE URL.
INTERFACE.
CITATION.
The absence of an identifier should remain blank or absent rather than be simulated.
Metadata gains credibility through refusal to invent.
This point is more important than completeness.
An unknown field is better than a fabricated one.
A provisional field should be marked provisional.
A future DOI should not be anticipated as if already assigned.
The schema should represent the real state of the object.
Truthful incompleteness is stronger than false completion.
This principle applies throughout the field.
Unknown date.
Uncertain authorship.
Broken source URL.
Unverified series relation.
Each condition should be handled explicitly.
Metadata can encode uncertainty.
This is theoretically important because archives often present clean fields that conceal messy histories.
Socioplastics should preserve uncertainty where uncertainty exists.
A field named DATE? or APPROXIMATE DATE may sometimes be more accurate than forcing a false exactness.
The field can become sophisticated enough to distinguish precision from certainty.
This is where metadata approaches epistemology directly.
To describe something is to decide what distinctions matter.
To encode uncertainty is to acknowledge the limits of that description.
To create persistent identity is to claim continuity across manifestations.
To version an object is to claim meaningful change.
To define a series is to claim recurrence.
To close a Book is to claim structural completeness.
Metadata therefore contains propositions.
These propositions should be inspectable.
At eleven thousand nodes, the cumulative consequence is substantial.
The field can be read historically because dates exist.
It can be audited because identifiers exist.
It can be compared because series exist.
It can be traced because URLs exist.
It can be cited because bibliographic and DOI identities exist.
It can be computationally inspected because structured text exists.
It can preserve heterogeneity because the schema does not require all objects to become the same.
This is the mature meaning of metadata in Socioplastics.
Metadata is not beneath theory.
Metadata is where theory becomes repeatable structure.
The strongest formulation is therefore direct.
The design of metadata is the design of possible knowledge.
A field can only retrieve what it has made addressable.
It can only compare what it has distinguished consistently enough to compare.
It can only preserve provenance if source relations have survived.
It can only reconstruct change if temporal semantics remain explicit.
It can only coordinate multiple manifestations if identity has been separated from interface.
The metadata schema is therefore not merely a record of the field.
It is one of the instruments through which the field becomes thinkable.
SERIES: SOCIOPLASTICS — TEN FIELD PAPERS
NODE: 10994
READING ORDER: 11000 → 10991
SLUG: METADATA-IS-THEORY
STATUS: 11K CLOSURE
LANGUAGE: English
KEYWORDS
Metadata studies · Knowledge organisation · Information science · Archival studies · Digital humanities · Epistemology · Infrastructure studies · Publishing studies· bibliography · knowledge organisation · digital humanities
ADJACENT FIELDS
Metadata studies · Knowledge organisation · Information science · Archival studies · Digital humanities · Epistemology · Infrastructure studies · Publishing studies
REFERENCES
Bowker, G.C. and Star, S.L. (1999) Sorting Things Out: Classification and Its Consequences. Cambridge, MA: MIT Press.
Drucker, J. (2014) Graphesis: Visual Forms of Knowledge Production. Cambridge, MA: Harvard University Press.
Gitelman, L. (ed.) (2013) Raw Data Is an Oxymoron. Cambridge, MA: MIT Press.
Kitchin, R. (2014) The Data Revolution: Big Data, Open Data, Data Infrastructures and Their Consequences. London: Sage.
Pomerantz, J. (2015) Metadata. Cambridge, MA: MIT Press.
Star, S.L. and Ruhleder, K. (1996) ‘Steps toward an ecology of infrastructure: Design and access for large information spaces’, Information Systems Research, 7(1), pp. 111–134.
Zeng, M.L. and Qin, J. (2016) Metadata. 2nd edn. Chicago: ALA Neal-Schuman.