Skip to content

[HACK] Catalogue repository for echoIA #53

Description

@joachimi

Summary (1–2 sentences)

How should we organise an echoIA repo for value-added IA catalogues? They are too large for GitHub. Zenodo, local hosting? What datasets do we want to store? How do we get hold of past measurements? Documentation?

Leads & Contacts

  • Lead(s): @joachimi
  • Backup (optional):
  • Slack channel (if any):

Proposed Timing & Format

  • Preferred day(s): Mon / Tue / Wed / Thu / Fri
  • Duration: 90 / 120 min (or multi-day)
  • Modality: in-person / hybrid
  • Session type: working session

Team / Participants (initial list)

Goals & Deliverables

  • Plan for the repo and its content
  • Initial documentation and guidance for adding and using datasets
  • An example dataset served if possible

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions