Merge pull request #3 from ABCD-DEVCOM/documentation-3.3.x

Archives version 3.2.x documentation and creates version 3.3.x structure

Author: rogercgui

docusaurus.config.js

@@ -66,10 +66,20 @@ const config = {
 
           versions: {
             current: {
-              label: '3.2.X', // O nome no menu dropdown
+              label: '3.3.X', // O nome no menu dropdown
               path: '',       // <--- O TRUQUE: Deixar vazio remove o prefixo da URL
               banner: 'none', // Remove o aviso de "versão não lançada"
             },
+            '3.2': {
+              label: '3.2.x',
+              path: '3.2',
+              banner: 'none',
+            },
+            '2.0': {
+              label: '2.0.x',
+              path: '2.0', 
+              banner: 'none',
+            },
           },
 
           // Outras configurações visuais úteis

versioned_docs/version-3.2/abcd-administration/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "Database Architecture and Administration",
+    "position": 6,
+    "link": {
+        "type": "generated-index",
+        "description": "Everything a system administrator needs to know to keep ABCD running."
+    }
+}

versioned_docs/version-3.2/abcd-administration/access-management/_category_.json

@@ -0,0 +1,8 @@
+{
+  "label": "Access Management",
+  "position": 4,
+  "link": {
+    "type": "doc",
+    "id": "index"
+  }
+}

versioned_docs/version-3.2/abcd-administration/access-management/index.md

@@ -0,0 +1,22 @@
+---
+title: Access Management Overview
+sidebar_label: Access Management
+---
+
+# Access Management
+
+Security in ABCD is controlled by a relationship between **Operators** (who logs in) and **Profiles** (what they can do). This section guides administrators through configuring secure access to the system.
+
+## Core Concepts
+
+### 1. Profiles (Authorization)
+Profiles act as templates for permissions. Instead of assigning rights to each user individually, you define a role (e.g., "Cataloger", "Loan Officer") and assign users to that role.
+* **[Manage Profiles](profiles.md)**: Learn how to create and edit permission sets.
+
+### 2. Operators (Authentication)
+Operators are the actual user accounts. Each operator must be assigned to a valid profile to access the system.
+* **[Manage Operators](operators.md)**: Learn how to create users, reset passwords, and restrict access by library branch.
+
+:::tip Security Best Practice
+Avoid using the generic `adm` or `abcd` accounts for daily work. Create individual accounts for every staff member to ensure actions can be traced back to a specific person in the system logs.
+:::

versioned_docs/version-3.2/abcd-administration/access-management/operators.md

@@ -0,0 +1,53 @@
+---
+title: User Management
+sidebar_label: User Management
+---
+
+# User Management
+
+Effective user management is essential for system security. In ABCD, access control is managed via two interacting components: **Operators** (the people) and **Profiles** (the permissions).
+
+All user data is stored in the `acces` database.
+
+## 1. Access Profiles
+
+Before creating users, you must define what they can do. Profiles act as templates for permissions.
+
+* **Path:** **Central > Administration > User administration > Create/edit profiles**
+
+Instead of assigning permissions to each person individually, you create a profile (e.g., `loan_operator`) and assign it to multiple users. If you update the profile, all associated users are updated instantly.
+
+:::tip Strategy
+Create strict profiles. It is better to have a `cataloger` profile that *only* accesses the Cataloging module than to give everyone the `adm` (Administrator) profile.
+:::
+
+## 2. Managing Operators
+
+Operators are the individual accounts used to log in to the system.
+
+* **Path:** **Central > Administration > User administration > User administration**
+
+### Creating a New Operator
+
+To create a new account, click **New user** and complete the following fields:
+
+#### Essential Fields
+* **Username**: The login ID. Case sensitive (e.g., `maria`). **Avoid spaces or special characters.**
+* **Full name**: The real name of the staff member (e.g., `Maria Silva`).
+* **Profile**: Select the authorization level defined in the previous step.
+* **Password**: Define the initial password.
+* **Confirm password**: Retype to validate.
+
+#### Advanced Configuration
+* **Library Code**: Critical for multi-branch libraries. Restricts the operator to managing copies owned by a specific branch (e.g., `MAIN`, `MED`).
+* **Cataloger Code**: A short code (e.g., `MS`) recorded in the database logs (typically field 900) to audit who created or modified a record.
+* **Expiration Date**: YYYYMMDD format. The account effectively locks after this date. Useful for temporary staff or students.
+
+### Maintenance Tasks
+
+* **Reset Password**: If a user forgets their password, edit their record here. You cannot see the old password (it is encrypted), but you can overwrite it with a new one.
+* **Deactivate User**: To remove access without losing the history of records created by that user, set an **Expiration Date** in the past (do not delete the record unless necessary).
+
+:::danger Security Best Practice
+Never share the generic `abcd` or `adm` accounts. Every staff member must have their own named account to ensure accountability in the system logs.
+:::

versioned_docs/version-3.2/abcd-administration/access-management/profiles.md

@@ -0,0 +1,36 @@
+---
+title: Profiles and Permissions
+sidebar_label: Profiles & Permissions
+sidebar_position: 3
+---
+
+# Profiles and Permissions
+
+In ABCD, permissions are not defined checkbox-by-checkbox for every user. Instead, you define **Profiles** (Roles), and assign users to these profiles.
+
+## How Profiles Work
+A profile is essentially a list of authorized system functions. If a function is not listed in the profile, the menu option will not appear for that user.
+
+Common examples of profiles included by default:
+* **`adm` (System Administrator):** Has access to everything, including file editing and database creation.
+* **`dbadmin` (Database Administrator):** Can manage database structures (FDT/FST) but cannot change system core files.
+* **`operator` (Cataloger):** Can search and edit records but cannot delete databases or change structures.
+* **`loan` (Circulation):** Can only access the Loan module.
+
+## creating or Editing a Profile
+1.  Go to **Administration > User administration**.
+2.  Click on **Create/edit profiles**.
+
+### The Profile Editor
+The editor shows a tree view of all available system functions.
+
+1.  **Select a Profile:** Choose an existing one to edit or type a new name to create one.
+2.  **Grant Permissions:**
+    * Browse the tree structure.
+    * **Check** the boxes for the modules and functions this profile should access.
+    * *Example:* For a "Student Assistant", you might only check **Cataloging > Data Entry** and uncheck everything else.
+3.  **Save:** Click the save button to write the changes to the profile file.
+
+:::tip File Location
+Profiles are physically stored as text files in `bases/par/profiles/`. Advanced users can edit these files directly to create highly granular restrictions.
+:::

versioned_docs/version-3.2/abcd-administration/backup-restore.md

@@ -0,0 +1,101 @@
+---
+title: Backup and Restore
+sidebar_label: Backup & Restore
+sidebar_position: 8
+description: Strategies for data preservation, including the Backup Manager tool, ISO 2709 exports, and file-system backups.
+---
+import Video from '@site/src/components/Video';
+
+# Backup and Restore Strategies
+
+Data preservation in ABCD relies on multiple layers of security. You can use the built-in **Backup Manager** for quick snapshots of your environment, the **ISO 2709 standard** for bibliographic data exchange/preservation, or manual **file-system backups** for server-level redundancy.
+
+---
+
+## 1. The Backup Manager (New)
+
+The **Backup Manager** is a built-in tool introduced in recent versions that allows system administrators to create compressed backups (`.zip`) of the database structures and records directly from the administrative interface.
+
+### Accessing the Tool
+1. Go to the **System Configuration** menu (Central Module).
+2. Click on **Backups**.
+
+<Video src="https://www.youtube.com/embed/pX8h9m5SPbk" />
+
+:::info
+You must have administrative privileges (`adm` profile) to access this tool.
+:::
+
+### Creating a Backup
+The tool offers three specific backup strategies:
+
+#### A. Full Backup (No Media)
+* **Filename tag:** `FULL_NOMEDIA`
+* **Includes:** All databases found in the `bases/` directory.
+* **Excludes:** Temporary files (`wrk/`) and digital object folders (`collection/`).
+* **Best for:** Routine backups. It saves all bibliographic data and structures without heavy digital files, resulting in a lightweight `.zip` file.
+
+#### B. Full Backup (With Media)
+* **Filename tag:** `FULL_MEDIA`
+* **Includes:** All databases in `bases/`, **including** the `collection/` folders (digital objects).
+* **Excludes:** Only the `wrk/` folder.
+* **Best for:** Complete system snapshots including PDFs and images.
+* **⚠️ Warning:** Depending on your collection size, this file can be extremely large and take a long time to generate.
+
+#### C. Single Database
+* **Filename tag:** `DB-[BASENAME]`
+* **Includes:** Only the folder of the specific database selected.
+* **Excludes:** The `collection/` folder of that specific base.
+* **Best for:** When you have made changes to a specific database definition or want to export a single set of records.
+
+### Operating System Detection
+Since ABCD uses ISIS database technology, files generated on Windows are not always compatible with Linux/Unix (due to case-sensitivity). The system automatically adds a prefix to the filename:
+* **`Win_`**: Created on a **Windows** server.
+* **`Lin_`**: Created on a **Linux/Unix** server.
+
+### Managing Backups
+The tool lists all available backups stored on the server (in `/bases/wrk/backups/`). You can **Download** them to your local computer or **Delete** them to save server space.
+
+---
+
+## 2. ISO 2709 Export/Import (Standard)
+
+While the Backup Manager zips the physical files, the **ISO 2709** format is the international standard for bibliographic data interchange. This is the safest way to migrate data between different operating systems (e.g., moving from Windows to Linux) or between different library software (e.g., Koha to ABCD).
+
+### Exporting to ISO (Backup)
+1. Navigate to **Utilities > Export/Import > Export ISO**.
+2. Select the Database.
+3. **Parameters**:
+    * **FST**: Usually leave blank to export all fields (or select an FST to export only indexed fields).
+    * **Type of conversion**: ANSI or UTF-8 (depending on your target system).
+    * **Separator**: Usually `#` or another unique character.
+4. Click **Export**.
+5. Download the resulting `.iso` file to your local machine.
+
+### Importing from ISO (Restore)
+To restore data or migrate from another system:
+
+1. Navigate to **Utilities > Export/Import > Import ISO**.
+2. **Upload** your `.iso` file to the server.
+3. Select the target Database.
+4. **Options**:
+    * **Append**: Adds records to the end of the existing database.
+    * **Create/New**: **Erases** the existing database and creates a new one from the ISO.
+5. Click **Import**.
+
+:::warning Data Loss Risk
+Using the "Create" option will delete all existing records in the selected database. Ensure you have a backup before proceeding.
+:::
+
+---
+
+## 3. Manual Server-Side Backup
+
+If you are a system administrator with access to the server's file system, you may prefer to use tools like `rsync`, `tar`, or standard backup software.
+
+The **Backup Manager** (Section 1) essentially automates the zipping of the `/bases/` directory, but for a total system restoration (including the software executables), you should ensure the following directories are preserved:
+
+* **`/bases/`**: Contains all data, FDTs, PFTs, and uploaded documents.
+* **`/htdocs/central/config.php`**: The main configuration file containing paths and URLs.
+* **`/cgi-bin/*.par`**: Parameter files defining database paths.
+* **`/htdocs/`**: If you have customized PHP scripts or added a custom OPAC design.

versioned_docs/version-3.2/abcd-administration/databases-registry.md

@@ -0,0 +1,18 @@
+---
+title: The Database Registry (bases.dat)
+sidebar_label: The Registry (bases.dat)
+sidebar_position: 3
+---
+
+# The Database Registry (bases.dat)
+
+Unlike some modern systems that automatically scan folders, ABCD requires you to explicitly "register" a database for it to appear in the selection menu. This registry is a plain text file named **`bases.dat`**.
+
+**Location:** `bases/bases.dat`
+
+## File Structure
+
+The file is a simple list where each line represents a database available in the system. The syntax relies on a pipe character (`|`) as a separator between the internal folder name and the public label.
+
+```text
+folder_name|Description displayed in menu