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

Retain membership to model sets #71

Open
brycefrank opened this issue Oct 4, 2024 · 0 comments
Open

Retain membership to model sets #71

brycefrank opened this issue Oct 4, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@brycefrank
Copy link
Contributor

brycefrank commented Oct 4, 2024

Right now, model sets are only used as a convenience for writing publication files, however they are often useful to know about because they may relate to a specific portion of a document (like a table or appendix) and can be essential for navigating large publications. Sets also, by definition, must have the same functional form, which creates a natural grouping structure.

One idea is to create an 8 character uuid for the set by hashing the uuids of the models inside. Then, assign this value to each model, say model.set_id and also store publication.set_ids. We can entertain if writing sets explicitly to their own collection is worthwhile later, but this should be enough to do basic queries.

@brycefrank brycefrank self-assigned this Oct 4, 2024
@brycefrank brycefrank added the enhancement New feature or request label Oct 4, 2024
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

1 participant