-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Request - add some locality attributes to FLAT? #8394
Comments
@dustymc I'm sure all the ones you highlighted would help. I think Era/Erathem would be particularly useful to our collections. |
With respect to this key point, what are the counts of values for locality attribute types? (https://arctos.database.museum/info/ctDocumentation.cfm?table=ctlocality_attribute_type#attribute_type) That MAY be a way to distinguish between useful stuff for flat. (i.e., Requests for little used attributes will not be considered!) thx |
Usage:
|
Is System/Period already in FLAT? Are we able to pull from the Chronostrat metadata to fill in higher Chronostrat ranks (for example, record is Albian, FLAT fills in Lower Cretaceous, Cretaceous, Mesozoic)? That would make having these values in FLAT more useful. As a collection manager, I function just fine without Chronostrat in my search results because usually I'm using Chronostrat in my query and am more interested in lithostrat in my results BUT I think this would be valuable for other types of paleo users. Particularly System/Period, Series/Epoch, and Stage/Age. |
Don't think so, structure below.
I can write the code, but I think https://github.com/ArctosDB/internal/issues/330 is probably a hard blocker. (Maintaining the cache is already using nearly everything nearly always, and that secondary data is particularly expensive.) That's not a 'no' but definitely recommend that proceed with a lot of caution.
Same reasons as above, I'd recommend not proceeding without a solid use case. (FLAT is really handy for reports - what started this - but not necessary for search, for example.)
|
Help us understand your request (check below):
Describe what you're trying to do
Make #8393 and #7348 and similar more efficient by caching some locality attribute summary data in FLAT.
I DO want to get the 'normal' stuff, the cost of pulling it dynamically is significant and limiting.
I DO NOT want to add anything to FLAT that won't get significant use; there are long-term costs in scalability, maintenance, and processing to this, and we're always resource limited.
Here's what I think we should add to the cache:
ES collection folks, HELP!
@keg34
@javanveldhuizen
@mvzhuang
@KatherineLAnderson
@aklompma
@droberts49
@wellerjes
@jrpletch
@Nicole-Ridgwell-NMMNHS
@ehalverson26
@kat-sterner
@jessicatir
@ufarrell
@ronaldeng
@WaigePilson
@Kmullineaux
The text was updated successfully, but these errors were encountered: