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

Project Media Schema #24

Open
S4mmyb opened this issue Oct 17, 2024 · 0 comments
Open

Project Media Schema #24

S4mmyb opened this issue Oct 17, 2024 · 0 comments

Comments

@S4mmyb
Copy link
Member

S4mmyb commented Oct 17, 2024

Context

In our current schema, project media (e.g., photos, videos, and other marketing materials) is integrated alongside anchored project metadata. However, project media differs significantly in both usage and accessibility:

  1. Anchored Project Metadata: This includes information that is publicly available, meant for other platforms to query, consume, and integrate into their applications. Anchored metadata informs about key project details and serves as an authoritative data source.
  2. Project Media: These include assets like photos and videos, which are typically intended for marketing or communication purposes. While important, these media files:
    • Do not necessarily contribute to the core project metadata.
    • May be privately hosted.
    • Do not always need to be anchored or publicly available for querying.

Goal

To avoid mixing project media with core anchored metadata, we propose creating a separate schema specifically for project media. This will ensure that project media is treated appropriately, whether it's privately hosted or has limited public relevance.

By doing this, we maintain a clear separation between:

  • Anchored, public-facing metadata that informs about the project.
  • Optional, potentially private media files that are more aligned with project presentation or marketing needs.
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