Skip to content

1. Overview and Access

This section explains who should use this manual, what it covers, and how to confirm you are ready to work in Vtext.

Goal

Understand the Vtext structure, permissions, and interface before creating or editing records.

Prerequisites

  • Staff account with appropriate Vtext permissions
  • Confirmed parent community or collection for the work
  • Metadata and files prepared in advance

Purpose of This Guide

  • Standardize staff workflows in the current Vtext interface
  • Reduce placement and metadata errors
  • Provide repeatable quality control checks

Who This Guide Is For

  • Repository administrators
  • Community and collection administrators
  • Staff responsible for item creation and maintenance

What This Guide Covers

  • Interface navigation
  • Creating communities
  • Creating collections
  • Adding items to collections
  • Editing existing content

Required Permissions

  • Community creation requires elevated administrative rights
  • Collection creation requires rights at the parent community level
  • Item creation and editing requires rights in the target collection

Repository Structure

  • Community: top-level organizational unit
  • Sub-community: nested unit under a community
  • Collection: container where items are deposited
  • Item: individual record containing metadata and files
  1. Identify the correct parent community or collection.
  2. Gather required metadata and files in advance.
  3. Review local Vtext policies for naming and controlled vocabularies.

Logging In

  1. Sign in with your staff credentials.
  2. Confirm you are authenticated by checking for staff/admin options.

Left-Side Management Sidebar

The left sidebar is the primary control panel for creating, editing, and administering records.

  • Management
  • New
  • Edit
  • Import / Export
  • Access Control
  • Admin Search
  • Registries
  • Curation Task
  • Processes
  • Workflow

Note

Sidebar options vary by permission level. If a menu is missing, verify your assigned role first.

QC Checklist

  • [ ] Staff account is confirmed and active
  • [ ] Correct destination in hierarchy is identified
  • [ ] Required metadata and files are ready
  • [ ] You can see the sidebar options needed for the task

Troubleshooting

  • Missing sidebar options: verify role permissions and contact a repository admin
  • Unsure where content belongs: pause and confirm hierarchy before creating records

Platform References