8. A label data procurement and management method comprising the steps of: a step of a user being assigned a password and an authorization level for access to certain features of an internet based label management system; a step of a user logging into an internet accessible label management system, and upon logging in viewing a list of pending actions for said user including edit requests pending, proofs pending, orders pending and links to a work flow screen for each listed task, with authority to perform tasks specified by the administrative function; a step of a user uploading label graphics and label data onto a server accessible to a plurality of users' computers over a network; a step of a searcher searching for an existing label for editing of label data said searcher is authorized to work on by creation of a label copy for editing purposes; a step of said searcher inspecting a display of said label data in said label copy; a step of moving said label copy to a label setup workbench configured to allow the user to define editable fields in a graphic file of said label copy; a step of said searcher creating a proposed precision text edit of said label data, with said proposed edit being shown in a preview which is an accurate representation of the graphic view of the edited label, with a visual marking of the proposed edit showing proposed changes in the label copy; a step of said system advancing said proposed edit and said label data to a first label inspector team comprising at least one label inspector, wherein if said proposed edit is satisfactory to all of said label said first label inspector team apply said proposed edit to said label data and said method continues to the next step, wherein if said proposed edit is not satisfactory to at least one dissenting member of said first label inspector team a dissenting label inspector performs the following steps: i) a step of providing at least one reason said proposed edit is not satisfactory to an edit applier; ii) approving or rejecting said reason said proposed edit is not satisfactory; iii) a step of if said reason is rejected continuing to step iv but if said reason is accepted repeating said steps of creating a proposed precision text edit, and advancing said proposed text edit until said label data is satisfactory; iv) a step of applying said proposed edit to said label data; a step of advancing said label data to a proofing team comprising at least one member to approve or reject said proposed edit, with approved edits shown in a different visual marking; a step of if at least one of said proofing team members disapproves of said label, performing steps xi-xiii: xi) a first step of providing at least one reason said label is not satisfactory; xii) a second step of a proofing team leader approving or rejecting said reason said proposed edit is not satisfactory; xiii) a third step of if said reason is rejected continuing to step h but if said reason is accepted repeating said steps of creating a proposed precision text edit, advancing said proposed edit to a label inspector team, advancing said label data to a proofing team, and said proofing team members approving or rejecting said proposed edit until said label data is satisfactory; and a step of advancing said order to an order cart wherein said label data is saved on a medium for delivery to a printing location.
8. A label data procurement and management method comprising the steps of: a step of a user being assigned a password and an authorization level for access to certain features of an internet based label management system; a step of a user logging into an internet accessible label management system, and upon logging in viewing a list of pending actions for said user including edit requests pending, proofs pending, orders pending and links to a work flow screen for each listed task, with authority to perform tasks specified by the administrative function; a step of a user uploading label graphics and label data onto a server accessible to a plurality of users' computers over a network; a step of a searcher searching for an existing label for editing of label data said searcher is authorized to work on by creation of a label copy for editing purposes; a step of said searcher inspecting a display of said label data in said label copy; a step of moving said label copy to a label setup workbench configured to allow the user to define editable fields in a graphic file of said label copy; a step of said searcher creating a proposed precision text edit of said label data, with said proposed edit being shown in a preview which is an accurate representation of the graphic view of the edited label, with a visual marking of the proposed edit showing proposed changes in the label copy; a step of said system advancing said proposed edit and said label data to a first label inspector team comprising at least one label inspector, wherein if said proposed edit is satisfactory to all of said label said first label inspector team apply said proposed edit to said label data and said method continues to the next step, wherein if said proposed edit is not satisfactory to at least one dissenting member of said first label inspector team a dissenting label inspector performs the following steps: i) a step of providing at least one reason said proposed edit is not satisfactory to an edit applier; ii) approving or rejecting said reason said proposed edit is not satisfactory; iii) a step of if said reason is rejected continuing to step iv but if said reason is accepted repeating said steps of creating a proposed precision text edit, and advancing said proposed text edit until said label data is satisfactory; iv) a step of applying said proposed edit to said label data; a step of advancing said label data to a proofing team comprising at least one member to approve or reject said proposed edit, with approved edits shown in a different visual marking; a step of if at least one of said proofing team members disapproves of said label, performing steps xi-xiii: xi) a first step of providing at least one reason said label is not satisfactory; xii) a second step of a proofing team leader approving or rejecting said reason said proposed edit is not satisfactory; xiii) a third step of if said reason is rejected continuing to step h but if said reason is accepted repeating said steps of creating a proposed precision text edit, advancing said proposed edit to a label inspector team, advancing said label data to a proofing team, and said proofing team members approving or rejecting said proposed edit until said label data is satisfactory; and a step of advancing said order to an order cart wherein said label data is saved on a medium for delivery to a printing location. 12. The method of claim 8 wherein at least one of a team leader, an assistant administrator, or a master administrator reviews said proposed edits before said proposed edits are advanced to said order cart.