Why English? | Reading BASE Document Types, Open-Access Status and Repository Sources Before Choosing Research

BASE research literacy matters because a search record harvested from a repository, an open-access indicator, a normalised document type, a language label, a licence code and a link to a source landing page describe different parts of discoverability and reuse.

For students, parents, educators and adult learners, precise English prevents “found in an academic search engine” from becoming “peer reviewed,” “open access” from becoming “free to reuse without conditions,” and an unknown access flag from becoming proof that no lawful full text exists.

This guide uses current official BASE and Bielefeld University Library information checked on 3 November 2026. It explains repository harvesting, normalised document types, open-access status, licence mapping, language and subject fields, identifiers, source links and duplicate-looking records; BASE improves discovery, but the originating repository and document still need direct checking.

Reading routes

• Understand BASE and harvested records
• Read document types and language
• Interpret open access and licences
• Verify repositories, versions and citations
• Run the BASE source check

Chapter 1 of 18: BASE is a discovery service over many content providers

What this BASE record, field or status actually represents

BASE harvests and indexes metadata from repositories and academic web sources. A result is therefore part of an aggregated search layer over records maintained elsewhere.

The access and provenance wording that protects the reader

Use aggregator for the discovery service, provider for the repository or collection and work for the underlying research object.

For BASE is a discovery service over many content providers, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A student finds a thesis in BASE and follows the link to the university repository that hosts its record and file.

Aggregator coverage and provider freshness can differ.

• Record the BASE search.
• Name the provider.
• Open the source page.
• Check update dates.

Draw the route from query to work.

The reasoning in BASE is a discovery service over many content providers transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Next chapter

Chapter 2 of 18: A harvested record is metadata, not automatically full text

What this BASE record, field or status actually represents

BASE indexes descriptive fields and links to source landing pages. Some records lead to full text; others expose only metadata or uncertain access.

The access and provenance wording that protects the reader

The verbs indexed, linked and read mark different states. Finding a record does not mean the whole document was examined.

For A harvested record is metadata, not automatically full text, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A learner records that an abstract was available but waits for authorised full text before quoting the methods.

Repository interfaces and file availability can change.

• List visible fields.
• Open the provider link.
• Identify available files.
• Mark reading extent.

Write a found-versus-read log.

The reasoning in A harvested record is metadata, not automatically full text transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 3 of 18: Repository provenance helps explain the record

What this BASE record, field or status actually represents

The BASE collection or provider field indicates where metadata came from. Provenance can help interpret institutional context, update responsibility and access route.

The access and provenance wording that protects the reader

The phrase from a repository does not necessarily mean created by or endorsed by that institution. Repositories can host work by affiliates or collections.

For Repository provenance helps explain the record, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A student distinguishes the university hosting the thesis from the author and awarding department.

Provider names can change and imported collections can contain legacy records.

• Record repository name.
• Read the local record.
• Check author affiliation.
• Avoid endorsement claims.

Write a provenance sentence with three roles.

The reasoning in Repository provenance helps explain the record transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 4 of 18: Heterogeneous metadata requires careful normalisation

What this BASE record, field or status actually represents

BASE documentation notes that Dublin Core fields are used heterogeneously across providers and describes efforts to normalise selected fields. Normalisation supports broad searching.

The access and provenance wording that protects the reader

The verb normalise means map varied source values into more consistent categories; it does not erase every ambiguity.

For Heterogeneous metadata requires careful normalisation, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

Several repositories label theses differently, while BASE maps them toward a shared document-type category.

Source values and normalised values can disagree or lose local detail.

• Read the normalised field.
• Open the original record.
• Preserve useful local labels.
• Report ambiguity.

Compare two provider values and one mapped category.

The reasoning in Heterogeneous metadata requires careful normalisation transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 5 of 18: Document type is a category, not an evidence grade

What this BASE record, field or status actually represents

BASE documents normalised types such as journal article, conference object, report, course material, thesis, manuscript, patent, software and dataset. The label helps choose a reading strategy.

The access and provenance wording that protects the reader

A thesis is not a journal article; a manuscript is not necessarily a final publication; a dataset is not an interpretation.

For Document type is a category, not an evidence grade, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A student filters to doctoral theses for detailed methods, then checks later articles for peer-reviewed updates.

Type mapping can be unknown or too broad when provider metadata is weak.

• Read the type.
• Open the item.
• Check publication state.
• Use the matching appraisal.

Assign a reading job to six types.

The reasoning in Document type is a category, not an evidence grade transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 6 of 18: A thesis record needs institution, degree and date context

What this BASE record, field or status actually represents

Theses can contain substantial original work and detailed literature reviews, but their examination and publication context differs from journal publishing.

The access and provenance wording that protects the reader

Use submitted, awarded, published and deposited only for the events shown.

For A thesis record needs institution, degree and date context, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A learner checks the title page and repository statement before describing a doctoral thesis as completed.

A deposited thesis can have later corrections, embargoes or derived articles.

• Check degree and institution.
• Read date labels.
• Find later publications.
• Cite the version used.

Build a thesis identity line.

The reasoning in A thesis record needs institution, degree and date context transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 7 of 18: Conference objects and manuscripts can be preliminary

What this BASE record, field or status actually represents

BASE can classify conference objects and manuscripts separately from journal articles. These materials may surface emerging work or fuller versions of talks.

The access and provenance wording that protects the reader

The adjective preliminary should be based on status and content, not used as a casual dismissal.

For Conference objects and manuscripts can be preliminary, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A student finds a conference paper, checks whether a journal version exists and labels both accurately.

The records may overlap without being exact duplicates.

• Check event and date.
• Search title and authors.
• Compare versions.
• Avoid double counting.

Create a version relationship note.

The reasoning in Conference objects and manuscripts can be preliminary transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 8 of 18: Language fields can be original, normalised or unknown

What this BASE record, field or status actually represents

BASE documentation distinguishes provider language values and normalised language codes. Unknown values reflect missing or unrecognised metadata, not necessarily an unreadable document.

The access and provenance wording that protects the reader

Use language metadata unknown rather than “the document has no language.”

For Language fields can be original, normalised or unknown, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A multilingual thesis has an English abstract and another full-text language; the learner records both.

Automatic and provider-supplied language fields can be incomplete.

• Open the document.
• Check title and abstract languages.
• Record full-text language.
• Do not infer from repository country.

Write a multilingual access note.

The reasoning in Language fields can be original, normalised or unknown transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 9 of 18: Open-access status has more than one documented state

What this BASE record, field or status actually represents

BASE documentation distinguishes Open Access, Not Open Access and Unknown in its indexed status field. The third state matters.

The access and provenance wording that protects the reader

Unknown means the system lacks a conclusive status; it is not a synonym for closed, paid or inaccessible.

For Open-access status has more than one documented state, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A learner follows an unknown-status record to the repository and finds an authorised file after checking the item page.

A status can lag behind provider changes or depend on what BASE could recognise.

• Read the exact status.
• Open the source page.
• Check file availability.
• Date the observation.

Rewrite three binary access claims to include uncertainty.

The reasoning in Open-access status has more than one documented state transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 10 of 18: Open access concerns reading availability; licences govern reuse

What this BASE record, field or status actually represents

A document can be readable without a clearly recognised open licence, and an open licence can impose attribution, share-alike, non-commercial or no-derivatives conditions.

The access and provenance wording that protects the reader

The word open should not be expanded into “anything is allowed.” Access and reuse are separate questions.

For Open access concerns reading availability; licences govern reuse, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A student reads an openly accessible paper but checks the licence before adapting a figure.

Fair use, quotation and licensing rules depend on jurisdiction and purpose; obtain advice for high-stakes reuse.

• Locate the licence.
• Read its version and conditions.
• Attribute correctly.
• Seek permission when uncertain.

Compare reading permission with adaptation permission.

The reasoning in Open access concerns reading availability; licences govern reuse transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 11 of 18: Licence mapping can be useful without being exhaustive

What this BASE record, field or status actually represents

BASE maps recognised rights values to standard licence categories where possible and documents that source rights fields vary widely.

The access and provenance wording that protects the reader

A mapped licence is a normalised interpretation of provider metadata. Verify the exact statement on the repository page.

For Licence mapping can be useful without being exhaustive, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A learner sees CC BY in the aggregated record, then confirms the licence and version on the item page before reuse.

Unrecognised, conflicting or missing rights text should remain uncertain.

• Read BASE value.
• Open provider rights statement.
• Check version.
• Preserve evidence of permission.

Audit one licence route end to end.

The reasoning in Licence mapping can be useful without being exhaustive transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 12 of 18: Free full text does not prove peer review

What this BASE record, field or status actually represents

Repositories host many legitimate object types: accepted manuscripts, theses, reports, data, teaching materials and journal versions. Access status and review status are independent.

The access and provenance wording that protects the reader

Use openly accessible for availability and peer reviewed only when the publication process is documented.

For Free full text does not prove peer review, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A student finds an accessible manuscript, then checks the journal record for peer-review and version information.

Repository labels can vary, and some peer-reviewed works are closed while some open works are not reviewed.

• Read the object type.
• Check publication venue.
• Look for version labels.
• Avoid access-to-quality shortcuts.

Build a two-axis access/review table.

The reasoning in Free full text does not prove peer review transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 13 of 18: The provider link is the route to version and file truth

What this BASE record, field or status actually represents

BASE’s canonical link field points to a repository splash or landing page. That page can show files, dates, licences, identifiers and local notes.

The access and provenance wording that protects the reader

A landing page describes the object and its files; a direct PDF link can omit crucial context.

For The provider link is the route to version and file truth, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A learner saves the landing page identifier and uses the PDF only after reading version and rights information.

Direct files can move while landing pages persist, but repositories can also redesign routes.

• Save persistent identifiers.
• Prefer the record page.
• Check file labels.
• Record access date when required.

Explain why a landing page is safer than a copied download URL.

The reasoning in The provider link is the route to version and file truth transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 14 of 18: Identifiers help reconcile records from different providers

What this BASE record, field or status actually represents

BASE records can include URIs, DOIs, handles and other identifiers. Persistent identifiers help detect duplicates and trace the canonical source.

The access and provenance wording that protects the reader

An identifier names or routes to an object; it does not certify quality or guarantee that every copy is the same version.

For Identifiers help reconcile records from different providers, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A student matches two records by DOI, then keeps one citation while noting that one repository hosts an accepted manuscript.

Some works lack persistent identifiers or use multiple identifiers at different levels.

• Resolve identifiers.
• Match title and authors.
• Compare versions.
• Keep level-specific IDs.

Build an identifier hierarchy.

The reasoning in Identifiers help reconcile records from different providers transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 15 of 18: Duplicate-looking repository records can represent useful version history

What this BASE record, field or status actually represents

Aggregators can show records from several providers or multiple deposits. Similar titles may be duplicates, versions or related objects.

The access and provenance wording that protects the reader

Use duplicate record only after checking identifiers, files, dates and version labels.

For Duplicate-looking repository records can represent useful version history, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A preprint, accepted manuscript and Version of Record share a title but support different status statements.

Over-aggressive deduplication can erase access routes or correction information.

• Compare identifiers.
• Read version labels.
• Choose a citation target.
• Keep alternate lawful access notes.

Classify four record pairs.

The reasoning in Duplicate-looking repository records can represent useful version history transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 16 of 18: Subject and Dewey fields support discovery, not final relevance

What this BASE record, field or status actually represents

BASE documents subject and classification fields, including assigned or automatically produced Dewey codes. These can broaden or narrow discovery.

The access and provenance wording that protects the reader

A classification places a record in a scheme; it is not a summary of every argument in the work.

For Subject and Dewey fields support discovery, not final relevance, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A learner follows a subject facet to adjacent fields, then reads abstracts and methods before inclusion.

Automatic classification can be broad or imperfect, and interdisciplinary work can span categories.

• Use classification for exploration.
• Inspect the title and abstract.
• Check interdisciplinary terms.
• Evaluate item-level fit.

Describe one record under two plausible subjects.

The reasoning in Subject and Dewey fields support discovery, not final relevance transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 17 of 18: Search and filter choices should be recorded with the date

What this BASE record, field or status actually represents

A reproducible BASE search preserves keywords, fields, type, language, access status, provider and date. This allows another reader to understand the set.

The access and provenance wording that protects the reader

The verbs retrieved, screened, opened and included describe different stages.

For Search and filter choices should be recorded with the date, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A student saves a broad query, screens fifty records, opens ten full texts and includes four with reasons.

The index changes as repositories update and new providers are harvested.

• Save exact query.
• Record filters.
• Date the search.
• Keep inclusion reasons.

Write a five-line BASE search log.

The reasoning in Search and filter choices should be recorded with the date transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Next chapter

Chapter 18 of 18: A complete source card separates discovery, access and appraisal

What this BASE record, field or status actually represents

The strongest note records the BASE query, provider, object type, persistent identifier, version, access state, licence, reading extent and evidence judgement.

The access and provenance wording that protects the reader

The nouns record and source remain different: the record describes; the source argues, reports or stores data.

For A complete source card separates discovery, access and appraisal, complete the discovery note: “BASE harvested this record from __; it labels the type __ and access __; the repository page shows __; the identifier and version are __; the licence permits __; I read __; the source supports only __.” Keep the aggregator, provider, record and work separate.

A repository-search example, boundary and next move

A learner can explain how an open repository manuscript was found, which version was read and why it supports only a bounded claim.

Transparent provenance cannot rescue irrelevant or weak evidence, but it makes the weakness visible.

• Record discovery.
• Verify identity.
• Read the source.
• Explain inclusion.

Present one complete source card to a peer.

The reasoning in A complete source card separates discovery, access and appraisal transfers to CORE, OpenAIRE, institutional repositories and library discovery systems. Treat aggregator metadata as a discovery aid, follow the canonical source route and verify access, licence, version and evidence on the originating record.

Back to reading routes · Previous chapter · Continue to the FAQ

A twenty-minute BASE source check

Move from an aggregated search result to a verified repository source with honest access, version and licence language.

• Write the research question and save the dated BASE query.
• Read the normalised type, language, provider and access fields without treating them as verdicts.
• Open the repository landing page and verify title, contributors, date and identifier.
• Name the version and the extent actually read.
• Read the exact licence before reusing text, figures or data.
• Appraise the source’s method and fit before including it.

For parents and educators: ask the learner to show the BASE record and the originating repository page side by side. The differences make metadata and source checking easy to teach.

For students: BASE is a powerful door into open research. Walk through the door: verify the repository record, read the actual work and keep access, licence and quality as separate questions.

Frequently asked questions

Does a BASE result always include full text?

No. BASE indexes metadata and links to providers; the available file and access state must be checked on the source page.

Does “unknown” mean not open access?

No. It means the access status was not conclusively identified in the indexed metadata.

Is every open-access item peer reviewed?

No. Access status and review status are independent.

Can I reuse anything I can read?

No. Check the exact licence and applicable law before reuse.

Why can the same title appear more than once?

Different providers, versions or duplicate records can describe related material; compare identifiers and version labels.

Useful next reading

• BASE search
• BASE OAI documentation: fields, types, access and rights
• Bielefeld University Library: BASE project
• Bielefeld University Library: research and BASE
• Bielefeld University Library information for academic staff
• English Learning Hub: Primary to adult English
• Google Scholar for students: source and citation checks
• Zotero for students: research, citations and bibliographies
• How literature search and research discovery work
• How scholarly indexing works
• How citation works
• How research methods and source evaluation work
• How to use a library for academic journals and research papers

English matters in BASE because aggregator, provider, harvested record, document type, normalised field, open, closed, unknown, licence, identifier, landing page and version describe different discovery layers. Precise reading turns a promising result into a source that can be identified, accessed, reused and evaluated honestly.