About our VEO creation products
Public Record Office Victoria (PROV) has developed technical code and tools to convert permanent and long-term value digital records into VERS Encapsulated Objects (VEOs).
The code and tools have been created for:
- software developers in Victorian Government agencies to develop in-house tools and processes to convert their digital records into VEOs for transfer to PROV and/or long-term storage
- commercial software developers to create and sell records management products that can generate VEOs.
See our VEO creation, Commercial VEO creation products and Information for vendors pages for further information.
|
If you plan to create VEOs as part of a digital records transfer project: Please first refer to our Digital records transfer step-by-step page for complete guidance about the transfer process. |
Technical development packages
Two types of VEOs are currently supported by PROV:
- Version 2 VEOs (created under the requirements of PROS 99/007 Management of Electronic Records Standard and its Specifications)
- Version 3 VEOs (created under the requirements of PROS 19/05 Create, Capture and Control Standard and its Specifications)
|
PROV recommends Version 3 VEOs where possible as these types of VEOs have less stringent metadata requirements and they support records with multi-level, hierarchical folder structures. Software developers should consult the relevant PROS 19/05 or PROS 99/007 Technical Specifications for the type of VEOs they are generating. |
PROV has developed packages to generate and/or validate VEOs. The latest versions of these packages are available on GitHub.
|
If you are interested in VERS3, please download the following packageshttps://github.com/PublicRecordOfficeVictoria/neoVEO |
| If you are interested in VERS2, please download the following packageshttps://github.com/PublicRecordOfficeVictoria/VERSCommon https://github.com/PublicRecordOfficeVictoria/V2Check https://github.com/PublicRecordOfficeVictoria/V2Generator |
In each case the packages are Apache NetBeans projects, and the package files should be placed in the same directory.
The packages contain:
- Java code for the tools
- Supporting JAR files
- Sample files (e.g. PFX for signing VEOs, schemas and templates)
- BAT files to demonstrate how applications can be run
- Word and TXT files to provide instructional information