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

Renaming/fixing of content-item schema #42

Open
3 tasks
piconti opened this issue Dec 16, 2024 · 0 comments
Open
3 tasks

Renaming/fixing of content-item schema #42

piconti opened this issue Dec 16, 2024 · 0 comments
Assignees

Comments

@piconti
Copy link
Member

piconti commented Dec 16, 2024

The Content-item schema is meant to represent the rebuilt content-items, but it's not very clear of explicit and it might be outdated. It should be updated and made more clear.

In addition, as pointed out by @simon-clematide, the porperty "t" is present twice in the schema, both for title and token.
It's not at the same level of the schema hierarchy, so it has currently not caused too many issues, but is not ideal and should probably be changed.

Action points for this issue are thus:

  • Making it more explicit that the content-item schema corresponds to the rebuilt, potentially by renaming the schema
  • Ensuring it is up to date and still aligned with the actual content of the rebuilt data
  • Renaming the title or token property, once it has been modified in the data.
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

1 participant