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

Test using nested fields to store project specific info #105

Open
karindalziel opened this issue Dec 10, 2019 · 1 comment
Open

Test using nested fields to store project specific info #105

karindalziel opened this issue Dec 10, 2019 · 1 comment
Assignees
Labels

Comments

@karindalziel
Copy link
Member

If dynamic subfields could be added, we could have a single "miscellaneous" field (probably need a better name) and then use that to store extra info.

For instance, for African poetics citations, we need fields like "Source Access Date, Source Archive, Source Citation"

-misc
- citation_source_access_date
- citation_source_archive
- citation_source_full_citation

This is perhaps not the best example but the first step is to make sure we can create dynamic subfields at all.

@jduss4 jduss4 changed the title Test using subfields to store project specific info Test using nested fields to store project specific info Dec 17, 2019
@jduss4 jduss4 modified the milestone: v2 launch to power center multi project search Jan 6, 2020
@jduss4
Copy link
Contributor

jduss4 commented Feb 6, 2020

dynamic subfields can be added. i would still prefer not to get too wild with these, and to consider how other projects might be able to use the same ones (like petitioner_against_k type fields. Also, our API querying structure does not currently support nested-nested fields, for example:

miscellaneous:
  {
    citation_n:
      {
        citation_source_access_date_k: ""
      }
  }

@wkdewey wkdewey added this to the v2 launch to power center multi project search milestone May 12, 2022
@wkdewey wkdewey modified the milestones: v2 launch to power center multi project search, v2 Launch to power Petitioning for Freedom (Habeas Corpus) May 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants