Version: 9 (current) | Updated: 11/20/2025, 11:55:37 PM
Added description
**1. Create the collection described by pinax.json**
@test_2_collection:collection {
title: "Test-2 Collection",
creator: [@substack, @nchimicles, @arke_institute],
institution: @test_2,
created: @date_2017,
language: "en",
description: "A collection of various posts, datasets, and metadata files including tutorials, announcements, historical essays, and system files from the Arke Institute digital collection.",
access_url: "PLACEHOLDER",
source: "PINAX",
rights: "Copyright Substack, Unknown"
}
**2. Link the metadata document to the collection**
@file_pinax -> describes -> @test_2_collection
**3. Add creators, institution and place information**
@substack -> creator_of -> @test_2_collection
@nchimicles -> creator_of -> @test_2_collection
@arke_institute -> creator_of -> @test_2_collection
@test_2_collection -> place -> [@europe, @florence, @bruges, @paris, @spain, @jerusalem, @rome, @germany]
**4. Define additional concepts that appear only in the pinax subjects list**
@email_marketing:concept {description: "Use of electronic mail to promote products, services, or content"}
@content_management:concept {description: "Processes and tools for creating, storing, and delivering digital content"}
@newsletters:concept {description: "Periodic email publications sent to a subscriber list"}
**5. Connect the collection to all of its subjects (synthesis across sub‑directories)**
@posts_collection -> subject -> @substack
@posts_collection -> subject -> @editor_tutorial
@posts_collection -> subject -> @announcements
@posts_collection -> subject -> @subscriptions
@posts_collection -> subject -> @newsletter
@posts_collection -> subject -> @medieval_europe
@posts_collection -> subject -> @catholic_church
@posts_collection -> subject -> @indulgence_system
@posts_collection -> subject -> @wealth_inequality
@posts_collection -> subject -> @social_hierarchy
@posts_collection -> subject -> @christianity
@posts_collection -> subject -> @historical_analysis
@posts_collection -> subject -> @economic_history
@posts_collection -> subject -> @religious_history
@posts_collection -> subject -> @social_critique
@newsletter_posts_dataset -> subject -> @newsletters
@newsletter_posts_dataset -> subject -> @email_marketing
@newsletter_posts_dataset -> subject -> @content_management
@test_2_collection -> subject -> @substack
@test_2_collection -> subject -> @editor_tutorial
@test_2_collection -> subject -> @announcements
@test_2_collection -> subject -> @subscriptions
@test_2_collection -> subject -> @newsletter
@test_2_collection -> subject -> @medieval_europe
@test_2_collection -> subject -> @catholic_church
@test_2_collection -> subject -> @indulgence_system
@test_2_collection -> subject -> @wealth_inequality
@test_2_collection -> subject -> @social_hierarchy
@test_2_collection -> subject -> @christianity
@test_2_collection -> subject -> @historical_analysis
@test_2_collection -> subject -> @economic_history
@test_2_collection -> subject -> @religious_history
@test_2_collection -> subject -> @social_critique
@test_2_collection -> subject -> @newsletters
@test_2_collection -> subject -> @email_marketing
@test_2_collection -> subject -> @content_management
@test_2_collection -> subject -> @metadata
@test_2_collection -> subject -> @system_files
@test_2_collection -> subject -> @digital_preservation
**6. Show that the two collection‑level entities share material**
@test_2_collection -> related to -> @posts_collection {description: "Both aggregate the same set of Substack posts, newsletter datasets and system‑file metadata"}
**7. Aggregate the concrete documents that belong to the Test‑2 Collection**
@test_2_collection -> includes -> [
@substack_editor_tutorial,
@coming_soon_announcements,
@modern_indulgence,
@file_132220171_7fb:document,
@newsletter_posts_dataset,
@file_pinax,
@file_ds_store,
@file_posts_csv
]
**8. Link the newsletter‑posts dataset to the same documents already referenced in the posts subdirectory**
@newsletter_posts_dataset -> contains -> [@post_125962878_coming_soon, @post_133047701_modern_indulgence, @post_132220171_7fb, @post_125962877_how_to_use_the_substack_editor]
@post_125962878_coming_soon -> corresponds to -> @coming_soon_announcements
@post_133047701_modern_indulgence -> corresponds to -> @modern_indulgence
@post_132220171_7fb -> corresponds to -> @file_132220171_7fb:document
@post_125962877_how_to_use_the_substack_editor -> corresponds to -> @substack_editor_tutorial
**9. System‑files metadata synthesis**
@file_pinax -> has subject -> @metadata
@file_pinax -> has subject -> @system_files
@file_pinax -> has subject -> @digital_preservation
@file_ds_store -> type -> @image_asset
**10. Overall cross‑source picture**
- The **Test‑2 Collection** aggregates:
* Substack tutorial & announcement content (from *posts*).
* Newsletter‑post dataset and its individual newsletter documents (from *newsletter_posts*).
* System‑file metadata and auxiliary assets (from *system_files*).
- All three sub‑directories converge on a shared thematic core (Substack platform, medieval‑Europe religious/economic analysis, and digital‑preservation concerns), reflected by the extensive list of shared **subjects** and **places**.
- The collection’s creators (**@substack**, **@nchimicles**, **@arke_institute**) appear both as metadata creators and as platform hosts, establishing a clear **organizational synthesis** across the dataset. # Reorganization Summary The organizational strategy focuses on separating user-generated content from system-related files. The 'newsletter_posts' group contains the CSV file with newsletter post data, while the 'system_files' group includes the JSON reference file related to a system metadata file. This approach ensures clear distinction between content types and avoids unnecessary overlap. ## Groups Created - **newsletter_posts**: Files containing data related to newsletter posts, including post IDs, dates, publication status, and other metadata. - **system_files**: Files that are system-related, such as metadata or configuration files, which do not contain user-generated content.