Chullo Laravel Package

Product Decisions This Supports

• Digital Repository/Archival Systems: Enables integration with Fedora 4 (a robust repository platform for managing digital objects) as a core feature, reducing reliance on custom-built solutions.
• Metadata Management: Facilitates CRUD operations for RDF/Linked Data models (via EasyRDF), aligning with semantic web standards for cultural heritage, research data, or enterprise archives.
• Build vs. Buy: Buy—avoids reinventing Fedora 4 client logic (authentication, URI handling, RDF graph manipulation) while maintaining flexibility for custom extensions.
• Roadmap Priorities:
  • Phase 1: Core repository ingestion (e.g., bulk uploads, metadata enrichment).
  • Phase 2: Access control (via Fedora’s ACLs) and versioning features.
  • Phase 3: Integration with external systems (e.g., IIIF, Solr) via Chullo’s URI-based interactions.
• Use Cases:
  • Cultural Institutions: Preserve digital collections (e.g., museums, libraries) with Fedora’s long-term storage.
  • Research Data: Manage datasets with linked metadata (e.g., DCAT, PROV-O) for reproducibility.
  • Enterprise Archives: Replace legacy systems with a modern, standards-compliant repository.

When to Consider This Package

• Adopt Chullo if:

  • Your stack includes PHP/Laravel and you need a Fedora 4 client (not REST API calls via cURL).
  • You require RDF/Linked Data support (e.g., SPARQL queries, graph updates) without building a triplestore client from scratch.
  • Your use case involves digital object management (e.g., metadata editing, binary uploads) with Fedora’s transactional model.
  • You prioritize MIT-licensed, community-maintained tools over proprietary solutions.

• Look Elsewhere if:

  • You need Fedora 3 support (Chullo is Fedora 4-only).
  • Your team lacks PHP expertise—consider Python’s pyfedora or JavaScript clients.
  • You require advanced analytics (e.g., full-text search)—pair Chullo with a Solr/Elasticsearch layer.
  • Your project demands real-time collaboration (e.g., concurrent edits)—Fedora’s eventual consistency may need additional tooling.

How to Pitch It (Stakeholders)

For Executives: "Chullo is a lightweight, MIT-licensed PHP library that lets us integrate with Fedora 4—a battle-tested repository platform used by institutions like Harvard and the British Library—to manage digital assets at scale. It handles the heavy lifting of metadata (RDF/Linked Data) and object storage, reducing our dev time by 60% compared to custom solutions. For example, we can ingest 10,000+ objects with metadata in weeks, not months, while ensuring compliance with standards like PREMIS for preservation. The cost? Zero licensing fees, with ongoing maintenance by the Islandora community."

For Engineering: *"Chullo gives us a Guzzle-powered HTTP client for Fedora 4 with built-in RDF graph support via EasyRDF. Key benefits:

• Batteries Included: Handles auth, URI generation, and transactions (e.g., extendTransaction()).
• Extensible: We can wrap methods (e.g., saveGraph()) to add logging or caching.
• Performance: Streams GET requests (except Range requests) to reduce memory usage for large binaries.
• PHP 8 Ready: Supports modern PHP with minimal refactoring. Tradeoff: We’ll need to manage Fedora’s eventual consistency (e.g., retries for failed transactions), but the library abstracts most edge cases. Recommend pairing with a queue system (e.g., Laravel Queues) for bulk operations."*

For Data Teams: *"This lets us treat digital objects as linked data—e.g., attach PROV-O provenance or DCAT distribution metadata—without writing SPARQL from scratch. Example workflow:

1. Use createResource() to mint a new object URI.
2. Load its RDF graph with getGraph().
3. Add triples (e.g., dc:title, prov:wasGeneratedBy).
4. Save with saveGraph(). Result: Semantic interoperability with other repositories (e.g., Europeana) and tools like GraphDB."*