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 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 Alma 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?
TXT export uses the Export Electronic Portfolios job.
This ensures:
One row per portfolio
Platform-level granularity
Clear campus-level isolation when needed
Deterministic inclusion of scoped holdings
While Alma technically allows title-level export, BrowZine recommends portfolio-level export for consistency and predictability.
3. Why use Electronic Portfolios for TXT export?
Portfolio-level export provides:
One row = one access source
Accurate platform and coverage representation
Reliable campus-level scoping in multicampus environments
Cleaner separation when using campus codes, groups, or local coverage
Title-level export can aggregate portfolios under a single title, which may obscure platform-level distinctions or campus scoping differences.
For this reason, portfolio-level export is the recommended standard.
4. Will BrowZine accept one row per portfolio?
Yes.
BrowZine fully 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?
Manual upload → whenever you wish to generate and submit a file
Automated SFTP → typically weekly (we recommend Saturdays)
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 is processed exactly as generated by Alma’s Export Electronic Portfolios job.
Because normalization rules are not involved:
Portfolio-level export works without consolidation logic
Snapshot exports reflect the file exactly as generated
7. How should multicampus institutions define their set?
In multicampus or Shared Institution Zone (IZ) environments:
Your logical set should:
Be created at the Electronic Portfolio level
Include only the portfolios belonging to the intended campus(es)
Depending on your Alma configuration, filters may include:
Available explicitly for = [Campus Name]
Owning Institution
Portfolio Campus Code
Local Coverage
Group-based availability
Proper set scoping ensures portfolios from other campuses are excluded from the export.
In some Network Zone environments, inherited NZ content may require additional validation to ensure it is included in job exports. If expected NZ holdings do not appear, please contact us.
8. How can we validate our TXT export before sending it to BrowZine?
We recommend verifying:
Only Material Type = Journal is included
The row count aligns with expected campus holdings
Coverage dates and embargo values are correctly formatted
No unintended campus rows appear
If you operate in a Network Zone (NZ), expected Network-managed portfolios are included
If unintended campus rows appear and/or expected Network Zone content is missing, this typically indicates that the logical set requires adjustment in Alma. Please upload the file and include a note describing the issue you encountered. We will review the file and help determine the appropriate solution.
9. When should TXT export be used instead of OAI Publishing?
TXT export is typically appropriate when:
You operate in a multicampus or Shared Institution Zone (IZ) environment and
Campus-level scoping relies on Available For groups, campus codes, or local coverage and
Strict campus isolation is required but is not reliably reflected through OAI publishing
In these configurations, portfolio-level TXT export provides more predictable campus scoping.
For single-campus institutions with straightforward holdings and no group-based campus separation, the OAI Publishing Profile method is the recommended approach.