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

Integration of eMeal - Menüplanung into the eCamp3 Project #5202

Open
wp99cp opened this issue May 19, 2024 · 1 comment
Open

Integration of eMeal - Menüplanung into the eCamp3 Project #5202

wp99cp opened this issue May 19, 2024 · 1 comment

Comments

@wp99cp
Copy link

wp99cp commented May 19, 2024

I'm one of the maintainers of the project eMeal - Menüplanung. We are currently planning and conceptualize version 2 of our project. During that initial planning phase, the idea came up that we would like to provide some integration of our tool into eCamp3. As discussed in #5169 (comment), such coupling should be as loose as possible while providing a consistent experience to the end user. Thus, we are not planning to integrate eMeal into eCamp3 directly but rather to provide some integration based on cross-references and API calls.

We are thinking the following integrations would be beneficial:

  • Cross-Referencing between the tools:
    In eMeal (or eCamp), one can reference any existing camp in eCamp (or eMeal); the counterpart must confirm this reference. A link then allows for fast navigation between the two tools.

  • Synchronizing Schedule Entries and Activity-Meta-Data to eMeal
    The camp leader plans and places activity blocks for the type of meal inside the week overview. He may associate additional meta-data with every meal entry, such as a title, location and short description. Those meta-data are then displayed within eMeal. Data sent to eMeal could look as follows:

    type: Mittagessen
    time: 2024-07-01, 12.00
    description: "Grosses Festessen nach gewonnener Schlacht"
    location: "Im Lagerhaus"
    
  • Synchronizing Meal-Title back to eCamp3
    After the kitchen team creates a complementary meal inside eMeal, the data is synchronized back to eCamp3, i.e. the meal title (including some higher-level recipe info) is displayed inside eCamp3.

    type: Mittagessen
    time: 2024-07-01, 12.00
    meal-title: "Spaghetti-Plaus mit verschiedenen Saucen"
    
  • Optional: Synchronizing of Access Roles:
    Once linked, all managers within a camp in eCamp3 automatically get view access to the corresponding camp within eMeal. Thus, the camp leader can always view what the kitchen team is planning.

  • Optional: Synchronizing of Participants Counts:
    As far as I know, linking a camp within eCamp3 with a corresponding entry within MiData / CeviDB is not yet possible. If and once such a feature is implemented, sharing the participant count with eMeal would be beneficial. Usually, only the camp leader knows the exact participant count, whereas the kitchen team relies on him to report those numbers.

What does the eCamp3 community think of those plans? Which of the above interactions are realistic/valuable? Are there any essential things to consider? Are there any other requirements?

Disclaimer: The ideas discussed in this issue are very high-level; I know that many implementation details need in-depth discussions. We are currently pretty flexible as we are still planning our architecture.

@pmattmann pmattmann added the Meeting Discuss Am nächsten Core-Meeting besprechen label May 20, 2024
@carlobeltrame
Copy link
Member

Core Meeting Discussion

Thank you for reaching out. Any integrations with third-party tools are currently post-MVP territory for us, meaning we will first implement our course features before investing much time into features like this. For this reason, it's hard for us to make a statement right now how we would envision any integration.

We would love to meet and discuss some of the ideas verbally with you. Please contact us on Discord or via the contact form on ecamp3.ch/contact, so we can set up a call.

@carlobeltrame carlobeltrame removed the Meeting Discuss Am nächsten Core-Meeting besprechen label Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants