
Start your digital archive system requirements with the tasks people need to complete: finding a record, understanding what it contains, accessing the permitted version and recovering it after a problem. Turn those tasks into tests before comparing software proposals.
For a Nigerian university, library or business, that approach makes a supplier demonstration more useful. You can judge a proposed system against your collection and working conditions, with evidence for each requirement.
List the record types, approximate file count, annual growth and largest files. Include scanned books, photographs, audio and born-digital documents where relevant. Identify the people who contribute, review, administer and use the collection.
Write down which material is public, restricted to staff, or available only to named groups. Include network conditions, storage arrangements and staff capacity. These details influence configuration, hosting and training costs.
| Requirement | Demonstration to request |
|---|---|
| Search and discovery | Find a known item by title, creator, subject and a word inside its searchable text. |
| Metadata consistency | Import sample records and identify missing required fields and duplicate identifiers. |
| Access controls | Show what a public user, staff member and administrator can each see and download. |
| Export and portability | Export sample files and metadata, retaining their identifiers and relationships. |
| Recovery | Explain backup responsibilities and demonstrate restoration in an agreed test environment. |
| Usability | Ask a librarian or records officer to add and retrieve an item without coaching. |
Give each requirement an owner and priority. Separate essential launch needs from later improvements. Record whether the supplier demonstrated the function, proposed configuration work or identified a paid addition.
Prepare a small, authorised collection with varied file types, repeated names, incomplete records and at least one restricted item. Give the supplier a written script. For example: find a thesis when the user knows its subject but cannot remember the exact title.
Ask ordinary users to attempt the same tasks. Record how long each task takes, whether the result is correct and what assistance was required. A successful demonstration with the supplier’s own sample does not establish how your records will behave.
Request separate figures for setup, metadata cleaning, migration, hosting, storage growth, user training and support. Ask who maintains the software and how updates are tested. Agree the support period and escalation route in writing.
Include the work your institution must do: approving a metadata scheme, preparing files, assigning administrators and checking the migration. A system can meet a feature list and still launch late if those responsibilities remain unassigned.
A public collection may prioritise browsing, descriptive metadata and research access. An internal document system may prioritise approvals, version control and staff permissions. Map both needs before choosing whether one platform or connected systems are appropriate.
Read our explanation of what a digital archive system does and our archive feature overview for background. Use this checklist to turn that background into a procurement brief.
A requirement becomes easier to evaluate when it describes a person, a task and a result. For example: a librarian must locate approved dissertations by department and year, inspect their descriptions and open the permitted reading copy. Another user may need to contribute a new item without being able to publish it immediately.
Write several journeys covering discovery, contribution, administration and restricted access. Include users who know only part of an item’s description. A researcher may remember a subject and approximate year, while a records officer may know a reference number. Test those different starting points instead of assuming everybody searches by exact title.
For each story, define what constitutes success and which evidence the evaluator should retain. A screenshot of an attractive search page does not show whether the expected result was found, whether access was correct or whether the user completed the task independently.
Give essential requirements a pass-or-fail gate before comparing weighted scores. If a proposed system cannot meet an approved access restriction or export requirement, a strong score for visual design should not conceal that problem. Record how any unmet essential requirement would be resolved and whether the proposed remedy has been demonstrated.
| Rating | Evidence |
|---|---|
| Not demonstrated | No working example or clear implementation response was provided. |
| Partially demonstrated | The task worked only partly or depended on an unresolved step. |
| Demonstrated with assistance | The task succeeded with supplier intervention that users may need again. |
| Demonstrated by intended user | A representative user completed the agreed task in the proposed setup. |
Agree the importance of each task with stakeholders before the demonstration. Keep notes alongside the score. Those notes often explain a practical limitation more clearly than a total number can.
Describe the condition of the source collection. Are filenames consistent? Do records have stable identifiers? Are there multiple descriptions for the same item? The answers affect the work needed before import and the reliability of the resulting catalogue.
Ask the supplier to demonstrate a pilot migration with your sample and show how rejected records are reported. Confirm who cleans the source data, maps fields, resolves duplicates and checks the result. Agree how revised records can be reloaded without accidentally creating duplicate items or overwriting approved descriptions.
Include an acceptance reconciliation: source items, imported items, exceptions and approved exclusions should be accounted for. A migration should not be accepted solely because an upload process completed. Test the links between metadata and files, and repeat searches with the migrated records rather than a separate demonstration collection.
A backup feature does not identify who checks that backups finish, who can restore them or how long a recovery would take. Ask those questions explicitly. Discuss recovery priorities with the institution’s IT team and confirm what the supplier will demonstrate within the proposed environment.
Do the same for user administration, storage expansion and security updates. Record the institution’s responsibilities and the service provider’s responsibilities in plain language. If a staff member leaves, there should be another authorised person who understands how to maintain the service.
For Nigerian organisations with variable connectivity or limited technical cover, test the actual deployment assumptions. Review what users can do during an interruption, what depends on a remote connection and how support is reached. Request a clear explanation of any local network, hosting or third-party service requirements.
Ask how your organisation can retrieve its files and descriptive records if it later changes systems. Request a sample export that includes stable identifiers, file references and the relationships required to understand the collection. Have the receiving technical team inspect that sample.
Clarify which elements are portable and which depend on the platform. Search configurations, custom workflows, user accounts and display layouts may require separate work in a replacement system. Knowing that distinction early helps the institution assess future effort without assuming that every configuration will transfer automatically.
Document any export fees, assistance requirements and practical restrictions in the proposal. The purpose is to understand ownership and continuity throughout the system’s life, including a possible transition years after launch.
Divide acceptance into a configured pilot, a limited live collection and the wider rollout. At each stage, specify the tests, responsible reviewers and unresolved issues that would prevent expansion. This gives staff a manageable opportunity to learn the workflow and identify problems before they affect the whole archive.
For an illustrative institutional repository, the pilot might cover one approved collection and a small contributor group. The next stage could add another department only after search, permissions and the submission review process have passed. The exact boundaries should follow the institution’s workload rather than a fixed item count borrowed from another project.
Keep the final requirements and test results with the project records. They give administrators a reference when assessing upgrades, adding collections or checking whether a later configuration change has affected an important user task.
Invite representatives of the collection, ordinary users, IT and the person responsible for the budget or procurement. Give them the requirements, test results, proposed responsibilities and unresolved issues in advance. Each group sees a different part of the service the institution is buying.
Ask the collection owner to confirm descriptive and access requirements, users to confirm the tested journeys, and IT to confirm deployment and maintenance assumptions. Procurement should check that the agreed deliverables and commercial exclusions are reflected in the proposal.
Record the decision and its conditions. If approval depends on a successful migration pilot or export demonstration, identify who will confirm that condition and what evidence they need. This prevents a provisional agreement from being remembered later as an unconditional acceptance of every aspect of the proposed system.
Yes, a defined pilot can help validate metadata, permissions and staff procedures. Agree its acceptance criteria before expanding the import.
Compare connectivity, support capacity, access needs, costs and the organisation’s security requirements. Ask suppliers to explain their proposed deployment rather than assuming one model fits every institution.
Need help turning a collection into a workable brief? Review NAINUWA with Eemediba or request a scoped consultation. Include your record types, users and launch priorities.