Specification: Package Search for MVP

[Ipstenu]

We need to be able to search for a package by name, which can be called by the fair-plugin, to find a package for installation

Relates to #2

[toderash]

Unless I'm missing a specific requirement for this, it's likely addressed already within AspireCloud, since there's an API endpoint for the search query that can be used by the plugin. The next milestone release of AC will include improved performance for searches, especially when paginated. (Searching on AC is also being extended to support faceted search.)

[Ipstenu]

We Need for 1.0 - Define what we need to support the fair protocol.

This is an unorganized list and probably missing concepts. Please make SUB TICKETS as needed.

• Since = time - Have you updated anything? How often are we checking? What's the timestamp? (@toderash can explain more) -- this is between the Disco Aggregator and the Repository
• Should we return NEW packages only or New or Changed (renamed, updated, moved, etc)
• Mini Fair does not track when the publishing happened on Mini Fair itself - this should be included in the aggregator.
  • List new packages
  • Updated packages (new version)

Ideally an Aggregator is just taking the meta data from packages it knows about and sharing them with the client.

POST 1.0 stuff:

• Meta should be signed - but WHAT are we signing? @afragen Can you (or anyone) list out what Meta Git Updater is tracking?
• Need to keep a copy of the data (note: This won't really work from .org because it's legacy, Aspire currently normalizes it)
• Mini Faire needs to track Updated META (rename, etc) - this may need a metadata version
• Aspire should have an 'added to Aggregator' date

[afragen]

Meta should be signed - but WHAT are we signing? @afragen Can you (or anyone) list out what Meta Git Updater is tracking?

Where is the best place to document this?

[rmccue]

Meta should be signed - but WHAT are we signing? @afragen Can you (or anyone) list out what Meta Git Updater is tracking?

This isn't GU specific, it's the metadata we generate from the FAIR endpoint(s); tracked at #4 already.

[afragen]

This is the metadata returned from Git Updater.

fairpm/mini-fair-repo#43 (comment)