Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

[Epic] Next steps #5

Open
netsensei opened this issue Dec 19, 2023 · 0 comments
Open

[Epic] Next steps #5

netsensei opened this issue Dec 19, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@netsensei
Copy link
Contributor

In a first iteration of this service, we hit these milestones:

  • Initial project setup and codebase
  • Setup a secure REST API with OpenAPI
  • Setup a postgres database + migrations via Tern
  • CRUD operations for project management
  • A datamodel based on schema.org & FRAPO (http://www.sparontologies.net/ontologies/frapo)
  • Handling project identifiers
  • A pipeline which syncs this service with the original authority database as managed by the frontend application.
  • Containerization and deployment to Nomad

In a next iteration, we we can identify these major milestones:

  • Replace the current pipeline with a pipeline which feeds the service with up-to-date info from GISMO.
  • Sideload CORDIS for information about projects funded through European grants.
  • Fine tune the search capabilities
    • Finetune how searching / autocomplete should work.
    • Re-evaluate ElasticSearch v6 (OpenSearch? Typesense? Postgres vector search?)
@netsensei netsensei added the enhancement New feature or request label Dec 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant