Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As a program manager I want to define which fields are shown in the Guide #495

Open
knomepasi opened this issue May 27, 2024 · 1 comment
Labels
guide-v2-embedded Program Guide V2 Embedded

Comments

@knomepasi
Copy link
Contributor

Case: Ropecon has many additional fields that should be shown in the Guide, for example:

  • ropecon2023_workshop_fee: Työpajamaksu
  • ropecon2022_content_warnings: Listaa tähän ohjelmasi sisältämät aiheet, jotka voivat aiheuttaa joillekin osallistujille epämiellyttäviä tuntemuksia tai ahdistusta.
  • ropecon2023_other_accessibility_information: Muu saavutettavuus

How do we request these fields from the GraphQL API dynamically and how do we know, where to show them (popup content area vs. popup meta area)?

@knomepasi knomepasi added the guide-v2-embedded Program Guide V2 Embedded label May 27, 2024
@knomepasi knomepasi changed the title As a program manager I want to define which fields are show in the Guide As a program manager I want to define which fields are shown in the Guide May 27, 2024
@japsu
Copy link
Contributor

japsu commented May 27, 2024

In the V2 data model, these fields belong in the otherFields. We also need to provide an ontology about them (event.program.otherFieldsSchema or something) ie. localized field titles, expected data types, public/sensitive and display settings such as "please show this on the detail page".

In the V1 to V2 transitional period, we should define the mapping from V1 flags (ropecon20XX_*) to otherFields in the importer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
guide-v2-embedded Program Guide V2 Embedded
Projects
None yet
Development

No branches or pull requests

2 participants