Skip to Main Content

The Vault - JIBC's Institutional Repository: What goes in The Vault

Who can contribute?

The Vault includes work created by individuals or groups affiliated with a JIBC division, program, research team, working group, collaborative project, or conference, such as:

  • JIBC faculty, researchers, and staff
  • JIBC schools, divisions and academies
  • JIBC research projects
  • Undergraduate students with faculty sponsorship

Other Institute-affiliated entities will be considered on a case-by-case basis.

Questions?

Email vault@jibc.ca.

What goes in The Vault?

The Vault collects scholarly materials created by the Justice Institute of British Columbia community, as well as important documents related to the institute's history, which are made freely available to the public.

Current collection efforts will focus on building up several core content areas:

  • Faculty, staff and researcher scholarship (articles, presentations, multimedia)
    • Works must be created or published while the author is affiliated with JIBC.
    • The work must show the affiliation with JIBC.
    •  Theses are not added to The Vault. They are usually stored in the repository of the granting institution. 
  • Student capstone projects
    • Instructors recommend exceptional capstones (including posters and research briefs) for inclusion
  • Documentation of JIBC-hosted conferences and events (papers, presentations, programs, videos, proceedings)
  • Research reports 
  • Institute reports (academic plans, annual reports, financial reports and strategic plans)

Other types of materials will be considered on a case-by-case basis. 
If you would like to deposit your work and are unsure if you fit these requirements, please contact vault@jibc.ca
Items are added to The Vault with the permission of the author/creator, and when permitted under Copyright law.

Limits on Public Access to Materials

A Submitter may request that their Materials be withheld from public access for a certain period of time (otherwise known as a publication delay or embargo). The application and approval process for a publication delay/embargo is as follows:

  1. All requests must be made to the JIBC Library at the time of submission, together with the reason for the publication delay/embargo (for example: pending publication, publisher embargo, and/or the confidential or commercially sensitive nature of the information the Materials contain).
  2. The JIBC Library will consider all of the circumstances when making determinations regarding whether to grant a publication delay/embargo, and the length of any such delay. The JIBC Library is not obligated to approve any request for a publication delay/embargo, but the JIBC Library will respect publication delay/embargo policies agreed upon by the JIBC Library and groups representing Submitters or setting standards for Submissions (e.g. faculties).
  3. A publication delay/embargo agreed upon by the JIBC Library and the Submitter is only valid and binding after it has been put into writing.

Retention and withdrawal

Retention Period

Once an item is deposited in the repository a persistent URL will be generated. The Vault is meant to be a permanent scholarly record. Items will be stored indefinitely.

Withdrawal

Items may not normally be withdrawn from the repository. Acceptable reasons for withdrawal include, but are not limited to:

  • proven copyright violation or plagiarism
  • legal requirements and proven violations
  • falsified research

Withdrawn Items

Withdrawn items are not deleted, per se, but are removed from public view. Withdrawn items' identifiers/URLs are retained indefinitely. Original URL's will continue to point to ‘tombstone' citations, to avoid broken links and retain item histories.The metadata of withdrawn items will not be searchable.

Version Control

Changes to deposited items are not permitted. Errata and corrigenda may be included with the original record, if required. If necessary, an updated version may be deposited. There will be links between the earlier and later versions, with the most recent version clearly identified.Items are allocated a checksum to facilitate the detection of alterations