search

jackba / arctos

Automatically exported from code.google.com/p/arctos
0 stars 0 forks source link

cleanup@code tables #493

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Code table values should be either documented or eliminated. Some code tables 
may need eliminaated.

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTABUNDANCE - 
I have no idea what any of those values could possible mean at any useful 
scale. Document/define or relegate to specimen remarks.

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTAGENT_TYPE 
- I think we have 4 ways of saying "something else." One would be a more 
appropriate number.

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTACCN_TYPE - 
recommend removing this concept from the model.

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTADDR_TYPE - 
Address Type Previous and valid/invalid are used in very confusing ways, and 
it's not clear when or if one should pick a Correspondence address over a 
Shipping address. Recommend eliminating Previous address type, documenting the 
remainder.

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTAGENT_NAME_T
YPE - I see zero value in the undocumented name types.

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTAGE_CLASS - 
Ack.

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTATTRIBUTE_TY
PE - wow

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTCOLLECTING_S
OURCE - I have no idea what the photo things might mean or why they're here

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTCOLL_OBJ_DIS
P - there are about 15 ways of saying "we have no idea." The rest are condition 
information.

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTCONTAINER_TY
PE - I filled in the blanks, poorly

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTDATUM - are 
those self-evident?

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTFEATURE - 
may not be definable without temporal information and/or geospatial capability 
- the strings are as good as it gets.

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTGEOG_SOURCE_
AUTHORITY - all useless values - get rid of the concept.

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTINFRASPECIFI
C_RANK - needs serious attention from a botanist

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTISLAND_GROUP
 - see FEATURE - recommend ignoring until GIS capability

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTJOURNAL_NAME
 - this is an almost-infinitely long list that may not properly belong as a 
code table, and may be considered a strong symptom that we're over-atomizing 
publication data.

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTKILL_METHOD 
- talk to the bug people

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTLAT_LONG_ERR
OR_UNITS - "mi" could mean 1,852m or 1,609m.

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTLOAN_STATUS 
- in process=open. unknown=we might have sent some stuff out but we don't 
remember why or ????

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTLOAN_TYPE - 
how is transfer of custody different than consumable? Both are not expected 
back. Other no-description values need defended or removed.

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTMEDIA_RELATI
ONSHIP - left comments in description

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTNATURE_OF_ID
 - ya'll know I hate it

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTPERMIT_TYPE 
- Do we lose anything if we get rid of this altogether?

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTPREFIX - 
conflicting/confusing (one is not born a Colonel, and one hopes to get 
promoted) evidence of over-atomization of agent names - this should go away, 
and any useful information should be relegated to strings inside agent names

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTPROJECT_AGEN
T_ROLE - how do these things add value to Projects? Can it go away? Also: Why 
do we use agent_name rather than agent in Projects?

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTPUBLICATION_
ATTRIBUTE - see also ctjournal_name, CTPUBLICATION_TYPE, CTSECTION_TYPE, etc. 
Is there value in structuring publications as we do? If so, what? I hereby 
propose new publication structure:

PUBLICATION
publication_id NUMBER PKEY
full_citation varchar2(4000) NOT NULL
short_citation varchar2(255) NOT NULL
DOI varchar2(255) NULL

PUBLICATION_AUTHOR
publication_id NUMBER FKEY
agent_id NUMBER FKEY

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTSEX_CDE - 
fill in the blanks

http://arctos.database.museum/Admin/ctspecimen_part_name.cfm - fill in the 
many, many blanks

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTSUFFIX - 
fill in blanks

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTTAXA_FORMULA
 - fill in the blanks

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTTAXONOMIC_AU
THORITY - is there any value here? If so, what?

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTTAXON_RELATI
ON - can this be reduced to "synonym of"?

http://arctos.database.museum/CodeTableEditor.cfm?action=edit&tbl=CTTAXON_STATUS
 - fill in the blanks

Original issue reported on code.google.com by dust...@gmail.com on 9 Aug 2011 at 1:01

GoogleCodeExporter commented 9 years ago 
Someone's going to have to take the lead (or just do it) if we have any 
intentions of actually standardizing vocabulary. We should also document and 
enforce how this stuff gets into the code tables - I suggest that no one person 
should be able to unilaterally do anything to code tables as a matter of policy.

Original comment by dust...@gmail.com on 3 Jul 2012 at 2:58