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

Create a Knowledge Panel compliant route for the Folksonomy Engine list of properties for a given barcode #185

Open
teolemon opened this issue Jun 7, 2024 · 4 comments · May be fixed by #255

Comments

@teolemon
Copy link
Member

teolemon commented Jun 7, 2024

Problem

  • Create a Knowledge Panel compliant route for each barcode, so that we can integrate it in the ProductOpener Product Page or in the mobile app
  • This will allow for a flexible and evolutive layout, driven by the Folksonomy server
  • Optional is a link to a webview allowing property input (view to be created, you can open another ticket), until we can have basic server driven editing

Code pointers

Related issue

@teolemon
Copy link
Member Author

teolemon commented Mar 4, 2025

We're also considering exposing a webcomponent. The two can be complementary, the webcomponent using the Knowledge Panel compliant API exposed by the Folksonomy Engine.

@shradiphylleia
Copy link

hi, would like to work on this if it’s up for grabs
Just to clarify, my understanding of the task is:

  1. setting up a backend route to fetch product data based on the barcode numeric of the product.
  2. ensuring the route is knowledge panel compliant so it integrates with the product page and the mobile app.

@alexgarel
Copy link
Member

@shradiphylleia yes that's it.

I have created an issue to have a knowledge panel web component here. (but it's independent).

@shradiphylleia
Copy link

@alexgarel would like to work on this issue while the knowledge panel component is being worked on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

3 participants