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

Provide BEACON file #122

Closed
lehkost opened this issue Jan 31, 2022 · 3 comments
Closed

Provide BEACON file #122

lehkost opened this issue Jan 31, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@lehkost
Copy link
Member

lehkost commented Jan 31, 2022

Building on the discussion in #51, we should discuss the best way to provide a BEACON file for our data (works and authors) plays.

For starters, which authority should we rely on, GND, or Wikidata, or both?

@lehkost lehkost added the enhancement New feature or request label Jan 31, 2022
@lehkost lehkost added this to the 1.2 milestone Jan 31, 2022
@cmil
Copy link
Member

cmil commented Jan 31, 2022

For a BEACON file for authors wouldn't we first have to implement author pages?

@lehkost
Copy link
Member Author

lehkost commented Jan 31, 2022

Very true. I forgot that we didn't even do this for main DraCor yet. 😬 So it would be works only for now…

@cmil cmil changed the title Provide BEACON file for works and authors Provide BEACON file Feb 11, 2022
cmil added a commit that referenced this issue Feb 11, 2022
cmil added a commit that referenced this issue Feb 11, 2022
@lehkost
Copy link
Member Author

lehkost commented Feb 17, 2022

Should we change the BEACON pointers from slugs to IDs, now that we have them?

cmil added a commit that referenced this issue Feb 27, 2022
@cmil cmil closed this as completed Feb 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants