Improve collections how to

Author: Ndpnt

content/collections/how-to/create-repositories.md

@@ -116,10 +116,3 @@ For collections within the Open Terms Archive organization:
    - Versions repository: "Triage" access
 4. Add team members
 5. Add repositories to Bots team with "Write" access
-
-## Verify setup
-
-1. Check that all repositories were created successfully
-2. Verify repository settings are correctly configured
-3. Ensure team permissions are properly set
-4. Test basic operations (e.g., creating an issue, making a PR)

content/collections/how-to/define-metadata.md

@@ -5,7 +5,7 @@ weight: 2
 
 # How to define metadata
 
-This guide will help you create the metadata.yml file for your Open Terms Archive collection.
+This guide will help you define the metadata for your Open Terms Archive collection.
 
 ## Prerequisites
 
@@ -18,68 +18,53 @@ This guide will help you create the metadata.yml file for your Open Terms Archiv
 1. Create a new file named `metadata.yml` in your collection's root directory.
 
 2. Define the required basic information:
-   ```yaml
-   name: "Your Collection Name"    # Keep it under 3 words
-   id: "your-collection-id"        # Create a simple dash-separated identifier
-   tagline: "Brief description"    # Write a one-line collection summary
-   languages: ["en"]               # List ISO 639 language codes
-   jurisdictions: ["US"]           # List ISO 3166-2 country codes
-   ```
-
-3. Add detailed description and URLs:
-   ```yaml
-   description: "A more detailed explanation of your collection's purpose"
-   dataset: "https://github.com/YourOrg/your-collection-versions/releases"
-   declarations: "https://github.com/YourOrg/your-collection-declarations"
-   versions: "https://github.com/YourOrg/your-collection-versions"
-   snapshots: "https://github.com/YourOrg/your-collection-snapshots"
-   ```
-
-4. Configure tracking periods:
-   ```yaml
-   trackingPeriods:
-     - startDate: "YYYY-MM-DD"    # When tracking begins
-       schedule: "0 0 * * *"      # Cron expression for frequency
-       serverLocation: "City, CC"  # Server location (City, Country code)
-   ```
 
-5. Define governance structure:
-   ```yaml
-   governance:
-     hosts:
-       - name: "Host Organization"
-         url: "https://organization-website.com"
-         logo: "https://path-to-logo.png"
-     administrators:
-       - name: "Admin Organization"
-         url: "https://admin-website.com"
-         logo: "https://path-to-logo.png"
-   ```
-
-6. Add optional fields as needed:
-   ```yaml
-   logo: "https://path-to-collection-logo.png"
-   donation: "https://donation-page-url.com"
-   ```
-
-7. Validate your YAML syntax using a YAML validator.
+    ```yaml
+    name: "Your Collection Name"    # Keep it under 3 words
+    id: "your-collection-id"        # Create a simple dash-separated identifier
+    tagline: "Brief description"    # Write a one-line collection summary
+    languages: ["en"]               # List ISO 639 language codes
+    jurisdictions: ["US"]           # List ISO 3166-2 country codes
+    ```
+
+3. Add detailed description and repositories URLs:
+
+    ```yaml
+    description: "A more detailed explanation of your collection's purpose"
+    dataset: "https://github.com/YourOrg/your-collection-versions/releases"
+    declarations: "https://github.com/YourOrg/your-collection-declarations"
+    versions: "https://github.com/YourOrg/your-collection-versions"
+    snapshots: "https://github.com/YourOrg/your-collection-snapshots"
+    ```
+
+4. Define tracking periods:
+
+    ```yaml
+    trackingPeriods:
+      - startDate: "YYYY-MM-DD"    # When tracking begins
+        schedule: "0 0 * * *"      # Cron expression for frequency
+        serverLocation: "City, CC"  # Server location (City, Country code)
+    ```
 
-## Validation
-
-Ensure your metadata file:
-- Contains all required fields
-- Uses correct YAML syntax
-- Has valid URLs
-- Uses proper date formats (YYYY-MM-DD)
-- Contains valid language and jurisdiction codes
+5. Define governance structure:
 
-## Result
+    ```yaml
+    governance:
+    - name: "Host entity"
+      url: "https://entity-website.com"
+      logo: "https://path-to-logo.png"
+      roles: ["curator", "maintainer"]
+    - name: "Admin entity"
+      url: "https://admin-website.com"
+      logo: "https://path-to-logo.png"
+      roles: ["administrator"]
+    ```
 
-A properly configured `metadata.yml` file in your collection's root directory that defines your collection's essential characteristics and operational parameters.
+6. Add optional fields as needed:
 
-## Next Steps
+    ```yaml
+    logo: "https://path-to-collection-logo.png"
+    donations: "https://donation-page-url.com"
+    ```
 
-After creating your metadata.yml file:
-1. Commit it to your collection's repository
-2. Test it with the Open Terms Archive engine
-3. Update as needed based on validation results
+7. Validate your YAML syntax using a YAML validator.