- top level switch is at the corp level...
	who is connected to who

- top level master list and all adding and editing is done there
	if editing, make those changes to all subs

- on sub levels, then can only pull from a master list (say E1)

- each one is already a corp, the E1 corp is just a master level corp

- we want to start with vendors and then eventually go to items/parts. eventually on to customers

- we need to use chuck for a good look and feel
	- we could go both ways... look and feel first or backend first

- c=corps, t=transactional data corps, e=enterprise corp (master), all of these corps live on the same server

- the database table is called cross_corp_mapping

- to find the files... search for "map" in the top_secret/secure folder

-all transactional systems need to be on the same server (for now)

- at some future point, we would like some super high master catalogs where anybody could get to... basically, we have a huge list and then the different companies could pull down what they want.

- mappings could be corp to corp, vendor to vendor, customer to customer, item to item, etc.

- alan was talking about future updates and more advanced tie-ins

- steve wants them to be able to add/pull one or more vendors at the same time.

- each record that gets pulled down will be duplicated into the new transactional system.

- alan was talking about checking enterprise/transactional relationships at the login and/or switching corps.

- if the enterprise corp does an update, we can cascade those updates to the sub transactional systems

- eventually we may need to tie in the new mapping pieces... currently, they are not connected - just standalone pages.

- enterprise and aggregate - words - have been used somewhat interchangable - as of right now

- to browse what we currently have (just a stick house) - top_secret/secure/cross_corp_enterprise_mapping.cfm - that page has differnet modes (still somewhat under construction)

- steve and alan were talking about possibly adding in a new super high level permission or something to allow a user to get to the enterprise mapping options.

- on the aggregate stuff... we want master lists from the top down. we also want aggregated info going from the bottom up (differnet project). there were some other talks about direction of travel... still kinda figuring some of that stuff out. top down or bottom up...

- standardizing the data and creating some kind of a template type interface

- there may be some smoke and mirrors stuff to create the mappings but still allow some controls at the smaller transactional layers or systems.

- talking parts... maybe go up a full level and have it controlled on the vendor level and then down from there.

- eventually, there will be media/content galleries and picture/photo galleries that may be used as master catalog type interfaces. expand... to whatever. somewhat of a master/slave or bulk pick and choose type option for (fill in the blank).

- on the transactional servers (corps) - locations and banks will need to more open because not all corps have the same values. let's start with the known similarities vs the random pieces.

- future project, think of train with box cars... - how much weight/history do you want to pull along. when needed, we could split off the different train cars.