Php Gedcom Laravel Package

Technical Evaluation

Baseline assessment for liberu-genealogy/php-gedcom v4.2.0. The package is a PHP/GEDCOM domain library with Laravel integration potential via Composer and service-container usage. This release adds cross-cutting UID/_UID support across all GEDCOM record types with GedcomX export, plus a work-in-progress GEDCOM-to-GEDCOM-X mapping. The minor version bump implies backward compatibility, but the breadth of UID handling and the WIP nature of GEDCOM-X mapping require integration validation before production adoption.

• Architecture fit: Strong fit for Laravel applications that need GEDCOM import/export, genealogy record normalization, or GEDCOM-X interoperability. Best integrated behind an application service or queue-backed import/export pipeline rather than called directly from controllers.
• Integration feasibility: Composer install is straightforward. The main integration effort is fixture-based validation of GEDCOM round-tripping, UID preservation, and GEDCOM-X output correctness.
• Technical risk: Medium. The UID/_UID change touches all record types and can affect serialization, deduplication, and export fidelity. The GEDCOM-to-GEDCOM-X mapping is explicitly WIP and contributed via Copilot, so it should be treated as experimental until test coverage and maintainer review are confirmed.
• Key questions:
  • Which PHP and Laravel versions are supported by this release?
  • Are GEDCOM 5.5/5.5.1/7 and GEDCOM-X mappings covered by automated fixtures?
  • How are duplicate, missing, or malformed UID/_UID values handled?
  • Does UID support change existing export output for records that previously omitted UIDs?
  • Is the GEDCOM-X mapping intended for production use in v4.2.0 or only experimental?
  • What is the package’s backward-compatibility and security-review policy for automated contributions?

Integration Approach

• Stack fit: Use as a domain library inside a Laravel service layer. Wrap imports/exports in application services, validate with form requests, dispatch long-running jobs to queues, and persist normalized records through Eloquent or a repository layer.
• Migration path: Upgrade from v4.1.1 to v4.2.0 in a non-production branch first. Pin the exact version in composer.json, run existing GEDCOM fixtures, and compare import/export outputs before and after. Avoid combining this upgrade with unrelated genealogy-model changes.
• Compatibility: Treat v4.2.0 as semver-compatible but verify UID behavior against existing data. Existing consumers that ignore UID fields should be unaffected; consumers that compare raw GEDCOM output may see added or changed UID/_UID lines.
• Sequencing:
  1. Confirm PHP/Laravel support and dependency constraints.
  2. Add golden-file tests for representative GEDCOM imports and exports.
  3. Validate UID/_UID preservation across individuals, families, events, sources, and other record types.
  4. Trial GedcomX export behind a feature flag or internal-only endpoint.
  5. Roll out to production with monitoring on import/export failures and schema validation errors.
  6. Revisit the WIP GEDCOM-to-GEDCOM-X mapping only after maintainer confirmation of production readiness.

Operational Impact

• Maintenance: Low-to-moderate. The package is community-maintained; this release includes automated/AI-assisted contributions, so dependency updates should include review of changelogs and test coverage rather than blind upgrades.
• Support: Relies on open-source maintainers and community issue response. Teams should retain internal GEDCOM fixtures and be prepared to patch or wrap edge cases.
• Scaling: Parsing and transforming large GEDCOM files can be CPU- and memory-intensive. Run imports/exports in queued jobs, enforce upload limits, stream where possible, and isolate GEDCOM-X conversion from request paths.
• Failure modes: Malformed or duplicate UIDs, missing _UID values, unexpected export changes, incomplete GEDCOM-X mapping, schema validation failures, and round-trip data loss. These should fail loudly in validation and be logged with source-record identifiers.
• Ramp-up: Moderate. Engineers need basic GEDCOM and GEDCOM-X domain familiarity to interpret UID semantics, record hierarchy, and export fidelity. A short internal runbook plus fixture library will reduce onboarding time.