Ha!  Sorry, I spelled it wrong (ANZSIC).  That was pretty much it 
though - except we want to go a level deeper than they display.  Also I got the 
order wrong, it's group, then class.For example:

Division A - Agriculture,
Forestry and Fishing

Subdivision 01: Agriculture 




 
  
  
  
  
  011: Nursery and Floriculture Production
  
 
 
  
  
  
  
  0111
  
  
  Nursery Production (Under Cover)
  
 
 
  
  
  
  
  0112
  
  
  Nursery Production (Outdoors)
  
 
 
  
  
  
  
  0113
  
  
  Turf Growing
  
 
 
  
  
  
  
  0114
  
  
   Floriculture Production (Under Cover)
  
 
 
  
  
  
  
  0115
  
  
  Floriculture Production (Outdoors)
  
 






        Thanks!
        -- Tim McEwanSent with Sparrow
                
                
        On Friday, 26 November 2010 at 15:30, Simon Russell wrote:
        
            Is there somewhere good that describes the structure of the 
numbers?A quick Google found 
this:http://www.bizexchange.com.au/services/usercontentpage.aspx?pageid=qaanzicOn
 Fri, Nov 26, 2010 at 15:23, Tim McEwan <[email protected]> wrote: Considering the 
potential purpose of this app, I think it'd be best to store it in parts to 
facilitate lookups by the different classifiers.  Also the strings might change 
- the government revises them every 5 years or so, I believe. -- Tim McEwan 
Sent with Sparrow On Friday, 26 November 2010 at 15:18, Simon Russell wrote: 
Once your model has the code assigned, do you need to link to the code parts? 
Could you just store it as a string? (And use the hierarchy to help build up 
the string) On Fri, Nov 26, 2010 at 15:14, Tim McEwan  wrote: Hey guys, I have 
a model that has_one "ANZIC code".  ANZIC codes are classifiers set by the gov 
that are 4 or fewer levels deep: division, sub-division, class & group. Most of 
the time, the objects we're track
ing won't have an advertised code, so the data entry person will need to drill 
down into the classifications to hone in on the most appropriate code.  I'm 
thinking 4 sequential select lists for UI.  (Let me know if you've a better 
idea. :-) What about model-wise?  I'm not keen on the idea of creating 3 
has_many relationships, resulting in 4 look-up queries, but I also think a ne 
sted set may be overkill because this isn't n-levels deep, it's always 4 or 
less.  How should it be designed so that it'll be easy to reference and easy to 
display the full compound code string? Please and thank you! -- Tim McEwan Sent 
with Sparrow -- You received this message because you are subscribed to the 
Google Groups "Ruby or Rails Oceania" group. To post to this group, send email 
to [email protected]. To unsubscribe from this group, send email 
to [email protected]. For more options, visit this 
group at http://groups.google.com/group/rails-oceania?hl=en. -- You
 received this message because you are subscribed to the Google Groups "Ruby or 
Rails Oceania" gro up. To post to this group, send email to 
[email protected]. To unsubscribe from this group, send email to 
[email protected]. For more options, visit this group 
at http://groups.google.com/group/rails-oceania?hl=en. -- You received this 
message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 
group. To post to this group, send email to [email protected]. To 
unsubscribe from this group, send email to 
[email protected]. For more options, visit this group 
at http://groups.google.com/group/[email protected]>-- You 
received this message because you are subscribed to the Google Groups "Ruby or 
Rails Oceania" group.To post to this group, send email to 
[email protected] unsubscribe from this group, send email to 
[email protected] more option
s, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
                        
                        
                        
                        
        
                
                
    

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

Reply via email to