Minutes_Standards_2024 09 - airr-community/airr-standards GitHub Wiki

Standards Call 2024-09

Agenda

  • Discussion/Summary of AIRR Community Meeting VII

Minutes

Meta

  • Date: Mon, 2024-06-10 18:00 UTC
  • Present: Brian, Chaim, Christian, Jason
  • Regrets: Ulrik

Topics

  • AIRR Community Meeting VII (Porto, PT)
    • Feedback received during poster presentation:
      • Standards / Christian
        • Most common question: How do I store data in an AIRR-compliant fashion?
        • Answer: Use libraries from Standards WG to create files, upload to ADC (also see ComRepo)
      • Common Repository WG / Brian
        • Most common question: How do I share data?
        • Answer: It's (unfortunately) not that easy:
          • Running an own repository is the preferred way, but a big hurdle for people who do not want to maintain infrastructure
          • iReceptor public archive does not support direct user uploads. This is mainly due to limited capacity for curation, but also due to the fact that long-term availability cannot be guaranteed.
          • VDJServer should allow for user uploads (which the undergo automated processing), but the limited amount of new public data set over the last two years suggest that if present it is not used at a relevant rate.
          • Technically, data sets could be submitted to GEO/ArrayExpress. However, these ressources only provide storage, but no ADC API search capability. Also, uploads to GEO are quire time consuming if good metadata is provided (~10 hours per data set).
      • Software WG / Chaim
        • "Where has this (AIRR-C tools) been all my life?"
    • Sum-up: AIRR-C tools and services are in line with the needs of the community, but are not sufficiently known or require better documentation.
    • Further rumors
      • Adaptive is apparently thinking about discontinuing ImmunoSeq service
  • Future of Standards WG
    • Let's get v2.0 done until April 2025!!
    • (... and if it is not done by then, lets call what we have v1.6)
    • Discussions in Porto suggest that we are indeed feature-complete, but we will need to sort out a lot of details.
⚠️ **GitHub.com Fallback** ⚠️