This FAQ explains how to use the Alma TXT export method (manual or automated job export via SFTP) to provide holdings data to BrowZine.
This FAQ applies specifically to the TXT export method. If you are using the OAI-PMH Publishing Profile method instead, please refer to the Alma Publishing Profile FAQ.
1. What is the TXT export method?
The TXT export method uses Alma’s Export Electronic Portfolios or Export Electronic Titles job to generate a structured TXT (tab-delimited) file that is uploaded to BrowZine.
This export may be:
A one-time manual export
A scheduled job
An automated SFTP delivery
Unlike the OAI Publishing Profile, TXT exports are full snapshot files and do not rely on incremental OAI harvesting or the BrowZine normalization rule.
2. Does TXT export require Electronic Titles or Electronic Portfolios?
It depends on your Alma configuration.
Single-campus Alma
Electronic Titles are recommended.
Title-level export is simple and consistent when campus separation is not a concern.
Multicampus Alma (Shared Institution Zone)
Electronic Portfolios are recommended when campus-level scoping is required.
In multicampus environments, portfolio-level export:
Reflects actual scoped holdings more deterministically
Avoids known limitations with Alma’s OAI publishing and group-based availability
Prevents unintended campus bleed-through at the title level
3. Why would multicampus institutions use Electronic Portfolios instead of Titles?
In a multicampus Alma configuration:
Multiple institutions share one Institution Zone (IZ)
Campus codes, local coverage, or Alma Groups may be used to separate holdings
Title-level exports can:
Aggregate portfolios across campuses
Mask gaps between portfolios
Reflect unintended campus availability if not carefully scoped
Portfolio-level export ensures:
One row = one portfolio
Only the portfolios included in the defined set are exported
Cleaner and more predictable campus isolation
For institutions requiring strict campus separation, portfolio export is typically the safer approach.
4. Will BrowZine accept one row per portfolio?
Yes.
BrowZine supports TXT files that contain one row per portfolio.
Duplicate ISSNs across multiple providers or packages are expected and supported.
Each row represents a distinct access source and is processed accordingly.
5. How often should TXT exports be run?
Unlike OAI publishing, TXT exports are not automatically harvested.
The frequency depends on how the export is configured:
Manual upload → whenever you generate and submit a file
Scheduled Alma job → according to your job schedule
Automated SFTP → according to your scheduled job frequency
Most libraries run TXT exports weekly.
6. Does TXT export use the BrowZine normalization rule?
No.
TXT export does not rely on the custom BrowZine normalization rule used in the OAI Publishing Profile.
The TXT file must simply conform to the required BrowZine schema (column names and formatting).
Because normalization rules are not involved:
Title-level consolidation behavior is not required
Portfolio-level export is fully supported
7. How should multicampus institutions define their set?
For multicampus environments using portfolio-level export:
Your Logical Set should be defined at the Electronic Portfolio level and scoped to include only the desired campus holdings.
Depending on your Alma configuration, filters may include:
Portfolio Campus Code
Owning Institution
Available For Group
Local Coverage
Collection-level campus scoping
Set configuration should ensure that portfolios belonging to other campuses are excluded from the export.
8. How can we validate our TXT export before sending it to BrowZine?
We recommend verifying:
Only Material Type = Journal is included.
No unintended campus codes appear in coverage_notes.
The row count aligns with expected campus holdings.
Coverage dates and embargo values appear correctly formatted.
This validation step is especially important in multicampus environments.
9. When should TXT export be used instead of OAI Publishing?
TXT export may be preferred when:
Multicampus scoping is complex
Group-based availability is not reliably reflected in OAI publishing
You require deterministic campus-level isolation
You prefer snapshot-based exports over incremental publishing
For single-campus institutions with straightforward holdings, the OAI Publishing Profile method is typically sufficient.