Feature #1353

AWS: Create table lookup protocol for long-list value labels

Added by Mike Smyser about 4 years ago. Updated over 3 years ago.

Status:OpenStart date:08/20/2013
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Complexity:

Description

Need way to reference and call lookup metadata information for long-list value labels. Good test example would be to create the value label look ups for state fips codes (see attached csv) file. Needs to be referenced from the standard metadata labels. E.g., see Feature Request #1352 where the label information looks like:

Instead of separate values/label columns method use a single column format such as the following: {
title: "my column title",
keyType: "my keyType",
...
[all other weave metadata],
...
value_lookup: {
"<fips>": "<[SCHEMA].[TABLE]>"
}
}

In this example, the standard config table references a lookup for values of "fips" referencing another table. The angle brackets or some other character flag might be necessary to tell AWS that this is a table lookup. Don't know if this is the best way to do this, but something along these lines might do...

usstates_fips_example.csv Magnifier (1.25 KB) Mike Smyser, 08/20/2013 01:10 PM

History

#1 Updated by Andy Dufilie about 4 years ago

Instead of using a value_lookup object for multiple purposes (value lookups and sql table locations), it's better to create a separate metadata field for a sql table lookup. I suggest having a private metadata field that contains a SQL query. For example, the field name could be "sqlValueLookupQuery" and the value would be "SELECT fips,name from myschema.fips_lookup". Each column could have a different lookup query in its metadata.

#2 Updated by Mike Smyser about 4 years ago

A a separate metadata field for a sql table lookup sounds like a great idea and and would work for us.

#3 Updated by Andy Dufilie over 3 years ago

  • Project changed from Weave to Analyst Workstation
  • Category deleted (Performance)

Also available in: Atom PDF