mediacenter.software · School library & media center · Early access · 2026
The school media center is where students learn to find, evaluate, and use information — and increasingly, where they learn to publish it. mediacenter.software is building the platform for that whole arc: curated reading lists, structured research workflows, media-literacy programs, and a publishing hub that connects the media center to the school’s newspaper, yearbook, and literary magazine. What the platform does not claim today: a catalog, a circulation system, MARC records, holds, or barcode scanning. Those are a build-scope decision we are still working through; we will not fake them. Early access — no pricing commitment, no signup, no live checkout today.
The media center’s role — more than the circulation desk
The school media specialist does three things most library software ignores. She teaches research skills — how to evaluate a source, construct an argument, track a citation through a draft. She curates reading: summer lists, classroom sets, genre series, Lexile-matched recommendations that tie to what teachers are doing in class. And increasingly, she is a publishing partner: the media center is where the newspaper story starts, where the literary magazine submission is drafted, where the student finds a research question and works it through to a byline. Existing integrated library systems handle the last step of the workflow (circulate the book) and almost none of the rest.
mediacenter.software is building for that broader role. The platform’s near-term surface is the research-to-publication arc: reading lists the media specialist controls, research workflows students move through, and a publishing hub that connects the media center to the school’s existing newspaper, yearbook, and literary magazine — through the same multi-surface editor-design engine that already powers those publications. The ILS — catalog, circulation, holds, MARC, Dewey — is a separate build-scope decision. We have not made it yet, and we will not claim otherwise.
That honesty is the point. The media specialist deserves a platform that says clearly: here is what is built, here is what is coming, and here is what we have not decided to build yet. Early access means building alongside the people who know what the media center actually needs.
How it works
From the media specialist’s initial configuration to student work arriving in the school’s publications — every stage described honestly, with what is built and what is in development clearly labelled.
Step 1 · Media specialist configures the program
The librarian or media specialist sets up reading lists, media-literacy lesson frameworks, and research-workflow templates inside the platform. Consent for student activity recording is configured here: what is recorded, who can see it, and under what family opt-in terms. No IT ticket required. The configuration belongs to the media specialist — not a district-wide default imposed from outside.
Step 2 · Students engage with reading lists and research workflows
Students work through research workflows assigned by the media specialist: evaluating sources, tracking citations, annotating, building toward a finished piece. Reading activity and research notes stay in the org-owned platform. No student work is copied to a consumer app or a third-party service. All activity is consent-gated and owned by the school.
Step 3 · Work flows into the school’s publications
Finished student work can route from the media center’s research workflow directly into the school’s newspaper editorial queue, literary magazine submission process, or yearbook editor — through the connected multi-surface editor-design engine substrate. Adviser approval is required at every step. Nothing publishes without the adviser’s explicit consent.
Step 4 · Records stay with the school — one-click export at any time
Reading activity, research history, and media-literacy program participation belong to the school. No behavioral profiling. Families can request a full export of their child’s records at any time, or withdraw consent for activity recording going forward. If the school ever leaves the platform, every record leaves with it — in a portable format the school can read without the platform.
Capabilities
Every capability is labelled: Built means the underlying engine is production-ready. In development means the surface or wire-up is in active build. For this greenfield vertical, the honest label is “in development” for every media-center-specific surface. The publishing-hub pillar notes that the shared editor-design engine substrate is already built — only the media-center wire-up is in development.
The media specialist builds and shares reading lists by grade level, subject, or theme — visible to students and teachers inside the school’s own consent-gated platform. A summer reading list, a middle-grades nonfiction series, a teacher-requested title set for a unit: each curated by the librarian and surfaced to the right audience without a third-party consumer app in the chain. Student reading activity stays org-owned and never feeds an advertising profile. The reading-list surface is in active development — not production-ready today.
Reading-list surface in active development
Structured student research workflows guide students through source identification, credibility evaluation, citation tracking, and annotation — with every note and draft kept inside the school’s own platform, not copied to a consumer note-taking service. The media specialist designs the workflow template; students move through it toward a finished piece. Research notes, evaluated sources, and working drafts stay in the school’s org-owned record. The research-workflow module is in active development — not production-ready today.
Research-workflow module in active development
The media center’s research and writing pipeline connects to the school’s publications: the newspaper, the literary magazine, the yearbook. Student work that begins in a research workflow can route into a newspaper editor’s queue or a literary magazine submission process through the same multi-surface editor-design engine that already powers those publications. Adviser approval is required at every step before anything publishes. The editor-design engine substrate — the shared publishing infrastructure behind the newspaper and yearbook — is built and production-ready. The wire-up connecting the media center’s research-to-byline arc to that substrate is in active development.
Publishing-hub wire-up in active development · editor-design engine substrate built
Structured media-literacy lesson frameworks authored by the media specialist: source credibility rubrics, digital citizenship standards, copyright and fair-use frameworks, information literacy progressions. The media specialist writes and publishes frameworks to classes; students engage with them through the platform. Materials stay in the org-owned platform, not a third-party lesson tool. The media-literacy program surface is in active development — not production-ready today.
Media-literacy program surface in active development
Student reading activity, research history, and program participation are org-owned: the school is the data controller, not the platform. No student reading data feeds a behavioral advertising profile. Student data is never sold to third parties. Families can request a complete export of their child’s records, or withdraw participation, at any time. Consent is collected at enrollment and is withdrawable. Minor student records are never visible to other families. The consent and privacy layer is an architectural guarantee built into the platform’s foundation — not a bolt-on setting added later. This surface is in active development alongside the rest of the platform.
Consent/privacy architecture in active development as a first-class platform layer
For media specialists
A summer reading list is a curation decision: which titles, for which grades, with which reading levels and themes in mind. A classroom-request set is a teacher-librarian collaboration: the English department is teaching memoir, the media specialist builds the title list, and students find it inside the school’s platform — not in a generic consumer app. Reading lists built and managed by the media specialist, surfaced to the right audience, with student reading activity staying org-owned and never feeding an ad profile.
The media specialist teaches the research process — source credibility, database navigation, citation format, argument construction. The platform gives that instruction a structured home: research-workflow templates the media specialist designs, media-literacy lesson frameworks she publishes to classes, and student research notes that stay in the school’s own platform. The research coach’s work persists in the org-owned record rather than disappearing into a consumer note-taking tool.
The newspaper story that starts as a research question in the media center. The litmag submission drafted in a research workflow. The yearbook profile researched during a media literacy unit. The publishing hub connects the media center to the school’s publications through the shared editor-design engine substrate that already runs those publications. The media specialist is not just the person who circulates books — she is a co-author of the school’s publishing pipeline.
Student data & family consent — minors deserve a different standard
A student’s reading history — which books she read, which research topics she pursued, which sources she flagged as credible — is not a behavioral profile for advertisers. It belongs to her school and, in a meaningful sense, to her. The platform stores it for the school’s educational use and for nothing else. No student reading or research data is sold to third parties. No data feeds an external advertising network. The school is the data controller.
Family consent is required before a minor student’s reading activity is recorded. Consent is not assumed at enrollment — it is collected, and it can be withdrawn by the family at any time. Minor student records are never visible to other families. An export of the student’s full activity record is available to the school and the family in writing. These protections are architectural: built into the platform’s data model, not added as a policy overlay on top of a system not designed for them.
What is built and what is not — plainly stated
Built and production-ready today: the multi-surface editor-design engine that powers the school’s newspaper, yearbook, and literary magazine. That shared publishing infrastructure is the substrate the media center’s publishing hub will wire into. The consent and privacy architecture at the platform’s data layer is also a built foundation.
In active development: the reading-list surface, the research-workflow module, the media-literacy program surface, and the publishing-hub wire-up connecting the media center to the editor-design engine substrate. These are being built; none is production-ready today.
Not yet decided: the integrated library system — catalog, circulation, holds, MARC records, Dewey classification, barcode scanning, patron accounts, book renewals. This is a real build-scope decision (build a full ILS vs. position as a media-creation and research hub) that we are working through. We will not claim those capabilities exist until they are built. There is no live checkout, no billing, and no subscription on this page.
Connected to the school platform
mediacenter.software connects the media center to the school’s publishing ecosystem. homeroom.software is the school publishing platform: the newspaper, yearbook, and literary magazine that student work flows into from the media center. Assembly is the moment layer: live school events captured, archived, and shared — the author reading, the debate tournament, the documentary screening. Seen is the recognition layer: the programme that ensures every student author, researcher, and creator lands on a real page in the school’s publications — adviser-approved and consent-verified.
Early access · School librarians and media specialists
mediacenter.software is in active development. A conversation starts with your media center’s actual program: what your students research, how you teach source evaluation, how student work flows into the school’s publications, and what your current tools miss. We map that against what is built, what is in development, and what the ILS build-scope decision means for your school’s timeline. There is no pricing commitment and no signup. Early access means building the right platform, not signing up for the one that already exists.
To book: email [email protected].
FAQ
No — and we are being direct about that. mediacenter.software is an early-access platform focused on the media center’s role as a publishing and media-literacy hub. A full integrated library system with a bibliographic catalog, patron records, and circulation management is a build-scope decision we are still working through — none of it is built today. If a circulation system is your primary requirement, this platform cannot serve that need yet.
Not yet. Book lending, holds, due-date tracking, barcode scanning, and MARC record management are not built. These are the core capabilities of a traditional ILS — and honestly, they are absent here today. We are not going to build a fake circulation desk and call it a media center platform.
The multi-surface editor-design engine that powers the school’s newspaper, yearbook, and literary magazine is built and production-ready. That shared infrastructure is the substrate the media center’s publishing hub will connect to. The media-center-specific surfaces — reading lists, research workflows, media-literacy programs, and the wire-up to the publishing substrate — are all in active development. Every capability on this page is labelled honestly.
The school’s newspaper, literary magazine, and yearbook run on the same multi-surface editor-design engine. A student who completes a research workflow in the media center can route their draft into the newspaper’s editorial queue directly through that shared substrate — without copying into a separate tool. Adviser approval is required before anything moves from draft to published. The editor-design engine substrate is built; the wire-up connecting the media center’s research workflow to it is in active development.
Yes — architecturally, not just by policy. Student reading activity, research history, and program participation are org-owned. No student data feeds a behavioral advertising profile. No data is sold to third parties. The school is the data controller; the platform is the data processor. Families can request a complete export of their child’s records or withdraw at any time.
The school owns the data. We operate the platform infrastructure, but your district’s data-governance policies apply. We do not mine student reading or research activity for any purpose outside the school’s own use. An export of every student record is available to the school in a portable format at any time — including on departure from the platform.
Parent visibility is a school-configured option. The platform supports a parent-facing view of reading and research activity. What is shown is determined by the school’s configuration and the family’s consent choices — not set unilaterally by the platform. A family that has not opted in does not have their child’s data surfaced to others.
No. None of those exist today. The platform does not have a bibliographic catalog, an OPAC, an ISBN lookup service, or a MARC record import. We are committed to not overstating what is built. If you need those features today, this platform is not the right fit yet.
It means you are building alongside us. Early-access schools shape the platform’s direction — the reading-list structures, the research-workflow templates, the media-literacy frameworks, and the publishing hub integrations. It also means you see the honest state of development, not a polished sales deck. There is no pricing commitment and no signup required to have a conversation.
Book a conversation. We talk through your media center’s actual program — what your students need, what your current tools miss, how research and publishing work in your school — and map that against what is built and what is coming. To book: email [email protected].