8 Next | First| Previous TEI Guidelines P5

Not making the switch


Lots of potential reasons not to upgrade, including

  • cost of retooling (updating programs, stylesheets, search protocols; retraining staff);
  • cost of migration itself, although low, may be too much for projects with a lot of data and not much funding (e.g., no longer in active development);
  • interuption of workflow would be too disruptive;
  • If it ain't broke, don't fix it … if P4 is working just fine for you, why switch.

P4 should be supported (bug fixes, pizza chef) for at least 5 years after P5 is out. Expertise will exist for even longer.