- There should be an
\App\Models\FAIR\Beacon Model class with at least name, uri, git_updater_uri (optional), and created_at properties (and likely more as we find them)
- There should be a
/admin/api/v1/fair/beacon REST endpoint to do CRUD operations on beacons.
The purpose of this is to track FAIR Beacon instances we want included in AspireCloud, so that AspireSync can pull in all their package metadata and aggregate it in AspireCloud. AS will also look for Git Updater running on the instance and provide legacy metata through that endpoint if present.
This API will eventually implement a FAIR specification for aggregation, but for now we just need to get it working for AspireCloud's use case.
\App\Models\FAIR\BeaconModel class with at leastname,uri,git_updater_uri(optional), andcreated_atproperties (and likely more as we find them)/admin/api/v1/fair/beaconREST endpoint to do CRUD operations on beacons.The purpose of this is to track FAIR Beacon instances we want included in AspireCloud, so that AspireSync can pull in all their package metadata and aggregate it in AspireCloud. AS will also look for Git Updater running on the instance and provide legacy metata through that endpoint if present.
This API will eventually implement a FAIR specification for aggregation, but for now we just need to get it working for AspireCloud's use case.