[open-ils-commits] [GIT] Evergreen ILS branch rel_2_2 updated. 99d66fee76e2c96798408086d44822e4c6932403
Evergreen Git
git at git.evergreen-ils.org
Fri Jul 13 23:55:51 EDT 2012
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Evergreen ILS".
The branch, rel_2_2 has been updated
via 99d66fee76e2c96798408086d44822e4c6932403 (commit)
via 260eb05e7b394a22906af7b7e83124f28a60da96 (commit)
via 0438e4eeafbdb773409252ac464c2295ecb7062f (commit)
via 2a78333727a8b0ee4514948308fe02e9d238bfab (commit)
via 652f22ae282c9a99c8d40763884fb3bd686bb518 (commit)
via 654e8a21ddfcd76526976fd80930f87b109bf14a (commit)
via 1e8c1b810f34f4fccda11f0d88120320c3a4d0ce (commit)
via 7753dd6b1722320b8a1c9034a82293e9a0102c1f (commit)
via 6891ac8b8e5b1b0257e5f32b7016eb1587f25335 (commit)
via 15769b7f63de1143f69a00f26c1f17360406dc10 (commit)
via 4ea6279c37a5035472879281ae251aff9259554d (commit)
via 2ed40844755f81d399e0f5ae855e20906aa8fdc1 (commit)
via 018034d1305d139228584006586174ac1117fde6 (commit)
via f76dfb090b1275f44c6b976da76e0c5123eb5939 (commit)
via 88eeea970dfeb43e88ac24a56e2c23b979f06a1c (commit)
via 8f88ffb5e0f9dafd83370e6bfcc3336c5561ce51 (commit)
via 5606846c01951cf71ad18ba4dbb898c0abdea8c6 (commit)
via 8c444ed288503da4680ea2f8560855ed0c6c2e8b (commit)
via 17705d5c282fde30c548a6a8cae759801076f520 (commit)
via 73e551df5330d46468038f0a841f0e93090fcc10 (commit)
via c852772950eb8980464e7888cc901cb1bf13c3b0 (commit)
via d73f293625fc16de030b104041c8a8a6edd6c2c6 (commit)
via 34014ea938cd107d37ae51129ef2285fe305536c (commit)
via 1f665ea0bab3f96ce0210c315dd578e0f65b4098 (commit)
via a77276ad1303d46bed831264f86d448a923538e5 (commit)
via 7b6460f9a719e343541a021c1c1a21fbe738272b (commit)
via 40c9d176411b41f07f36b3eaf9569c572eb75a8d (commit)
via 98947b52706cd7816ff0da24242c859d580e2813 (commit)
via 726d12d1c0c2744b34b940269db14b8cd8404b19 (commit)
via b55ad43d63322e21aa7a0177b63dbe73d4aa5f60 (commit)
via bac321e2b7f4c7609067ba618e759d78acba832b (commit)
via bafddfbf2ae01e21873925bac87f7749f4fb3f95 (commit)
via 80150843a0f3e571b1f892c8ddf770c5ca4beaa7 (commit)
via 2411f44b023e5d2c59074e2f95e2d9fa0adf8898 (commit)
via 549beb44194e46a657bc31f3b01482b52095215b (commit)
via 7e8efd9f03e6630c56820dc6b93bc13b3e692e99 (commit)
via fd47798e65e7de00cabcb06b2ea3794e2961fbc1 (commit)
via 6caaff3f7311b5702cc9babe3529722afc1e65ac (commit)
via e2543823c8e024b7fcecbfdbe095092a0e687400 (commit)
via c446b88ebfedf37942a02e5400284fb0f339570d (commit)
via 3eb482a76937b210454402d379614beb09335760 (commit)
via cf92d0036f75b0e4ed068f1ae3ea1eff6145742c (commit)
via 507efef4a5b05c7d95030c220d1bbe9851b80c25 (commit)
via aaae4eeaec0769e622e65a6654316497b21e61c6 (commit)
via 55334100be480ce8e87cb41bcd4f4f3de9458bb5 (commit)
via ed287098f29915ba416c0afc0be3ea64aa49c809 (commit)
via 414242d766f16880043a741de6182503bb344132 (commit)
via 906ee078a27aab4d38a46c325f0a6230037b4cd2 (commit)
via c0bf4d97f0e74c33ae6df01b60f699a615eade8c (commit)
via 3b75dfb2c697ae52e54c73fd6d6a285cf2482a31 (commit)
via ff29e81a564c3d532fd84734ebefeb9f29e6d182 (commit)
via 3c60536250f99c8ed7c4e373e4837b90614a2924 (commit)
via 92250851d2df6cc9fb0bdbffcb8df768f147b5b9 (commit)
via ec9f7461af898b55b29f218067c7d4ddc294aae0 (commit)
via bbda6b0160079d62dac347378da796e7504f3099 (commit)
via a090e7bb3e01f661d7a446a2d8270fc0d4bf37f3 (commit)
via d9b19712ea3eb31826e09e5ac6325098e8536e1a (commit)
via f99235f156c88b82decc558ddcbe87d89d7a1a19 (commit)
via 36fbd062a57a04f783537ff5a59fa2457ea4af17 (commit)
via d1dbc1b945ebc211226ac630066474626e53db79 (commit)
via c2ffc4e20e9eef10290a4084a88988b3178ddf50 (commit)
via 5387209cdcbf5a728fb3a3aed6b01441f3d03c5d (commit)
via 95bfa0c304406cba9fd2af682f727dcaaa93ba88 (commit)
via 11318befcf85280c43a1787ab3a64acf33bafb7b (commit)
via 0669d4b78da12b281b5ccb5a17626cdead0c62f0 (commit)
via 245e1b7e4d8778a02543a7fc23b887e02fdc13f4 (commit)
via 509524c0ac5e5f465cd87d943435531132c9a49c (commit)
via 1f10e1bdff72ebdd65dd6d0c5ffa1eeb54d7e1c2 (commit)
via 922922017ea47c5d758879558153781247430f2e (commit)
via 64e2949db79d1016044cae305b40fb23988ca892 (commit)
via ac2cd60a344f413b1c86680e12725efae2006cf1 (commit)
via 90210a0e719200606958b9d42f59d6edb85ef7ee (commit)
via 92f9ce72326dd4265323765bc97cd27bfe2c99db (commit)
via d5f8b4af7d80baa70f556bece622ce7a33a4a479 (commit)
via 25e6e23a44f99b59595cb1a2c216111eb6800533 (commit)
via 9c914766caee528962b91ad03d6e458f97caac48 (commit)
via ba882034898b352964d45fd317fab9e5cb185ea1 (commit)
via e22fe1eef6249f978cf71ec23375c66d0ddb66ad (commit)
via 8618f246e7f9c01dabbf6f100c00a72afc4fd1b7 (commit)
via 871ced900478109bfdb41e067f138fbf27e7c8e5 (commit)
via eb294428b451463169c9df6abe6c4d58f6f8ba15 (commit)
via e203990945754c73a63fdc4a1632758642223526 (commit)
via 6e10b134ce94f322b51fa2aebd13087a732678b0 (commit)
via c50afb8eb34c56424b9cca0c68fae356afa6c242 (commit)
via 4da6c45b0ded0a2a974f99d1dc4ce0d29b205bc3 (commit)
via ec81a500222ad705913daa85e4fafc1bcd8cf0c7 (commit)
via 1cdf1ed990117bc5ff6939d4cb4fbe831c210742 (commit)
via da6ef79e65f5763e8100c301f02e7347449216ed (commit)
via c9a9007c6f7eb6a1a41a1d4d3c1f86445090faad (commit)
via 7b03b2ecd97f8e0ab6795016e8a2f49194f588b9 (commit)
via 52ca4a273238be5405eb829c5691baa98f3a096e (commit)
via eee31284f8f9fc1da522d320786fae36021af3a8 (commit)
via f8af3a323632ed4f6154c5e1a71ec30d96ff6e44 (commit)
via 440fbad14e6c4f5ab93c6088ec95a19ff6707413 (commit)
via c241ad6fd439bbd1a1111441b33fe86c7aab0005 (commit)
via 4323d5f2f872c6902f4387bb69f6369f8a87d130 (commit)
via 6f2e941d4ec01c863c9ad10aeeecf22170d8df8b (commit)
via 3381cc31c48d955b6c4279aa99c7108cd4d64318 (commit)
via a67e0448c53a0568d574e62e1b20c8d5d6f196de (commit)
via a253ff70531e8d47e6eb99aeaf0ddbd3aae2a3cd (commit)
via 18d46da920992e5e3f5bd4e66179b3b374d30495 (commit)
via 14e1a68ca376beac41efe202d158cd7b3259c7ed (commit)
via 02bef5c8b735a8ef2fd563994dbb944fb445e5e9 (commit)
via e16223f7f76f6948205daa07d6a8a93223b1b8dc (commit)
via 454e48153af10fcf54170b3fc567edb7807e91aa (commit)
via 118517e3a3e45ec57a0b651256145b3f7a1a43b6 (commit)
via 509aea764bdd053750c32e0ccfe5f1d90c346f17 (commit)
via c1657cd4db4186a8d8042bc2b5c946bad6114561 (commit)
via 7959e634f4b458516bccf5a372f1a0b556e51213 (commit)
via 9074c83a949e4ea999d451d843ba45ec72dd5328 (commit)
via f390baea83a350200546e41dee4f68c2d4266cfc (commit)
via b36ddc072e35466624f89efa1c4f1daabab4303c (commit)
via 462c283d14e1bb0fab254ce67889b0917dee03af (commit)
via 91b64e636c461456a4cbd2073b57064504d27532 (commit)
via 24b598fd701f1ef1a903b3f657afbf180cb72d7a (commit)
via 02751b09c5f68c42153ac450d2a40bb788e99fae (commit)
via ba3e60d2215508bca5f58be1c56a4ca517f32ddd (commit)
via 07363e18dc452c27193dfaf097e791380a60c7cd (commit)
via 6ec70d8e5bfd4f380ce18df5da0880b8f6f01669 (commit)
via f2aed470bf715b8ff38b194571d18e273405cda4 (commit)
via 67b1a34162b9d2643bcacfb769f348c50815353e (commit)
via f3f99b4e7b06c003c95fbaaa9429258636e104b6 (commit)
via a0b980caf3605b4f508f575316a16c260440689a (commit)
via 0c191170c1831d981e1ec3e626ebe483b7d07d48 (commit)
via 2d9311e54e1b08bba2bd9be4d365ec0fee84e133 (commit)
via b14c4d1d3bdb1dc8321706af539264c462129050 (commit)
via 194fe309dc8742a5a8fa4c404d695c1ae9ae0dba (commit)
via 76ff17b63b7ce729a52c44be87e0f1312aa38096 (commit)
via 3364720c6efe8afb76d3e3122b85bb8081446663 (commit)
via 492338d0036b411ec21025ca7748f810fac78b52 (commit)
via 80068ef598fee2cdc8ef71108566933a19b22c4f (commit)
via f8ec199e7a04543e41e8b91eae100e45528b831b (commit)
via c14ce07ae2a01531a8ac1330cf0280111917ef6c (commit)
via c336aaa13ff941348f321c79fca768f2217805b8 (commit)
via a865c96a3278a69624db31fdb2e90e60ea570a98 (commit)
via d98e936a1a6c7bdb1f81b52f858b2c8e219b7076 (commit)
via 361dc5d617ceda7c01c5c35198239f4ba7f3d6b2 (commit)
via 363a7c572e3b0bdec3c81cc437748aab8344661c (commit)
via 92f258b8f235637a43f1f52d37b208586d20f72e (commit)
via 668303542a69551a594193be6938f11cc7f264b3 (commit)
via c91cbf3925b67429174f4a29e5860928a032d2f5 (commit)
via e30fd1385cf40c620909e2f557ed1e0334926fde (commit)
via 8ef95efb25d6ba825ffc807f61a6df1c708395a7 (commit)
via c6e0cae324fcca251ee67b71bad7cee560fe98c3 (commit)
via 7577d952757ce6bfc3bf934dc7cf7a16bae8d1db (commit)
via 371b5247444f625fff06d6e9e9a92c0023d7cccb (commit)
via fa8ca5d0cfb3cfaa7583077092858fa75adc8485 (commit)
via 59bf26c513b97370caa89ae765772e29b61de244 (commit)
via 539138423c15097d505e59d3482a624775497da0 (commit)
via 0efe68c0805b8b549a333f8de3a082de46a50859 (commit)
via 25f2cabb70b018f8a710b5855cb0a78806da0db2 (commit)
via b5865b91292202b444329ee0c1b57a1555008bf5 (commit)
via 8b554d824d74eec6ffa2b9c867bc53d1ef6f60d5 (commit)
via bf547c2b6833f9fd0e43e729552964b80065354d (commit)
via bb479408aa34a80ca20b570e5e07cccbc521d101 (commit)
via 383108fedb4d1c4f97c6bcfffd19178c33a76709 (commit)
via 6e4fd8acb45d6418970631524f84c5995e6dc7c6 (commit)
via 6f3793cfbbea409ba59f76d6d9f50b01ee1e3072 (commit)
via fd6f6146e3dc72291ebcb43fbcdfe8c00e4bfeb0 (commit)
via 59bdad2f76cc795bea4632d01f9c6cb236adca01 (commit)
via 991ee07dacf89b3b3f13a43a4f2f8be88b0a37a5 (commit)
via 6e8f16be6a205cc2bbb52d62d42794c266122adf (commit)
via 5d938057cec0ae8ef4455071c62abace6958961e (commit)
via 2fec8a8503d578b78d9baa948674001dc38d2701 (commit)
via 18bd50c29a81500e45e4c997a9c5f9223d643125 (commit)
via 44ae4760107fd59dd21cdbd1c9bc9d878af7648f (commit)
via 57b50727bad328e0d14007888b84fd6a6019d2c7 (commit)
via a1c083fdc6f07303568126f17bdfcd7332208ce9 (commit)
via 40c87fb339175aa0a39943acf43f43b9bce99d9d (commit)
via edc2f2fb36498b275e49114145a1030c8cf2a658 (commit)
via 676ad9bc4486a16bad11196b1b4d2c2748f38675 (commit)
via e3d8aeb8a3376362e387c17498999bdc888da916 (commit)
via 22ab080544c367f37ac33b0fb369455a0693612a (commit)
via 4a9e4f975a0445ca93be0b227becb1d3e6a0a5e6 (commit)
via e9330061ad5d6c7f4baaaaec347d114373cf1e7c (commit)
via 7e5475d4e0070fb1026036b421c70c461786da51 (commit)
via 2f683b9f009f61a0de54a86104a593b6922d6718 (commit)
via e120bcb1208a60a257461f35918acb6977b4ae8e (commit)
via 9e7c10b8440c8969deda620c41ce3426cc0d14b3 (commit)
via 949cb930c94198aeb8c102a4d2aa23b3b20948f8 (commit)
via e42425e6aee1485e353182f44b030cef770dab06 (commit)
via 7fcc44c148ceee2e27ad94ccfb45e6a6e66a5254 (commit)
via a9eb24a12426a458daf53e2f0ff892caaf75d3bc (commit)
via 47962e0f25729deccb42f61de635c184c3afb8de (commit)
via 0ce0d305db913e192bbb7ed2235febc03bcc5147 (commit)
via 179e1a0d1443cece0accc063227afb28780fc362 (commit)
via 114263972515edbdb838a837d7d085de51b867c1 (commit)
via 49aba51b71f1e1167dab4a6aa116d9b4000632b4 (commit)
via d955b8f2aadda236edbb53f23ccd69482ad8d062 (commit)
via 0a6c942cf2422f59d41a0c72ac925e5f1ea3bb86 (commit)
via 98944557d56a7ae2a95108455968f63f45e56256 (commit)
via db108a739fb2d04b47f34571a58ad3659545fe0e (commit)
via 1b76957bcc7b7561b3126d06cd2bd836a9b773f2 (commit)
via 8c9f1732ce240bfef304a2f2e440a3dfd93f6cfc (commit)
via 8c0e86e94257178ea154760ac9b80dc9710e5507 (commit)
via f0059431848ef890a47779d4508a20566763fa48 (commit)
via 6a96892860373d681562f005104bec0590ce73ab (commit)
via 91a284820233b6c798e29f99e2a1b0cf24fb5422 (commit)
via c8c54c25e89ee5547af75fcbb909f82c703ccaac (commit)
via 39616b90fa2b6693929109863ac6e9068674e800 (commit)
via 698bc6e29ab9c8159f56fbe138eb6386a1852558 (commit)
via 680d74d72e89a21ab8b15ed1ef757c1fbd8b0b70 (commit)
via a82cf91297a4afa067af7f909a5252bf74577b54 (commit)
via 305c9ddaf1bee721c99c3b1962d032617a407b59 (commit)
via 71bd47c65dfbc309e686322c1d9e72b7773f4136 (commit)
via 6be61e038d1923bc79469b1dcdad12df07e4a919 (commit)
via 658b52f57751e4cd1e68ad4797babe8b573ea53c (commit)
via e432ca57e7d6fe664a84cfe0e0ace5ac5c1eed46 (commit)
via 0949c0a89a9dd39f7f751ed98d1c33a37f3b0cc9 (commit)
via 7952424704ce9d34a0a2dcbf2aed2706acae350f (commit)
via cca9719202627b36e0809e97aeaac65a2b8e673e (commit)
via 3968d58f30db6825192f0ff85aeecf87f26b4919 (commit)
via bff539dbfcb15723212036d039a86a1027685c6c (commit)
via 0d17cd4ca49ed696ac84a5acbbd57dda6abaf6aa (commit)
via 92b438418db10057cd9645fb9fbc6e2fca07c8b1 (commit)
via 489c7f8a0689e747beb2a26daef533eb54d27f88 (commit)
via 7047fce0eacac1b89fd2361ed6a06a09e5035aca (commit)
via 6aaa90eaab993a9e0fd36ab4b3c37edbb5c93c4e (commit)
via 81ded2cbe74d09844c3be4c47057d39c2887e469 (commit)
via ee1c57d4e595266c9c041afffe4d5888c432fb61 (commit)
via 9901bc30771ba910d00296fff12cce98d08eb934 (commit)
via 07976c4389a7f4ff7e6fdb5bbbb3eafad4a63f90 (commit)
via ecee4e74a9803c229cf6021973ce8a62923b3b03 (commit)
via b48ef76900711198b4028c26ef2c0d99c6d5b837 (commit)
via 01f1cae45e26b13819546131fd5a57181e656bbb (commit)
via 7cd9a824f0eadc452751af29cadaed766ae819ff (commit)
via c193508f05ab1c6573be6339e86fbc45fe8160b2 (commit)
via 0f0de211caa4c0b0bdefdb8f0466f0a628654038 (commit)
via 6a6e1fef279d3d13450020fca14edbccef4fd7af (commit)
via 3f90096d8239fa46626bca0c599fc8abf4806e87 (commit)
via 708bc148d1a7d798fc757bb3b917cb8ee058690b (commit)
via bab7a49f9643b798fd0c15a2c463a507479e43e0 (commit)
via d4b0a79b9d915d7aa5782b06835a593aa68e0d18 (commit)
via 1b285872f544ce8191df52f71a3ad03789aae373 (commit)
via 5c197cdd8fb4d14e838bda271242e5b8b80dfd86 (commit)
via 99c56dd552a6bd47b6244a8e4dd0b9514d30717c (commit)
via ff0259ca392ea66dc137db2fcda129e747bb7ff1 (commit)
via fc9ced9c63ba837c752f72cd840f951e47473299 (commit)
via 93425776da43aadded8c5a575e5c39607bc78492 (commit)
via 1a0741a91c624f3a7676c0828e4e7a1229ae5b65 (commit)
via 428a4982af577d1dfacb3c8ba4e5345245dd9779 (commit)
via cdea52885afc0d86ddf7fa50f742efceaed2a510 (commit)
via 4a934b1ca8f8db53243b85a3586957b7aeb00f3b (commit)
via 37c2e3132f47fbe3e9c9ae187eef7b701c7114d3 (commit)
via d44539e2b3046e3f0f520687fe7a0e9f23422518 (commit)
via 15fbf422e3771752f9970cfd9640d115afdc58b9 (commit)
via 556e023ae11822d15918351c9e091fe1e4553249 (commit)
via 7771110c43c967f0726da4894229f42874ce5f07 (commit)
via 7d6d571993caeeae77e00ed8640aa2f5f19ffbff (commit)
via ec711ce9c220d599d4894b7e86c94ccf3f55ecbf (commit)
via 079f26b933d8ec89eee15f76f8ac5df39c7b29b7 (commit)
via e7dc9bb45c2fa61a596340d093dacf5fe567ca6a (commit)
via ef33a8f516b923dcd6861f6f3119ecf3a138dca7 (commit)
via 4467c484976204b7bbe3cbe152601d4ba85303cf (commit)
via d9ef39a3c963f76a5c3529ef8f9fed207c84eb79 (commit)
via 707e19665aea19c2be8da8d0c65295de8eeb71d0 (commit)
via 8f046859c3a48b683077eac20cb043b1f6c6c3d7 (commit)
via b4c94d1f87fe2bd7d6fcf46cae645f0b629d143a (commit)
via 9c0e4295f2a9e8c032192106f859feeda4cd6982 (commit)
via a4f04a013a7aab95cbde822e4833a1acc1bff276 (commit)
via 82bb764d0931979c20152e78083498dfa79d28b2 (commit)
via c82367ddab213d2ac2000292821ae7fe8a5baed0 (commit)
via b69bc2798ba2673e18663d93e5d4a7602dfc8984 (commit)
via cc51fde59c3cbe43ac6404abfc719f05779392a2 (commit)
via 22feb5851d2f872f7f1814f65c6b7f65bdbd5db6 (commit)
via 92c309d43b8a7d8f41342a8547f2c52a1462f40a (commit)
via b01017d23bea803c717fa77270d02ff351aa80fd (commit)
via e020c5504e63e982be0a088a073f2dbc3b117f47 (commit)
via 5ed0506599405e41b63a0a6d19055f5f1dfc574d (commit)
via b142f354b2ef2c929e5860ed4eaff9e95d98c1f3 (commit)
via a340f5a51d54068f9e804c574e7518a1795962cb (commit)
via 3a60c742234a60c73f5705a35dad0e3f6aea94e8 (commit)
via 4569f71b2b541fd539dcadf9c1c4596ef05e29bf (commit)
via 84af16f73d653eb46d8ec47e7d4b70e490689dd6 (commit)
via cf7c4f35e7f7c7fc1e0565ac3e91ac23cd0edf68 (commit)
via 03f5aba50c345c79eeb1f8b4be87cf4b2b27d5f2 (commit)
via f7bd83e7a46ced49b8e1c706802cf8fe15c6607b (commit)
via 8832e36d739d1f1f6b0b66fc8fc3c4ff28e1a5f8 (commit)
via 39b79e8bf7645c958f56130b8211187f1c197f0f (commit)
via aafe9bd1dd1dc00b6218d46c5fd1017b797d4c98 (commit)
via 023f3395eeafa3ecb4a4714c5f9d0a41ad1965bf (commit)
via 58b988991faee344f5ece45319db04d22213a7a8 (commit)
via 4d26063f7b10de5d34f6a1fe3df58f13ac924386 (commit)
via fc28b91452d3a0cf021fc4d8368bada846e0402c (commit)
via 5abb68cc1f7b52178fd81116bdb3be43226820cf (commit)
via 85d9ca261fe009d489a665dc41e4b4bebda33c3f (commit)
via 22dc21233f891c5495167940421c163a3842cf0b (commit)
via 205cb7d5bdfad55cbd2176cadb9789cdbc0a62f7 (commit)
via 363aa4eabc31e693bd8d0d254b85598a2f5abd1a (commit)
via fb2042cde3642828d52f984961d525dd0ebaa816 (commit)
via e65d724588bafcba6e1fb641103ba4d2e44e895a (commit)
via 52b0fc2356af5db79bcd59cc59e739313aa43131 (commit)
via 63639d2530cdf7977b80e05057d3d5c61b6558b0 (commit)
via 593d6cdfd9b4fa0c21863e1ad12826b617cf5912 (commit)
via 94f3df6d36c3afd8ba791d773d0fdc5ea19d2c46 (commit)
via b35c129e79e35a789dc67f3fa7c8285379377d62 (commit)
via e154c690d543a089085596d93636c9719baf4a80 (commit)
via 4f8e33df2f83b423d303bc02202c63ad2f3c09ff (commit)
via b637d7890ef6ee13c10cd24a412678921dd6f409 (commit)
via a42494951a07aeb7b2822aba1b876e1beb8de4ae (commit)
via e1d799ca19b59c129e5a10d0542d56a20d80da2a (commit)
via 248a1ac6533ad56ff2ece7a8166fadf62aeb600e (commit)
via 043e871ab3e52fedd277b8fdca9187be9b5b1184 (commit)
via b665b5ecd1263d3c359c197e8aa8be89ba67783e (commit)
via 72cd9de6043626ffe304d7696e05b969b700de3b (commit)
via 88cb2a1b346c96d03224355b519dd9964e783fc3 (commit)
via 3355fdd8bd6c329f55118ebe5b5063ced102309a (commit)
via f3a0e02a67ec8eb49bb6098847692716c51b6539 (commit)
via 8f3405b55be0c357ad88991a53ad60fd56fd743f (commit)
via 99fcdc2bf8c491d8b482e5ba6be18ce432c2a700 (commit)
via 00e5c66a78483b00ecd67b0270dc90d9f7465c68 (commit)
via b2a667bbb35b0901c00b5b47f635459eb4450c00 (commit)
via 00af6ca8b15f07f721356b48f9da0042a6408dbd (commit)
via 1aa3a7ec3fd07e90ba3914a23a2daf2e2d612fbb (commit)
via 3940d6ff8b4b562a4ae46a796a0b239154ab52f6 (commit)
via 90f74e4424101940627532073580e527f7bf3d43 (commit)
via c5da36630460aa29754dd5503e012ad8e40cbe70 (commit)
via c756f6bebb8bcff1de84f9243aa640c5a3ac06dd (commit)
via 0e8eab4fd4685c25768ed0769b7ce85a954d5a6b (commit)
via bd9358d0ee25e9997e686fd1b3cf60b8b3a70431 (commit)
via 875febe7127a12f03e53cc90269087ac1b916c97 (commit)
via 78a0ca402923dd6302accd354317e537c440670f (commit)
via a12e3b4182d8ffcefb544200736a0a50c0c904f9 (commit)
via 1cb3b643b9977949f18fd19cfdd9e4bcebadd0aa (commit)
via c5cf9343b51d656246b894dbf82289e3979cb0af (commit)
via 6ea96f0e9da23c5c2e499b9caa7c907ea72a4fba (commit)
via 0e8f2d92f3e40ecb44a30ec0685dffc64a783e6f (commit)
via daaffb1962b977e1708a79ad1ffbb0619a011a19 (commit)
via 59c7dc68c4b22fb6b47a184d1d943f58a75ec23a (commit)
via c1cea1dfd18c52de77a05bf60790879001692b8d (commit)
via cc395dd329e2dbcc8b02d972b02ebf36b3924cdb (commit)
via b44ad6e1b8d9a94be42258370e8b6f5f890d2afc (commit)
via 245b6a93c2a6557df64ca2c28c70469c23c06c0a (commit)
via 7530060ab0959a6cc98f6a809c0c1369c5a0298d (commit)
via 3e156c4f999c6d6b9b88bd067cc0887f7b119381 (commit)
via 1dfb8bda97fd16fc45c56508c8b798f565eb360b (commit)
via 1c0597ac3c254f3b132e88491c7b14fc7355847e (commit)
via ef7c3f19863ee10e9e08da735b0ea376a5c6c9e4 (commit)
via 280ac9d5c306a161934c62681905d2d9b28831cc (commit)
via 16474ec4e99963b3fa87ef2d9e13d5dbc9e9ad19 (commit)
via 49e210889e59ce65b52b8d7f340dbffb7b35d134 (commit)
via 9ca3721fad92cccd0fc1370fae247732f534c6d8 (commit)
via 583e924159aaec16845b399e9e12993035db6651 (commit)
via 41b5eb3bb278f2eca8f5e7a6e5d438a155809b47 (commit)
via d052987b6671a638868d2d2026529d0135499d36 (commit)
via 8cf67369f21d7071a9621809b3953fa838c7a15b (commit)
via 858ddcb2e6a33c4eced71e3c3bc9159145a529d4 (commit)
via 05817cc3cd4f905d71206a88c29b1b6a77e8d5db (commit)
via 530ef8dabca2962e6cc47656e2ff8036eb370e7d (commit)
via 618813663d69cf6ca183444eaa5fd6b92a112e34 (commit)
via 10f7b57a63344c11cf07c4678e074ff1887e3f10 (commit)
via 9959cc948ff79fca16143b94ba4accbb860c61a4 (commit)
via 86b2a7b29ff803706522a4a50820531105897741 (commit)
via b5b32f1338e2caabfea9bc89b753f36982198533 (commit)
via b4509efea6a53aa57f172625089741ec30775ec2 (commit)
via f7486521d3cf0b1f52c4dc2a18a12682b435116c (commit)
via 56e6a3aeaeb43a99d3b0579faa82f80173200d4e (commit)
via a61ecffa889af0a1e7407684001fa569744f1d26 (commit)
via 3194ddcd4a8e8a61c86031e6e63e15b2a4e2b682 (commit)
via b4eb7e06636c9aac9ecf05f9997e8bbdd8feb3bc (commit)
via b190188507e3023970b76816e8d3f6bd15f2e485 (commit)
via c725d20c576951210f700856b81413d5c016344f (commit)
via d91e52409357dca5b6d0e966fddc9e0527bba4da (commit)
via af577cf0257a88bf4144fe822c885337730978d8 (commit)
via f8fff7dd7e87e9293574c72a27695ea584261a18 (commit)
via 0a221250c197de5b14a998ec6c4e3e9d0a463769 (commit)
via 829bd143d0bc010aff8c6cd55dad910639625837 (commit)
via c3b592236d45c3e49575a64f08acd8ee07854b3f (commit)
via 9ec8a65e8c9478594ed4f06de4fbb34eeb56dc27 (commit)
via 01c700730ee62ac8549678c369a1d586b3d4f63e (commit)
via fe1224c952cfe1a54875f916482fb2158908ddbe (commit)
via a354bf8c3deff1e9b182ae705787973b8cbfa3d7 (commit)
via d6e50c546d240817fe1a401ef7454626276a4ccf (commit)
via d1957a1fcbd73c5d1b81fa0164cee610b04e4c46 (commit)
via 246232e321e83d29c2de7413a24d953542ed29c3 (commit)
via c775f2e75b107d33792725b03b1173c1d0cbf537 (commit)
via 20e31599ee71f2dbafc8f263686914606d46823c (commit)
via 6231126430af15285f86ee08ca29fe1ba2c9887a (commit)
via e2aab478e81298662c663cec6277c12760624ddd (commit)
via 55e7abe57502d5e5e2e45b9e9b1ff6a82b64ae8b (commit)
via 37816281bbc6b181bdb3e08abf59e29fcf971b3c (commit)
via a4d0142e0068364b5c81d9d64ffb2345a7d23e82 (commit)
via e5b3da38385053a41bea3bbeaf0e74bd0e3b760b (commit)
via 72eb18d06bbdb130c68f8d3fc1231e5e8b371fc0 (commit)
via c604a0713379bbdbb735aa43acc72f6f1e00b24a (commit)
via 51e6ba20d0a1b67c8ba587e0cd104ac239c6f3d7 (commit)
via d549721f218c5d9c26b6ef4087a63d302c342c2e (commit)
via e17d79fd88bdcfe539e5e7e49d3b18093d229ddd (commit)
via 599a0689f728f4fc392634587bde1a6d7c1e2f50 (commit)
via a1206a7a008d166461bdfe00dccc6da32307de96 (commit)
via f4e345969577f905f36c6855e5be9bfead289bd8 (commit)
via 4c6669f543c69fc8adb041933ff419d72a602d76 (commit)
via 3bdb1865e437a00a4d2cc4f3be4724a7c14a7f92 (commit)
via 6cfe1547e8b30815518583c55d6fd723d95abc8e (commit)
via 2f990cea64d8b0b9f1454e8fe5ac6125833b61d8 (commit)
via 7023b587a6af8e7a4a13411de023d9acb8a8b9b4 (commit)
via b236d2664eba3656c677a9aeb0329c2a4830801d (commit)
via bd2c63e13427d0f669dbe865953a0f0205685c56 (commit)
via c64368f78e7a605b2280f39660fdc3ea0d21e094 (commit)
via fbebb33f16ff618a42451e3e377164d09c730189 (commit)
via 07b120da063b8a11605e6da7e41055456744f702 (commit)
via a3fb79743829e24090fc9462a1cca73c3dee7b67 (commit)
via 41b0bc489e66909b401169187be80b91f452d4a8 (commit)
via bce4d3b2df85a02e639b8095424095643bdf4a6c (commit)
via 01c1c92adb6e355c1d98e189cb5f09f14bf0bc5d (commit)
via ec56f24736d4d863f285657bcb867f6835e1c287 (commit)
via 1d5217e9a9838aec4de34d43b856c82a933d8dc3 (commit)
via eebc7af1e2337dc0f3f388e45675d2c51694f165 (commit)
via cd1b1763f7ac75289d0405b2836a663c8d7ddd0b (commit)
via f2707b16c24228ddbe5f20038a80025bde45b1a1 (commit)
via 264131fc6332fc8241160388d8576b890963e514 (commit)
via 78c7882371e1c6d41bae6ffe5b206c5727c0fb1d (commit)
via 267bb3dc51c05ee2ffd39c356f3edade78fab5b4 (commit)
via 3432cc42af17f92ecf4a2c0b072fd5341953d87b (commit)
via 8a7d3baedb8ea2986642d30892660ae33e3524da (commit)
via f6eccc6ad0f8f4c856a7fa28558899df67d81b7d (commit)
via b89897a52fc4a0fd94375bc1ad79aa340cdcabfe (commit)
via 993c4f135a722460e313679694ff674c09c95966 (commit)
via 00169f28b976c14ff39b36f9347fbc58f9c22617 (commit)
via 194056de365b9c0c1ff9369e201d0030e1fdf2d5 (commit)
via 29d765837481ca207ecf71adcf76f2dd8768ecd9 (commit)
via 799dfb261ee7be9037af435190a406c14fe5eb42 (commit)
via 8ebc997fbe589f661384aeb37f0eb2861bca66b6 (commit)
via d62457b6eb109ca923d92dea2101721021b477e8 (commit)
via 62b801add3e315c1ceb2b977fe590b137239e8e1 (commit)
via f0e25ca5fedb4f3f4de5900f1b9f0c0e6d046b41 (commit)
via 891610d59b6c2b72e70c04696f4cbd06adfa6365 (commit)
via 16579be0ef62926e9cd597dae90dca2c4f2341fc (commit)
via ade699f7a6444da99efdb61d2a392b4976b1d053 (commit)
via a73059bad541c15c5b2de924ca367f1dd0c613be (commit)
via 4af3813642a44d36c473f5310ca53af076505a0b (commit)
via 0b5dbc9166248695ed8d9898a01d8512ee8fd707 (commit)
via 142bd7a2f623f58066d0b7a84c320ffef35e830c (commit)
via 225d2813ac57dfff8310e0331c1a205104ce5a59 (commit)
via 3f2605dbd1d3138e295e9a64c8afeb2d3ef6461d (commit)
via 32466c57a8c4d92f551b0ddb4fba8bcd0fcf15d0 (commit)
via c3450b7dc8cd9289ecab77c22a322abd53d76e1f (commit)
via ef916b299211fd74c740551242b6d48090063733 (commit)
via 536e26c65a06ff787dce9184c4491553445633dd (commit)
via 5436b4d39fd809afc998a24261e25e85bfd3d208 (commit)
via feffd3eb9fa0b25933e6e8889b5c9d337692fa3f (commit)
via e21cce24ae1586df8200dce17b52ed2c53b49839 (commit)
via 45915d9697f1a287593cd70d0c8b482ebdfa972a (commit)
via aff1bda8403f4af213cb591f8dfbeb304e763203 (commit)
via b0debd30f4b2817d980c27b53b79a936f989c868 (commit)
via 6a008f32bf8d74295a7880c93b07b748365ee605 (commit)
via 57c269b1a49f53fd027d7d2aca944b1e1492262d (commit)
via f4aeda7840994a33060b99390bfb9451438cb26b (commit)
via 6ad8375807b9a49ebd056f3f8973f1d67fe47f4a (commit)
via ee9cd67ea19829596dccd1a584f8498ce820cd06 (commit)
via b319acf7fe703b6c4257c8610003b007ff312821 (commit)
via 6309e03eff7d792c0a587483032a8c7e641a53f1 (commit)
via 6d1c2ebd816aad988da26a71df134b51b6147f0b (commit)
via 0a303bfbcd3b5f6410f1240cede9d8c25b6d7740 (commit)
via 9ae9a832c0c7778392658e0a95ea8e2b563c2975 (commit)
via b3dea50e763e7de813f8854f02ee2253605fac48 (commit)
via 07c022e7fbf40800f274f1f05514581070fb6c58 (commit)
via f66a3d1c04edca0cf63932dc99ff3fe6f9b533ce (commit)
via 213db39a4ecfb3e3121a5b2ccf28bb6bb141f180 (commit)
via 1e37d199d5a1735d3c9a9b2e88b76597a4850ec5 (commit)
via dd2fb35da51e24e3ef9667223e2e89479cde13e2 (commit)
via e6ede471b476bc1d69f27d6eed8257bbefa62198 (commit)
via c422f3f431019ac1615c65fb9132994800d0bd96 (commit)
via ffb5cf33a61cca649db9375a6e0c5c8a02c67388 (commit)
via c1dad5af99db0ed40dde126a5fd626c9dff05794 (commit)
via 70060572deb0f4fdc97825b2ff983057b816361f (commit)
via 78f625d3ebeb1c0e82c774b6f16c6fd82e1e52c3 (commit)
via acb0b42e2c62c5d51786a7079a7c922c6dbcea15 (commit)
via 72dd649f3a003cacb5cf1e6974ac37b082f66a38 (commit)
via 6f7fad712235d8d68972dd892e2800b423263591 (commit)
via 3075349c8b5412476d76ddae3907a521a883f261 (commit)
via c1e68493c18a9d02c80f2d66a2370e4df109bdaf (commit)
via a1464462acb7f03daa35e144dcc548f2eb377c25 (commit)
via d022433d0ac90c5fad6691ba1e1a2e40d06422f5 (commit)
via b157d2f08a6850706b1754acb213ff4b14eb39eb (commit)
via 47957aa391cb450a1686f740c99e1791553ebf29 (commit)
via 290cc6c0ef3909c2e5dae631f232268bd2d30253 (commit)
via fb12c91c561a872916b1e446b46fa10c0037be86 (commit)
via c5fb44aa2a10f26af71c9d9f4df6fbdc0709e745 (commit)
via bd31eeb89697f2a1d46f76e6fc812a5a10302891 (commit)
via 0615f330785f8f03f3e4974e8d3061751a6bb713 (commit)
via bdf84a5af3f3f9c877b840ebbfddc0e878bf8ce7 (commit)
via 610ab6a4a57b5f273ea6753fec24036e5dac679b (commit)
via 43f6bd02753f0d01dbd760aa79e54fe3ce343f53 (commit)
via 031282dcbff13f79a791577e847074cb8e3951ef (commit)
via bd9f636e05b711d011f683fdaac25c50710a77f3 (commit)
via 69e2c5d197a7441df95c17126b91de4f9cd224a0 (commit)
via 328aa9653362725e322dae03f9a77333a35f0fd1 (commit)
via 1dd420d7adf72d801cc11a24be58dcc48dda3c69 (commit)
via 4e78e9ee6d3fc30ae0cdaca6ddeae9b4fcc1ca73 (commit)
via 9ff5250899c8ec353f49bdce7d15a9f55c0c1aa0 (commit)
via cb0011e0f0477bd0fbe6245e40d511547ddd3065 (commit)
via b4b8c606a8b9d010a69a93632778a6393539767b (commit)
via b6705eae61e12e7029532e730a38135bd90f0a90 (commit)
via cd1eaca741f330181baec0770c728d45fde0e3c6 (commit)
via 6612fad39dadbe70bf210692fea44d89642704f2 (commit)
via 8a15f4893893e3c24054a5704749e3b823b31550 (commit)
via bb65896aad3f425ed1b7bb103dc3c0eee53d0b2f (commit)
via 078959b6085cde3f188fb50df672956f0997facf (commit)
via 08974269244aee90141eb7220c3c9927b437f3c1 (commit)
via 1910535878ad7d5b852487f7218579db871445b7 (commit)
via ff7c9e4b27194c2b4276d3c9d91c537d38c093dd (commit)
via bcff3505270238a6dd59119c7342eee80eef845c (commit)
via fcb9426fdf4589666d7c382090b836b11be5bc76 (commit)
via 5e50a9c09f940c07b81146f0bc1b74a0cd9d0228 (commit)
via 4d754f360019a0cb7c2f1c23d6e432b24b37f108 (commit)
via d5ddbbd9e154898f526c81fff448f19b89761c5f (commit)
via 5baa9cbff53400bc93fe6fd56824b67253103fba (commit)
via d7545acfb3e35c75cd8d52bf8ca16ca95df72832 (commit)
via c0a5b8432131f48ab01e73bf31c919c2f18f5385 (commit)
via 73261d90399720c35b332f3ec583ef915829d936 (commit)
via c510ffd69e960a6a09e20ff598fae15c481f162a (commit)
via 0d0eea47897ed2ec5b02370af89137c1a438f50d (commit)
via 52cfea629b7625aaa85eca0c1187d5a7e17fd501 (commit)
via d608cabbdd878c60632ebfe0c00228b86087a7c4 (commit)
via 691f0148907c4174199c13815d49ee520e7eb7a5 (commit)
via 17884f1ae3e0f91d1cbfbf23394f323c8ca0b847 (commit)
via e03efa27ea66cd8e3dadfc1878a56d7389e0997e (commit)
via 260cd614f0f7e2a024c098fa7740be06aa60fb14 (commit)
via 60766396ffb87d1a5d30a2331f28f49a323b92a7 (commit)
via 5df674331209dded57c5e68ac781d5453b71fff3 (commit)
via c9e92f882e6d16aa2ec5460f35ffe528ad86ada2 (commit)
via 857ab620cc1e91646ca842bfc67dbb4a5f49736a (commit)
via 02326cbdd19ccc02c97cf9e0f0c7e973abea627f (commit)
via cd716ddd492299af3e5347f0e9d63947b0c87fd4 (commit)
via 269d2f1a325d718ee7b84829ac27a30b50a07239 (commit)
via c392730ae1a5e00367d562c5b7f50dcbfcc31d33 (commit)
via b26712edb91113a3250aa3b35401379a60780740 (commit)
via 63266cbf34fc7735653d39bcf15d3d79d9b07b91 (commit)
via 819a50311fa53fe984924268124c3f956112ee5b (commit)
via 39f304aae1fa011b18d7308b6b5f2201f3acc860 (commit)
via 24001211e5c9efbb4be9c500dacf334cf22bf540 (commit)
via 90b711c7e73d73ea29b61010aaf7f8b79762a4bf (commit)
via 8d128adb3679879ef00f556e174f2216d43401ee (commit)
via 8bc4a6804e68d7776964e9b02db5f8b3db02b9cd (commit)
via a34e9b3a46caa3481e3beb8a5ce557f568d298ef (commit)
via 927ebb75727aa43f8c729efdf08b8a7207f8624e (commit)
via 2999da568433e36dae6b79693f77cd793c9e99e9 (commit)
via b01f55cfe1c54617692525e8be0aa2c96d0cc543 (commit)
via 888da76ac57158319ea138dd8e1a7cb518c7d78a (commit)
via 3dade98a0fbdae6f3147c5d0b4b0cfb7bb89259d (commit)
via 37097b66617835dc29816c4e4af7f55a49ccdde5 (commit)
via bd5d7cc50db31904217a1ce14c33524f0c261af1 (commit)
via 11a4d7825c04c82903de2b31ae9172af04d5cc54 (commit)
via f0b2f526370293faa286601322debb40b07504f3 (commit)
via 1561a5edf0d2a78caf59b7743c79a9e3c61d9e1a (commit)
via 09b3bfdb08fd7c8df510a313070fd0a92c8cbe34 (commit)
via e522afb662de3efd0320060491ce29aaec9c5fb3 (commit)
via 50930c07f239a88846f4d77695c8bb804d6d3f0a (commit)
via 75860582874e2afd641edaf2ae6c0ba6147b2734 (commit)
via f384cb3906a8333c253a14ef0bc511ada9ab93eb (commit)
via 4162d7f98cb90e0b7f93b30036d330faf6e529ad (commit)
via 85fc9321856d7c6db1bf59e1802a4193f9cd8837 (commit)
via 1b90ec96457de743ecfad4ed5fab37c57dd014e9 (commit)
via b27bcc59aee883f3f5178d7a46dd9e6c679344e5 (commit)
via ce1d07c02061bb9e981520e7e5f9fed868ead2d5 (commit)
via 5ffdfb8bff9e9b8b56dda6750c3323032b1b31c9 (commit)
via e54aceec23d5b6360796ec8224c33f746cf06969 (commit)
via 0a48da9fca14f0b96a7c191617ace69eff948e55 (commit)
via b253f46fddf27d47df6ba151affeff352c824a27 (commit)
via ff85a2cfed227b13a906fa3bcad67ce3f66d50c1 (commit)
via e2d9d374f93b617cb4b756a503e086084a25942f (commit)
via e294d92f2fb348a03c05bae9eb1cbdd07be5b11c (commit)
via e794b1179d9357623c74081d956ae462321b28ad (commit)
via 18849fd4d4869f962abbfc915f0cae54fa3c0273 (commit)
via f4c0a369a168f4b29c118b26398a101149feecb8 (commit)
via 5d594554d805df00b1dd05197c60ac02cb6dea96 (commit)
via a7b8170a405dc670370fe2f393da436b0924aeee (commit)
via 8c3d133df5964f05844210138d4ef38ab9355991 (commit)
via e3d6eef632307ee27bc59cca64a104a4cfc0d846 (commit)
via 574becfe27bd8b824dc0f7221dcad296bb5e28fb (commit)
via 95886cf1095c619624b6311f1cb6a4c81f55f682 (commit)
via ae01e6eea71b4472d35eeae47a725b5df1bded55 (commit)
via 8ed07237a9bae1a735b987139f9ccc0fe79f3fdb (commit)
via 19b0dd5363ea14265a88f50778ddd201fc75d3b1 (commit)
via 2f58cc74501e67b8e12645fee56596a3407b48df (commit)
via 1c2a39cc7642b0bb9fb5711e35fa5ddf877a82d1 (commit)
via 2819f2e4ced9f6fc35126fe7ed208d051dc47125 (commit)
via 582847170427c677a9d7c52ae76c30329e5026b4 (commit)
via d2178485d8c4978fb42795c91ee64b3db0bb7ef8 (commit)
via c1f0a6952a71e76fd7dd7cbfcd01780ccb64d506 (commit)
via 3fcfdfc9fb249b413259119036b81263a3769e05 (commit)
via 0962128cb8d8291fd8fed7b5a31ef8a2d2b17f1d (commit)
via 5989f3a8520974c73bd1d095287d04071b77b4d2 (commit)
via c531b63fbee1da3426ba8d2034b387b84950aa54 (commit)
via dcb438e316c8f03f160f461b62e644bd050ecdeb (commit)
via 1eec7cd64f9939e254b2341c9f73ef7fbc64af76 (commit)
via 73b5a1c9f18d1b825a4c1f57c136ed0be4046ffe (commit)
via dfae60d7a6581d9909db49a9bff178e3bf9f29e7 (commit)
via eab2741603ea7677681afe0930df0de3e04b0f15 (commit)
via 9dcffa8593ecd86268be3802828a21907f1d7cbe (commit)
via 6be597a3353c4a76b792b06a3c53d3fcd63476a2 (commit)
via bb0f4d137f724815503b7022102ea5a2f1844f59 (commit)
via dcf4767f8df03cfe481425abd7e00456b2704ade (commit)
via fb03c03bea9aac73a532dcee3fdad22fa107666f (commit)
via 39234412a53e8edd4b9f6e707c94aa686af6941e (commit)
via 0d8ea5f84a0cf60d5526e8d5a4b5c921b995539b (commit)
via 4e78160172f630240f49c98b85986b6bc59b418e (commit)
via ac8b03d9dd060c1f8ce83ef1c9d6f53fd243b6a2 (commit)
via 3761f951549ff605aa143406fe275595bb6efdb0 (commit)
via dfec337b6a9e07628598364f5347deed0618dae7 (commit)
via ced333dd612ffad8135a2c3f5061c4d5e06fb0a8 (commit)
via 80cc33bac16a7da24973888a92e9df4c73d21c79 (commit)
via b09427917e2181830adaf2a73cc245b81a7066c1 (commit)
via 234775bcfacbc8e009343270db6907ab85ac13b5 (commit)
via a3fcd5da943153ebca803295e04166ecaa4256e4 (commit)
via 47a02e114b12f0544d471d416266b3c788824330 (commit)
via d292860d20c923d1a4f49cb82e9644c9adb82d32 (commit)
via 8f1fa977eb338f2947f4650b7734df9f5d4d889c (commit)
via 3df41bbdc12804c6a142695524760d656d559343 (commit)
via d6723970a0da52aa533e8f760a490788fd8d3f7a (commit)
via a65c2f3d0eeaa5a2494c7e226333d15988223cef (commit)
via 072a7a8a5ab10a90c0e0c6674566524fed98f8cd (commit)
via 096de436b019de69d34495dfc8ec6364bb5964cb (commit)
via e3e1bf80e144c4b82a54b35de55bfb26fef756cb (commit)
via 31f2a570a8fb72aa9fb187ec4ffb03a10bd9e00c (commit)
from a5e10400bf6f2f988c96477d3b9e7a83a729a325 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 99d66fee76e2c96798408086d44822e4c6932403
Author: Jennifer Turner <jennifer.turner at mnsu.edu>
Date: Fri Jul 13 14:16:32 2012 -0400
Documentation: Add Circulation, Patron management Chapter
Content provided by Jennifer Turner at PALS. Converted to Asciidoc by Robert Soulliere. Robert also added indexing terms. Appendices for documentation cleaned up as well.
Signed-off-by: Robert Soulliere <robert.soulliere at mohawkcollege.ca>
diff --git a/docs/attributions.txt b/docs/attributions.txt
index 3d8e6e0..0705d01 100644
--- a/docs/attributions.txt
+++ b/docs/attributions.txt
@@ -1,4 +1,5 @@
[[attributions]]
+[appendix]
Attributions
============
diff --git a/docs/circulation/circulation_patron_records.txt b/docs/circulation/circulation_patron_records.txt
new file mode 100644
index 0000000..e9406e8
--- /dev/null
+++ b/docs/circulation/circulation_patron_records.txt
@@ -0,0 +1,318 @@
+Circulation - Patron Record
+---------------------------
+
+[[circulation_searching_patrons]]
+Searching Patrons
+~~~~~~~~~~~~~~~~~
+
+indexterm:[patrons, searching for]
+
+To search for a patron, select the Patron Search option from the toolbar, _Search -> Search for Patrons_ from the menu bar, or *F4*.
+
+The Patron Search screen will display. The orientation of the search pane may be vertical or horizontal, depending on your library’s configuration. It will contain options to search on the following fields:
+
+* Last Name
+* First Name
+* Middle Name
+* Alias
+* Address 1
+* Address 2
+* City
+* Zip
+* Phone
+* Email
+* State
+* Barcode
+* OPAC Login
+* ID
+
+Use the options above the search fields to include patrons marked ``inactive'' in your search results or to limit results to patrons in a specific library branch or in a specific permission group.
+
+image::media/circulation_patron_records-1.png[circulation_patron_records 1]
+
+.Tips for searching
+[TIP]
+===================
+* Search one field or combine fields for more precise results.
+* Truncate search terms for more search results.
+===================
+
+Once you have located the desired patron, highlight the entry for this patron in the results screen. A summary for this patron will display in place of the search fields.
+
+image::media/circulation_patron_records-2.png[circulation_patron_records 2]
+
+Use the _Retrieve Patron_ button to retrieve the patron for circulation or editing.
+
+image::media/circulation_patron_records-3.png[circulation_patron_records 3]
+
+The _Search Form_ button may be used to resume searching for patrons.
+
+Registering New Patrons
+~~~~~~~~~~~~~~~~~~~~~~~
+
+indexterm:[patrons, registering]
+
+To register a new patron, select _Patron Registration_ from the toolbar, _Circulation -> Register Patron_ from the menu bar, or *shift + F1*. The Patron Registration form will display.
+
+image::media/circulation_patron_records-4.png[circulation_patron_records 4]
+
+Mandatory fields display in yellow.
+
+image::media/circulation_patron_records-5.png[circulation_patron_records 5]
+
+The _Show Only Required Fields_ and _Show Suggested Fields_ may be used to limit the options on this page.
+
+image::media/circulation_patron_records-6.png[circulation_patron_records 6]
+
+When one of these options is selected, it is possible switch to the other limited view or to revert to the original view by selecting _Show All Fields_.
+
+image::media/circulation_patron_records-7.png[circulation_patron_records 7]
+
+When finished entering the necessary information, select _Save_ to save the new patron record or _Save & Clone_ to register a patron with the same address. When _Save & Clone_ is selected, the address information is copied into the resulting patron registration screen. It is linked to the original patron. Address information may only be edited through the original record.
+
+image::media/circulation_patron_records-8.png[circulation_patron_records 8]
+
+[TIP]
+================================================================================
+* Requested fields may be configured in the _Library Settings Editor_ (_Admin ->
+* Local Admin -> Library Settings Editor_).
+* Statistical categories may be created for information tracked by your library
+* that is not in the default patron record. These may be configured in the
+* _Statistical Categories Editor_ (_Admin -> Local Admin -> Statistical Categories Editor_).
+* Staff accounts may also function as patron accounts.
+===========================================================================================
+
+[[updating_patron_information]]
+Updating Patron Information
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+indexterm:[patrons, updating]
+
+Retrieve the patron record as described in the section <<circulation_searching_patrons,Searching Patrons>>.
+
+Select _Edit_ from the options that display at the top of the patron record.
+
+image::media/circulation_patron_records-9.png[circulation_patron_records 9]
+
+Edit information as required. When finished, select _Save_. If you attempt to close out of the patron account before the information is received, an alert will display.
+
+image::media/circulation_patron_records-10.png[circulation_patron_records 10]
+
+Select _OK_ to continue or _Cancel_ to return to the editing form.
+
+After selecting _Save_, the page will refresh. The edited information will be reflected in the patron summary pane.
+
+NOTE: If collapsed, you will need to manually ``un-collapse'' this pane.
+
+Renewing Library Cards
+~~~~~~~~~~~~~~~~~~~~~~
+
+indexterm:[library cards, renewing]
+
+Expired patron accounts display with a black box around the patron’s name, a note that the patron is expired, and – when initially retrieved – an alert stating that the ``Patron account is EXPIRED.''
+
+image::media/circulation_patron_records-11.png[circulation_patron_records 11]
+
+Open the patron record in edit mode as described in the section <<updating_patron_information,Updating Patron Information>>.
+
+Navigate to the information field labeled _Privilege Expiration Date_.
+Enter a new date in this box. When you place your cursor in the _Patron Expiration Date box_, a calendar widget will display to help you easily navigate to the desired date.
+
+image::media/circulation_patron_records-12.png[circulation_patron_records 12]
+
+Select the date using the calendar widget or key the date in manually. Click the _Save_ button. The screen will refresh and the ``expired'' alerts on the account will be removed.
+
+Lost Library Cards
+~~~~~~~~~~~~~~~~~~
+
+indexterm:[library cards, replacing]
+
+Retrieve the patron record as described in the section <<circulation_searching_patrons,Searching Patrons>>.
+
+Open the patron record in edit mode as described in the section <<updating_patron_information,Updating Patron Information>>.
+
+Next to the _Barcode_ field, select the _Replace Barcode_ button.
+
+image::media/circulation_patron_records-13.png[circulation_patron_records 13]
+
+This will clear the barcode field. Enter a new barcode and _Save_ the record. The screen will refresh and the new barcode will display in the patron summary pane.
+
+If a patron’s barcode is mistakenly replaced, the old barcode may be reinstated. Retrieve the patron record as described in the section <<circulation_searching_patrons,Searching Patrons>>. Open the patron record in edit mode as described in the section <<updating_patron_information,Updating Patron Information>>.
+
+Select the _See All_ button next to the _Replace Barcode_ button. This will display the current and past barcodes associated with this account.
+
+image::media/circulation_patron_records-14.png[circulation_patron_records 14]
+
+Check the box(es) for all barcodes that should be ``active'' for the patron. An ``active'' barcode may be used for circulation transactions. A patron may have more than one ``active'' barcode. Only one barcode may be designated ``primary.'' The ``primary'' barcode displays in the patron’s summary information in the _Library Card_ field.
+
+Once you have modified the patron barcode(s), _Save_ the patron record. If you modified the ``primary'' barcode, the new primary barcode will display in the patron summary screen.
+
+Resetting Patron's Password
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+indexterm:[patrons, passwords]
+
+A patron’s password may be reset from the OPAC or through the staff client. To reset the password from the staff client, retrieve the patron record as described in the section <<circulation_searching_patrons,Searching Patrons>>.
+
+Open the patron record in edit mode as described in the section <<updating_patron_information,Updating Patron Information>>.
+
+Select the _Reset Password_ button next to the _Password_ field.
+
+image::media/circulation_patron_records-15.png[circulation_patron_records 15]
+
+NOTE: The existing password is not displayed in patron records for security reasons.
+
+A new number will populate the _Password_ and _Verify Password_ text boxes. Make note of the new password and _Save_ the patron record. The screen will refresh and the new password will be suppressed from view.
+
+Barring a Patron
+~~~~~~~~~~~~~~~~
+
+indexterm:[patrons, barring]
+
+A patron may be barred from circulation activities. To bar a patron, retrieve the patron record as described in the section <<circulation_searching_patrons,Searching Patrons>>. Open the patron record in edit mode as described in the section <<updating_patron_information,Updating Patron Information>>.
+
+Check the box for _Barred_ in the patron account.
+
+image::media/circulation_patron_records-16.png[circulation_patron_records 16]
+
+_Save_ the user. The screen will refresh. The patron account will now display an alert stating that the patron account is *BARRED*. Additionally a red box and note will indicate the patron’s barred status.
+
+image::media/circulation_patron_records-17.png[circulation_patron_records 17]
+
+NOTE: Barring a patron from one library bars that patron from all consortium member libraries.
+
+To unbar a patron, uncheck the Barred checkbox.
+
+Barred vs. Blocked
+~~~~~~~~~~~~~~~~~~
+
+indexterm:[patrons, barring]
+
+*Barred*: Stops patrons from using their library cards; alerts the staff that the patron is banned/barred from the library. The ``check-out'' functionality is disabled for barred patrons (NO option to override – the checkout window is unusable and the bar must be removed from the account before the patron is able to checkout items). These patrons may still log in to the OPAC to view their accounts.
+
+indexterm:[patrons, blocking]
+
+*Blocked*: Often, these are system-generated blocks on patron accounts.
+
+Some examples:
+
+* Patron exceeds fine threshold
+* Patron exceeds max checked out item threshold
+
+A notice appears when a staff person tries to checkout an item to blocked patrons, but staff may be given permissions to override blocks.
+
+Patron Alerts
+~~~~~~~~~~~~~~
+
+indexterm:[patrons, Alerts]
+
+When an account has an alert on it, a Stop sign is displayed when the record is retrieved.
+
+image::media/circulation_patron_records-18.png[circulation_patron_records 18]
+
+Navigating to an area of the patron record using the navigation buttons at the top of the record (for example, Edit or Bills) will clear the message from view.
+
+If you wish to view these alerts after they are cleared from view, they may be retrieved. Use the Other menu to select _Display Alert_ and _Messages_.
+
+image::media/circulation_patron_records-19.png[circulation_patron_records 19]
+
+There are two types of Patron Alerts:
+
+*System-generated alerts*: Once the cause is resolved (e.g. patron's account has been renewed), the message will disappear automatically.
+
+*Staff-generated alerts*: Must be added and removed manually. To add an alert to a patron account, retrieve the patron record as described in the section <<circulation_searching_patrons,Searching Patrons>>. Open the patron record in edit mode as described in the section <<updating_patron_information,Updating Patron Information>>.
+
+Enter the alert text in the Alert Message field.
+
+image::media/circulation_patron_records-20.png[circulation_patron_records 20]
+
+_Save_ the record. The screen will refresh and the alert will display. Additionally, the patron name will be highlighted in yellow and a note will indicate that there is an alert on the account.
+
+image::media/circulation_patron_records-21.png[circulation_patron_records 21]
+
+To remove the alert, retrieve the patron record as described in the section <<circulation_searching_patrons,Searching Patrons>>. Open the patron record in edit mode as described in the section <<updating_patron_information,Updating Patron Information>>.
+
+Delete the alert text in the _Alert Message_ field. _Save_ the record. The screen will refresh and the indicators for the alert will be removed from the account.
+
+Patron Notes
+~~~~~~~~~~~~
+
+indexterm:[patrons, notes]
+
+When a patron account contains a note, a _See Notes_ message appears beneath the patron’s name in the patron summary pane.
+
+image::media/circulation_patron_records-22.png[circulation_patron_records 22]
+
+Notes are strictly communicative and may be made visible to the patron via their account on the OPAC. In the JSPAC, these notes display on the account summary screen in the OPAC.
+
+image::media/circulation_patron_records-23.png[circulation_patron_records 23]
+
+To insert or remove a note, retrieve the patron record as described in the section <<circulation_searching_patrons,Searching Patrons>>. Open the patron record in edit mode as described in the section <<updating_patron_information,Updating Patron Information>>.
+
+Use the Other menu to navigate to _Notes_.
+
+image::media/circulation_patron_records-24.png[circulation_patron_records 24]
+
+Select the _Add New Note_ button. An _Add Note_ window displays.
+
+Enter note information.
+
+Select the check box for _Patron Visible_ to display the note in the OPAC.
+
+image::media/circulation_patron_records-25.png[circulation_patron_records 25]
+
+Select _Add Note_ to save the note to the patron account.
+
+To delete a note, go to _Other -> Notes_ and use the _Delete This Note_ button under each note.
+
+image::media/circulation_patron_records-26.png[circulation_patron_records 26]
+
+An alert will display. Click _Yes_ to delete the note or No to retain the note. A confirmation box will display; click _OK_.
+
+Merging Patron Records
+~~~~~~~~~~~~~~~~~~~~~~
+
+indexterm:[patrons, merging]
+
+When patron records are erroneously duplicated, they may be merged into one record. As described in the section <<circulation_searching_patrons,Searching Patrons>>, search for the term(s) shared by the two records.
+
+Select the two records to merge by pressing down the CTRL key and clicking each record.
+
+Click the _Merge Patrons_ button next to the _Search Form_ and _Retrieve Patron_ buttons on the top of the screen.
+
+image::media/circulation_patron_records-27.png[circulation_patron_records 27]
+
+A Record Merging window will display. Compare the two records. Select the record you want to keep by checking the radio button _Lead Record_ next to the appropriate record.
+
+image::media/circulation_patron_records-28.png[circulation_patron_records 28]
+
+After making your selection, click the _Merge_ button. The screen will refresh. Only one of the two patron names will display.
+
+NOTE: Once two records have been merged, the notes, bills, holds and outstanding items under the non-lead record are brought to the lead record. Staff-inserted alert messages are not transferred from the non-lead record; lead record alerts are retained.
+
+Patron records may also be merged from the _Patron Group_ screen
+Retrieve one of the two patron records you want to merge. Go to _Other -> Group Member Details_.
+
+image::media/circulation_patron_records-29.png[circulation_patron_records 29]
+
+The patron records are displayed as group members. If both patron records are not already displayed on this screen, click _Choose an Action -> Move another patron to this patron group_.
+
+image::media/circulation_patron_records-30.png[circulation_patron_records 30]
+
+At the prompt, scan or type the patron's barcode. Click _OK_. Confirm the move by clicking the _Move_ button on top of the screen.
+
+image::media/circulation_patron_records-31.png[circulation_patron_records 31]
+
+Click _OK_ on the confirmation pop-up window.
+
+Both records are displayed as group members.
+
+Select both records by pressing *CTRL* key and clicking each record.
+
+Click _Choose an Action -> Merge Selected Patrons_. The merging records window pops up.
+
+Choose the lead record and continue to merge records as described in the above.
+
+NOTE: The merged record will still show under group members. Both members point to the same patron record.
+
+
diff --git a/docs/licensing.txt b/docs/licensing.txt
index a9f2ec3..d04c9b1 100644
--- a/docs/licensing.txt
+++ b/docs/licensing.txt
@@ -1,3 +1,4 @@
+[appendix]
Licensing
=========
diff --git a/docs/media/circulation_patron_records-1.png b/docs/media/circulation_patron_records-1.png
new file mode 100644
index 0000000..0fba3d9
Binary files /dev/null and b/docs/media/circulation_patron_records-1.png differ
diff --git a/docs/media/circulation_patron_records-10.png b/docs/media/circulation_patron_records-10.png
new file mode 100644
index 0000000..923720c
Binary files /dev/null and b/docs/media/circulation_patron_records-10.png differ
diff --git a/docs/media/circulation_patron_records-11.png b/docs/media/circulation_patron_records-11.png
new file mode 100644
index 0000000..3c0cfb2
Binary files /dev/null and b/docs/media/circulation_patron_records-11.png differ
diff --git a/docs/media/circulation_patron_records-12.png b/docs/media/circulation_patron_records-12.png
new file mode 100644
index 0000000..25bc8c8
Binary files /dev/null and b/docs/media/circulation_patron_records-12.png differ
diff --git a/docs/media/circulation_patron_records-13.png b/docs/media/circulation_patron_records-13.png
new file mode 100644
index 0000000..f4e5bbf
Binary files /dev/null and b/docs/media/circulation_patron_records-13.png differ
diff --git a/docs/media/circulation_patron_records-14.png b/docs/media/circulation_patron_records-14.png
new file mode 100644
index 0000000..bcd74f9
Binary files /dev/null and b/docs/media/circulation_patron_records-14.png differ
diff --git a/docs/media/circulation_patron_records-15.png b/docs/media/circulation_patron_records-15.png
new file mode 100644
index 0000000..b2545a4
Binary files /dev/null and b/docs/media/circulation_patron_records-15.png differ
diff --git a/docs/media/circulation_patron_records-16.png b/docs/media/circulation_patron_records-16.png
new file mode 100644
index 0000000..4e660c3
Binary files /dev/null and b/docs/media/circulation_patron_records-16.png differ
diff --git a/docs/media/circulation_patron_records-17.png b/docs/media/circulation_patron_records-17.png
new file mode 100644
index 0000000..3b5eb45
Binary files /dev/null and b/docs/media/circulation_patron_records-17.png differ
diff --git a/docs/media/circulation_patron_records-18.png b/docs/media/circulation_patron_records-18.png
new file mode 100644
index 0000000..cc9c346
Binary files /dev/null and b/docs/media/circulation_patron_records-18.png differ
diff --git a/docs/media/circulation_patron_records-19.png b/docs/media/circulation_patron_records-19.png
new file mode 100644
index 0000000..59614f1
Binary files /dev/null and b/docs/media/circulation_patron_records-19.png differ
diff --git a/docs/media/circulation_patron_records-2.png b/docs/media/circulation_patron_records-2.png
new file mode 100644
index 0000000..9cdf324
Binary files /dev/null and b/docs/media/circulation_patron_records-2.png differ
diff --git a/docs/media/circulation_patron_records-20.png b/docs/media/circulation_patron_records-20.png
new file mode 100644
index 0000000..6a2b184
Binary files /dev/null and b/docs/media/circulation_patron_records-20.png differ
diff --git a/docs/media/circulation_patron_records-21.png b/docs/media/circulation_patron_records-21.png
new file mode 100644
index 0000000..e56eb62
Binary files /dev/null and b/docs/media/circulation_patron_records-21.png differ
diff --git a/docs/media/circulation_patron_records-22.png b/docs/media/circulation_patron_records-22.png
new file mode 100644
index 0000000..5e97c36
Binary files /dev/null and b/docs/media/circulation_patron_records-22.png differ
diff --git a/docs/media/circulation_patron_records-23.png b/docs/media/circulation_patron_records-23.png
new file mode 100644
index 0000000..0f255a2
Binary files /dev/null and b/docs/media/circulation_patron_records-23.png differ
diff --git a/docs/media/circulation_patron_records-24.png b/docs/media/circulation_patron_records-24.png
new file mode 100644
index 0000000..b97d7fa
Binary files /dev/null and b/docs/media/circulation_patron_records-24.png differ
diff --git a/docs/media/circulation_patron_records-25.png b/docs/media/circulation_patron_records-25.png
new file mode 100644
index 0000000..e5a8bfc
Binary files /dev/null and b/docs/media/circulation_patron_records-25.png differ
diff --git a/docs/media/circulation_patron_records-26.png b/docs/media/circulation_patron_records-26.png
new file mode 100644
index 0000000..0092b02
Binary files /dev/null and b/docs/media/circulation_patron_records-26.png differ
diff --git a/docs/media/circulation_patron_records-27.png b/docs/media/circulation_patron_records-27.png
new file mode 100644
index 0000000..d01b952
Binary files /dev/null and b/docs/media/circulation_patron_records-27.png differ
diff --git a/docs/media/circulation_patron_records-28.png b/docs/media/circulation_patron_records-28.png
new file mode 100644
index 0000000..69a29a5
Binary files /dev/null and b/docs/media/circulation_patron_records-28.png differ
diff --git a/docs/media/circulation_patron_records-29.png b/docs/media/circulation_patron_records-29.png
new file mode 100644
index 0000000..0c864f1
Binary files /dev/null and b/docs/media/circulation_patron_records-29.png differ
diff --git a/docs/media/circulation_patron_records-3.png b/docs/media/circulation_patron_records-3.png
new file mode 100644
index 0000000..f016101
Binary files /dev/null and b/docs/media/circulation_patron_records-3.png differ
diff --git a/docs/media/circulation_patron_records-30.png b/docs/media/circulation_patron_records-30.png
new file mode 100644
index 0000000..27166ec
Binary files /dev/null and b/docs/media/circulation_patron_records-30.png differ
diff --git a/docs/media/circulation_patron_records-31.png b/docs/media/circulation_patron_records-31.png
new file mode 100644
index 0000000..067ed74
Binary files /dev/null and b/docs/media/circulation_patron_records-31.png differ
diff --git a/docs/media/circulation_patron_records-4.png b/docs/media/circulation_patron_records-4.png
new file mode 100644
index 0000000..da9a7f1
Binary files /dev/null and b/docs/media/circulation_patron_records-4.png differ
diff --git a/docs/media/circulation_patron_records-5.png b/docs/media/circulation_patron_records-5.png
new file mode 100644
index 0000000..5bc5973
Binary files /dev/null and b/docs/media/circulation_patron_records-5.png differ
diff --git a/docs/media/circulation_patron_records-6.png b/docs/media/circulation_patron_records-6.png
new file mode 100644
index 0000000..59415fd
Binary files /dev/null and b/docs/media/circulation_patron_records-6.png differ
diff --git a/docs/media/circulation_patron_records-7.png b/docs/media/circulation_patron_records-7.png
new file mode 100644
index 0000000..7dbafa3
Binary files /dev/null and b/docs/media/circulation_patron_records-7.png differ
diff --git a/docs/media/circulation_patron_records-8.png b/docs/media/circulation_patron_records-8.png
new file mode 100644
index 0000000..dfae3ae
Binary files /dev/null and b/docs/media/circulation_patron_records-8.png differ
diff --git a/docs/media/circulation_patron_records-9.png b/docs/media/circulation_patron_records-9.png
new file mode 100644
index 0000000..1de4cca
Binary files /dev/null and b/docs/media/circulation_patron_records-9.png differ
diff --git a/docs/root.txt b/docs/root.txt
index aa41183..2f53866 100644
--- a/docs/root.txt
+++ b/docs/root.txt
@@ -255,6 +255,8 @@ include::circulation/circulating_items.txt[]
include::circulation/booking.txt[]
+include::circulation/circulation_patron_records.txt[]
+
Reports
=======
@@ -296,11 +298,12 @@ include::attributions.txt[]
include::licensing.txt[]
+[appendix]
Admonitions
===========
Images used for Admonitions
----------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Note
@@ -318,4 +321,7 @@ image::media/caution.png[]
image::media/tip.png[]
+[index]
+Index
+=====
commit 260eb05e7b394a22906af7b7e83124f28a60da96
Author: Robert Soulliere <robert.soulliere at mohawkcollege.ca>
Date: Thu Jul 12 15:46:29 2012 -0400
Set unix file format to remove trailing "\r"s in file.
Signed-off-by: Robert Soulliere <robert.soulliere at mohawkcollege.ca>
diff --git a/docs/serials/Group_Serials_Issues_in_the_OPAC_2.2.txt b/docs/serials/Group_Serials_Issues_in_the_OPAC_2.2.txt
index ec18cd3..958afb2 100644
--- a/docs/serials/Group_Serials_Issues_in_the_OPAC_2.2.txt
+++ b/docs/serials/Group_Serials_Issues_in_the_OPAC_2.2.txt
@@ -1,51 +1,51 @@
-Group Serials Issues in the Template Toolkit OPAC
--------------------------------------------------
-
-In previous versions of Evergreen, issues of serials displayed in a list ordered by publication date. The list could be lengthy if the library had extensive holdings of a serial.
-Using the Template Toolkit OPAC that is available in version 2.2, you can group issues of serials in the OPAC by chronology or enumeration. For example, you might group issues by date published or by volume. Users can expand these hyperlinked groups to view holdings of specific issues. The result is a clean, easy-to-naviagte interface for viewing holdings of serials with a large quantity of issues.
-
-NOTE: This feature is only available in the Template Toolkit OPAC.
-
-Administration
-~~~~~~~~~~~~~~
-
-Enable the following organizational unit settings to use this feature:
-
-. Click *Admin* -> *Local Administration* -> *Library Settings Editor*.
-. Search or scroll to find *Serials: Default display grouping for serials distributions presented in the OPAC*.
-. Click *Edit*.
-. Enter *enum* to display issues by enumeration, or enter *chron* to display issues in chronological order. This value will become your default setting for display issues in the OPAC.
-. Click *Update Setting*.
-. Search or scroll to find *OPAC: Use fully compressed serials holdings*.
-. Select the value, *True*, to view a compressed holdings statement.
-. Click *Update Setting*.
-
-Displaying Issues in the OPAC
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Your library system has a subscription to the periodical, _Bon Appetit_. The serials librarian has determined that the issues at the Forest Falls branch should display in the OPAC by month and year. The issues at the McKinley branch should display by volume and number. The serials librarian will create two distributions for the serial that will include these groupings.
-
-. Retrieve the bibliographic record for the serial, and click *Actions for this Record* -> *Alternate Serial Control*.
-. Create a *New Subscription* or click on the hyperlinked ID of an existing subscription.
-. Click *New Distribution*.
-. Create a label to identify the distribution.
-. Select the holding library from the drop down menu that will own physical copies of the issues.
-. Select a display grouping. Select *chronology* from the drop down menu.
-. Select a template from the drop down menu to receive copies.
-. Click *Save*.
-+
-image::media/Group_Serials_Issues_in_the_OPAC2.jpg[Group_Serials_Issues_in_the_OPAC2]
-+
-. Click *New Distribution* and repeat the process to send issues to the McKinley Branch. Choose *enumeration* in the *Display Grouping* field to display issues by volume and number.
-. Complete the creation of your subscription.
-. Retrieve the record from the catalog.
-. Scroll down to and click the *Issues Held* link. The issues label for each branch appears.
-. Click the hyperlinked issues label.
-
-The issues owned by the Forest Falls branch are grouped by chronology:
-
-image::media/Group_Serials_Issues_in_the_OPAC5.jpg[Group_Serials_Issues_in_the_OPAC5]
-
-The issues owned by the McKinley branch are grouped by enumeration:
-
-image::media/Group_Serials_Issues_in_the_OPAC7.jpg[Group_Serials_Issues_in_the_OPAC7]
+Group Serials Issues in the Template Toolkit OPAC
+-------------------------------------------------
+
+In previous versions of Evergreen, issues of serials displayed in a list ordered by publication date. The list could be lengthy if the library had extensive holdings of a serial.
+Using the Template Toolkit OPAC that is available in version 2.2, you can group issues of serials in the OPAC by chronology or enumeration. For example, you might group issues by date published or by volume. Users can expand these hyperlinked groups to view holdings of specific issues. The result is a clean, easy-to-naviagte interface for viewing holdings of serials with a large quantity of issues.
+
+NOTE: This feature is only available in the Template Toolkit OPAC.
+
+Administration
+~~~~~~~~~~~~~~
+
+Enable the following organizational unit settings to use this feature:
+
+. Click *Admin* -> *Local Administration* -> *Library Settings Editor*.
+. Search or scroll to find *Serials: Default display grouping for serials distributions presented in the OPAC*.
+. Click *Edit*.
+. Enter *enum* to display issues by enumeration, or enter *chron* to display issues in chronological order. This value will become your default setting for display issues in the OPAC.
+. Click *Update Setting*.
+. Search or scroll to find *OPAC: Use fully compressed serials holdings*.
+. Select the value, *True*, to view a compressed holdings statement.
+. Click *Update Setting*.
+
+Displaying Issues in the OPAC
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Your library system has a subscription to the periodical, _Bon Appetit_. The serials librarian has determined that the issues at the Forest Falls branch should display in the OPAC by month and year. The issues at the McKinley branch should display by volume and number. The serials librarian will create two distributions for the serial that will include these groupings.
+
+. Retrieve the bibliographic record for the serial, and click *Actions for this Record* -> *Alternate Serial Control*.
+. Create a *New Subscription* or click on the hyperlinked ID of an existing subscription.
+. Click *New Distribution*.
+. Create a label to identify the distribution.
+. Select the holding library from the drop down menu that will own physical copies of the issues.
+. Select a display grouping. Select *chronology* from the drop down menu.
+. Select a template from the drop down menu to receive copies.
+. Click *Save*.
++
+image::media/Group_Serials_Issues_in_the_OPAC2.jpg[Group_Serials_Issues_in_the_OPAC2]
++
+. Click *New Distribution* and repeat the process to send issues to the McKinley Branch. Choose *enumeration* in the *Display Grouping* field to display issues by volume and number.
+. Complete the creation of your subscription.
+. Retrieve the record from the catalog.
+. Scroll down to and click the *Issues Held* link. The issues label for each branch appears.
+. Click the hyperlinked issues label.
+
+The issues owned by the Forest Falls branch are grouped by chronology:
+
+image::media/Group_Serials_Issues_in_the_OPAC5.jpg[Group_Serials_Issues_in_the_OPAC5]
+
+The issues owned by the McKinley branch are grouped by enumeration:
+
+image::media/Group_Serials_Issues_in_the_OPAC7.jpg[Group_Serials_Issues_in_the_OPAC7]
commit 0438e4eeafbdb773409252ac464c2295ecb7062f
Author: Sally Fortin <sfortin at esilibrary.com>
Date: Thu Jul 12 15:36:03 2012 -0400
Add Group Serials Issues Chapter from Sally Fortin at Equinox Software. Source: http://www.esilibrary.com/esi/availableDocs.php.
Tested in documentation processing.
Signed-off-by: Robert Soulliere <robert.soulliere at mohawkcollege.ca>
diff --git a/docs/media/Group_Serials_Issues_in_the_OPAC2.jpg b/docs/media/Group_Serials_Issues_in_the_OPAC2.jpg
new file mode 100644
index 0000000..4c775be
Binary files /dev/null and b/docs/media/Group_Serials_Issues_in_the_OPAC2.jpg differ
diff --git a/docs/media/Group_Serials_Issues_in_the_OPAC5.jpg b/docs/media/Group_Serials_Issues_in_the_OPAC5.jpg
new file mode 100644
index 0000000..f1dd239
Binary files /dev/null and b/docs/media/Group_Serials_Issues_in_the_OPAC5.jpg differ
diff --git a/docs/media/Group_Serials_Issues_in_the_OPAC7.jpg b/docs/media/Group_Serials_Issues_in_the_OPAC7.jpg
new file mode 100644
index 0000000..574aaf0
Binary files /dev/null and b/docs/media/Group_Serials_Issues_in_the_OPAC7.jpg differ
diff --git a/docs/root.txt b/docs/root.txt
index a60641b..aa41183 100644
--- a/docs/root.txt
+++ b/docs/root.txt
@@ -240,6 +240,7 @@ include::serials/G-Special_issue.txt[]
include::serials/H-holdings_statements.txt[]
+include::serials/Group_Serials_Issues_in_the_OPAC_2.2.txt[]
Circulation
===========
diff --git a/docs/serials/Group_Serials_Issues_in_the_OPAC_2.2.txt b/docs/serials/Group_Serials_Issues_in_the_OPAC_2.2.txt
new file mode 100644
index 0000000..ec18cd3
--- /dev/null
+++ b/docs/serials/Group_Serials_Issues_in_the_OPAC_2.2.txt
@@ -0,0 +1,51 @@
+Group Serials Issues in the Template Toolkit OPAC
+-------------------------------------------------
+
+In previous versions of Evergreen, issues of serials displayed in a list ordered by publication date. The list could be lengthy if the library had extensive holdings of a serial.
+Using the Template Toolkit OPAC that is available in version 2.2, you can group issues of serials in the OPAC by chronology or enumeration. For example, you might group issues by date published or by volume. Users can expand these hyperlinked groups to view holdings of specific issues. The result is a clean, easy-to-naviagte interface for viewing holdings of serials with a large quantity of issues.
+
+NOTE: This feature is only available in the Template Toolkit OPAC.
+
+Administration
+~~~~~~~~~~~~~~
+
+Enable the following organizational unit settings to use this feature:
+
+. Click *Admin* -> *Local Administration* -> *Library Settings Editor*.
+. Search or scroll to find *Serials: Default display grouping for serials distributions presented in the OPAC*.
+. Click *Edit*.
+. Enter *enum* to display issues by enumeration, or enter *chron* to display issues in chronological order. This value will become your default setting for display issues in the OPAC.
+. Click *Update Setting*.
+. Search or scroll to find *OPAC: Use fully compressed serials holdings*.
+. Select the value, *True*, to view a compressed holdings statement.
+. Click *Update Setting*.
+
+Displaying Issues in the OPAC
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Your library system has a subscription to the periodical, _Bon Appetit_. The serials librarian has determined that the issues at the Forest Falls branch should display in the OPAC by month and year. The issues at the McKinley branch should display by volume and number. The serials librarian will create two distributions for the serial that will include these groupings.
+
+. Retrieve the bibliographic record for the serial, and click *Actions for this Record* -> *Alternate Serial Control*.
+. Create a *New Subscription* or click on the hyperlinked ID of an existing subscription.
+. Click *New Distribution*.
+. Create a label to identify the distribution.
+. Select the holding library from the drop down menu that will own physical copies of the issues.
+. Select a display grouping. Select *chronology* from the drop down menu.
+. Select a template from the drop down menu to receive copies.
+. Click *Save*.
++
+image::media/Group_Serials_Issues_in_the_OPAC2.jpg[Group_Serials_Issues_in_the_OPAC2]
++
+. Click *New Distribution* and repeat the process to send issues to the McKinley Branch. Choose *enumeration* in the *Display Grouping* field to display issues by volume and number.
+. Complete the creation of your subscription.
+. Retrieve the record from the catalog.
+. Scroll down to and click the *Issues Held* link. The issues label for each branch appears.
+. Click the hyperlinked issues label.
+
+The issues owned by the Forest Falls branch are grouped by chronology:
+
+image::media/Group_Serials_Issues_in_the_OPAC5.jpg[Group_Serials_Issues_in_the_OPAC5]
+
+The issues owned by the McKinley branch are grouped by enumeration:
+
+image::media/Group_Serials_Issues_in_the_OPAC7.jpg[Group_Serials_Issues_in_the_OPAC7]
commit 2a78333727a8b0ee4514948308fe02e9d238bfab
Author: Robert Soulliere <robert.soulliere at mohawkcollege.ca>
Date: Tue Jun 19 12:23:55 2012 -0400
Update Evergreen upgrade instructions to reflect the 2.2.0 release.
Update download reference to point to 2.2.0. Also moved
database updates to the end of the process. It seemed out of order since
the database update scripts were run before the download of the 2.2 tar file.
Signed-off-by: Robert Soulliere <robert.soulliere at mohawkcollege.ca>
diff --git a/docs/installation/server_upgrade.txt b/docs/installation/server_upgrade.txt
index f8c25ff..907b95d 100644
--- a/docs/installation/server_upgrade.txt
+++ b/docs/installation/server_upgrade.txt
@@ -24,35 +24,6 @@ To switch from the root user to a different user, issue the `su - [user]`
command; for example, `su - opensrf`. Once you have become a non-root user, to
become the root user again simply issue the `exit` command.
-[CAUTION]
-Pay attention to error output as you run these scripts. If you encounter errors
-that you cannot resolve yourself through additional troubleshooting, please
-report the errors to the http://evergreen-ils.org/listserv.php[Evergreen
-Technical Discussion List].
-
-Upgrade the Evergreen database schema
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The upgrade of the Evergreen database schema is the lengthiest part of the
-upgrade process for sites with a significant amount of production data.
-
-Before running the upgrade script against your production Evergreen database,
-back up your database, restore it to a test server, and run the upgrade script
-against the test server. This enables you to determine how long the upgrade
-will take and whether any local customizations present problems for the
-stock upgrade script that require further tailoring of the upgrade script.
-The backup also enables you to cleanly restore your production data if
-anything goes wrong during the upgrade.
-
-Run the following script as a user with the ability to connect to the
-database server. Adjust the arguments to the `psql` command to reflect your
-database server connection information:
-
-[source, bash]
-----------------------------------------------------------
-cd /home/opensrf/Evergreen-ILS-2.1-rc1/Open-ILS/src/sql/Pg
-psql -U evergreen -h localhost -f version_upgrade/2.1-2.2-upgrade-db.sql evergreen
-----------------------------------------------------------
-
Upgrade the Evergreen code
~~~~~~~~~~~~~~~~~~~~~~~~~~
The following steps guide you through a simplistic upgrade of a production
@@ -75,8 +46,8 @@ the http://evergreen-ils.org/opensrf.php[OpenSRF download page].
+
[source, bash]
-----------------------------------------------
-wget http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.2-rc1.tar.gz
-tar xzf Evergreen-ILS-2.2-rc1.tar.gz
+wget http://evergreen-ils.org/downloads/Evergreen-ILS-2.2.0.tar.gz
+tar xzf Evergreen-ILS-2.2.0.tar.gz
-----------------------------------------------
+
[NOTE]
@@ -86,7 +57,7 @@ For the latest edition of Evergreen, check the http://evergreen-ils.org/download
+
[source, bash]
----------------------------------------------
-cd /home/opensrf/Evergreen-ILS-2.2-rc1
+cd /home/opensrf/Evergreen-ILS-2.2.0
---------------------------------------------
+
On the next command, replace `[distribution]` with one of these values for your
@@ -105,7 +76,7 @@ make -f Open-ILS/src/extras/Makefile.install [distribution]
+
[source, bash]
------------------------------------------------------------
-cd /home/opensrf/Evergreen-ILS-2.2-rc1
+cd /home/opensrf/Evergreen-ILS-2.2.0
./configure --prefix=/openils --sysconfdir=/openils/conf
make
------------------------------------------------------------
@@ -114,8 +85,8 @@ make
+
[source, bash]
------------------------------------------------------------
-cd /home/opensrf/Evergreen-ILS-2.2-rc1
-make STAFF_CLIENT_STAMP_ID=rel_2_2_rc1 install
+cd /home/opensrf/Evergreen-ILS-2.2.0
+make STAFF_CLIENT_STAMP_ID=rel_2_2_0 install
------------------------------------------------------------
+
. As the root user, change all files to be owned by the opensrf user and group:
@@ -129,7 +100,7 @@ chown -R opensrf:opensrf /openils
+
[source, bash]
-----------------------------------------------------------
-cd /home/opensrf/Evergreen-ILS-2.2-rc1
+cd /home/opensrf/Evergreen-ILS-2.2.0
perl Open-ILS/src/support-scripts/eg_db_config.pl \
--create-offline --user evergreen --password evergreen \
@@ -142,7 +113,7 @@ perl Open-ILS/src/support-scripts/eg_db_config.pl \
-----------------------------------------------------------
cd /openils/var/web/xul/
rm server
-ln -s rel_2_2_rc1/server
+ln -s rel_2_2_0/server
----------------------------------------------------------
+
. As the opensrf user, update opensrf_core.xml and opensrf.xml by copying the
@@ -175,13 +146,43 @@ opensrf.xml.example, then:
[source, bash]
-------------------------------------------------------------------------
cp -b /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml
-cd /home/opensrf/Evergreen-ILS-2.2-rc1
+cd /home/opensrf/Evergreen-ILS-2.2.0
perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config --service all \
--database evergreen --host localhost --user evergreen --password evergreen
-------------------------------------------------------------------------
+
Otherwise, compare /openils/conf/opensrf.xml with /openils/conf/opensrf.xml.example and manually copy the new pieces into place in your existing opensrf.xml file
+
+Upgrade the Evergreen database schema
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+The upgrade of the Evergreen database schema is the lengthiest part of the
+upgrade process for sites with a significant amount of production data.
+
+Before running the upgrade script against your production Evergreen database,
+back up your database, restore it to a test server, and run the upgrade script
+against the test server. This enables you to determine how long the upgrade
+will take and whether any local customizations present problems for the
+stock upgrade script that require further tailoring of the upgrade script.
+The backup also enables you to cleanly restore your production data if
+anything goes wrong during the upgrade.
+
+[CAUTION]
+Pay attention to error output as you run the upgrade scripts. If you encounter errors
+that you cannot resolve yourself through additional troubleshooting, please
+report the errors to the http://evergreen-ils.org/listserv.php[Evergreen
+Technical Discussion List].
+
+Run the following script as a user with the ability to connect to the
+database server. Adjust the arguments to the `psql` command to reflect your
+database server connection information:
+
+[source, bash]
+----------------------------------------------------------
+cd /home/opensrf/Evergreen-ILS-2.2.0/Open-ILS/src/sql/Pg
+psql -U evergreen -h localhost -f version_upgrade/2.1-2.2-upgrade-db.sql evergreen
+----------------------------------------------------------
+
Restart Evergreen and Test
~~~~~~~~~~~~~~~~~~~~~~~~~~
. As the opensrf user, start all Evergreen and OpenSRF services:
commit 652f22ae282c9a99c8d40763884fb3bd686bb518
Author: Robert Soulliere <robert.soulliere at mohawkcollege.ca>
Date: Thu Jun 14 14:35:24 2012 -0400
Remove antiquated 1.6 directory from docs folder.
This was used for early DocBook testing and is no longer needed.
Signed-off-by: Robert Soulliere <robert.soulliere at mohawkcollege.ca>
Signed-off-by: Dan Scott <dan at coffeecode.net>
diff --git a/docs/1.6/book1/sysadmin/indexedfieldweighting.xml b/docs/1.6/book1/sysadmin/indexedfieldweighting.xml
deleted file mode 100644
index 565a502..0000000
--- a/docs/1.6/book1/sysadmin/indexedfieldweighting.xml
+++ /dev/null
@@ -1,233 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<section xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="indexedfieldweighting">
- <title>Indexed-Field and Matchpoint Weighting</title>
- <info>
- <abstract>
- <para>This chapter describes indexed field weighting and matchpoint weighting, which
- control relevance ranking in Evergreen catalog search results.</para>
- <para>
- <tip>
- <para>In tuning search relevance, it is good practice to make incremental
- adjustments, capture search logs, and assess results before making further
- adjustments. </para>
- </tip>
- </para>
- </abstract>
- </info>
- <section>
- <title>Indexed-field Weighting</title>
- <para>Indexed-field weighting is configured in the Evergreen database in the weight column
- of the config.metabib_field table, which follows the other four columns in this table:
- field_class, name, xpath, and format. </para>
- <para>The following is one representative line from the config.metabib_field table:</para>
- <para> author | conference |
- //mods32:mods/mods32:name[@type='conference']/mods32:namePart[../mods32:role/mods32:roleTerm[text()='creator']]
- | mods32 | 1 ) </para>
- <para>The default value for index-field weights in config.metabib_field is 1. Adjust the
- weighting of indexed fields to boost or lower the relevance score for matches on that
- indexed field. The weight value may be increased or decreased by whole integers. </para>
- <para>For example, by increasing the weight of the title-proper field from 1 to 2, a search
- for <emphasis role="bold">jaguar</emphasis> would double the relevance for the book
- titled <emphasis role="italic">Aimee and Jaguar</emphasis> than for a record with the
- term <emphasis role="bold">jaguar</emphasis> in another indexed field. </para>
- </section>
- <section>
- <title>Matchpoint Weighting</title>
- <para> Matchpoint weighting provides another way to fine-tune Evergreen relevance ranking,
- and is configured through floating-point multipliers in the multiplier column of the
- search.relevance_adjustment table.</para>
- <para> Weighting can be adjusted for one, more, or all multiplier fields in
- search.relevance_adjustment. </para>
- <para>You can adjust the following three matchpoints:</para>
- <itemizedlist>
- <listitem>
- <para><indexterm>
- <primary>first_word</primary>
- </indexterm> boosts relevance if the query is one term long and matches the
- first term in the indexed field (search for <emphasis role="bold"
- >twain</emphasis>, get a bonus for <emphasis role="bold">twain,
- mark</emphasis> but not <emphasis role="bold">mark twain</emphasis>)</para>
- </listitem>
- <listitem>
- <para><indexterm>
- <primary>word_order</primary>
- </indexterm> increases relevance for words matching the order of search terms,
- so that the results for the search <emphasis role="bold">legend
- suicide</emphasis> would match higher for the book <emphasis role="italic"
- >Legend of a Suicide</emphasis> than for the book, <emphasis role="italic"
- >Suicide Legend</emphasis></para>
- </listitem>
- <listitem>
- <para><indexterm>
- <primary>full_match</primary>
- </indexterm> boosts relevance when the full query exactly matches the entire
- indexed field (after space, case, and diacritics are normalized). So a title
- search for <emphasis role="italic">The Future of Ice</emphasis> would get a
- relevance boost above <emphasis role="italic">Ice Ages of the
- Future</emphasis>.</para>
- </listitem>
- </itemizedlist>
- <para> Here are the default settings of the search.relevance_adjustment table: </para>
- <table xml:id="search.relevance">
- <title>search.relevance_adjustment table</title>
- <tgroup cols="4">
- <thead>
- <row>
- <entry>field_class</entry>
- <entry>name</entry>
- <entry>bump_type</entry>
- <entry>multiplier</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>author</entry>
- <entry>conference</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>author</entry>
- <entry>corporate</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>author </entry>
- <entry>other </entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>author</entry>
- <entry>personal</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>keyword</entry>
- <entry>keyword</entry>
- <entry>word_order</entry>
- <entry>10</entry>
- </row>
- <row>
- <entry>series</entry>
- <entry>seriestitle</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>series</entry>
- <entry>seriestitle</entry>
- <entry>full_match</entry>
- <entry>20</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>abbreviated</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>abbreviated</entry>
- <entry>full_match</entry>
- <entry>20</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>abbreviated</entry>
- <entry>word_order</entry>
- <entry>10</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>alternative</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>alternative</entry>
- <entry>full_match</entry>
- <entry>20</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>alternative</entry>
- <entry>word_order</entry>
- <entry>10</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>proper</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>proper</entry>
- <entry>full_match</entry>
- <entry>20</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>proper</entry>
- <entry>word_order</entry>
- <entry>10</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>translated</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>translated</entry>
- <entry>full_match</entry>
- <entry>20</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>translated</entry>
- <entry>word_order</entry>
- <entry>10</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>uniform</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>uniform</entry>
- <entry>full_match</entry>
- <entry>20</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>uniform</entry>
- <entry>word_order</entry>
- <entry>10</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </section>
- <section>
- <title>Combining Index Weighting and Matchpoint Weighting</title>
- <para>Index weighting and matchpoint weighting may be combined. The relevance boost of the
- combined weighting is equal to the product of the two multiplied values. </para>
- <para>If the relevance setting in the config.metabib_field were increased to 2, and the
- multiplier set to 1.2 in the search.relevance_adjustment table, the resulting matchpoint
- increase would be 240%. </para>
- <note>
- <para>In practice, these weights are applied serially -- first the index weight, then
- all the matchpoint weights that apply -- because they are evaluated at different
- stages of the search process.</para>
- </note>
- </section>
-</section>
diff --git a/docs/1.6/styleguide/admon.xml b/docs/1.6/styleguide/admon.xml
deleted file mode 100644
index 53a1a30a..0000000
--- a/docs/1.6/styleguide/admon.xml
+++ /dev/null
@@ -1,104 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="admonitions">
- <title>Admonitions</title>
- <section>
- <title>Overview</title>
- <para>Admonitions are pieces of text that are offset from the main flow of text. They include
- things like warnings, notes, and tips. They should be used sparingly because they interrupt
- the flow of the text. However, if you think one is needed, use one.</para>
- <para>As a general rule, warnings and notes are the <emphasis role="bold">preferred</emphasis>
- admonitions in Evergreen' documentation. That does not mean the use of the other types are
- prohibited. It only means that they should be used with caution.</para>
- </section>
- <section xml:id="warn">
- <title>Warnings</title>
- <simplesect>
- <title>Overview</title>
- <para>Warnings are used to call out instances where a serious loss of data could occur. The
- text of the warning should make it clear what will cause the data loss and what data is at
- risk. For example, if using a value greater than 1 million will cause a method invocation to
- return garbage, use a warning to mention this.</para>
- </simplesect>
- <simplesect>
- <title>Markup</title>
- <para>Warnings are marked up using a <tag class="element">warning</tag> element. The <tag
- class="element">warning</tag> element should contain a single <tag class="element"
- >para</tag> element that contains the text for the warning.</para>
- <para>The <tag class="element">warning</tag> element can, however, contain more than one
- paragraph, a code listing, or a table. These are exceptions that are to be used
- sparingly.</para>
- </simplesect>
- </section>
- <section xml:id="note">
- <title>Notes</title>
- <simplesect>
- <title>Overview</title>
- <para>Notes are used to call out information that the reader should be aware of, but is
- ancillary to the topic being discussed in the main flow of the text.</para>
- </simplesect>
- <simplesect>
- <title>Markup</title>
- <para>Notes are marked up using a <tag class="element">note</tag> element. Like the <tag
- class="element">warning</tag> element, the <tag class="element">note</tag> element should
- contain a single <tag class="element">para</tag> element that contains the text for the
- warning. The <tag class="element">note</tag> element can also contain more than one
- paragraph, a code listing, or a table.</para>
- </simplesect>
- </section>
- <section xml:id="caution">
- <title>Cautions</title>
- <simplesect>
- <title>Overview</title>
- <para>Cautions are intended for use when a <link linkend="warn">warning</link> is too strong.
- For example, a caution may be used when an action will potentially cause a service to return
- an exception, but not crash or result in any loss of critical data. In general, it is best
- to use a <link linkend="warn">warning</link>.</para>
- </simplesect>
- <simplesect>
- <title>Markup</title>
- <para>Cautions are marked up using the <tag class="element">caution</tag> element. As with
- warnings elements, the <tag class="element">caution</tag> element should contain only a
- single <tag class="element">para</tag> element.</para>
- </simplesect>
- </section>
- <section xml:id="important">
- <title>Important Notes</title>
- <simplesect>
- <title>Overview</title>
- <para>Important notes are used to point out information that is important for the user to
- know, but that may not be obvious. For example, if you change a value in a context and the
- new value overrides a transport setting for the service. Or if the new value persists for
- all future uses of the context.</para>
- </simplesect>
- <simplesect>
- <title>Markup</title>
- <para>Important notes are marked up using the <tag class="element">important</tag> element.
- The <tag class="element">important</tag> element should contain only a single <tag
- class="element">para</tag> element. However, it is allowable to use other block elements
- in an important note.</para>
- </simplesect>
- </section>
- <section xml:id="tip">
- <title>Tips</title>
- <simplesect>
- <title>Overview</title>
- <para>Tips are bits of information that may help a user be more productive, but that are not
- critical to using the product. In general, this type of information should either be worked
- directly into the text or placed in a <link linkend="note">note</link>.</para>
- </simplesect>
- <simplesect>
- <title>Markup</title>
- <para>Tips are marked up using the <tag class="element">tip</tag> element. The <tag
- class="element">tip</tag> element should contain only a single <tag class="element"
- >para</tag> element. However, it is allowable to use other block elements in a tip.</para>
- </simplesect>
- </section>
- <section>
- <title>Footnotes</title>
- <simplesect>
- <title>Overview</title>
- <para>Footnotes are not used in Evergreen documentation. </para>
- </simplesect>
- </section>
-</chapter>
diff --git a/docs/1.6/styleguide/authoring.xml b/docs/1.6/styleguide/authoring.xml
deleted file mode 100644
index 9d45c84..0000000
--- a/docs/1.6/styleguide/authoring.xml
+++ /dev/null
@@ -1,93 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="authoring">
- <title>Authoring Documentation</title>
- <info>
- <abstract>
- <para>DocBook ....</para>
- </abstract>
- </info>
- <section>
- <title>Structure: Concept, Task, Reference</title>
- <para> Every chapter in Evergreen documentation, and in some cases sections, should begin by
- explaining this chapter's concepts, or core ideas, to the reader. This gives you the
- opportunity to clarify new or ambiguous terminology for otherwise experienced readers:
- for example, in a circulation overview you will want to differentiate non-cataloged
- items vs. pre-cataloged items. Explaining concepts also gives less experienced readers a
- chance to fill in gaps in their knowledge. </para>
- <para> For example, in the circulation section of the manual, you may write the following
- set of tasks: </para>
- <itemizedlist>
- <listitem>
- <para>Checking out an item Checking in an item Renewing items Recording in-house
- uses</para>
- </listitem>
- </itemizedlist>
- <para> Separating the concepts from the tasks gives your readers the chance to jump directly
- to the task they want to complete, if they are already familiar with the concepts. </para>
- <para> When you write your task information, try to organize it as a set of numbered steps
- that covers the most common cases. Compose each step in two sentences: first, describe
- the action the reader must complete, followed by a sentence describing the results of
- successfully performing the action if applicable. Preface optional steps with
- (Optional):. For example: </para>
- <para> To check out a cataloged item to a patron: </para>
- <orderedlist>
- <listitem>
- <para>In the staff client, select Circulation→Check Out Items. The Check Out tab
- appears.</para>
- </listitem>
- <listitem>
- <para>Enter the patron barcode in the Barcode text field. The system retrieves and
- displays the patron information, with the Check Out button highlighted in the
- action bar.</para>
- </listitem>
- <listitem>
- <para>Enter the item barcode in the text field beside the Barcode: selection in the
- drop-down menu.</para>
- </listitem>
- </orderedlist>
- <!-- the following was copied from the wiki and has not been marked up yet. It is wrapped
- with para elements so that it will not trigger the XML validator -->
-
- <para>(Optional): Select a different due date from the date selector. 4. Click Submit to
- check out the item to the patron. The item barcode, due date, and title appear in the
- transaction summary table. 5. Repeat steps 3 and 4 for each additional item the patron
- wants to borrow. 6. (Optional): Click Print Receipt to print a receipt summarizing the
- transactions for the patron. The Print Receipt window opens. Reference Reference
- information consists of lists of commands, configuration files and settings, software
- prerequisites, APIs, etc that need to be rigorously documented to support use cases
- outside the core task documentation. Reference information is typically organized by
- type, then by alphabetical order. For example, all system commands will be documented in
- their own section of the manual in alphabetical order, and all APIs will be documented
- in their own section of the manual in alphabetical order. System commmands: * autogen.sh
- * import_holdings.pl * marc2bre.pl * osrf_ctl.sh * … APIs: *
- open-ils.auth.authenticate.complete * open-ils.auth.authenticate.init * … Discuss how
- each system feature would be used by each scenario institution If applicable, provide an
- example of how each institutional scenario (Le Grande University vs. Metropolitan Public
- Library Consortium) would likely put the feature being discussed into use. You will
- probably want to include this information in the concept topic(s) introducing the
- feature, or as a separate concept topic or set of topics following the introductory
- concept topic. The scenarios give you a few different facets to describe when explaining
- the topic to your reader: * academic vs. public libraries * consortiums vs. standalone
- libraries * libraries with large collections vs. libraries with small collections Style
- guidelines Use the active voice Avoid the passive voice. For example: Rather than: The
- barcode is checked for a valid check digit when it is scanned. Use the active voice:
- When you scan the barcode, the system checks for a valid check digit. If your sentence
- contains “is”, be careful: it might be using the passive voice. Write concise sentences
- Try to keep your sentences brief. Avoiding complex phrases with related clauses helps
- readers concentrate on a single idea at a time. It also helps translators. Prefix
- conditional clauses If your sentence is conditional, place the conditional clause at the
- beginning of the sentence. When your reader skims your text and only sees the first part
- of the sentence, they might take the wrong action. For example: Rather than: Click the
- **Cancel** button to prevent the changes from being applied if the results did not match
- your expectations. Use: If the results did not match your expectations, click the
- **Cancel** button to prevent the changes from being applied. Contractions,
- abbreviations, and acronyms Do not use contractions (“you're”, “we've”, “it's”) or Latin
- abbreviations (e.g., etc., i.e.). These can be hard to translate and hard to read. If
- you use an acronym, provide the full form of the acronym and include the acronym in
- parentheses in the first use in your topic. After the acronym has been introduced, you
- can use the acronym on its own for the remainder of the topic. Highlighting Use bold to
- highlight the names of GUI elements such as field and button labels, window names, and
- menu options. </para>
- </section>
-</chapter>
diff --git a/docs/1.6/styleguide/books.xml b/docs/1.6/styleguide/books.xml
deleted file mode 100644
index 2d69f24..0000000
--- a/docs/1.6/styleguide/books.xml
+++ /dev/null
@@ -1,256 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="books" status="draft">
- <title>Creating a Book</title>
- <info>
- <abstract>
- <para>Books are the top level of organization for topics in a library. They are a collection
- of sub-topics organized into chapters. This chapter describes how to create books in XML. </para>
- <para>
- <note>
- <para>In most cases Evergreen documentation authors will not create books, but will be
- authoring chapters or sections within books, as described in the chapter on document
- structure. </para>
- </note>
- </para>
- </abstract>
- </info>
- <section>
- <title>Common Elements</title>
- <simplesect>
- <title>Overview</title>
- <para>XML based books share a number of common elements. These include:</para>
- <itemizedlist>
- <listitem>
- <para>A <tag class="element">XML version and encoding</tag> element</para>
- </listitem>
- <listitem>
- <para>A <tag class="element">root</tag> element</para>
- </listitem>
- <listitem>
- <para>A <tag class="element">title</tag> element</para>
- </listitem>
- <listitem>
- <para>An <tag class="element">info</tag> element describing the book's front matter</para>
- </listitem>
- </itemizedlist>
- </simplesect>
- <simplesect>
- <title>Root element</title>
- <para>The root element of an XML book is the <tag class="element">book</tag> element. The <tag
- class="element">book</tag> element provides a wrapper for parts, chapters, appendices,
- indexes, and glossaries.</para>
- <para>The <tag class="element">book</tag> element needs to include the XML namespace
- declarations shown in <xref linkend="BookRootXMLNS"/>:</para>
- <example xml:id="BookRootXMLNS">
- <title>XML Namespace Declarations</title>
- <programlisting><book <emphasis role="bold">xmlns="http://docbook.org/ns/docbook"
-xmlns:xi="http://www.w3.org/2001/XInclude"
-xmlns:xl="http://www.w3.org/1999/xlink"</emphasis>
-... ></programlisting>
- </example>
- <para>The <tag class="element">book</tag> element's <tag class="attribute">version</tag>
- attribute must be set to <tag class="attvalue">5.0</tag>.</para>
- <para>You must also specify a value for the <tag class="element">book</tag> element's <tag
- class="attribute">xml:id</tag> attribute. </para>
- <para>You can also use the <tag class="element">book</tag> element's <tag class="attribute"
- >status</tag> attribute to embed a draft stamp in the book. You do this by setting <tag
- class="attribute">status</tag> attribute to <tag class="attvalue">draft</tag>.</para>
- </simplesect>
- <simplesect>
- <title>Title</title>
- <para>The first child of the <tag class="element">book</tag> element is the <tag
- class="element">title</tag> element. The contents of the <tag class="element">title</tag>
- element is the title of the book.</para>
- </simplesect>
- <simplesect>
- <title>Front matter</title>
- <para>The production templates fill in the required graphics and other formatting for the
- front matter of a book. However, the author needs to include the proper legal notices and
- copyright information. All of the legal notices should be imported from the template folder
- in the library. This way you do not have to worry about updating your books when the legal
- notices change.</para>
- <para>The front matter also includes the following information:</para>
- <itemizedlist>
- <listitem>
- <para>The release date</para>
- </listitem>
- <listitem>
- <para>The product name and version</para>
- </listitem>
- <listitem>
- <para>The date the document was updated</para>
- </listitem>
- <listitem>
- <para>The common keywords for the book</para>
- </listitem>
- <listitem>
- <para>The graphics for the front page</para>
- </listitem>
- </itemizedlist>
- <para>All of the information in the front matter is boiler plate and should not be
- updated.</para>
- <para><xref linkend="legal"/> shows a book file with the front matter imported.</para>
- <example xml:id="legal" pgwide="1">
- <?dbfo pgwide="1"?>
- <title>Front Matter Imported</title>
- <programlisting><?xml version="1.0" encoding="UTF-8"?>
-<book xmlns="http://docbook.org/ns/docbook"
-xmlns:xi="http://www.w3.org/2001/XInclude"
-xmlns:xl="http://www.w3.org/1999/xlink"
-version="5.0"
-xml:id="overview">
-<title>What is &prodname;?</title>
-<info>
-<xi:include href="../common/keywords.xml" />
-<mediaobject>
- <imageobject role="html">
- <imagedata depth="100" contentwidth="146" contentdepth="55"
- valign="middle" fileref="./imagesdb/cover_logo.gif"/>
- </imageobject>
-</mediaobject>
-<productname>&prodname;?</productname>
-<releaseinfo>Version &version;?</releaseinfo>
-<date>&reldate?</date>
-<xi:include href="../common/legalblurb.xml" />
-<xi:include href="../common/copynotice.xml" />
-<xi:include href="../common/copydate.xml" />
-<pubdate><?dbtimestamp format="d b Y"?></pubdate>
-<corpauthor>Evergreen Documentation Interest Group</corpauthor>
-</info>
-...
-</book></programlisting>
- </example>
- </simplesect>
- </section>
- <section>
- <title>Preface</title>
- <simplesect>
- <title>Overview</title>
- <para>The preface of your book is placed into the XML file just after the <tag class="element"
- >info</tag> element. It is specified inside of a <tag class="element">preface</tag>
- element. The preface should be created in a separate file and imported, using an <tag
- class="element">xinclude</tag> element, into the book file.</para>
- </simplesect>
- <simplesect>
- <title>Parts of the preface</title>
- <para>The preface of your book will have the following sections that are unique to a
- book:</para>
- <itemizedlist>
- <listitem>
- <para>What is covered in this book?</para>
- </listitem>
- <listitem>
- <para>Who should read this book?</para>
- </listitem>
- <listitem>
- <para>How to use this book?</para>
- </listitem>
- </itemizedlist>
- <para>In addition there are several sections that are common to all of the books in the
- library. These include:</para>
- <itemizedlist>
- <listitem>
- <para>Library</para>
- </listitem>
- <listitem>
- <para>How to get the latest updates</para>
- </listitem>
- <listitem>
- <para>Additional support resources</para>
- </listitem>
- <listitem>
- <para>Documentation conventions</para>
- </listitem>
- </itemizedlist>
- <para>These common sections should be imported, using <tag class="element">xinclude</tag>
- elements, from a common template area. This ensures that any changes are propagated across
- the entire library.</para>
- </simplesect>
- <simplesect>
- <title>Adding content to a preface</title>
- <para>Writing a preface is identical to writing a chapter. This is discussed in <olink
- targetdoc="StyleGuide" targetptr="chapter"/>.</para>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="preface"/> shows a preface that can be imported into a book file.</para>
- <example xml:id="preface" pgwide="1">
- <?dbfo pgwide="1"?>
- <title>Book Preface</title>
- <programlisting><?xml version="1.0" encoding="UTF-8"?>
-<preface xmlns="http://docbook.org/ns/docbook"
-xmlns:xi="http://www.w3.org/2001/XInclude"
-xmlns:xl="http://www.w3.org/1999/xlink"
-version="5.0"
-xml:id="inferno">
-<title>Preface</title>
-<section>
-<title>What is Covered in This Book</title>
-<para>A bunch of technical stuff.</para>
-</section>
-<section>
-<title>Who Should Read This Book</title>
-<para>Engineers interested in learning about the stuff discussed.</para>
-</section>
-<section>
-<title>How to Use This Book</title>
-<para>Very carefully...</para>
-</section>
-<xi:include href="../common/library.xml" />
-<xi:include href="../common/latest.xml" />
-<xi:include href="../common/searching.xml" />
-<xi:include href="../common/resources.xml" />
-<xi:include href="../common/coventions.xml" />
-</preface></programlisting>
- </example>
- </simplesect>
- </section>
- <section>
- <title>Chapters</title>
- <simplesect>
- <title>Overview</title>
- <para>After the preface, you add the chapters to your book. Chapters are created in separate
- files and imported into the book file using <tag class="element">xinclude</tag> elements. </para>
- <para>You do not need to worry about adding a table of contents, list of figures, or list of
- tables. These are all created when the book is published.</para>
- </simplesect>
- <simplesect>
- <title>Writing chapters</title>
- <para>Adding content to a chapter is discussed in the <olink targetdoc="chapters"
- targetptr="chapters"/></para>
- </simplesect>
- <simplesect>
- <title>Importing chapters</title>
- <para>Chapters are imported into a book using <tag class="element">xinclude</tag>
- elements.</para>
- </simplesect>
- </section>
- <section>
- <title>Example Book</title>
- <para><xref linkend="sectLevel"/> shows a book.</para>
- <example xml:id="sectLevel" pgwide="1">
- <?dbfo pgwide="1"?>
- <title>An XML Book</title>
- <programlisting><?xml version="1.0" encoding="UTF-8"?>
-<book xmlns="http://docbook.org/ns/docbook"
-xmlns:xi="http://www.w3.org/2001/XInclude"
-xmlns:xl="http://www.w3.org/1999/xlink"
-version="5.0"
-xml:id="overview">
-<title>Evergreen Guide to Martian Living</title>
-<info>
-<xi:include href="../common/legalblurb.xml" />
-<xi:include href="../common/copynotice.xml" />
-<xi:include href="../common/copydate.xml" />
-</info>
-<xi:include href="preface.xml" />
-<xi:include href="migration.xml" />
-<xi:include href="housekeeping.xml" />
-<xi:include href="recipes.xml" />
-<xi:include href="shopping.xml" />
-<index />
-</book></programlisting>
- </example>
- </section>
-</chapter>
diff --git a/docs/1.6/styleguide/build.xml b/docs/1.6/styleguide/build.xml
deleted file mode 100644
index f21cb32..0000000
--- a/docs/1.6/styleguide/build.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project name="StyleGuide" default="all" basedir=".">
- <property environment="env" />
- <import file="${env.DBCK_HOME}/lib/build_artix_ns_common.xml"/>
-
- <property name="DOCID" value="StyleGuide" />
- <property name="LOGO" value="iona" />
- <property name="ROOT" value="styleguide" />
- <property name="HTMLSITEMAP" value="../site.xml" />
- <property name="PDFSITEMAP" value="../sitepdf.xml" />
-
- <!-- DO NOT MODIFY ANYTHING BELOW THIS LINE -->
- <target name="all" depends="db,html,pdf" description="Builds everything" />
- <target name="content" depends="html,pdf" description="Builds just the content" />
-
- <target name="db" description="Builds the olink databases">
- <antcall target="docbook.db">
- <param name="docbook.in" value="${ROOT}.xml" />
- </antcall>
- </target>
-
- <target name="html" description="Builds the html for the book">
- <antcall target="docbook.html">
- <param name="docbook.in" value="${ROOT}.xml" />
- <param name="docbook.docid" value="${DOCID}" />
- <param name="docbook.logo" value="${LOGO}" />
- </antcall>
- </target>
-
- <target name="pdf" description="Builds the PDF version of the book">
- <antcall target="docbook.pdf">
- <param name="docbook.in" value="${ROOT}.xml" />
- <param name="docbook.docid" value="${DOCID}" />
- <param name="docbook.pdf" value="${ROOT}.pdf" />
- </antcall>
- </target>
-</project>
\ No newline at end of file
diff --git a/docs/1.6/styleguide/chapter.xml b/docs/1.6/styleguide/chapter.xml
deleted file mode 100644
index 754fb87..0000000
--- a/docs/1.6/styleguide/chapter.xml
+++ /dev/null
@@ -1,117 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="chapter">
- <title>Chapters and Other Root Elements</title>
- <section>
- <title>Guidance for Evergreen Authors</title>
- <para>The following information is intended to clarify the elements in the documents you are
- working with. If you use the Evergreen templates, they will at minimum have top-level
- declarations filled out. </para>
- <para>In most cases, you will be working with chapters or sections, as described below. However,
- in some cases you may need to create a document from another root element, such as <tag
- class="element">glossary</tag>.</para>
- </section>
- <section>
- <title>Top-level Declarations</title>
- <para>The first few lines of an XML chapter contains boilerplate markup. These lines include the
- XML encoding statement and an entity declarations for the variables used in the chapter. If
- you use the Evergreen templates, these will be filled out for you.</para>
- </section>
- <section>
- <title>Root Element</title>
- <para>The root element of an XML chapter is the <tag class="element">chapter</tag> element. The
- <tag class="element">chapter</tag> element provides a wrapper for sections and
- blocks.</para>
- <para>The <tag class="element">chapter</tag> element needs to include the XML namespace
- declarations shown in <xref linkend="ChaptRootXMLNS"/>:</para>
- <example xml:id="ChaptRootXMLNS">
- <title>XML Namespace Declarations</title>
- <programlisting><chapter xmlns="http://docbook.org/ns/docbook"
-xmlns:xi="http://www.w3.org/2001/XInclude"
-xmlns:xl="http://www.w3.org/1999/xlink"></programlisting>
- </example>
- <para>The <tag class="element">chapter</tag> element's <tag class="attribute">version</tag>
- attribute must be set to <tag class="attvalue">5.0</tag>.</para>
- </section>
- <section>
- <title>Title</title>
- <para>The first child of the <tag class="element">chapter</tag> element is the <tag
- class="element">title</tag> element. The contents of the <tag class="element">title</tag>
- element is the title of the chapter, such as Evergreen Circulation or Evergreen System
- Administration.</para>
- <para>Titles in Evergreen documentation are determined by the DIG, and follow the format:
- Evergreen [Function]. </para>
- </section>
- <section xml:id="ChaptInfo">
- <title>Chapter Info</title>
- <para>After the <tag class="element">title</tag> element, a chapter should have an <tag
- class="element">info</tag> element. This element contains the chapter summary and a list of
- keywords that will be put into the generated metadata for this chapter.</para>
- <para>The chapter summary is placed inside an <tag class="element">abstract</tag> element. The
- <tag class="element">abstract</tag> element requires a nested <tag class="element"
- >para</tag> element to wrap the text.</para>
- <para>The keyword list is placed inside of a <tag class="element">keywordset</tag> element. Each
- keyword in the list must be wrapped in a <tag class="element">keyword</tag> element. (Do we
- want to use this?)</para>
- </section>
- <section xml:id="ChaptStructElements">
- <title>Structural Elements</title>
- <simplesect>
- <title>Overview</title>
- <para>Chapters are broken into sections and blocks.</para>
- </simplesect>
- <simplesect>
- <title>Sections</title>
- <para>Generally, a chapter should have five or fewer sections. If you need more sections, it
- may be because the topic for your chapter is too broad or you need to reconsider how you are
- chunking the information. Top level sections are denoted using <tag class="element"
- >section</tag> elements.</para>
- <para>Top-level sections can be broken down into five or fewer subsections. Subsections are
- also denoted using <tag class="element">section</tag> elements.</para>
- </simplesect>
- <simplesect>
- <title>Blocks (simplesect)</title>
- <para>Block are the smallest structural unit of organization in a chapter. They divide up the
- information in a section into manageable chunks of information. There should be no more than
- five block-sections in a section.</para>
- <para>Block-sections are denoted using <tag class="element">simplesect</tag> elements. Blocks
- cannot be subdivided.</para>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="chapter_detailExample"/> shows a more detailed view of a chapter.</para>
- <example xml:id="chapter_detailExample" pgwide="1">
- <?dbfo pgwide="1"?>
- <title>Detailed View of a Chapter</title>
- <programlisting><?xml version="1.0" encoding="UTF-8"?>
-<chapter xmlns="http://docbook.org/ns/docbook"
-xmlns:xi="http://www.w3.org/2001/XInclude"
-xmlns:xl="http://www.w3.org/1999/xlink"
-version="5.0"
-xml:id="chapter">
- <title>This is a Chapter</title>
- <info>
- <abstract>
- <para>This is a chapter summary.</para>
- </abstract>
- </info>
- <section id="section">
- <title>This is a section</title>
- ...
- </section>
- <section id="...">
- ...
- <section id="subsection">
- <title>Sample Subsection</title>
- ...
- <simplesect id="block">
- <title>Sample Block Section</title>
- ...
- </simplesect>
- </section>
- </section>
-</chapter></programlisting>
- </example>
- </simplesect>
- </section>
-</chapter>
diff --git a/docs/1.6/styleguide/conditional.xml b/docs/1.6/styleguide/conditional.xml
deleted file mode 100644
index c56b999..0000000
--- a/docs/1.6/styleguide/conditional.xml
+++ /dev/null
@@ -1,203 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="conditional">
- <title>Conditional Text</title>
- <section xml:id="ConditionalWriting">
- <title>Writing with Conditional Text</title>
- <simplesect>
- <title>Overview</title>
- <para>The guidelines on using conditional text are based on the <emphasis>Profiling</emphasis>
- chapter from <link xl:href="http://www.sagehill.net/docbookxsl/index.html">DocBook XSL: The
- Complete Guide</link>, by Bob Stayton. The current chapter does not describe all of the
- features supported by DocBook XSL. In particular, this chapter discusses profiling using
- only the <tag class="attribute">condition</tag> attribute, whereas the <emphasis>DocBook
- XSL</emphasis> book also describes how to support profiling using other DocBook
- attributes.</para>
- </simplesect>
- <simplesect>
- <title>Conditionalizing elements</title>
- <para>To conditionalize an element, set the element's <tag class="attribute">condition</tag>
- attribute to the name of the condition you want to apply. For example, to conditionalize a
- text block with the <code>fuse</code> condition:</para>
- <programlisting><simplesect condition="fuse">
- ...
-</simplesect></programlisting>
- <para>When you conditionalize an element, the condition is applied to <emphasis>all of the
- enclosed text and every sub-element</emphasis> of the conditionalized element. This
- mechanism is flexible, because every element in DocBook supports the <tag class="attribute"
- >condition</tag> attribute. For example, you can conditionalize an entire <tag
- class="element">chapter</tag>, a <tag class="element">section</tag>, a <tag
- class="element">figure</tag>, an <tag class="element">example</tag>, or even an individual
- <tag class="element">code</tag> element.</para>
- </simplesect>
- <simplesect>
- <title>Conditionalizing free-standing text</title>
- <para>There is one special case not covered by the mechanism for conditionalizing elements.
- What do you do, if you want to conditionalize a fragment of text that does not correspond to
- an element? For example, you might want to conditionalize a sentence within a paragraph. In
- this case, you can use the <tag class="element">phrase</tag> element to enclose the text
- fragment and then apply the requisite condition to the <tag class="element">phrase</tag>
- element.</para>
- <para>The following example shows how to conditionalize a sentence so that it appears only in
- the Artix version of the book:</para>
- <programlisting><para>&prodname; supports a multitude of integration options.
-<phrase condition="artix">In particular, you can optionally plug in a mainframe integration kit</phrase>
-</para></programlisting>
- </simplesect>
- <simplesect>
- <title>Conditionalizing comments</title>
- <para>You can also use conditional text to manage draft comments in a book. These are the kind
- of comments that you would like to make visible in a draft copy of the output: for example,
- reminders to self and directions to the reviewer. It is recommended that you insert comments
- using the remark element with the <code>comment</code> condition applied. For
- example:</para>
- <programlisting><remark condition="comment">REVISIT - Your comment here!</remark></programlisting>
- <para>To simplify entering comments, the Evergreen template for the Oxygen editor includes a
- custom option, <guimenuitem>DocBook4 | Insert Comment</guimenuitem>, which automatically
- inserts a conditionalized <tag class="element">remark</tag> element.</para>
- </simplesect>
- <simplesect>
- <title>Applying multiple conditions</title>
- <para>If required, you can apply multiple conditions to a single element, using the semicolon,
- <literal>;</literal>, as the separator character. For example, to apply both the
- <code>unix</code> and <code>win</code> conditions to a <tag class="element"
- >simplesect</tag> element, set the <tag class="attribute">condition</tag> attribute as
- follows:</para>
- <programlisting><simplesect condition="unix;win"> ... </simplesect></programlisting>
- <para>Semantically, the effect of setting both of these conditions is that, at build time, the
- <tag class="element">simplesect</tag> element will be included in the output if either the
- <code>unix</code> condition OR the <code>win</code> condition is enabled.</para>
- </simplesect>
- </section>
- <section xml:id="ConditionalBuilding">
- <title>Building Books with Conditional Text</title>
- <simplesect>
- <title>Overview</title>
- <para>When building a book with conditional text, you need to use a special Ant build file to
- produce the output. The targets of the conditional build file are the same as a regular
- build file, but the process for generating the output is slightly different. When building a
- conditional book, the build system first generates an intermediate file,
- <filename><replaceable>bookname</replaceable>.prfl</filename>, which contains a version
- of the <filename><replaceable>bookname</replaceable>.xml</filename> book where all of the
- conditions have been applied. The
- <filename><replaceable>bookname</replaceable>.prfl</filename> file is then used as the
- input for the next stage of book building, using the regular templates for HTML and
- PDF.</para>
- </simplesect>
- <simplesect>
- <title>Steps for building with conditions</title>
- <para>To build a book with conditions, perform the following steps:</para>
- <orderedlist>
- <listitem>
- <para><xref linkend="ConditionalBuildingGet"/></para>
- </listitem>
- <listitem>
- <para><xref linkend="ConditionalBuildingSet"/></para>
- </listitem>
- <listitem>
- <para><xref linkend="ConditionalBuildingBuild"/></para>
- </listitem>
- </orderedlist>
- </simplesect>
- <simplesect xml:id="ConditionalBuildingGet">
- <title>Get the conditional build.xml file</title>
- <para>To build a book with conditional text, use the conditional version of the Ant
- <filename>build.xml</filename> file. In the <filename>docs_tools</filename> SVN
- repository, look for the following file:
- <filename>trunk/docbook-output/dcbk/custom/build_book_with_conditions.xml</filename></para>
- <para>Copy this build file into your book directory and rename it to
- <filename>build.xml</filename>.</para>
- </simplesect>
- <simplesect xml:id="ConditionalBuildingSet">
- <title>Set conditions in build.xml</title>
- <para>In addition to the usual book properties that you must set in a
- <filename>build.xml</filename> file (that is, <code>ROOT</code>, <code>DOCID</code>, and
- <code>LOGO</code>), you must also set a <code>CONDITIONS</code> property that lists the
- conditions you want to enable. If you want to enable multiple conditions, separate them
- using a semicolon character, for example:</para>
- <programlisting> <property name="CONDITIONS" value="condition1;condition2" /></programlisting>
- <para>This setting would ensure that any conditions marked with <code>condition1</code> AND
- any conditions marked with <code>condition2</code> are included in the output. In other
- words, the more conditions you specify here, the more output text you might get.</para>
- </simplesect>
- <simplesect xml:id="ConditionalBuildingBuild">
- <title>Build the book</title>
- <para>The conditional <filename>build.xml</filename> file supports the same Ant targets for
- building a book as the normal <filename>build.xml</filename> file. For example, to build
- both the HTML and PDF output, you can execute Ant with the default target, as
- follows:</para>
- <programlisting>> ant</programlisting>
- <para>The build file also supports the <code>db</code>, <code>pdf</code>, and
- <code>html</code> Ant targets. In the course of generating the document output, the build
- file produces an intermediate file,
- <filename><replaceable>bookname</replaceable>.prfl</filename>, which is a DocBook XML file
- to which the conditions have been applied.</para>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="ConditionalBuildingExSSCBF"/> shows the top of the
- <filename>build.xml</filename> file for the FUSE Mediation Router Programmer's Guide,
- including conditional settings. This book is shared between the FUSE and Artix product.
- FUSE-specific parts of the book are marked with the condition, <code>fuse</code>, and
- Artix-specific parts of the book are marked, <code>artix</code>. <xref
- linkend="ConditionalBuildingExSSCBF"/> shows the settings for building the FUSE version of
- the book in draft format.</para>
- <example xml:id="ConditionalBuildingExSSCBF">
- <title>Sample Settings in a Conditional build.xml File</title>
- <programlisting><?xml version="1.0" encoding="UTF-8"?>
-<project name="MRGettingStarted" default="all" basedir=".">
- <property environment="env" />
- <!-- Choose one of the following common build files to import:
- build_artix_common.xml (Artix)
- build_fuse_common.xml (FUSE)
- -->
- <import file="${env.DBCK_HOME}/lib/build_fuse_common.xml"/>
-
- <!-- Edit the following properties for your book: -->
- <property name="ROOT" value="prog_guide" />
- <property name="DOCID" value="FuseMRProg" />
- <property name="LOGO" value="fmr" />
- <property name="CONDITIONS" value="fuse;comment" />
-
- <!-- DO NOT MODIFY ANYTHING BELOW THIS LINE -->
- ...</programlisting>
- </example>
- <para>Where the <code>CONDITIONS</code> property specifies two conditions: <code>fuse</code>
- and <code>comment</code>. This build file processes the conditions as follows:</para>
- <itemizedlist>
- <listitem>
- <para>Unmarked elements not enclosed by conditionalized elements are included in the
- output.</para>
- </listitem>
- <listitem>
- <para>Elements marked with the <code>artix</code> condition are
- <emphasis>excluded</emphasis> from the output.</para>
- </listitem>
- <listitem>
- <para>Elements marked with the <code>fuse</code> condition are
- <emphasis>included</emphasis> in the output.</para>
- </listitem>
- <listitem>
- <para>Elements marked with the <code>comment</code> condition are
- <emphasis>included</emphasis> in the output.</para>
- </listitem>
- </itemizedlist>
- </simplesect>
- <simplesect>
- <title>Managing comments</title>
- <para>Unlike other conditions, which typically remain unchanged for a long time, the
- <code>comment</code> condition changes relatively frequently, as you switch between
- producing draft copies and release copies. It is something that you need to keep in mind,
- when building a release, that you need to disable the <code>comment</code> condition before
- building the output.</para>
- </simplesect>
- <simplesect>
- <title>Building without conditions</title>
- <para>It is not possible to build a book with a blank <code>CONDITIONS</code> property. If you
- want to build a book without conditions, you could either replace the conditional
- <filename>build.xml</filename> file with a regular <filename>build.xml</filename> file or
- you could enable every condition in the <code>CONDITIONS</code> property (thereby ensuring
- that the complete source is processed).</para>
- </simplesect>
- </section>
-</chapter>
diff --git a/docs/1.6/styleguide/exclude.xml b/docs/1.6/styleguide/exclude.xml
deleted file mode 100644
index 3da6953..0000000
--- a/docs/1.6/styleguide/exclude.xml
+++ /dev/null
@@ -1,370 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="exclusions">
- <title>Elements Currently Unused in Evergreen Documentation</title>
- <para>Evergreen documentation uses a subset of elements defined by DocBook. The following elements
- are not planned to be used. If you believe you need to use one of these tags, contact the
- Documentation Interest Group for more guidance.</para>
- <itemizedlist>
- <listitem>
- <para><tag class="element">ackno</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">address</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">affiliation</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">artpagenums</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">audiodata</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">audioobject</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">authorblurb</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">beginpage</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">bibliocoverage</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">bibliodiv</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">biblioentry</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">bibliography</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">bibliographyinfo</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">biblioid</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">bibliolist</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">bibliomixed</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">bibliomset</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">biblioref</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">bibliorelation</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">biblioset</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">bibliosource</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">blockinfo</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">citation</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">citebiblioid</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">citerefentry</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">citetitle</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">city</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">collab</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">collabname</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">colophone</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">confdates</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">confgroup</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">conftitle</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">contractnum</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">contractsponsor</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">corpname</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">country</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">dedication</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">fax</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">firstname</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">glossaryinfo</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">highlights</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">honorific</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">informalequation</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">inlineequation</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">invpartnumber</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">isbn</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">issn</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">issuenum</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">jobtitle</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">lineage</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">manvolnum</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">modespec</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">orgdiv</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">otheraddr</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">pagenums</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">partintro</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">personblurb</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">personname</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">phone</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">pob</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">postcode</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">prefaceinfo</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">primaryie</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">printhistory</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">productnumber</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">publisher</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">publishername</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">pubsnumber</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">refsect1</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">refsect1info</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">refsect2</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">refsect2info</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">refsect3</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">refsect3info</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">revdescription</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">revhistory</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">revision</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">screeninfo</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">secondaryie</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">sect1</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">sect1info</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">sect2</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">sect2info</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">sect3</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">sect3info</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">sect4</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">sect4info</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">sect5</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">sect5info</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">seealsoie</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">seeie</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">seg</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">seglistitem</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">segmentedlist</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">segtitle</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">seriesvolnums</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">shortaffil</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">sidebar</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">sidebarinfo</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">simpara</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">state</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">street</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">surname</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">tertiaryie</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">titleabbrev</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">toc</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">tocback</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">tocchap</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">tocentry</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">tocfront</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">toclevel1</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">toclevel2</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">toclevel3</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">toclevel4</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">toclevel5</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">tocpart</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">videodata</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">videoobject</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">volumenum</tag></para>
- </listitem>
- </itemizedlist>
-</chapter>
diff --git a/docs/1.6/styleguide/figures.xml b/docs/1.6/styleguide/figures.xml
deleted file mode 100644
index cc8c725..0000000
--- a/docs/1.6/styleguide/figures.xml
+++ /dev/null
@@ -1,169 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="figures">
- <title>Figures, Diagrams, Screen Shots, and In-Line Graphics</title>
- <section>
- <title>Overview</title>
- <para>Graphics, such as a diagram or a screen shot of a user interface, make a document more
- readable. Often, graphics also help clarify abstract concepts.</para>
- <para>Figures, diagrams, and screen shots contain images stored in external files. They are
- denoted using one of two elements: <tag class="element">figure</tag> or <tag class="element"
- >screenshot</tag>. The <tag class="element">figure</tag> element is used to denote a figure
- or a diagram. The <tag class="element">screenshot</tag> element is used to denote a screen
- shot.</para>
- </section>
- <section>
- <title>Image Data</title>
- <para>The preferred data format for images is PNG. However, images can be accepted in the
- following formats:</para>
- <itemizedlist>
- <listitem>
- <para>JPEG</para>
- </listitem>
- <listitem>
- <para>GIF</para>
- </listitem>
- </itemizedlist>
- <para>Images should be placed in an <filename class="directory">images</filename> folder
- directly under the folder containing the document source. </para>
- <para>Image size...</para>
- </section>
- <section>
- <title>Image Size</title>
- <para>Image files should have a maximum width of 900 pixels.</para>
- <para>Image scaling should be set to 75%. This is ignored for HTML output and ensures images are
- optimally sized for PDF files. </para>
- </section>
- <section>
- <title>Figures and Diagrams</title>
- <para>Figures and diagrams are marked up the same way. They are both placed in a <tag
- class="element">figure</tag> element. The <tag class="element">figure</tag> element is a
- container for the caption and data that make up the figure or diagram.</para>
- <para>The caption is specified by a <tag class="element">title</tag> element. The <tag
- class="element">title</tag> element is the first child element of the<tag class="element"
- >figure</tag> element. The contents of the <tag class="element">title</tag> element is the
- caption used for the figure. It is also the default text used when you cross reference the
- figure.</para>
- <para>The image data is specified in a <tag class="element">mediaobject</tag> element. The <tag
- class="element">mediaobject</tag> element is a wrapper for an <tag class="element"
- >imageobject</tag> element. The <tag class="element">imageobject</tag> element is also a
- wrapper element. The <tag class="element">imageobject</tag> element wraps an <tag
- class="element">imagedata</tag> element that specifies the name of the file containing the
- image.</para>
- <para>The <tag class="element">imagedata</tag> element has no content. All of the information is
- specified using three attributes:</para>
- <table>
- <title>Attributes for imagedata Element</title>
- <tgroup cols="2">
- <thead>
- <row>
- <entry>Attribute</entry>
- <entry>Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <tag class="attribute">align</tag>
- </entry>
- <entry>Specifies how the image is aligned on the page. Valid values are <tag
- class="attvalue">left</tag>, <tag class="attvalue">right</tag>, and <tag
- class="attvalue">center</tag>.</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">fileref</tag>
- </entry>
- <entry>Specifies the location of the file containing the image.</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">format</tag>
- </entry>
- <entry>Specifies the type of data used to specify the image. Valid values are <tag
- class="attvalue">GIF</tag>, <tag class="attvalue">JPG</tag>, and <tag
- class="attvalue">PNG</tag>.</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- <para><xref linkend="figure_example"/> shows the mark-up for a figure.</para>
- <example xml:id="figure_example">
- <title>Mark-up for a Figure</title>
- <programlisting><figure xml:id="fig_1">
- <title>CeltiXfire WAR Structure</title>
- <mediaobject>
- <imageobject>
- <imagedata align="center"
- fileref="./images/tomcat_war.gif"
- format="GIF" />
- </imageobject>
- </mediaobject>
- ...
-</figure></programlisting>
- </example>
- </section>
- <section>
- <title>Screen Shots</title>
- <para>Screen shots are also marked up using a <tag class="element">figure</tag> element.
- However, a screen shot uses one additional wrapper element. The <tag class="element"
- >screenshot</tag> element wraps the <tag class="element">mediaobject</tag> element as shown
- in <xref linkend="screen_example"/>.</para>
- <example xml:id="screen_example">
- <title>Mark-up for a Screen Shot</title>
- <programlisting><figure xml:id="screen_1">
- <title>SOA Tools Welcome Screen</title>
- <screenshot>
- <mediaobject>
- <imageobject>
- <imagedata align="center"
- fileref="./images/welcome.gif"
- format="GIF" />
- </imageobject>
- </mediaobject>
- </screenshot>
- ...
-</figure></programlisting>
- </example>
- </section>
- <section>
- <title>In-Line Graphics</title>
- <para>Graphical elements that need to be placed in-line with the text of a paragraph are marked
- up using the <tag class="element">inlinemediaobject</tag> element. Like the <tag
- class="element">mediaobject</tag> element, the <tag class="element">inlinemediaobject</tag>
- element is a wrapper for an <tag class="element">imageobject</tag> element. <xref
- linkend="inline_example"/> shows the mark-up for an in-line graphic.</para>
- <example xml:id="inline_example">
- <title>Mark-up for an In-Line Graphic</title>
- <programlisting><inlinemediaobject>
- <imageobject>
- <imagedata align="center" fileref="./images/larrow.gif"
- format="GIF" />
- </imageobject>
- ...
-</inlinemediaobject></programlisting>
- </example>
- </section>
- <section>
- <title>Adding Alternative Text</title>
- <para>For better accessibility and to comply with federal and local accessibility guidelines,
- all images in DocBook files should include alternative text.</para>
- <para>To include alternative text with a graphic, add a <tag class="element">textobject</tag>
- element after the <tag class="element">imageobject</tag> element. The <tag class="element"
- >textobject</tag> element has a single <tag class="element">phrase</tag> child element. The
- value of the <tag class="element">phrase</tag> element is the alternative text used when the
- documentation is generated to HTML.</para>
- <example xml:id="alttext_example">
- <title>Mark-up for Alternative Text</title>
- <programlisting><mediaobject>
- <imageobject>
- <imagedata align="center" fileref="./images/config.gif"
- format="GIF" />
- </imageobject>
- <textobject>
- <phrase>Configuration Hierarchy</phrase>
- </textobject>
-</mediaobject></programlisting>
- </example>
- </section>
-</chapter>
diff --git a/docs/1.6/styleguide/filenames.xml b/docs/1.6/styleguide/filenames.xml
deleted file mode 100644
index f729c83..0000000
--- a/docs/1.6/styleguide/filenames.xml
+++ /dev/null
@@ -1,76 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="filenames">
- <title>File Structure and Filenames</title>
-
- <info>
- <abstract>
- <para>This chapter describes the physical file structure for Evergreen documentation and file
- naming conventions, including the <tag class="element">olink</tag> element. </para>
- </abstract>
- </info>
- <section>
- <title>File Structure for Evergreen Documentation</title>
- <simplesect>
- <title>Overview</title>
- <para>The files for Evergreen documentation reside within a public directory on
- evergreen-ils.org. </para>
- </simplesect>
- <simplesect>
- <title>File structure for Evergreen documents</title>
- <itemizedlist>
- <listitem>
- <para>The set is represented by set.xml, a single file in the docs subdirectory of
- evergreen-ils.org</para>
- </listitem>
- <listitem>
- <para>The two book elements are in separate subdirectories under the docs subdirectory,
- and are labeled book1.xml and book2.xml</para>
- </listitem>
- <listitem>
- <para>Chapter elements are in their own separate subdirectories under their respective
- book directories</para>
- </listitem>
- <listitem>
- <para>Glossaries and similar chapter-like elements are treated like chapters, and are in
- separate subdirectories under their respective book directories</para>
- </listitem>
- <listitem>
- <para>Images and similar media files are placed in subdirectories under their respective
- folders.</para>
- </listitem>
- </itemizedlist>
- </simplesect>
- </section>
- <section>
- <title>Filename conventions</title>
- <itemizedlist>
- <listitem>
- <para>Evergreen filenames are in lower case without underscores or periods.</para>
- </listitem>
- <listitem>
- <para>The folders for images and other multimedia are named media. </para>
- </listitem>
- <listitem>
- <para>The XML id for the chapter is the same as the XML filename, such as sysadmin. </para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title>Conventions for olinks</title>
- <itemizedlist>
- <listitem>
- <para>To simplify the creation of olinks between between books, every Evergreen file has a
- <glossterm>document id</glossterm> that parallels the file's filename and xml:id
- attribute. Therefore, a book-level file called book2.xml has an xml:id of book2 and a
- document id of book2, while a chapter file called sysadmin.xml has an xml:id of sysadmin
- and also a document id of sysadmin.</para>
- </listitem>
- <listitem>
- <para>The document id is the first element within the file after the xml declaration, and
- has the structure element id="name".</para>
- </listitem>
- </itemizedlist>
- </section>
-</chapter>
diff --git a/docs/1.6/styleguide/general.xml b/docs/1.6/styleguide/general.xml
deleted file mode 100644
index a0fc586..0000000
--- a/docs/1.6/styleguide/general.xml
+++ /dev/null
@@ -1,208 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="general">
- <title>General Elements and Other Elements not Discussed Elsewhere</title>
- <section>
- <title>Overview</title>
- <para>Since DocBook was defined to describe a wide range of publishable content, it includes a
- number of elements that are used to perform common tasks. These elements include ones that
- specify superscripts and emphasis.</para>
- </section>
- <section>
- <title>Formatting Elements</title>
- <para>The following are common formatting elements used in DocBook:</para>
- <segmentedlist>
- <segtitle>Element</segtitle>
- <segtitle>Description</segtitle>
- <seglistitem>
- <seg>
- <tag class="element">emphasis</tag>
- </seg>
- <seg>Specifies that the content of the element is to be emphasized by either
- <emphasis>italics</emphasis> or <emphasis role="strong">boldface</emphasis>. The default
- is to use italics. Specify boldface by setting the <tag class="attribute">role</tag>
- attribute to <tag class="attvalue">bold</tag>.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">literallayout</tag>
- </seg>
- <seg>Specifies that the content of the element is to be reproduced with all of the
- whitespace preserved.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">subscript</tag>
- </seg>
- <seg>Specifies that the content of the element is a subscript as in
- H<subscript>2</subscript>O.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">superscript</tag>
- </seg>
- <seg>Specifies that the content of the element is a superscript as in
- E=MC<superscript>2</superscript>.</seg>
- </seglistitem></segmentedlist>
- </section>
- <section>
- <title>General Computing Elements</title>
- <para>The following are elements used for describing computer technology:</para>
- <segmentedlist>
- <segtitle>Element</segtitle>
- <segtitle>Description</segtitle>
- <seglistitem>
- <seg>
- <tag class="element">action</tag>
- </seg>
- <seg>Specifies that content describes a response to some user initiated action.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">application</tag>
- </seg>
- <seg>Specifies that the content is the name of a piece of software.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">computeroutput</tag>
- </seg>
- <seg>Specifies that the content is text printed on a computer display.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">database</tag>
- </seg>
- <seg>Specifies that the content is the name of a database, or part of a database.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">email</tag>
- </seg>
- <seg>Specifies that the content is an e-mail address.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">envar</tag>
- </seg>
- <seg>Specifies that the content is the name of an environment variable.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">errorcode</tag>
- </seg>
- <seg>Specifies that the content is an error code.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">errorname</tag>
- </seg>
- <seg>Specifies that the content is the name of an error.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">errortext</tag>
- </seg>
- <seg>Specifies that the content is the text generated when an error occurs.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">filename</tag>
- </seg>
- <seg>Specifies that the content is the name of a file.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">hardware</tag>
- </seg>
- <seg>Specifies that the content is a piece of computer hardware.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">option</tag>
- </seg>
- <seg>Specifies that the content is an option to a command.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">prompt</tag>
- </seg>
- <seg>Specifies that the content is the string used as a prompt for data on a computer
- screen.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">userinput</tag>
- </seg>
- <seg>Specifies that the content is data a user enters into a computer system.</seg>
- </seglistitem></segmentedlist>
- </section>
- <section>
- <title>Other General Elements</title>
- <para>The following are other general use elements used in DocBook:</para>
- <segmentedlist>
- <segtitle>Element</segtitle>
- <segtitle>Description</segtitle>
- <seglistitem>
- <seg>
- <tag class="element">abbrev</tag>
- </seg>
- <seg>Specifies that the content is an abbreviation.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">acronym</tag>
- </seg>
- <seg>Specifies that the content is an acronym.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">firstterm</tag>
- </seg>
- <seg>Specifies that the content is the first occurrence of a new term or is a term that is
- used a context specific manner.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">literal</tag>
- </seg>
- <seg>Specifies that the content is a literal value.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">optional</tag>
- </seg>
- <seg>Specifies that the content is optional information. It is typically used in command
- synopsis.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">replaceable</tag>
- </seg>
- <seg>Specifies that the content represents a value that will be replaced by the user in
- using the product.</seg>
- </seglistitem></segmentedlist>
- </section>
- <section>
- <title>GUI Elements</title>
- <para>The following are DocBook elements used in documenting a GUI:</para>
- <segmentedlist>
- <segtitle>Element</segtitle>
- <segtitle>Description</segtitle>
- <seglistitem>
- <seg>
- <tag class="element">accel</tag>
- </seg>
- <seg>Specifies that the content is a keyboard shortcut.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">guibutton</tag>
- </seg>
- <seg>Specifies that the content is the label on a GUI button.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">guilabel</tag>
- </seg>
- <seg>Specifies that the content is a label on a GUI element other than a button.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">guimenu</tag>
- </seg>
- <seg>Specifies that the content is the name of a menu.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">guimenuitem</tag>
- </seg>
- <seg>Specifies that the content is a selectable item on a menu.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">guisubmenu</tag>
- </seg>
- <seg>Specifies that the content is the name of a sub-menu.</seg>
- </seglistitem><seglistitem>
- <seg>
- <tag class="element">mousebutton</tag>
- </seg>
- <seg>Specifies that the content is the name of a mouse button.</seg>
- </seglistitem></segmentedlist>
- </section>
-</chapter>
diff --git a/docs/1.6/styleguide/glossary.xml b/docs/1.6/styleguide/glossary.xml
deleted file mode 100644
index 08cebcc..0000000
--- a/docs/1.6/styleguide/glossary.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<glossary version="5.0" xmlns="http://docbook.org/ns/docbook"
- xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude"
- role="auto" xml:id="glossary">
-
- <para>The recommendation here is to build a glossary database (Chapter 17 of Stayton's
- book) that is writable by any author or editor with commit privileges. Authors can
- populate it with whatever terms they like, using a simple rule for id
- disambiguation (such as gloss.term, where gloss is constant and term is the term
- itself). If we need to disambiguate two forms of the same term, we can add a
- suffix. The build process described in Stayton's book builds a glossary for each
- document based on the terms used in that document.</para>
-
- <para>For authors without commit privileges, this becomes a little more complex. One
- thought would be to have authors submit their glossary entries in a separate file,
- which editor-committers can then upload.</para>
-
-</glossary>
diff --git a/docs/1.6/styleguide/indexterms.xml b/docs/1.6/styleguide/indexterms.xml
deleted file mode 100644
index 7c0b79b..0000000
--- a/docs/1.6/styleguide/indexterms.xml
+++ /dev/null
@@ -1,74 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="indexterms">
- <title>Marking Terms for Dynamic Index Creation</title>
- <info>
- <abstract>
- <para>This chapter describes how to mark up terms for generating a dynamic index of Evergreen
- documentation. </para>
- </abstract>
- </info>
- <section>
- <title>Marking Terms for Index Entry</title>
- <simplesect>
- <title>Overview</title>
- <para>DocBook supports two methods for generating an index. One is to explicitly create the
- index. The other is to generate the index when the book is published based on elements
- included in the text. We use the second approach. </para>
- <para>Authors are not required to mark up index elements; editors will complete any index
- tagging not accomplished at the authoring stage.</para>
- </simplesect>
- <simplesect>
- <title>Specifying index entries</title>
- <para>Index entries are specified by adding <tag class="element">indexterm</tag> elements in
- the text of the book. An index entry must contain one <tag class="element">primary</tag>
- element. The value of the <tag class="element">primary</tag> element is the top-level entry
- that will appear in the generated index.</para>
- <para>In addition, an <tag class="element">indexterm</tag> element can contain the following
- optional elements:</para>
- <itemizedlist>
- <listitem>
- <para>One <tag class="element">secondary</tag> element that specifies a second level entry
- in the generated index.</para>
- </listitem>
- <listitem>
- <para>One <tag class="element">tertiary</tag> element that specifies a third level index
- entry.</para>
- </listitem>
- <listitem>
- <para>One <tag class="element">see</tag> element that specifies an alternate entry to
- which the reader is redirected.</para>
- </listitem>
- <listitem>
- <para>One <tag class="element">seealso</tag> element that specifies an additional entry
- with relevant information.</para>
- </listitem>
- </itemizedlist>
- <para>If you want to mark an <tag class="element">indexterm</tag> and you aren't sure what
- elements to assign it, use the <tag>primary</tag> element.</para>
- </simplesect>
- <simplesect>
- <title>Example: Marking a Primary Index Term</title>
- <para>The Open Scalable Request Framework (<indexterm>
- <primary>OpenSRF</primary>
- </indexterm>, pronounced 'open surf'), is a stateful, decentralized service architecture
- that allows developers to create applications for Evergreen with a minimum of knowledge of
- its structure.</para>
- </simplesect>
- <simplesect>
- <title>Example: Marking a Secondary Index Term</title>
- <para> Indexed-field weighting, which controls relevance ranking in Evergreen, is configured
- in the 'weight' column of the <indexterm>
- <primary>Evergreen Tables</primary>
- <secondary>config.metabib_field</secondary>
- </indexterm> table of the Evergreen database.</para>
- </simplesect>
- <simplesect>
- <title>Specifying where the Index is Generated</title>
- <para>In order for the index to auto-generate, every Evergreen book has an <tag
- class="emptytag">index</tag> element. The index will be generated in the position that
- corresponds to the element's location in the book file. The <tag class="emptytag"
- >index</tag> element follows all other chapters and appendices.</para>
- </simplesect>
- </section>
-</chapter>
diff --git a/docs/1.6/styleguide/links.xml b/docs/1.6/styleguide/links.xml
deleted file mode 100644
index 022aabf..0000000
--- a/docs/1.6/styleguide/links.xml
+++ /dev/null
@@ -1,489 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="links">
- <title>Cross-References and Links</title>
- <info>
- <abstract>
- <para>DocBook has three linking elements that are used to create internal cross-references,
- external cross-references, and links to locations on the Web. Some of the linking elements
- perform multiple tasks and some have overlapping functionality. Authors choose the proper
- element based on the specifics of the task at hand. A portion of the link text is generated
- by the publication system and the author has some control over it.</para>
- </abstract>
- </info>
- <section xml:id="linksInternal">
- <title>Cross-References within the Same File or Book</title>
- <simplesect>
- <title>Overview</title>
- <para>Internal cross-references link to targets within the same file or book. There are two
- linking elements that can be used to make an internal cross-reference:</para>
- <itemizedlist>
- <listitem>
- <para><link linkend="xref">
- <tag class="element">xref</tag>
- </link>-generates a cross-reference whose target is in the same file.</para>
- </listitem>
- <listitem>
- <para><link linkend="link">
- <tag class="element">link</tag>
- </link>-generates a cress-reference whose target is in the same file but allows the
- author to provide the link text.</para>
- </listitem>
- <listitem>
- <para><link linkend="olinkInternal">
- <tag class="element">olink</tag>
- </link>-generates a cross-reference whose target is in a different file. The <tag
- class="element">olink</tag> element allows the author to use either generated link
- text or author supplied link text.</para>
- </listitem>
- </itemizedlist>
- </simplesect>
- <simplesect xml:id="xref">
- <title>Inserting a cross-reference in the same file, using generated text</title>
- <indexterm>
- <primary>xref element</primary>
- </indexterm>
- <indexterm>
- <primary>linking</primary>
- <secondary>using generated text</secondary>
- </indexterm>
- <indexterm>
- <primary>cross referencing</primary>
- </indexterm>
- <para>The <tag class="element">xref</tag> element creates a link to an element in the same
- file. It requires the use of the <tag class="attribute">linkend</tag> attribute to identify
- the target element.</para>
- <para>The <tag class="element">xref</tag> element does not have any content. The link text is
- generated based on the contents of the target element. <anchor xml:id="xreftextgen"/>If the
- target element has a <tag class="element">title</tag> element, such as a <tag
- class="element">section</tag> element or an <tag class="element">example</tag> element,
- the contents of the <tag class="element">title</tag> element is used as the link text.
- Alternatively, the value of the target element's <tag class="attribute">xreflabel</tag>
- attribute will be used as the link text.</para>
- <important>
- <para>If the referenced element has both a <tag class="element">title</tag> element and a
- value specified in its <tag class="attribute">xreflabel</tag> attribute, the value of the
- <tag class="attribute">xreflabel</tag> attribute is used.</para>
- </important>
- <tip>
- <para>The default generated text for a PDF cross-reference includes the page number of the
- target. The generated text can be changed using the <tag class="attribute">xrefstyle</tag>
- attribute. See <xref linkend="linkStyling"/>.</para>
- </tip>
- <para><xref linkend="xrefexample1"/> shows an example of a cross reference whose text is
- derived from the <tag class="element">title</tag> element of the referenced element. The
- resulting link text would be <literal>the section called "Coco Crisp"
- shows</literal>.</para>
- <example xml:id="xrefexample1">
- <title>Cross Reference to a Titled Element</title>
- <programlisting><para><emphasis role="bold"><xref linkend="topsect" /></emphasis> shows ...</para>
-...
-<section id="topsect">
- <title>Coco Crisp</title>
-...
-</section></programlisting>
- </example>
- <para><xref linkend="xrefexample2"/> shows an example of a cross reference whose text is
- derived from the <tag class="attribute">xreflabel</tag> attribute of the targeted element.
- The resulting link text would be <literal>outfielder shows</literal>.</para>
- <example xml:id="xrefexample2">
- <title>Cross Reference to an Element with an xreflabel</title>
- <programlisting><para><xref linkend="example1" /> shows ...</para>
-...
-<example id="example1" xreflabel="outfielder">
- <title>Catching Coco Crisp</title>
- ...
-</example></programlisting>
- </example>
- </simplesect>
- <simplesect xml:id="link">
- <title>Inserting link using author supplied text</title>
- <indexterm>
- <primary>link element</primary>
- </indexterm>
- <indexterm>
- <primary>linking</primary>
- <secondary>using author text</secondary>
- </indexterm>
- <para>Internal links are created using the <tag class="element">link</tag> element. The <tag
- class="element">link</tag> element has one required attribute, <tag class="attribute"
- >linkend</tag>, whose value is the id of element anchoring the link. The anchoring element
- can be any valid DocBook element that uses the <tag class="attribute">xml:id</tag>
- attribute. For example if you wanted to create a link to an image in your document, you
- would use the id of the <tag class="element">figure</tag> element that wraps the
- image.</para>
- <para>The text used for the link is the content of the <tag class="element">link</tag>
- element. <xref linkend="linkexample"/> shows the mark up for this <link linkend="link">link
- to the top</link> of this section.</para>
- <example xml:id="linkexample">
- <title>Example of an Internal Link</title>
- <programlisting><section xml:id="link">
- ...
- <para>... this <emphasis role="bold"><link linkend="link">link to the top</link></emphasis> of ...</para>
- ...
-</section></programlisting>
- </example>
- <tip>
- <para>The default generated text for a PDF link includes the page number of the target. The
- generated text can be changed using the <tag class="attribute">xrefstyle</tag> attribute.
- See <xref linkend="linkStyling"/>.</para>
- </tip>
- </simplesect>
- <simplesect xml:id="olinkInternal">
- <title>Inserting a link to a target element in a different source file</title>
- <indexterm>
- <primary>olink element</primary>
- </indexterm>
- <indexterm>
- <primary>linking</primary>
- <secondary>external source file</secondary>
- </indexterm>
- <para>The <tag class="element">olink</tag> element facilitates cross-linking among DocBook
- files (just as <tag class="element">xref</tag> and <tag class="element">link</tag> elements
- enable linking within files).</para>
- <indexterm>
- <primary>olink element</primary>
- </indexterm>
- <indexterm>
- <primary>linking</primary>
- <secondary>across books</secondary>
- </indexterm>
- <indexterm>
- <primary>site map</primary>
- </indexterm>
- <para>You create a link to another book using the <tag class="element">olink</tag>
- element.</para>
- <para>Two attributes associated with the <tag class="element">olink</tag> element are used to
- specify the link target:</para>
- <variablelist>
- <varlistentry>
- <term>
- <tag class="attribute">targetptr</tag>
- </term>
- <listitem>
- <para>The value of the link target's <tag class="attribute">xml:id</tag>
- attribute</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>
- <tag class="attribute">targetdoc</tag>
- </term>
- <listitem>
- <para>The value of the <tag class="attribute">targetdoc</tag> attribute of the target
- document. </para>
- </listitem>
- </varlistentry>
- </variablelist>
- <para>For simplicity's sake, use the document's xml:id attribute as the document identifier;
- it will then function as both the <tag class="element">targetdoc</tag> and <tag
- class="element">targetptr</tag> element. So the <tag class="element">olink</tag> reference
- for this file would be filenames, as in this example:</para>
- <para>See the chapter on <olink targetdoc="lists" targetpr="lists">creating
- lists</olink> </para>
- </simplesect>
- </section>
- <section>
- <title>Cross-References to Other Books</title>
- <simplesect>
- <title>Overview</title>
- <para>Authors can create cross-references to a different book in a set using the <tag
- class="element">olink</tag> element. When linking to a different book, an author needs to
- use an additional attribute to specify the book in which the target element is located. The
- external linking mechanism relies on a site map and a number of target databases.</para>
- </simplesect>
- <simplesect>
- <title>Specifying the link text</title>
- <para>DocBook provides two methods for specifying link text for <tag class="element"
- >olink</tag> elements: author-supplied and auto-generated. Evergreen documentation uses
- author-supplied link text.</para>
- <para>Creating an olink between books</para>
- <para>adfasfsda</para>
- </simplesect>
- <simplesect>
- <title>Setting up the olink site map</title>
- <indexterm>
- <primary>site map</primary>
- </indexterm>
- <indexterm>
- <primary>linking</primary>
- <secondary>external XML source</secondary>
- <tertiary>making a site map</tertiary>
- </indexterm>
- <para>
- <note>
- <para>Most Evergreen documentation authors do not have to worry about creating or
- maintaining the site map for olinks in Evergreen documentation. This is set up in
- advance by the same team that manages the file commits.</para>
- </note>
- </para>
- <para>Stayton notes in DocBook XSL, "To form cross references between documents in HTML, their
- relative locations must be known." The olink site map defines how the published
- documentation set will be laid out and allows the publication system to resolve the links
- between all of the documents in the set.</para>
- <para>The site map for a documentation set is placed at the root of the documentation source
- tree and is always called <filename>site.xml</filename>. <xref linkend="LinksCalloutExample"
- /> shows a sample site map.</para>
- <example xml:id="LinksCalloutExample" pgwide="1">
- <?dbfo pgwide="1"?>
- <title>Document Set Site Map</title>
- <programlisting language="xml"><?xml version="1.0" encoding="utf-8"?> <co linkends="sitemapptr0" xml:id="sitemapco0"/>
-<targetset><co linkends="sitemapptr3" xml:id="sitemapco3"/>
- <targetsetinfo><co linkends="sitemapptr4" xml:id="sitemapco4"/>
- <title>Library Title</tite> <co linkends="sitemapptr41" xml:id="sitemapco41"/>
- <desc>Site map for the Evergreen XML Style Guide</desc> <co linkends="sitemapptr42" xml:id="sitemapco42"/>
- </targetsetinfo>
- <sitemap><co linkends="sitemapptr5" xml:id="sitemapco5"/>
- <dir name="docs_rls_inferno"><co linkends="sitemapptr6" xml:id="sitemapco6"/>
- <dir name="fluff"><co linkends="sitemapptr75" xml:id="sitemapco75"/>
- <dir name="overview"><co linkends="sitemapptr7" xml:id="sitemapco7"/>
- <document targetdoc="InfernoOverview"> <co linkends="sitemapptr8" xml:id="sitemapco8"/>
- <xi:include href="overview/target.db" xmlns:xi="http://www.w3.org/2001/XInclude" /> <co linkends="sitemapptr9" xml:id="sitemapco9"/>
- </document>
- </dir>
- </dir>
- <dir name="install_guide">
- <document targetdoc="InfernoInstall">
- <xi:include href="install_guide/target.db" xmlns:xi="http://www.w3.org/2001/XInclude" />
- </document>
- </dir>
- <dir name="getting_started">
- <document targetdoc="InfernoGetStarted">
- <xi:include href="get_started/target.db" xmlns:xi="http://www.w3.org/2001/XInclude" />
- </document>
- </dir>
- </dir>
- </sitemap>
-</targetset></programlisting>
- </example>
- <calloutlist>
- <title>Elements of the Site Map</title>
- <callout arearefs="sitemapco0" xml:id="sitemapptr0">
- <para>The site map should always be encoded as UTF-8. This ensures that all of the
- generated target data has the same encodings regardless of the encodings used by the XML
- source files.</para>
- </callout>
- <callout arearefs="sitemapco3" xml:id="sitemapptr3">
- <para>The <tag class="element">targetset</tag> element is the root of the site map.</para>
- </callout>
- <callout arearefs="sitemapco4" xml:id="sitemapptr4">
- <para>The <tag class="element">targetsetinfo</tag> element allows you to provide a
- description for the document set or any other information that is relevant to the site
- map.</para>
- </callout>
- <callout arearefs="sitemapco41" xml:id="sitemapptr41">
- <para>The <tag class="element">title</tag> element allows you to provide a title to be
- used on the generated index page.</para>
- </callout>
- <callout arearefs="sitemapco42" xml:id="sitemapptr42">
- <para>The <tag class="element">desc</tag> element allows you to provide a description for
- the document set that will appear at the top of the generated index page.</para>
- </callout>
- <callout arearefs="sitemapco5" xml:id="sitemapptr5">
- <para>The <tag class="element">sitemap</tag> element contains the directory layout of the
- output files.</para>
- </callout>
- <callout arearefs="sitemapco6" xml:id="sitemapptr6">
- <para>The name of the top-level directory is not important in the generation of the target
- databases for the links. The links are generated relative to the top-level
- directory.</para>
- </callout>
- <callout arearefs="sitemapco75" xml:id="sitemapptr75">
- <para>This is a directory that only contains other directories.</para>
- </callout>
- <callout arearefs="sitemapco7" xml:id="sitemapptr7">
- <para>This directory holds a generated book.</para>
- </callout>
- <callout arearefs="sitemapco8" xml:id="sitemapptr8">
- <para>The <tag class="element">document</tag> element's <tag class="attribute"
- >targetdoc</tag> attribute specifies the identifier used in the <tag class="element"
- >olink</tag> element's <tag class="attribute">targetdoc</tag> attribute when linking
- to targets in the document.</para>
- </callout>
- <callout arearefs="sitemapco9" xml:id="sitemapptr9">
- <para>The target database is included in the site map using an <tag class="element"
- >xi:include</tag> element. The path for each book's target database should be
- <filename><replaceable>book_src_dir</replaceable>/target.db</filename>.</para>
- </callout>
- </calloutlist>
- </simplesect>
- </section>
- <section xml:id="ulink">
- <title>Linking to Web Pages</title>
- <simplesect>
- <title>Creating the link</title>
- <indexterm>
- <primary>link element</primary>
- <secondary>xl:href attribute</secondary>
- </indexterm>
- <indexterm>
- <primary>linking</primary>
- <secondary>Web pages</secondary>
- </indexterm>
- <para>Links to Web pages are created using the <tag class="element">link</tag> element. You
- identify the target Web site using the <tag class="attribute">xl:href</tag> attribute. The
- value must be a valid URL.</para>
- </simplesect>
- <simplesect>
- <title>Specifying the link text</title>
- <para>The link text can be specified in one of two ways. You can specified the desired link
- text as the value of the <tag class="element">link</tag> element. If you leave the <tag
- class="element">link</tag> element empty, the value of the <tag class="attribute"
- >xl:href</tag> attribute will be used as the link text.</para>
- <tip>
- <para>The PDF will always show the URL in the generated text.</para>
- </tip>
- </simplesect>
- <simplesect>
- <title>Examples</title>
- <para><xref linkend="ulinkexample1"/> shows an example of an external link with supplied link
- text.</para>
- <example xml:id="ulinkexample1">
- <title>External Link with Link Text</title>
- <programlisting language="xml"><link xl:href="http://www.cxf.org">CXF Home</link></programlisting>
- </example>
- <para><xref linkend="ulinkexample2"/> shows an example of an external link that uses the
- default link text.</para>
- <example xml:id="ulinkexample2">
- <title>External Link Using Default Link Text</title>
- <programlisting><link xl:href="http://www.cxf.org" /></programlisting>
- </example>
- </simplesect>
- </section>
- <section xml:id="linkAnchor">
- <title>Creating Anchor Points</title>
- <indexterm>
- <primary>anchor element</primary>
- </indexterm>
- <indexterm>
- <primary>linking</primary>
- <secondary>creating a target</secondary>
- </indexterm>
- <simplesect>
- <title>Overview</title>
- <para>Authors can create anchor points in your text using the <tag class="element"
- >anchor</tag> element. The <tag class="element">anchor</tag> element does not have any
- content and does not result in any generated text. It simply marks a place in the content
- that can be the target of a link.</para>
- </simplesect>
- <simplesect>
- <title>Marking an anchor point</title>
- <para>The <tag class="element">anchor</tag> element is empty. It has a required <tag
- class="attribute">xml:id</tag> attribute that is the ID used for linking to the anchor. In
- addition, it can take a <tag class="attribute">xreflabel</tag> attribute that provides the
- generated text for an <tag class="element">xref</tag> element or an empty <tag
- class="element">olink</tag> element.</para>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="anchorEx"/> shows the mark-up for placing an anchor in a document.</para>
- <example xml:id="anchorEx">
- <title>Creating an Anchor</title>
- <programlisting language="docbook"><section ...>
- ...
- <emphasis role="bold"><anchor xml:id="anchorID" xreflabel="here" /></emphasis>
- ...
- <para><xref linkend="anchorID" /> is a link to an anchor.</para>
- ...
-</section></programlisting>
- <para>The generated text from the mark-up in <xref linkend="anchorEx"/> is <literal>here is
- a to an anchor.</literal> and the <literal>here</literal> would be a link back to the
- anchor.</para>
- </example>
- </simplesect>
- </section>
- <section xml:id="linkStyling">
- <title>Controlling the Generated Link Text</title>
- <simplesect>
- <title>Overview</title>
- <para>The publication system adds page numbers to all cross-references in PDF books. For
- cross-references that use generated text, the publication makes choices about what text is
- appropriate for the cross-reference. In some cases the defaults used by the publication is
- not appropriate. In these cases, the author can modify the generated link text using the
- <tag class="attribute">xrefstyle</tag> attribute.</para>
- </simplesect>
- <simplesect>
- <title>The xrefstyle attribute</title>
- <para>The <tag class="attribute">xrefstyle</tag> attribute's value is a string pattern. All of
- the patterns that can be used are described in Bob Stayton's <citetitle
- xl:href="http://sagehill.net/docbookxsl/CustomXrefs.html#Xrefstyle">DocBook XSL: The
- Complete Guide</citetitle>.</para>
- <para>The pattern most commonly used in the Evergreen authoring system is the
- <literal>select</literal> pattern. This pattern is specified using the syntax shown in
- <xref linkend="xrefstyleSelectEx"/>.</para>
- <example xml:id="xrefstyleSelectEx">
- <title>Syntax for the Select Pattern</title>
- <programlisting language="docbook"><xref ... <emphasis role="bold">xrefstyle="select: <replaceable>opt1</replaceable> <replaceable>opt2</replaceable> ... <replaceable>optN</replaceable>"</emphasis> /></programlisting>
- </example>
- <para>The values for <replaceable>optN</replaceable> select the text generated for the link
- text.</para>
- </simplesect>
- <simplesect>
- <title>Turning off page numbers</title>
- <para>Authors can turn off the generation of page numbers in the PDF using the
- <literal>nopage</literal> option in the select pattern. This option instructs the link
- generation algorithm to not generate page numbers, however it does not provide any guidance
- about what to include in the generated text. For <tag class="element">link</tag> elements
- and <tag class="element">olink</tag> elements that provide a value for the link text, the
- <literal>nopage</literal> option produces a the supplied link text without a page number.
- For <tag class="element">xref</tag> elements and <tag class="element">olink</tag> elements
- that rely on the publication system to generate the link text, the <literal>nopage</literal>
- is insufficient to create a valid link. The author will need to provide either the <link
- linkend="linksLabel" xrefstyle="select: nopage">label</link> option to the pattern or the
- <link linkend="linksTitle" xrefstyle="select: nopage">title</link> option to the selection
- pattern.</para>
- <para><xref linkend="linkexample2"/> shows a <tag class="element">link</tag> element that
- would not generate a page number.</para>
- <example xml:id="linkexample2" pgwide="1">
- <?dbfo pgwide="1"?>
- <title>Example of an Internal Link with no Page Number</title>
- <programlisting><section xml:id="link">
- ...
- <para>... this <emphasis role="bold"><link linkend="link" xrefstyle="select: nopage">link to the top</link></emphasis> of ...</para>
- ...
-</section></programlisting>
- </example>
- </simplesect>
- <simplesect xml:id="linksLabel">
- <title>Using the target's label</title>
- <para>Figures, tables, and examples have labels that are used to generate the link text. To
- ensure that an <tag class="element">xref</tag> element or an <tag class="element"
- >olink</tag> element that relies on the publication system to generate the link text will
- produce link text when page numbering is turned off, the author needs to provide the
- <literal>label</literal> option to the selection pattern.</para>
- <para><xref linkend="linkexample3"/> shows an <tag class="element">xref</tag> element that
- generates a label without a page number.</para>
- <example xml:id="linkexample3" pgwide="1">
- <?dbfo pgwide="1"?>
- <title>A Cross-Reference to a Figure with no Page Number</title>
- <programlisting><figure xml:id="link">
- ...
-</figure>
-<para><emphasis role="bold"><xref linkend="link" xrefstyle="select: nopage label" /></emphasis> shows ...</para>
-...
-</programlisting>
- </example>
- </simplesect>
- <simplesect xml:id="linksTitle">
- <title>Using the target's title</title>
- <para>Chapters, sections, and blocks have titles that are used to generate the link text. To
- ensure that an <tag class="element">xref</tag> element or an <tag class="element"
- >olink</tag> element that relies on the publication system to generate the link text will
- produce link text when page numbering is turned off, the author needs to provide the
- <literal>title</literal> option to the selection pattern.</para>
- <para><xref linkend="linkexample4"/> shows an <tag class="element">xref</tag> element that
- generates a title without a page number.</para>
- <example xml:id="linkexample4" pgwide="1">
- <?dbfo pgwide="1"?>
- <title>A Cross-Reference to a Block with no Page Number</title>
- <programlisting><simplesect xml:id="link">
- ...
-</simplesect>
-...
-<para>As discussed in <emphasis role="bold"><olink targetptr="link" xrefstyle="select: nopage label" /></emphasis> ...</para>
-...
-</programlisting>
- </example>
- </simplesect>
- </section>
-</chapter>
diff --git a/docs/1.6/styleguide/lists.xml b/docs/1.6/styleguide/lists.xml
deleted file mode 100644
index b1d125c..0000000
--- a/docs/1.6/styleguide/lists.xml
+++ /dev/null
@@ -1,400 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="lists">
- <title>Lists</title>
- <info>
- <abstract>
- <para>DocBook has several list structures to choose from. It has the standard numbered lists
- and bulleted lists. In addition it provides specialized types of lists for glossaries and
- other occasions. All of these lists may be used in Evergreen documentation. </para>
- </abstract>
- </info>
- <section>
- <title>Simple Lists</title>
- <simplesect>
- <title>Overview</title>
- <para>Simple lists are like a grocery list. They are a simple list of words or phrases without
- any delimiter. Their elements can only consist of simple, in-line tags, and therefore cannot
- contain sublists, examples, code listings or multiple paragraphs. Simple lists are rarely
- used in Evergreen' documentation.</para>
- </simplesect>
- <simplesect>
- <title>Specifying a simple list</title>
- <para>A simple list is specified by a <tag class="element">simplelist</tag> element. <tag
- class="element">simplelist</tag> has two optional attributes:</para>
- <table pgwide="1">
- <title>Attributes of the <tag class="element">simplelist</tag> Element</title>
- <tgroup cols="3">
- <thead>
- <row>
- <entry>Attribute</entry>
- <entry>Values</entry>
- <entry>Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <tag class="attribute">type</tag>
- </entry>
- <entry><tag class="attvalue">inline</tag>, <tag class="attvalue">horiz</tag>, <tag
- class="attvalue">vert</tag> (default)</entry>
- <entry>Specifies how the items in the list are to be listed.</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">columns</tag>
- </entry>
- <entry>>=1</entry>
- <entry>Specifies the number of columns to use when <tag class="attribute">type</tag>
- is set to <tag class="attvalue">horiz</tag> or <tag class="attvalue"
- >vert</tag>.</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- <para>The elements of a simple list are specified using a <tag class="element">member</tag>
- element. The contents of each <tag class="element">member</tag> element can only contain
- character data and in-line elements.</para>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="simpmarkup"/> shows the markup for a simple list.</para>
- <example xml:id="simpmarkup" xreflabel="Example 1">
- <title>Simple List Markup</title>
- <programlisting><simplelist>
- <member>Swedish Fish</member>
- <member>Mike & Ike</member>
- <member>Sour Patch Kids</member>
- <member>Gummy Bears</member>
-</simplelist></programlisting>
- </example>
- </simplesect>
- </section>
- <section>
- <title>Itemized Lists</title>
- <simplesect>
- <title>Overview</title>
- <para>An itemized list is used for lists where the order of the items in the list does not
- matter. They are like bulleted lists or the lists that are created by the <tag
- class="element">ul</tag> tag in HTML.</para>
- </simplesect>
- <simplesect>
- <title>Specifying an itemized list</title>
- <para>An itemized list is specified by an <tag class="element">itemizedlist</tag> element. You
- can specify an <tag class="attribute">xml:id</tag> attribute for itemized lists. If the list
- is going to referenced by an <tag class="element">xref</tag> element, you should also
- specify a value for the <tag class="attribute">xreflabel</tag> attribute.</para>
- <para>Each item in an itemized list is specified by a <tag class="element">listitem</tag>
- element. The <tag class="element">listitem</tag> element is a wrapper element and can
- contain any container elements such as a <tag class="element">para</tag> element. All
- content within a <tag class="element">listitem</tag> element will be indented to the same
- level. You can also specify sub-lists within a <tag class="element">listitem</tag>
- element.</para>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="itemmarkup"/> shows the markup for an itemized list.</para>
- <example xml:id="itemmarkup" xreflabel="Example 2">
- <title>Itemized List Markup</title>
- <programlisting><itemizedlist>
- <listitem>
- <para>This is the first item in my list</para>
- </listitem>
- <listitem>
- <para>This is the second item in my list.</para>
- <para>It has two paragraphs.</para>
- </listitem>
- <listitem>
- <para>This item has a sublist.</para>
- <itemizedlist>
- <listitem><para>first</para></listitem>
- <listitem><para>second</para></listitem>
- </itemizedlist>
- </listitem>
-</itemizedlist></programlisting>
- </example>
- </simplesect>
- </section>
- <section>
- <title>Ordered List</title>
- <simplesect>
- <title>Overview</title>
- <para>An ordered list is a list where the order of the elements is important and made
- explicit. They are like numbered lists and lists that are created using the <tag
- class="element">ol</tag> tag in HTML.</para>
- </simplesect>
- <simplesect>
- <title>Specifying an ordered list</title>
- <para>Ordered lists are specified by an <tag class="element">orderedlist</tag> element. In
- addition to the <tag class="attribute">xml:id</tag> attribute and <tag class="attribute"
- >xreflabel</tag> attribute, <tag class="element">orderedlist</tag> elements have three
- optional elements.</para>
- <table pgwide="1">
- <title>Attributes of the <tag class="element">orderedlist</tag> Element</title>
- <tgroup cols="3">
- <thead>
- <row>
- <entry>Attribute</entry>
- <entry>Values</entry>
- <entry>Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <tag class="attribute">continuation</tag>
- </entry>
- <entry><tag class="attvalue">continues</tag>, <tag class="attvalue">restarts</tag>
- (default)</entry>
- <entry>Specifies whether the item numbering should restart at one or continue from the
- previous ordered list.</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">inheritnum</tag>
- </entry>
- <entry><tag class="attvalue">inherit</tag>, <tag class="attvalue">ignore</tag>
- (default)</entry>
- <entry>Valid only for nested lists. Specifies whether the items in the nested list
- contain a reference to the item of the parent list.</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">numeration</tag>
- </entry>
- <entry><tag class="attvalue">arabic</tag>, <tag class="attvalue">loweralpha</tag>,
- <tag class="attvalue">lowerroman</tag>, <tag class="attvalue">upperalpha</tag>,
- <tag class="attvalue">upperroman</tag></entry>
- <entry>Specifies the numbering style to use for the list.</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- <para>Items in an ordered list are specified using a <tag class="element">listitem</tag>
- element. The <tag class="element">listitem</tag> element is a wrapper element and can
- contain any container elements such as a <tag class="element">para</tag> element. All
- content within a <tag class="element">listitem</tag> element will be indented to the same
- level. You can also specify sub-lists within a <tag class="element">listitem</tag>
- element.</para>
- </simplesect>
- </section>
- <section xml:id="VariableLists">
- <title>Variable Lists</title>
- <simplesect>
- <title>Overview</title>
- <para>A variable list looks similar to a glossary. It consists of a word, or phrase, and some
- text describing the word, or phrase. <xref linkend="varexample"
- xrefstyle="select: title nopage"/> shows a variable list.</para>
- <variablelist xml:id="varexample">
- <title>List of Rooms</title>
- <varlistentry>
- <term>Kitchen</term>
- <listitem>
- <para>The room where food is stored and prepared.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Garage</term>
- <listitem>
- <para>Where the cars are parked.</para>
- <note>
- <para>Bikes are also here.</para>
- </note>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Living room</term>
- <term>Family room</term>
- <listitem>
- <para>This is where we watch TV.</para>
- </listitem>
- </varlistentry>
- </variablelist>
- </simplesect>
- <simplesect>
- <title>Specifying the list</title>
- <para>Variable lists are specified by a <tag class="element">variablelist</tag> element. The
- <tag class="element">variablelist</tag> element can have the optional <tag
- class="attribute">xml:id</tag> attribute and <tag class="attribute">xreflabel</tag>
- attribute specified. You can also supply a title for a variable list by adding a <tag
- class="element">title</tag> element as the <tag class="element">variablelist</tag>
- element's first child.</para>
- <para>The items in a variable list are specified using a <tag class="element"
- >varlistentry</tag> element. The <tag class="element">varlistentry</tag> element has two
- children elements that specify the contents of the item:</para>
- <itemizedlist>
- <listitem>
- <para><tag class="element">term</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">listitem</tag></para>
- </listitem>
- </itemizedlist>
- </simplesect>
- <simplesect>
- <title>Specifying terms</title>
- <para>You can specify one or more <tag class="element">term</tag> elements in a <tag
- class="element">varlistentry</tag> element. Each <tag class="element">term</tag> element
- can contain text and in-line markup elements. Each <tag class="element">term</tag> element
- should contain a single term or phrase that the list item describes.</para>
- </simplesect>
- <simplesect>
- <title>Describing a term</title>
- <para>You describe the term, or terms, defined by the <tag class="element">term</tag> elements
- using a single <tag class="element">listitem</tag> element. The <tag class="element"
- >listitem</tag> element is a wrapper element and can contain any container elements such
- as a <tag class="element">para</tag> element. All content within a <tag class="element"
- >listitem</tag> element will be indented to the same level. You can also specify sub-lists
- within a <tag class="element">listitem</tag> element.</para>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="varmarkup"/> shows the markup representing <xref linkend="varexample"
- />.</para>
- <example xml:id="varmarkup">
- <title>Variable List Markup</title>
- <programlisting><variablelist xml:id="varexample">
- <title>List of Rooms</title>
- <varlistentry>
- <term>Kitchen</term>
- <listitem>
- <para>The room where food is stored and prepared.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Garage</term>
- <listitem>
- <para>Where the cars are parked.</para>
- <note>
- <para>Bikes are also here.</para>
- </note>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Living room</term>
- <term>Family room</term>
- <listitem>
- <para>This is where we watch TV.</para>
- </listitem>
- </varlistentry>
-</variablelist></programlisting>
- </example>
- </simplesect>
- </section>
- <section xml:id="GlossList">
- <title>Glossary Lists</title>
- <simplesect>
- <title>Overview</title>
- <para>A glossary list is a special case of a variable list. It is used specifically for lists
- that define terms and where you may want to refer the reader back to the definition of a
- specific term. <xref linkend="glossexample" xrefstyle="select: nopage label"/> shows a use
- of a glossary list.</para>
- <glosslist xml:id="glossexample" xreflabel="List of Terms">
- <title>List of Terms</title>
- <glossentry xml:id="consumerdef">
- <glossterm>consumer</glossterm>
- <glossdef>
- <para>The end user of a service, also called a client for that service.</para>
- </glossdef></glossentry>
- <glossentry xml:id="endptdef">
- <glossterm>endpoint</glossterm>
- <glossdef>
- <para>The point of contact that a <glossterm linkend="servicedef">service</glossterm>
- provides for its <glossterm linkend="consumerdef">consumers</glossterm>.</para>
- </glossdef></glossentry>
- <glossentry xml:id="servicedef">
- <glossterm>service</glossterm>
- <glossdef>
- <para>A collection of operations that perform a useful set of functions in a network,
- access to which is implemented as an <glossterm linkend="endptdef"
- >endpoint</glossterm>. In a service-oriented network, services are defined by a
- service contract.</para>
- </glossdef></glossentry>
- <glossentry>
- <glossterm>service consumer</glossterm>
- <glosssee otherterm="consumerdef"/></glossentry>
- </glosslist>
- </simplesect>
- <simplesect>
- <title>Specifying the list</title>
- <para>A glossary list is specified using the <tag class="element">glosslist</tag> element. If
- you want to refer back to a glossary list, you can provide values for the <tag
- class="attribute">xml:id</tag> attribute and the <tag class="attribute">xreflabel</tag>
- attribute. Like variable lists, glossary lists can have titles.</para>
- <para>The entries in a glossary list are specified using a <tag class="element"
- >glossentry</tag> element. The <tag class="element">glossentry</tag> element typically has
- two children: <tag class="element">glossterm</tag> and <tag class="element">glossdef</tag>.
- You can also use the <tag class="element">glosssee</tag> element to xref with other
- definitions.</para>
- </simplesect>
- <simplesect>
- <title>Specifying a term</title>
- <para>A <tag class="element">glossentry</tag> element can have only one <tag class="element"
- >glossterm</tag> element. This element specifies the term being defined by this entry. If
- you are going to refer back to this term, you can supply a value for the parent <tag
- class="element">glossentry</tag> element's <tag class="attribute">xml:id</tag>
- attribute.</para>
- <note>
- <para>The <tag class="element">glossterm</tag> element can also be used in text entries to
- refer to terms defined in a glossary entry. When used in this manner, you supply a value
- for the <tag class="attribute">linkend</tag> attribute.</para>
- </note>
- </simplesect>
- <simplesect>
- <title>Defining a term</title>
- <para>You define a term using either one or more <tag class="element">glossdef</tag> elements
- or a <tag class="element">glosssee</tag> element. The <tag class="element">glossdef</tag>
- element is a content element that contains markup specifying a definition. If you use more
- than one <tag class="element">glossdef</tag> element, they are treated as separate
- definitions for the same term.</para>
- <para>The <tag class="element">glosssee</tag> element redirects the reader to a term with the
- same meaning. It acts like a "See" entry in a dictionary. It has one attribute,
- <tag class="attribute">otherterm</tag>, whose value is the id of the term to which the
- reader is redirected.</para>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="glossmarkup"/> shows the markup for <xref linkend="glossexample"
- xrefstyle="select: nopage label"/>.</para>
- <example xml:id="glossmarkup" xreflabel="Example 4" pgwide="1">
- <?dbfo pgwide="1"?>
- <title>Glossary List Markup</title>
- <programlisting><glosslist xml:id="glossexample" xreflabel="List of terms";>
- <glossentry xml:id="consumerdef">
- <glossterm>consumer</glossterm>
- <glossdef>
- <para>The end user of a service, also called a
- client for that service.</para>
- </glossdef>
- </glossentry>
- <glossentry xml:id="endptdef">
- <glossterm>endpoint</glossterm>
- <glossdef>
- <para>The point of contact that a
- <glossterm linkend="servicedef">service</glossterm>
- provides for its
- <glossterm linkend="consumerdef">consumers</glossterm>.
- </para>
- </glossdef>
- </glossentry>
- <glossentry xml:id="servicedef">
- <glossterm>service</glossterm>
- <glossdef>
- <para>A collection of operations that perform a
- useful set of functions in a network, access to
- which is implemented as an
- <glossterm linkend="endptdef">endpoint</glossterm>.
- In a service-oriented network, services are defined
- by a service contract.</para>
- </glossdef>
- </glossentry>
- <glossentry>
- <glossterm>service consumer</glossterm>
- <glosssee otherterm="consumerdef" />
- </glossentry>
-</glosslist></programlisting>
- </example>
- </simplesect>
- </section>
-</chapter>
diff --git a/docs/1.6/styleguide/overview.xml b/docs/1.6/styleguide/overview.xml
deleted file mode 100644
index 8f3c09f..0000000
--- a/docs/1.6/styleguide/overview.xml
+++ /dev/null
@@ -1,149 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="overview">
- <title>Evergreen and DocBook</title>
- <section>
- <title>About our approach</title>
- <simplesect>
- <title>Overview</title>
- <para>This is the style guide for documentation produced for the Evergreen open-source library
- software project. This manual is intended to help everyone involved in the documentation
- "supply chain" by providing guidance wherever a decision about documentation formats needs
- to be made, from image size to file-naming conventions and the approved lists of tags and
- XSL stylesheets. </para>
- <para>This is a living document in a fairly new endeavor, so your feedback on areas that need
- correction or expansion is encouraged and warmly appreciated. </para>
- </simplesect>
- <simplesect>
- <title>History</title>
- <para>In May, 2009, the Evergreen Documentation Interest Group committed to single-source,
- XML, using the DocBook 5.0 documentation standard, for all Evergreen-wide documentation, and
- committed to working as a group. </para>
- <para>The rationales for this approach were as follows:</para>
- <itemizedlist>
- <listitem>
- <para>The Evergreen project needed to move past the gaps and duplicated efforts of having
- documentation written within local library systems and leverage its size and skills
- toward a common goal.</para>
- </listitem>
- <listitem>
- <para>The commitment to single-source documentation means that core Evergreen
- documentation would be could be repurposed as necessary into many different formats --
- one core set of files, many outputs.</para>
- </listitem>
- <listitem>
- <para>XML provides structure to a document and semantic "meaningfulness." </para>
- </listitem>
- <listitem>
- <para>The DocBook standard is a commonly-used documentation standard that has the
- advantages over other standards of relative ease of use and a long, well-established
- history of development and stewardship. DocBook is also the de facto standard XML schema
- and publishing tool set for a number of open source projects, so we will be able to
- capitalize on the work others have done before us.</para>
- </listitem>
- </itemizedlist>
- </simplesect>
- <simplesect>
- <title>DocBook 5.0</title>
- <para>DocBook 5.0 is the authoring language for Evergreen documentation. DocBook 5.0 provides
- a structured XML-based grammar for writing complex technical documentation. It is also an
- OASIS standard. The remainder of this style guide discusses how Evergreen uses
- DocBook.</para>
- </simplesect>
- <simplesect>
- <title>Our production model in a nutshell</title>
- <para>(Note: this primarily applies to documentation that is making its way into the Evergreen
- documentation XML toolchain for the first time. We have not yet developed a production model
- for revising XML documents.) </para>
- <para>
- <itemizedlist>
- <listitem>
- <para><emphasis role="bold">Documentation writers</emphasis> author Evergreen
- documentation in whatever format they choose (this is a guiding principal of the
- Evergreen documentation project), using the editors of their choice. While authors are
- encouraged to produce documentation in DocBook 5.0, we will accept new documentation
- in any form the author chooses to write it (and however "localized" it may be). Note
- that the DIG project will be providing heavily-commented template files for DocBook
- XML production. </para>
- </listitem>
- <listitem>
- <para>Authors submit documents to the <emphasis role="bold">intake team</emphasis>, who
- will submit the documentation to functional testing and revise content accordingly.
- </para>
- </listitem>
- <listitem>
- <para>If documentation needs conversion from its format to DocBook 5.0, the DIG
- <emphasis role="bold">XML conversion team</emphasis> wrangles it.</para>
- </listitem>
- <listitem>
- <para>One the files are in valid, well-formed XML conforming to the DocBook 5.0
- standard, <emphasis role="bold">DIG XML editors</emphasis> (the human kind of editors)
- review the files for conformance with Evergreen documentation style guidelines.</para>
- </listitem>
- <listitem>
- <para>When the XML files are ready, the <emphasis role="bold">DIG transform
- team</emphasis> members use a variety of back-end tools to process the files (or, in
- DocBook and XML terminology, <glossterm>transform</glossterm> the files) into HTML,
- PDF, and other formats. <emphasis role="bold">Web designers</emphasis> play a crucial
- role at this stage as well, creating and maintaining the Cascading Stylesheets (CSS)
- that make the documentation aesthetically pleasing and more user-friendly. Finally, a
- small group of <emphasis role="bold">"the buck stops here" editors</emphasis> move the
- HTML and PDF files into their folders on the website.</para>
- </listitem>
- </itemizedlist>
- </para>
- <para>
- </para>
- </simplesect>
- </section>
- <section>
- <title>Formatting XML</title>
- <simplesect>
- <title>Overview</title>
- <para>Documentation writers who author in XML generally fall into two camps: those who prefer
- a full-featured WYSIWYG editor with built-in validation tools, and those who prefer to code
- XML "by hand." </para>
- <para>DIG is neutral on this issue, but can recommend software for those interested in
- authoring, editing, revising, updating, or validating XML files. Documentation editors
- higher up in the XML chain will ultimately reformat all XML so it has appropriate indenting
- and wrapping. If you are using an editor such as oXygen, most of this formatting is already
- done for you by the software. If you are coding XML by hand, you are encouraged but not
- required to keep lines under 80 characters long, and to avoid leaving white space between
- elements. </para>
- </simplesect>
- <simplesect>
- <title>Validation</title>
- <para>More crucially than indenting and white space, the DIG would appreciate it if authors
- producing XML would attempt to validate their files prior to submitting them to ensure the
- markup is valid and well-formed XML that conforms with DocBook 5. However, if you run
- against insoluble validation problems, please do not let that hold you up; just submit the
- files and we will fix the problems and advise you of what we found. </para>
- </simplesect>
- </section>
- <section xml:id="info">
- <title>Other Resources</title>
- <simplesect>
- <title>DocBook References</title>
- <para>For more general references and familiarization with with DocBook, see the
- following:</para>
- <itemizedlist>
- <listitem>
- <para>
- <link xl:href="http://DocBook.org/">DocBook.org</link>
- </para>
- </listitem>
- <listitem>
- <para>
- <link xl:href="http://opensource.bureau-cornavin.com/crash-course/">The Crash Course to
- DocBook</link>
- </para>
- </listitem>
- <listitem>
- <para>
- <link xl:href="http://nwalsh.com/docbook/">Norman Walsh's DocBook page</link>
- </para>
- </listitem>
- </itemizedlist>
- </simplesect>
- </section>
-</chapter>
diff --git a/docs/1.6/styleguide/programming.xml b/docs/1.6/styleguide/programming.xml
deleted file mode 100644
index c4538fb..0000000
--- a/docs/1.6/styleguide/programming.xml
+++ /dev/null
@@ -1,493 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook"
-xmlns:xi="http://www.w3.org/2001/XInclude"
-xmlns:xl="http://www.w3.org/1999/xlink"
-version="5.0"
-xml:id="programming">
- <title>Working with Code</title>
- <info>
- <abstract>
- <para>There are several instances when you will need to show code in documentation. You may need to use a class name, an interface name,
- or an element name as part of a sentence. You will also need to provide long code samples in many places. DocBook has a number of
- elements that are used for placing code in your documentation.</para>
- </abstract>
- </info>
- <section>
- <title>Code Listings</title>
- <para>There are two types of code listings:</para>
- <itemizedlist>
- <listitem linkend="exampleSect">
- <para>Formal examples with titles</para>
- </listitem>
- <listitem linkend="codeBlockSect">
- <para>Untitled code blocks</para>
- </listitem>
- </itemizedlist>
- <para>Often when making long code listings a writer also needs to explain what specific lines of code do. This can be done using
- callouts as explained in <xref linkend="calloutSect" /></para>
- <section xml:id="exampleSect">
- <title>Examples</title>
- <simplesect>
- <title>When to use</title>
- <para>Examples are formal code listings that have a title. They are useful for code listings that are linked to from other places in
- the text. They are also added to the <emphasis>List of Examples</emphasis>.</para>
- </simplesect>
- <simplesect>
- <title>Marking up an example</title>
- <indexterm><primary>example element</primary></indexterm>
- <indexterm><primary>programlisting element</primary></indexterm>
- <para>Examples are marked up using the <tag class="element">example</tag> element. You should always provide a descriptive value for
- the <tag class="element">example</tag> element's <tag class="attribute">xml:id</tag> attribute. The
- <tag class="element">example</tag> element also takes a <tag class="attribute">pgwide</tag> attribute that signals that the
- code listing should span the width of the page.<footnote><para>The <tag class="attribute">pgwide</tag> attribute is not currently
- supported by the publication system. Writers will also need the PI for making code blocks wide as shown in
- <xref linkend="examplePgwideSS" />.</para></footnote></para>
- <para>The first child of the <tag class="element">example</tag> element is a <tag class="element">title</tag> element. The contents of
- the title element will be used as the caption of the example. It will also be used as the text for any cross references.</para>
- <para>The last child of the example element is the <tag class="element">programlisting</tag> element. The
- <tag class="element">programlisting</tag> element contains the code sample itself. Any text placed inside the
- <tag class="element">programlisting</tag> element is treated literally. Therefore, any spacing that you use will be exactly reproduced
- when the document is produced.</para>
- <warning>
- <para>When using XML inside a <tag class="element">programlisting</tag> element you must not use the <literal><</literal> or
- <literal>></literal> characters. Instead use <wordasword>&lt;</wordasword> and <wordasword>&gt;</wordasword>.</para>
- </warning>
- <para>The <tag class="element">programlisting</tag> element takes a <tag class="attribute">language</tag> attribute that
- specifies the type of code in the example. <xref linkend="languageAttrTbl"/> describes the acceptable values.</para>
- <table xml:id="languageAttrTbl">
- <title>Values for the Program Listing Language Attribute</title>
- <tgroup cols="2">
- <thead>
- <row>
- <entry>Value</entry>
- <entry>Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><tag class="attvalue">java</tag></entry>
- <entry>Specifies that the listing is Java code.</entry>
- </row>
- <row>
- <entry><tag class="attvalue">spring</tag></entry>
- <entry>Specifies that the listing is Spring XML. This is often used in configuration files.</entry>
- </row>
- <row>
- <entry><tag class="attvalue">wsdl</tag></entry>
- <entry>Specifies that the listing is WSDL.</entry>
- </row>
- <row>
- <entry><tag class="attvalue">xmlschema</tag></entry>
- <entry>Specifies that the code listing is XML Schema. This is often seen in the type's section of a WSDL document.</entry>
- </row>
- <row>
- <entry><tag class="attvalue">xml</tag></entry>
- <entry>Specifies that the code listing is XML.</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="example_example"/> shows the mark-up for an example.</para>
- <example xml:id="example_example" pgwide="1">
- <?dbfo pgwide="1"?>
- <title>Example Mark-Up</title>
- <programlisting><example id="example_example">
-<title>Example Service</title>
-<programlisting language="java">public class ServiceName extends javax.xml.ws.Service
-{
- ...
- public ServiceName(URL wsdlLocation, QName serviceName) { }
-
- public ServiceName() { }
-
- public Greeter getPortName() { }
- .
- .
- .
-}</programlisting>
-</example></programlisting>
- </example>
- <para>The mark-up shown in <xref linkend="example_example" /> is generated into <xref linkend="exampleExampleGen" />.</para>
- <example xml:id="exampleExampleGen">
- <title>Example Service</title>
- <programlisting language="java">public class ServiceName extends javax.xml.ws.Service
-{
- ...
- public ServiceName(URL wsdlLocation, QName serviceName) { }
-
- public ServiceName() { }
-
- public Greeter getPortName() { }
- .
- .
- .
-}</programlisting>
- </example>
- </simplesect>
- <simplesect xml:id="examplePgwideSS">
- <title>Making the example span the page</title>
- <para>The code used for an example does not always fit properly in the space allotted for text in the PDF output template. To fix this
- writers can specify that an example should span the entire page from the left margin to the right margin using the
- <markup><?dbfo pgwide="1"?></markup> PI.</para>
- <para>As shown in <xref linkend="examplePgwideEx"/>, the <markup><?dbfo pgwide="1"?></markup> PI is placed directly
- after the opening <tag class="element">example</tag> tag.</para>
- <example xml:id="examplePgwideEx">
- <?dbfo pgwide="1"?>
- <title>Wide Example Mark-Up</title>
- <programlisting><example id="examplePgwideEx">
-<?dbfo pgwide="1"?>
-<title>Example Service</title>
-<programlisting language="java">
- .
- .
- .
-}</programlisting>
-</example></programlisting>
- </example>
- </simplesect>
- </section>
- <section xml:id="codeBlockSect">
- <title>Code Blocks</title>
- <simplesect>
- <title>When to use</title>
- <para>Code blocks are useful for short code listings that show a specific action. They are not appropriate for code listings
- that need to be referenced later. They also do not appear in the <emphasis>List of Examples</emphasis>.</para>
- </simplesect>
- <simplesect>
- <title>Mark-up</title>
- <indexterm><primary>informalexample element</primary></indexterm>
- <indexterm><primary>programlisting element</primary></indexterm>
- <para>Code blocks are marked up using the <tag class="element">informalexample</tag> element.</para>
- <para>The only child of the <tag class="element">informalexample</tag> element is a <tag class="element">programlisting</tag> element.
- This element contains the code listing itself. Any text placed inside the <tag class="element">programlisting</tag> element is
- treated literally. Therefore, any spacing that you use will be exactly reproduced when the document is produced.</para>
- <warning>
- <para>When using XML inside a <tag class="element">programlisting</tag> element you must not use the <literal><</literal> or
- <literal>></literal> characters. Instead use <wordasword>&lt;</wordasword> and <wordasword>&gt;</wordasword>.</para>
- </warning>
- <para>The <tag class="element">programlisting</tag> element takes a <tag class="attribute">language</tag> attribute that
- specifies the type of code in the example. <xref linkend="languageAttrTbl"/> describes the acceptable values.</para>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="block_example"/> shows the mark-up for a standalone block of code.</para>
- <example xml:id="block_example" pgwide="1">
- <?dbfo pgwide="1"?>
- <title>Example Code Block</title>
- <programlisting><informalexample>
- <programlisting language="javascript">var WebServiceProvider1 = {
- 'wsdlLocation': 'file:./wsdl/hello_world.wsdl',
- 'serviceName': 'SOAPService1',
- 'portName': 'SoapPort1',
- 'targetNamespace': http://objectweb.org/hello_world_soap_http',
-};</programlisting>
-</informalexample></programlisting>
- </example>
- <para>The mark-up shown in <xref linkend="block_example"/> would be published as follows:</para>
- <informalexample>
- <programlisting language="javascript">var WebServiceProvider1 = {
- 'wsdlLocation': 'file:./wsdl/hello_world.wsdl',
- 'serviceName': 'SOAPService1',
- 'portName': 'SoapPort1',
- 'targetNamespace': 'http://objectweb.org/hello_world_soap_http',
-};</programlisting>
-</informalexample>
- </simplesect>
- <simplesect xml:id="codeBlockPgwideSS">
- <title>Making the code block span the page</title>
- <para>Code listings do not always fit properly in the space allotted for text in the PDF output template. To fix this
- writers can specify that a code listing should span the entire page from the left margin to the right margin using the
- <markup><?dbfo pgwide="1"?></markup> PI.</para>
- <para>As shown in <xref linkend="codeBlockPgwideEx"/>, the <markup><?dbfo pgwide="1"?></markup> PI is placed directly
- after the opening <tag class="element">informalexample</tag> tag.</para>
- <example xml:id="codeBlockPgwideEx">
- <?dbfo pgwide="1"?>
- <title>Wide Code Block Mark-Up</title>
- <programlisting><informalexample id="codeBlockPgwideEx">
-<?dbfo pgwide="1"?>
-<programlisting language="java">
- .
- .
- .
-}</programlisting>
-</informalexample></programlisting>
- </example>
- </simplesect>
- </section>
- <section xml:id="calloutSect">
- <title>Using Callouts</title>
- <indexterm><primary>co element</primary></indexterm>
- <indexterm><primary>calloutlist element</primary></indexterm>
- <para>It is often helpful to use callouts to explain what it happening in a section of code. Specifying callouts is a two step process:</para>
- <orderedlist>
- <listitem>
- <para>Specify where in the code listing you want to place callout markers.</para>
- </listitem>
- <listitem>
- <para>Specify the callout text for each callout.</para>
- </listitem>
- </orderedlist>
- <simplesect>
- <title>Specifying the callout locations</title>
- <para>To specify the placement of a callout in a program listing you place a <tag class="element">co</tag> element at the location inside of the program listing you want the callout to appear. The <tag class="element">co</tag> element requires that you set a value for its <tag class="attribute">id</tag> attribute. The value is used to associate the callout marker with the text that describes it. You should also provide a value for the <tag class="element">co</tag> element's <tag class="attribute">linkends</tag> attribute. This value will match the value of the <tag class="attribute">id</tag> attribute of the associated text. Using this attribute allows for a links to be generated between the callout and the associated text.</para>
- <note>
- <para>Setting the <tag class="attribute">linkends</tag> attribute before entering the callout text will result in an invalid XML file. Once you add the callout text, the file should be valid.</para>
- </note>
- </simplesect>
- <simplesect>
- <title>Specifying the callout text</title>
- <para>The text associated with a callout is specified outside of the <tag class="element">programlisting</tag> element and the <tag class="element">example</tag> element. Shortly after the <tag class="element">example</tag> element, preferably immediately after, you need to place a <tag class="element">calloutlist</tag> element. The <tag class="element">calloutlist</tag> element wraps the elements that specify the callout text. It contains an optional <tag class="element">title</tag> element and one <tag class="element">callout</tag> element for each callout specified for the associated program listing.</para>
- <para>Each <tag class="element">callout</tag> element must have its <tag class="attribute">arearefs</tag> attribute set to the value of <tag class="attribute">id</tag> attribute of the callout for which it defines the text. If you set the <tag class="attribute">linkends</tag> attribute of the associated <tag class="element">co</tag> element, you must also set the <tag class="element">callout</tag> element's <tag class="attribute">id</tag> attribute to the matching value. The callout text is the value of the <tag class="element">callout</tag> element.</para>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="callout_example"/> shows the mark-up for <olink targetptr="LinksCalloutExample"/>.</para>
- <example xml:id="callout_example" pgwide="1">
- <?dbfo pgwide="1"?>
- <title>Using Callouts</title>
- <programlisting><example xml:id="LinksCalloutExample">
-<dbfo pgwide="1"?>
- <title>Document Set Site Map</title>
- <programlisting><?xml version="1.0" encoding="utf-8"?> <co linkends="sitemapptr0" xml:id="sitemapco0"/>
-<targetset> <co linkends="sitemapptr3" xml:id="sitemapco3"/>
- <targetsetinfo> <co linkends="sitemapptr4" xml:id="sitemapco4"/>
- Site map for the Evergreen XML Style Guide
- </targetsetinfo>
- <sitemap> <co linkends="sitemapptr5" xml:id="sitemapco5"/>
- <dir name="docs_rls_inferno"> <co linkends="sitemapptr6" xml:id="sitemapco6"/>
- <dir name="fluff"> <co linkends="sitemapptr75" xml:id="sitemapco75"/>
- <dir name="overview"> <co linkends="sitemapptr7" xml:id="sitemapco7"/>
- <document targetdoc="InfernoOverview"> <co linkends="sitemapptr8" xml:id="sitemapco8"/>
- <xi:include href="overview/target.db" xmlns:xi="http://www.w3.org/2001/XInclude" /> <co linkends="sitemapptr9" xml:id="sitemapco9"/>
- </document>
- </dir>
- </dir>
- <dir name="install_guide">
- <document targetdoc="InfernoInstall">
- <xi:include href="install_guide/target.db" xmlns:xi="http://www.w3.org/2001/XInclude" />
- </document>
- </dir>
- <dir name="getting_started">
- <document targetdoc="InfernoGetStarted">
- <xi:include href="get_started/target.db" xmlns:xi="http://www.w3.org/2001/XInclude" />
- </document>
- </dir>
- </dir>
- </sitemap>
-</targetset></programlisting>
-</example>
-<calloutlist>
- <title>Elements of the Site Map</title>
- <callout arearefs="sitemapco0" xml:id="sitemapptr0">
- <para>The site map should always be encoded as UTF-8. This ensures that all of the generated target data has the same encodings regardless of the encodings used by the XML source files.</para>
- </callout>
- <callout arearefs="sitemapco3" xml:id="sitemapptr3">
- <para>The <tag class="element">targetset</tag> element is the root of the site map.</para>
- </callout>
- <callout arearefs="sitemapco4" xml:id="sitemapptr4">
- <para>The <tag class="element">targetsetinfo</tag> element allows you to provide a description for the document set or any other information that is relevant to the site map.</para>
- </callout>
- <callout arearefs="sitemapco5" xml:id="sitemapptr5">
- <para>The <tag class="element">sitemap</tag> element contains the directory layout of the output files.</para>
- </callout>
- <callout arearefs="sitemapco6" xml:id="sitemapptr6">
- <para>The name of the top-level directory is not important in the generation of the target databases for the links. The links are generated relative to the top-level directory.</para>
- </callout>
- <callout arearefs="sitemapco75" xml:id="sitemapptr75">
- <para>This is a directory that only contains other directories.</para>
- </callout>
- <callout arearefs="sitemapco7" xml:id="sitemapptr7">
- <para>This directory holds a generated book.</para>
- </callout>
- <callout arearefs="sitemapco8" xml:id="sitemapptr8">
- <para>The <tag class="element">document</tag> element's <tag class="attribute">targetdoc</tag> attribute specifies the identifier used in the <tag class="element">olink</tag> element's <tag class="attribute">targetdoc</tag> attribute when linking to targets in the document.</para>
- </callout>
- <callout arearefs="sitemapco9" xml:id="sitemapptr9">
- <para>The target database is included in the site map using an <tag class="element">xi:include</tag> element. The path for each book's target database should be <filename><replaceable>book_src_dir</replaceable>/target.db</filename>.</para>
- </callout>
-</calloutlist></programlisting>
- </example>
- </simplesect>
- </section>
- </section>
- <section xml:id="prog_arts">
- <title>In-line Code</title>
- <simplesect>
- <title>DocBook programming elements</title>
- <para>There are many instances where you need to place a code artifact in a block of text such as when you are referring to a Java class
- or an XML element. DocBook has a number of specialized elements for placing code artifacts in-line. The ones commonly used
- include:</para>
- <itemizedlist>
- <listitem>
- <para><tag class="element">tag</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">classname</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">interfacename</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">methodname</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">uri</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">package</tag></para>
- </listitem>
- <listitem>
- <para><tag class="element">code</tag></para>
- </listitem>
- </itemizedlist>
- </simplesect>
- <simplesect>
- <title>XML artifacts</title>
- <para>When placing XML artifacts such as element names or attribute names in your text wrap them in an
- <tag class="element">tag</tag> element. To specify the type of XML artifact, the <tag class="element">tag</tag> element's
- <tag class="attribute">class</tag> attribute is always used. <xref linkend="class_values"/> shows the values used for the
- <tag class="attribute">class</tag> attribute.</para>
- <table xml:id="class_values">
- <title>Values for the <tag class="attribute">class</tag> Attribute</title>
- <tgroup cols="2">
- <colspec colwidth="1.5in"/>
- <thead>
- <row>
- <entry>Value</entry>
- <entry>Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><tag class="attvalue">attribute</tag></entry>
- <entry>Specifies that the artifact is an attribute of an XML element.</entry>
- </row>
- <row>
- <entry><tag class="attvalue">element</tag></entry>
- <entry>Specifies that the artifact is an XML element.</entry>
- </row>
- <row>
- <entry><tag class="attvalue">attvalue</tag></entry>
- <entry>Specifies that the artifact is the value of an XML element's attribute.</entry>
- </row>
- <row>
- <entry><tag class="attvalue">emptytag</tag></entry>
- <entry>Specifies an XML element that does not hold any data such as <tag class="emptytag">foo</tag>.</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </simplesect>
- <simplesect>
- <title>Web Addresses, URIs, and E-Mail Addresses</title>
- <para>To specify a Web address or URI you use the <tag class="element">uri</tag> element.</para>
- <para>To specify an E-Mail address use the <tag class="element">email</tag> element.</para>
- </simplesect>
- <simplesect xml:id="gen_prog_arts">
- <title>General programming language artifacts</title>
- <para>DocBook defines a number of in-line tags for specifying programming artifacts. The commonly used tags are listed in
- <xref linkend="progarti"/>.</para>
- <table frame="all" xml:id="progarti">
- <title>Elements for In-Line Programming Artifacts</title>
- <tgroup cols="2">
- <colspec colnum="1" colname="c1" colwidth="1.5in"/>
- <colspec colnum="2" colname="c2"/>
- <thead>
- <row>
- <entry>Element</entry>
- <entry>Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><tag class="element">type</tag></entry>
- <entry>Specifies that the artifact is a data type such as <type>int</type>.</entry>
- </row>
- <row>
- <entry><tag class="element">constant</tag></entry>
- <entry>Specifies that the artifact is a constant such as <constant>NULL</constant> or <constant>9</constant>.</entry>
- </row>
- <row>
- <entry><tag class="element">exceptionname</tag></entry>
- <entry>Specifies that the artifact is an exception. It could be the name of the exception or the name of the class that
- implements the exception.</entry>
- </row>
- <row>
- <entry><tag class="element">function</tag></entry>
- <entry>Specifies that the artifact is a function such as <function>println()</function>.</entry>
- </row>
- <row>
- <entry><tag class="element">parameter</tag></entry>
- <entry>Specifies that the artifact is a parameter to a function or a method.</entry>
- </row>
- <row>
- <entry><tag class="element">varname</tag></entry>
- <entry>Specifies that the artifact is a variable.</entry>
- </row>
- <row>
- <entry><tag class="element">code</tag></entry>
- <entry>Used for generic code entries that do not fit into any other category.</entry>
- </row>
- <row>
- <entry><markup>code role="annotation"</markup></entry>
- <entry>Used for Java annotations.</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </simplesect>
- <simplesect>
- <title>Object-oriented programming language artifacts</title>
- <para>In addition to the elements listed in <xref linkend="gen_prog_arts"/>, DocBook defines a number of elements that are used
- specifically for object-oriented programming artifacts. They are listed in <xref linkend="oo_arts"/>.</para>
- <table frame="all" xml:id="oo_arts">
- <title>Elements for In-Line OO Programming Artifacts</title>
- <tgroup cols="2">
- <colspec colnum="1" colname="c1" colwidth="1.5in"/>
- <colspec colnum="2" colname="c2"/>
- <thead>
- <row>
- <entry>Element</entry>
- <entry>Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><tag class="element">interfacename</tag></entry>
- <entry>Specifies that the artifact is a Java interface the user must implement.</entry>
- </row>
- <row>
- <entry><tag class="element">oointerface</tag></entry>
- <entry>Specifies that the artifact is a Java interface the user must implement. Requires the use of an <tag class="element">modifier</tag> element that contains details about if the interface is public or private.</entry>
- </row>
- <row>
- <entry><tag class="element">classname</tag></entry>
- <entry>Specifies that the artifact is a Java class or an instantiated object.</entry>
- </row>
- <row>
- <entry><tag class="element">ooclass</tag></entry>
- <entry>Specifies that the artifact is a Java class. Requires the use of an <tag class="element">modifier</tag> element that
- contains details about if the class is public/private or static/final.</entry>
- </row>
- <row>
- <entry><tag class="element">methodname</tag></entry>
- <entry>Specifies that the artifact is a method. Methods are different from functions in that methods are associated with classes and objects.</entry>
- </row>
- <row>
- <entry><tag class="element">ooexception</tag></entry>
- <entry>Specifies that the artifact is a Java exception. Requires the use of an <tag class="element">modifier</tag> element that
- contains details about if the exception is public or private.</entry>
- </row>
- <row>
- <entry><tag class="element">package</tag></entry>
- <entry>Specifies that the artifact is the name of a Java or C++ package.</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </simplesect>
- </section>
-</chapter>
\ No newline at end of file
diff --git a/docs/1.6/styleguide/structure.xml b/docs/1.6/styleguide/structure.xml
deleted file mode 100644
index fcd46c2..0000000
--- a/docs/1.6/styleguide/structure.xml
+++ /dev/null
@@ -1,133 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="structure">
- <title>The Structure of Evergreen Documentation</title>
- <info>
- <abstract>
- <para>This chapter describes the structure of Evergreen documentation, common elements in XML
- files, and allowable documentation types.</para>
- </abstract>
- </info>
- <section>
- <title>Top-level Elements in Evergreen Documentation</title>
- <simplesect>
- <title>Overview</title>
- <para>There are two central books for Evergreen documentation, organized within a single set.
- The documentation files are arranged it hierarchically, beginning with docs, followed by the
- version:</para>
- <para>http://evergreen-ils.org/docs/1.6 ...</para>
- <para>The following is a common structural pattern for our documentation:</para>
- <itemizedlist>
- <listitem>
- <para><emphasis role="bold"><tag class="element">set</tag></emphasis></para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">book</tag></emphasis></para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis>--a major topic
- area, such as Circulation</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">section</tag></emphasis>--a subsection of
- an area, such as Patron Registration</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">simplesect</tag></emphasis>--subdivision
- of section, such as Family Accounts</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">para</tag></emphasis>--a basic paragraph
- marker</para>
- </listitem>
- </itemizedlist>
- <para>Most authors will be working at the <tag class="element">chapter</tag> or <tag
- class="element">section</tag> level. Chapters are created in separate files and imported
- into the book file using <tag class="element">xinclude</tag> elements.</para>
- <para>There are many more DocBook elements. The above is only intended to be illustrative of
- the "tree" that shapes Evergreen documentation. There are also exceptions to the "chapter"
- element, such as the <tag class="element" revision="">glossary</tag> element. </para>
- <para>The final chapter of this styleguide lists excluded tags for Evergreen documentation.
- </para>
- </simplesect>
- </section>
- <section>
- <title>The Sets and Chapters of Evergreen Documentation</title>
- <simplesect>
- <title>Overview</title>
- <para>Evergreen documentation has the following high-level set, books, and chapters. Filenames
- are in parentheses:</para>
- <para>
- <itemizedlist>
- <listitem>
- <para><emphasis role="bold"><tag class="element">set</tag></emphasis> (set.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">book</tag></emphasis> Evergreen
- Technical Reference (book1.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> Installing
- (installing.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> Upgrading
- (upgrading.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> Migrating from
- other Integrated Library Systems (migrating.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> System
- Administration (sysadmin.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> Software
- Developers' Reference (softwaredev.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> Web
- Developers' Reference (webdev.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">book</tag></emphasis> Evergreen (?)
- Reference (book2.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> Local
- Administration (localadmin.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> The OPAC
- (opac.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> Cataloging
- (cataloging.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> Circulation
- (circulation.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> Reports
- (reports.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> Acquisitions
- (acquisitions.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> Future
- Development (futuredev.xml)</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold"><tag class="element">chapter</tag></emphasis> Glossary
- (glossary.xml)</para>
- </listitem>
- </itemizedlist>
- </para>
- </simplesect>
- </section>
-</chapter>
diff --git a/docs/1.6/styleguide/styleguide.xml b/docs/1.6/styleguide/styleguide.xml
deleted file mode 100644
index 32bd252..0000000
--- a/docs/1.6/styleguide/styleguide.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<book xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="styleguide">
- <title>Evergreen Documentation Style Guide (Draft .01)</title>
-
- <info>
- <pubdate><?dbtimestamp format="d b Y"?></pubdate>
- </info>
- <xi:include href="overview.xml"/>
- <xi:include href="authoring.xml"/>
- <xi:include href="structure.xml"/>
- <xi:include href="books.xml"/>
- <xi:include href="filenames.xml"/>
- <xi:include href="chapter.xml"/>
- <xi:include href="indexterms.xml"/>
- <xi:include href="figures.xml"/>
- <xi:include href="lists.xml"/>
- <xi:include href="tables.xml"/>
- <xi:include href="admon.xml"/>
- <xi:include href="links.xml"/>
- <xi:include href="general.xml"/>
- <xi:include href="exclude.xml"/>
- <xi:include href="programming.xml"/>
- <xi:include href="glossary.xml"/>
- <index/>
-</book>
diff --git a/docs/1.6/styleguide/tables.xml b/docs/1.6/styleguide/tables.xml
deleted file mode 100644
index d5f6f0a..0000000
--- a/docs/1.6/styleguide/tables.xml
+++ /dev/null
@@ -1,818 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook"
-xmlns:xi="http://www.w3.org/2001/XInclude"
-xmlns:xl="http://www.w3.org/1999/xlink"
-version="5.0"
-xml:id="tables">
- <title>Tables</title>
- <section>
- <title>Types of Tables</title>
- <para>There are two types of tables in DocBook:</para>
- <itemizedlist>
- <listitem>
- <para>Informal tables</para>
- </listitem>
- <listitem>
- <para>Tables</para>
- </listitem>
- </itemizedlist>
- <para>An informal table is simply a table that does not have a title. Tables
-must have a title element and are listed in a list of tables if it is
-generated.</para>
- </section>
- <section>
- <title>Specifying a Table</title>
- <para>Both informal tables and tables use the same markup elements to define
-their structure. The differences are as follows:</para>
- <itemizedlist>
- <listitem>
- <para>Informal tables are specified using the <tag class="element">informaltable</tag> element and tables are specified using
-the <tag class="element">table</tag> element.</para>
- </listitem>
- <listitem>
- <para>Informal tables cannot contain a <tag class="element">title</tag> element and tables require a <tag class="element">title</tag> element.</para>
- </listitem>
- </itemizedlist>
- <para>Creating a table involves the following steps:</para>
- <procedure>
- <step>
- <para>Specify the proper root element.</para>
- </step>
- <step>
- <para>If you are creating a table, add a <tag class="element">title</tag> element.</para>
- </step>
- <step>
- <para>Add a <tag class="element">tgroup</tag> element to wrap the
-contents of the table.</para>
- </step>
- <step>
- <para>If needed, add <tag class="element">colspec</tag> elements to
-specify properties for specific columns.</para>
- </step>
- <step>
- <para>If needed, add <tag class="element">spanspec</tag> elements to
-define reusable column spans.</para>
- </step>
- <step>
- <para>If desired, add a <tag>thead</tag> element to specify a header
-row.</para>
- <substeps>
- <step>
- <para>Add a <tag class="element">row</tag> element.</para>
- </step>
- <step>
- <para>Add an <tag class="element">entry</tag> element for each column
-heading.</para>
- </step>
- </substeps>
- </step>
- <step>
- <para>Add a <tag class="element">tbody</tag> element to contain the
-body of the table.</para>
- <substeps>
- <step>
- <para>Add one <tag class="element">row</tag> element for each row in
-the table.</para>
- </step>
- <step>
- <para>In the <tag class="element">row</tag> elements, add an <tag class="element">entry</tag> element for each value that appear in the
-row.</para>
- </step>
- </substeps>
- </step>
- </procedure>
- <section>
- <title>Table Root Elements</title>
- <para>Depending on the type of table you are using you will use either the
-<tag class="element">informaltable</tag> element or the <tag class="element">table</tag> element as the root element of your table.
-Both elements use the attributes listed in <xref linkend="rootattrs"/>.</para>
- <table frame="all" xml:id="rootattrs" pgwide="1">
- <title>Attributes for <tag class="element">table</tag> Element and <tag class="element">informaltable</tag> Element</title>
- <tgroup cols="3" colsep="1" rowsep="1">
- <colspec colwidth="1.5in"/>
- <thead>
- <row>
- <entry align="center">Attribute</entry>
- <entry align="center">Description</entry>
- <entry align="center">Values</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <indexterm><primary>table</primary><secondary>pgwide</secondary></indexterm>
- <tag class="attribute">pgwide</tag>
- </entry>
- <entry>Specifies whether the table will be span the whole page in PDF output.</entry>
- <entry><tag class="attvalue">0</tag> (default), <tag class="attvalue">1</tag></entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">colsep</tag>
- </entry>
- <entry>Specifies whether a rule will be drawn between the columns in the table.</entry>
- <entry><tag class="attvalue">0</tag>, <tag class="attvalue">1</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">frame</tag>
- </entry>
- <entry>Specifies how the table will be framed.</entry>
- <entry><tag class="attvalue">all</tag>, <tag class="attvalue">bottom</tag>, <tag class="attvalue">none</tag>, <tag class="attvalue">sides</tag>, <tag class="attvalue">top</tag>, <tag class="attvalue">topbot</tag></entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">orient</tag>
- </entry>
- <entry>Specifies how the table will be oriented in relationship to the rest of the text.</entry>
- <entry><tag class="attvalue">land</tag>, <tag class="attvalue">port</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">rowsep</tag>
- </entry>
- <entry>Specifies whether a rule will be drawn between the rows in the table.</entry>
- <entry><tag class="attvalue">0</tag>, <tag class="attvalue">1</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">xml:id</tag>
- </entry>
- <entry>Specifies a unique identifier used to reference the table.</entry>
- <entry>a unique string</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">xreflabel</tag>
- </entry>
- <entry>
- <para>Specifies a label to be used when cross referencing the table.</para>
- </entry>
- <entry>a string</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- <note>
- <para>Attributes not listed in <xref linkend="rootattrs"/> are not used in Evergreen' documentation.</para>
- </note>
- </section>
- <section>
- <title>The tgroup Element</title>
- <indexterm><primary>tgroup</primary></indexterm>
- <para>The <tag class="element">tgroup</tag> element groups together the logical components of a table. It specifies the number of columns in a table and contains the column and span specifications used by the table. All of the rows, including the header, are defined inside of the <tag class="element">tgroup</tag> element.</para>
- <para>While most tables contain a single <tag class="element">tgroup</tag> element, it is possible for a complex table to have multiple tgroup elements. In such a case, each <tag class="element">tgroup</tag> element would define a unique portion of table where the columns and spans had different specifications.</para>
- <simplesect>
- <title>Attributes</title>
- <para><xref linkend="tgroupattrs"/> shows the attributes for the <tag class="element">tgroup</tag> element. Attributes in the <tag class="element">tgroup</tag> element override the corresponding attributes
-from the table's root element.</para>
- <table xml:id="tgroupattrs" pgwide="1">
- <title>Attributes for the <tag class="element">tgroup</tag> Element</title>
- <tgroup cols="3">
- <colspec colwidth="1.5in"/>
- <thead>
- <row>
- <entry align="center">Attribute</entry>
- <entry align="center">Description</entry>
- <entry align="center">Values</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <tag class="attribute">colsep</tag>
- </entry>
- <entry>Specifies whether a rule will be drawn between the columns of the group.</entry>
- <entry><tag class="attvalue">0</tag>, <tag class="attvalue">1</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">rowsep</tag>
- </entry>
- <entry>Specifies whether a rule will be drawn between the rows of the group.</entry>
- <entry><tag class="attvalue">0</tag>, <tag class="attvalue">1</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag>align</tag>
- </entry>
- <entry>Specifies the horizontal alignment of the entries in the group.</entry>
- <entry><tag class="attvalue">center</tag>, <tag class="attvalue">justify</tag>, <tag class="attvalue">right</tag>, <tag class="attvalue">left</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag>cols</tag>
- </entry>
- <entry>A required attribute that specifies the number of columns in the group.</entry>
- <entry>>=1</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- <note>
- <para>Attributes not listed in <xref linkend="tgroupattrs"/> are not used in Evergreen' documentation.</para>
- </note>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="groupexample"/> shows the markup for a <tag class="element">tgroup</tag> element that defines a 3 column table.</para>
- <informalexample xml:id="groupexample" xreflabel="The following">
- <programlisting><informaltable ...>
- <tgroup cols="3" colsep="1" rowsep="1" >
- ...
- </tgroup>
-</table></programlisting>
- </informalexample>
- </simplesect>
- </section>
- <section xml:id="ColProps">
- <title>Specifying Column Properties</title>
- <para>If you desire, you can specify a number of the display properties for
-the column in a table by adding <tag class="element">colspec</tag>
-elements to a <tag class="element">tgroup</tag> element. A <tag class="element">colspec</tag> element defines properties for all of the
-entries in one column in a group. You can set different properties for each
-column in a group.</para>
- <simplesect>
- <title>Attributes</title>
- <para><xref linkend="colattrs"/> shows the attributes for the <tag class="element">colspec</tag> element. Attributes in the <tag class="element">colspec</tag> element override corresponding attributes in
-the parent <tag class="element">tgroup</tag> element and the table's
-root element.</para>
- <table xml:id="colattrs" pgwide="1">
- <title>Attributes for the <tag class="element">colspec</tag> Element</title>
- <tgroup cols="3">
- <colspec colwidth="1.5in"/>
- <thead>
- <row>
- <entry align="center">Attribute</entry>
- <entry align="center">Description</entry>
- <entry align="center">Values</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <tag class="attribute">colsep</tag>
- </entry>
- <entry>Specifies whether a rule will be drawn to the right of entries in the column.</entry>
- <entry><tag class="attvalue">0</tag>, <tag class="attvalue">1</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">rowsep</tag>
- </entry>
- <entry>Specifies whether a rule will be drawn between the rows in the column.</entry>
- <entry><tag class="attvalue">0</tag>, <tag class="attvalue">1</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag>align</tag>
- </entry>
- <entry>Specifies the horizontal alignment of the entries in the column.</entry>
- <entry><tag class="attvalue">center</tag>, <tag class="attvalue">justify</tag>, <tag class="attvalue">right</tag>, <tag class="attvalue">left</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag>colnum</tag>
- </entry>
- <entry>Specifies the number of the column being specified.</entry>
- <entry>1<=<replaceable>X</replaceable><=number of columns</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">colname</tag>
- </entry>
- <entry>Specifies a unique identifier by which the column can be referenced by other elements in the group.</entry>
- <entry>a unique string</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">colwidth</tag>
- </entry>
- <entry>Specifies the width of the column.</entry>
- <entry>Can be either a fixed measure using either points (pts), inches (in), or centimeters (cm).</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- <note>
- <para>Attributes not listed in <xref linkend="colattrs"/> are not used in Evergreen' documentation.</para>
- </note>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="colspecexample"/> shows the markup for specifying a
-column that is two inches wide and whose content is justified.</para>
- <example xml:id="colspecexample">
- <?dbfo pgwide="1"?>
- <title>Setting Column Properties</title>
- <programlisting><table ...>
- <title>...</title>
- <tgroup ... >
- <colspec align="justify" colwidth="2in" colname="2incol" />
- ...
- </tgroup>
-</table></programlisting>
- </example>
- </simplesect>
- </section>
- <section xml:id="SpanProps">
- <title>Defining Spans</title>
- <para>DocBook allows you to define properties for cells that span columns and
-name them for use by the cells in the group. To define a span you use the
-<tag class="element">spanspec</tag> element.</para>
- <simplesect>
- <title>Required Attributes</title>
- <para>The <tag class="element">spanspec</tag> element has three
-required attributes as described in <xref linkend="spanreqattrs"/>.</para>
- <table xml:id="spanreqattrs" pgwide="1">
- <title>Required Attributes for the <tag class="element">spanspec</tag> Element</title>
- <tgroup cols="2">
- <colspec colwidth="1.5in"/>
- <thead>
- <row>
- <entry align="center">Attribute</entry>
- <entry align="center">Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <tag class="attribute">spanname</tag>
- </entry>
- <entry>Specifies the name by which cells will refer to the span.</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">namest</tag>
- </entry>
- <entry>Specifies the name, as declared in a <tag class="element">colspec</tag> element's <tag class="attribute">colname</tag> attribute, of the starting column for the span.</entry>
- </row>
- <row>
- <entry>
- <tag>nameend</tag>
- </entry>
- <entry>Specifies the name, as declared in a <tag class="element">colspec</tag> element's <tag class="attribute">colname</tag> attribute, of the ending column for the span.</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </simplesect>
- <simplesect>
- <title>Optional Attributes</title>
- <para>In addition to the required attributes, the <tag class="element">spanspec</tag> element can also have the attributes
-described in <xref linkend="spanoptattrs"/>. Attributes in the <tag class="element">spanspec</tag> element override corresponding attributes
-in the parent <tag class="element">tgroup</tag> element and the
-table's root element.</para>
- <table xml:id="spanoptattrs" pgwide="1">
- <title>Optional Attributes for the <tag class="element">spanspec</tag> Element</title>
- <tgroup cols="3">
- <colspec colwidth="1.5in"/>
- <thead>
- <row>
- <entry align="center">Attribute</entry>
- <entry align="center">Description</entry>
- <entry align="center">Values</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <tag class="attribute">colsep</tag>
- </entry>
- <entry>Specifies whether a rule will be drawn to the right of entries in the span.</entry>
- <entry><tag class="attvalue">0</tag>, <tag class="attvalue">1</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">rowsep</tag>
- </entry>
- <entry>Specifies whether a rule will be drawn below the rows in the span.</entry>
- <entry><tag class="attvalue">0</tag>, <tag class="attvalue">1</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag>align</tag>
- </entry>
- <entry>Specifies the horizontal alignment of the entry in the span.</entry>
- <entry><tag class="attvalue">center</tag>, <tag class="attvalue">justify</tag>, <tag class="attvalue">right</tag>, <tag class="attvalue">left</tag> (default)</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- <note>
- <para>Attributes not listed in <xref linkend="spanoptattrs"/> are not used in Evergreen' documentation.</para>
- </note>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="spanexample"/> shows the markup for a span that crosses
-the second and third column of a five column table. The contents of the span
-are centered.</para>
- <example xml:id="spanexample">
- <?dbfo pgwide="1"?>
- <title>Defining a Span</title>
- <programlisting><informaltable ...>
- <tgroup cols="5" >
- <colspec colnum="2" colname="c2" />
- <colspec colnum="3" colname="c3" />
- <spanspec spanname="midspan" namest="c2" nameend="c3"
- align="center" />
- ...
-</informaltable></programlisting>
- </example>
- </simplesect>
- </section>
- <section xml:id="TableHead">
- <title>Adding a Heading Row to a Table</title>
- <para>Tables in Evergreen documentation generally have one heading row. They are specified
-using a <tag class="element">thead</tag> element. The <tag class="element">thead</tag> element is a child of a
-<tag>tgroup</tag> element. It must be placed after any <tag class="element">colspec</tag> elements and <tag class="element">spanspec</tag> elements. It should also be placed before
-any <tag class="element">tbody</tag> elements.</para>
- <simplesect>
- <title>Attributes</title>
- <para><xref linkend="theadattrs"/> lists the attributes of the <tag class="element">thead</tag> element.</para>
- <table xml:id="theadattrs" pgwide="1">
- <title>Attributes for the <tag class="element">thead</tag> Element</title>
- <tgroup cols="3">
- <colspec colwidth="1.5in"/>
- <thead>
- <row>
- <entry align="center">Attribute</entry>
- <entry align="center">Description</entry>
- <entry align="center">Values</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <tag>valign</tag>
- </entry>
- <entry>Specifies the vertical alignment of the entry in the heading.</entry>
- <entry><tag class="attvalue">top</tag>, <tag class="attvalue">bottom</tag>, <tag class="attvalue">middle</tag> (default)</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </simplesect>
- <simplesect>
- <title>Adding content</title>
- <para>The content of the heading row is specified using a single <tag class="element">row</tag> element and one entry <tag class="element">child</tag> element for each column in the table. For more
-information on the row element and the entry element see <xref linkend="rowsect"/> and <xref linkend="entrysect"/>.</para>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="theadexample"/> shows the markup for tables used in this
-chapter.</para>
- <example xml:id="theadexample">
- <title>Adding a Table Header</title>
- <programlisting><table ...>
- <tgroup cols="3" >
- <colspec ... />
- <thead>
- <row>
- <entry align="center">
- Attribute
- </entry>
- <entry align="center">
- Description
- </entry>
- <entry align="center">
- Values
- </entry>
- </row>
- </thead>
- ...
- </tgroup>
-</informaltable></programlisting>
- </example>
- </simplesect>
- </section>
- <section xml:id="TableRows">
- <title>Adding Rows to a Table</title>
- <para>The rows that make up the body of a table are defined inside of a
-<tag class="element">tbody</tag> element. Each row in the table is
-defined using a <tag class="element">row</tag> element. The contents
-of each column in the row is defined using an <tag class="element">entry</tag> element.</para>
- <simplesect>
- <title>The <tag class="element">tbody</tag> Element</title>
- <para>The <tag class="element">tbody</tag> element is a wrapper for
-all of the rows in the body of a group. It is placed after all of the <tag class="element">colspec</tag> elements, all of the <tag class="element">spanspec</tag> elements, and the <tag class="element">thead</tag> element. It has a single attribute, <tag class="attribute">valign</tag>, that is described in <xref linkend="theadattrs"/>.</para>
- </simplesect>
- <simplesect xml:id="rowsect">
- <title>The <tag class="element">row</tag> Element</title>
- <para>Rows in a table are defined using the <tag>row</tag> element.
-Each <tag>row</tag> element wraps a number of <tag>entry</tag>
-children elements that cannot exceed the number columns specified in the
-<tag>tgroup</tag> element's <tag>cols</tag> attribute. It is
-possible to have less <tag>entry</tag> child elements. This can happen
-when you wish to have empty columns, when one entry spans multiple columns, or
-if there is an entry from a previous row that vertically spans the row being
-specified.</para>
- <important>
- <para>When spans are being used the number of <tag>entry</tag>
-elements plus the number of columns being spanned cannot add up to more than
-the number of columns defined for the group.</para>
- </important>
- <para>The <tag class="element">row</tag> element has two attributes as
-described in <xref linkend="rowattrs"/>. Attributes in the <tag class="element">row</tag> element override corresponding attributes in the
-parent <tag class="element">tbody</tag> element, the enclosing
-<tag class="element">tgroup</tag> element, the <tag class="element">colspec</tag> elements in the group, and the table's root
-element.</para>
- <table xml:id="rowattrs" pgwide="1">
- <title>Attributes for the <tag class="element">row</tag> Element</title>
- <tgroup cols="3">
- <colspec colwidth="1.5in"/>
- <thead>
- <row>
- <entry align="center">Attribute</entry>
- <entry align="center">Description</entry>
- <entry align="center">Values</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <tag class="attribute">rowsep</tag>
- </entry>
- <entry>Specifies whether a rule will be drawn below all of the entries in the row.</entry>
- <entry><tag class="attvalue">0</tag>, <tag class="attvalue">1</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag>valign</tag>
- </entry>
- <entry>Specifies the vertical alignment of the entry in the heading.</entry>
- <entry><tag class="attvalue">top</tag>, <tag class="attvalue">bottom</tag>, <tag class="attvalue">middle</tag> (default)</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </simplesect>
- <simplesect xml:id="entrysect">
- <title>The <tag class="element">entry</tag> Element</title>
- <para>The contents of of a table are specified using <tag>entry</tag>
-elements. <tag>entry</tag> elements are children of the
-<tag>row</tag> element and hold the contents for a column in the
-row.</para>
- <para>The contents of a table entry can be specified using either text with
-in-line markup elements or using block-level markup elements such as the
-<tag class="element">para</tag> element, the <tag class="element">procedure</tag> element, or one of the list types.
-However, if you intend to use one of the block-level markup elements you must
-place all of the content inside a block-level element. For example, if you
-want to use a list in a table entry, along with some text outside the list,
-you must place all of the content, including the list, inside a <tag class="element">para</tag> element.</para>
- <para>The <tag class="element">entry</tag> element's attributes are
-described in <xref linkend="entryattrs"/>. Attributes in the <tag class="element">entry</tag> element override corresponding attributes in
-the parent <tag class="element">row</tag> element, the enclosing
-<tag class="element">tbody</tag> element, the enclosing <tag class="element">tgroup</tag> element, the <tag class="element">colspec</tag> elements in the group, the <tag class="element">spansec</tag> elements in the group, and the table's root
-element.</para>
- <table xml:id="entryattrs" pgwide="1">
- <title>Attributes for the <tag class="element">entry</tag> Element</title>
- <tgroup cols="3">
- <colspec colwidth="1.5in"/>
- <thead>
- <row>
- <entry align="center">Attribute</entry>
- <entry align="center">Description</entry>
- <entry align="center">Values</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <tag class="attribute">rowsep</tag>
- </entry>
- <entry>Specifies whether a rule will be drawn below the entry.</entry>
- <entry><tag class="attvalue">0</tag>, <tag class="attvalue">1</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag>valign</tag>
- </entry>
- <entry>Specifies the vertical alignment of the entry.</entry>
- <entry><tag class="attvalue">top</tag>, <tag class="attvalue">bottom</tag>, <tag class="attvalue">middle</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">colsep</tag>
- </entry>
- <entry>Specifies whether a rule will be drawn to the right of the entry.</entry>
- <entry><tag class="attvalue">0</tag>, <tag class="attvalue">1</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">namest</tag>
- </entry>
- <entry>Specifies the name of the left-most column the entry will span.</entry>
- <entry>The value of the <tag class="attribute">name</tag> attribute of the <tag class="element">colspec</tag> element defining the left-most column of the span.</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">nameend</tag>
- </entry>
- <entry>Specifies the right-most column the entry will span.</entry>
- <entry>The value of the <tag class="attribute">name</tag> attribute of the <tag class="element">colspec</tag> element defining the right-most column of the span.</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">spanname</tag>
- </entry>
- <entry>Specifies a defined span to use for the entry. This attribute should not be used with <tag class="attribute">namest</tag> and <tag class="attribute">nameend</tag>.</entry>
- <entry>The value of the <tag class="attribute">name</tag> attribute of the <tag class="element">spanspec</tag> element defining the span to use for the entry.</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">align</tag>
- </entry>
- <entry>Specifies the horizontal alignment of the contents in the entry.</entry>
- <entry><tag class="attvalue">center</tag>, <tag class="attvalue">justify</tag>, <tag class="attvalue">right</tag>, <tag class="attvalue">left</tag> (default)</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">morerows</tag>
- </entry>
- <entry>Specifies the number of additional rows the entry will span.</entry>
- <entry>>1</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">colname</tag>
- </entry>
- <entry>
- <para>Specifies the column, defined by a <tag class="element">colspec</tag> element, in which the entry belongs.</para>
- <para><emphasis role="bold">Note: </emphasis>You must specify entries rom left to right.</para>
- </entry>
- <entry>The value of the <tag class="attribute">name</tag> attribute of the <tag class="element">colspec</tag> element defining the column of the span.</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- <note>
- <para>Attributes not listed in <xref linkend="entryattrs"/> are not used in Evergreen' documentation.</para>
- </note>
- </simplesect>
- <simplesect>
- <title>Example</title>
- <para><xref linkend="tbodyexample"/> shows the markup for tables used in this
-chapter.</para>
- <example xml:id="tbodyexample">
- <?dbfo pgwide="1"?>
- <title>Add Rows to a Table</title>
- <programlisting><table ...>
- <tgroup cols="3" >
- <colspec ... />
- ...
- <tbody>
- <row>
- <entry>
- <tag class="attribute">colsep</tag>
- </entry>
- <entry>Specifies whether a rule will be drawn to
- the right of entries in the span.</entry>
- <entry>
- <tag class="attvalue">0</tag>,
- <tag class="attvalue">1</tag>
- (default)</entry>
- </row>
- <row>
- <entry>
- <tag class="attribute">rowsep</tag>
- </entry>
- <entry>Specifies whether a rule will be drawn below
- the rows in the span.</entry>
- <entry>
- <tag class="attvalue">0</tag>,
- <tag class="attvalue">1</tag>
- (default)</entry>
- </row>
- <row>
- <entry><tag>align</tag></entry>
- <entry>Specifies the horizontal alignment of
- the entry in the span.</entry>
- <entry>
- <tag class="attvalue">center</tag>,
- <tag class="attvalue">justify</tag>,
- <tag class="attvalue">right</tag>,
- <tag class="attvalue">left</tag>
- (default)</entry>
- </row>
- </tbody>
- </tgroup>
-</informaltable></programlisting>
- </example>
- </simplesect>
- </section>
- <section>
- <title>Example</title>
- <para><xref linkend="tableexample"/> shows a table that uses most of the
-features of a table.</para>
- <table xml:id="tableexample" pgwide="1">
- <title>Complicated Table</title>
- <tgroup cols="6">
- <colspec colnum="1" colname="c1" align="center"/>
- <colspec colnum="2" colname="c2" align="justify"/>
- <colspec colname="c3"/>
- <colspec colnum="4" colname="c4"/>
- <colspec colnum="5" colname="c5" align="right"/>
- <colspec colname="c6" align="left"/>
- <spanspec namest="c2" nameend="c5" spanname="25" align="center"/>
- <spanspec namest="c1" nameend="c4" spanname="14" align="left"/>
- <thead>
- <row>
- <entry>c1</entry>
- <entry>c2</entry>
- <entry>c3</entry>
- <entry>c4</entry>
- <entry>c5</entry>
- <entry>c6</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>Pomegranate</entry>
- <entry>Pineapple</entry>
- <entry>Mango</entry>
- <entry>Carambola</entry>
- <entry>Banana</entry>
- <entry>Papaya</entry>
- </row>
- <row>
- <entry>Apples</entry>
- <entry align="right">Kiwis</entry>
- <entry namest="c3" nameend="c5" align="center">Passion Fruits</entry>
- <entry>Watermelon</entry>
- </row>
- <row>
- <entry spanname="14">Strawberries</entry>
- <entry>Cantaloupe</entry>
- <entry>Tamarind</entry>
- </row>
- <row>
- <entry>Lichee</entry>
- <entry spanname="25">Boysenberry</entry>
- <entry>Guava</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- <para><xref linkend="tablemarkup"/> shows the markup for <xref linkend="tableexample"/>.</para>
- <example xml:id="tablemarkup">
- <?dbfo pgwide="1"?>
- <title>Markup for a Table</title>
- <programlisting><table xml:id="tableexample" pgwide="1">
- <title>Complicated Table</title>
- <tgroup cols="6">
- <colspec align="center" colname="c1" colnum="1" />
- <colspec align="justify" colname="c2" colnum="2" />
- <colspec colname="c3" />
- <colspec colname="c4" colnum="4" />
- <colspec align="right" colname="c5" colnum="5" />
- <colspec align="left" colname="c6" />
- <spanspec align="center" nameend="c5" namest="c2"
- spanname="25" />
- <spanspec align="left" nameend="c4" namest="c1"
- spanname="14" />
- <thead>
- <row>
- <entry>c1</entry>
- <entry>c2</entry>
- <entry>c3</entry>
- <entry>c4</entry>
- <entry>c5</entry>
- <entry>c6</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>Pomegranate</entry>
- <entry>Pineapple</entry>
- <entry>Mango</entry>
- <entry>Carambola</entry>
- <entry>Banana</entry>
- <entry>Papaya</entry>
- </row>
- <row>
- <entry>Apples</entry>
- <entry align="right">Kiwis</entry>
- <entry align="center" nameend="c5"
- namest="c3">Passion
- Fruits</entry>
- <entry>Watermelon</entry>
- </row>
- <row>
- <entry spanname="14">Strawberries</entry>
- <entry>Cantaloupe</entry>
- <entry>Tamarind</entry>
- </row>
- <row>
- <entry>Lichee</entry>
- <entry spanname="25">Boysenberry</entry>
- <entry>Guava</entry>
- </row>
- </tbody>
- </tgroup>
-</table></programlisting>
- </example>
- </section>
- </section>
-</chapter>
commit 654e8a21ddfcd76526976fd80930f87b109bf14a
Author: Ben Shum <bshum at biblio.org>
Date: Sun May 27 16:55:39 2012 -0400
Convert docs files from DOS to UNIX format.
Signed-off-by: Ben Shum <bshum at biblio.org>
Signed-off-by: Robert Soulliere <robert.soulliere at mohawkcollege.ca>
diff --git a/docs/acquisitions/introduction.txt b/docs/acquisitions/introduction.txt
index 4680506..a257cc9 100644
--- a/docs/acquisitions/introduction.txt
+++ b/docs/acquisitions/introduction.txt
@@ -1,25 +1,25 @@
-Acquisitions
-------------
-
-This section is intended for those who are responsible for managing and processing acquisitions.
-
-Before beginning to use Acquisitions, the following must be configured by an administrator:
-
-* Cancel/Suspend Reasons (optional)
-* Claiming (optional)
-* Currency Types (defaults exist)
-* Distribution Formulas (optional)
-* EDI Accounts (optional) (see link:../installation/edi_setup.txt[Setting Up EDI Acquisitions] under Software Installation)
-* Exchange Rates (defaults exist)
-* Funds and Fund Sources
-* Invoice Types (defaults exist) and Invoice Payment Methods
-* Line Item Features (optional)
-* Merge Overlay Profiles and Record Match Sets (see link:../cataloging/batch_importing_MARC.txt[Batch Importing MARC Records] in Cataloging)
-* Providers
-
-Acquisitons Workflow
-~~~~~~~~~~~~~~~~~~~~
-
-The following diagram shows how the workflow functions in Evergreen. One of the differences in this process you should notice is that when creating a selection list on the vendor site, libraries will be downloading and importing the vendor bibs and item records.
-
-image::media/acq_workflow.jpg[workflow diagram]
+Acquisitions
+------------
+
+This section is intended for those who are responsible for managing and processing acquisitions.
+
+Before beginning to use Acquisitions, the following must be configured by an administrator:
+
+* Cancel/Suspend Reasons (optional)
+* Claiming (optional)
+* Currency Types (defaults exist)
+* Distribution Formulas (optional)
+* EDI Accounts (optional) (see link:../installation/edi_setup.txt[Setting Up EDI Acquisitions] under Software Installation)
+* Exchange Rates (defaults exist)
+* Funds and Fund Sources
+* Invoice Types (defaults exist) and Invoice Payment Methods
+* Line Item Features (optional)
+* Merge Overlay Profiles and Record Match Sets (see link:../cataloging/batch_importing_MARC.txt[Batch Importing MARC Records] in Cataloging)
+* Providers
+
+Acquisitons Workflow
+~~~~~~~~~~~~~~~~~~~~
+
+The following diagram shows how the workflow functions in Evergreen. One of the differences in this process you should notice is that when creating a selection list on the vendor site, libraries will be downloading and importing the vendor bibs and item records.
+
+image::media/acq_workflow.jpg[workflow diagram]
diff --git a/docs/acquisitions/receive_items_from_invoice.txt b/docs/acquisitions/receive_items_from_invoice.txt
index 8c0adca..f28665c 100644
--- a/docs/acquisitions/receive_items_from_invoice.txt
+++ b/docs/acquisitions/receive_items_from_invoice.txt
@@ -1,73 +1,73 @@
-Receive Items From an Invoice
------------------------------
-
-This feature enables users to receive items from an invoice. Staff can receive individual copies, or they can receive items in batch.
-
-Receive Items in Batch (List Mode)
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-In this example, we have created a purchase order, added line items and copies, and activated the purchase order. We will create an invoice from the purchase order, receive items, and invoice them. We will receive the items in batch from the invoice.
-
-1) Retrieve a purchase order.
-
-2) Click *Create Invoice*.
-
-image::media/Receive_Items_From_an_Invoice1.jpg[Receive_Items_From_an_Invoice1]
-
-3) The blank invoice appears. In the top half of the invoice, enter descriptive information about the invoice. In the bottom half of the invoice, enter the number of items for which you were invoiced, the amount that you were billed, and the amount that you paid.
-
-
-image::media/Receive_Items_From_an_Invoice2.jpg[Receive_Items_From_an_Invoice2]
-
-
-4) Click *Save*. You must choose a save option before you can receive items.
-
-
-5) The screen refreshes. In the top right corner of the screen, click *Receive Items*.
-
-
-6) The *Acquisitions Invoice Receiving* screen opens. By default, this screen enables users to receive items in batch, or *Numeric Mode*. You can select the number of copies that you want to receive; you are not receiving specific copies in this mode.
-
-
-7) Select the number of copies that you want to receive. By default, the number that you invoiced will appear. In this example, we will receive one copy of each title.
-
-
-NOTE: You cannot receive fewer items than 0 (zero) or more items than the number that you ordered.
-
-
-8) Click *Receive Selected Copies*.
-
-
-image::media/Receive_Items_From_an_Invoice4.jpg[Receive_Items_From_an_Invoice4]
-
-
-9) When you are finished receiving items, close the screen. You can repeat this process as you receive more copies.
-
-
-
-Receive Specific Copies (Numeric Mode)
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-In this example, we have created a purchase order, added line items and copies, and activated the purchase order. We will create an invoice from the purchase order, receive items, and invoice them. We will receive specific copies from the invoice. This function may be useful to libraries who purchase items that have been barcoded by their vendor.
-
-
-1) Complete steps 1-5 in the previous section.
-
-2) The *Acquisitions Invoice Receiving* screen by default enables user to receive items in batch, or *Numeric Mode*. Click *Use List Mode* to receive specific copies.
-
-3) Select the check boxes adjacent to the copies that you want to receive. Leave unchecked the copies that you do not want to receive.
-
-4) Click *Receive Selected Copies*.
-
-image::media/Receive_Items_From_an_Invoice5.jpg[Receive_Items_From_an_Invoice5]
-
-
-The screen will refresh. Copies that have not yet been received remain on the screen so that you can receive them when they arrive.
-
-
-5) When all copies on an invoice have been received, a message confirms that no copies remain to be received.
-
-6) The purchase order records that all items have been received.
-
-image::media/Receive_Items_From_an_Invoice7.jpg[Receive_Items_From_an_Invoice7]
-
+Receive Items From an Invoice
+-----------------------------
+
+This feature enables users to receive items from an invoice. Staff can receive individual copies, or they can receive items in batch.
+
+Receive Items in Batch (List Mode)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+In this example, we have created a purchase order, added line items and copies, and activated the purchase order. We will create an invoice from the purchase order, receive items, and invoice them. We will receive the items in batch from the invoice.
+
+1) Retrieve a purchase order.
+
+2) Click *Create Invoice*.
+
+image::media/Receive_Items_From_an_Invoice1.jpg[Receive_Items_From_an_Invoice1]
+
+3) The blank invoice appears. In the top half of the invoice, enter descriptive information about the invoice. In the bottom half of the invoice, enter the number of items for which you were invoiced, the amount that you were billed, and the amount that you paid.
+
+
+image::media/Receive_Items_From_an_Invoice2.jpg[Receive_Items_From_an_Invoice2]
+
+
+4) Click *Save*. You must choose a save option before you can receive items.
+
+
+5) The screen refreshes. In the top right corner of the screen, click *Receive Items*.
+
+
+6) The *Acquisitions Invoice Receiving* screen opens. By default, this screen enables users to receive items in batch, or *Numeric Mode*. You can select the number of copies that you want to receive; you are not receiving specific copies in this mode.
+
+
+7) Select the number of copies that you want to receive. By default, the number that you invoiced will appear. In this example, we will receive one copy of each title.
+
+
+NOTE: You cannot receive fewer items than 0 (zero) or more items than the number that you ordered.
+
+
+8) Click *Receive Selected Copies*.
+
+
+image::media/Receive_Items_From_an_Invoice4.jpg[Receive_Items_From_an_Invoice4]
+
+
+9) When you are finished receiving items, close the screen. You can repeat this process as you receive more copies.
+
+
+
+Receive Specific Copies (Numeric Mode)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+In this example, we have created a purchase order, added line items and copies, and activated the purchase order. We will create an invoice from the purchase order, receive items, and invoice them. We will receive specific copies from the invoice. This function may be useful to libraries who purchase items that have been barcoded by their vendor.
+
+
+1) Complete steps 1-5 in the previous section.
+
+2) The *Acquisitions Invoice Receiving* screen by default enables user to receive items in batch, or *Numeric Mode*. Click *Use List Mode* to receive specific copies.
+
+3) Select the check boxes adjacent to the copies that you want to receive. Leave unchecked the copies that you do not want to receive.
+
+4) Click *Receive Selected Copies*.
+
+image::media/Receive_Items_From_an_Invoice5.jpg[Receive_Items_From_an_Invoice5]
+
+
+The screen will refresh. Copies that have not yet been received remain on the screen so that you can receive them when they arrive.
+
+
+5) When all copies on an invoice have been received, a message confirms that no copies remain to be received.
+
+6) The purchase order records that all items have been received.
+
+image::media/Receive_Items_From_an_Invoice7.jpg[Receive_Items_From_an_Invoice7]
+
diff --git a/docs/acquisitions/selection_lists_po.txt b/docs/acquisitions/selection_lists_po.txt
index e308d05..7f5fd85 100644
--- a/docs/acquisitions/selection_lists_po.txt
+++ b/docs/acquisitions/selection_lists_po.txt
@@ -1,136 +1,136 @@
-Selection Lists and Purchase Orders
------------------------------------
-
-Selection Lists
-~~~~~~~~~~~~~~~
-
-Selection lists allow you to create, manage, and save lists of items that you may want to purchase. To view your selection list, click Acquisitions -> My Selection Lists. Use the general search to view selection lists created by other users.
-
-Create a selection list
-^^^^^^^^^^^^^^^^^^^^^^^
-
-Selection lists can be created in four areas within the module. Selection lists can be created when you link:brief_records.txt[Add Brief Records], Upload MARC Order Records, or find records through the link:federated.txt[MARC Federated Search]. In each of these interfaces, you will find the Add to Selection List field. Enter the name of the selection list that you want to create in that field.
-
-Selection lists can also be created through the My Selection Lists interface:
-
-. Click Acquisitions -> My Selection Lists.
-. Click the New Selection List drop down arrow.
-. Enter the name of the selection list in the box that appears.
-. Click Create.
-
-image::media/acq_selection_create.png[create selection list]
-
-Add items to a selection list
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-You can add items to a selection list in one of three ways: link:brief_records.txt[add a brief record]; upload MARC order records; add records through a link:federated.txt[federated search]; or use the link:federated.txt[View/Place Orders] menu item in the catalog.
-
-Clone selection lists
-^^^^^^^^^^^^^^^^^^^^^
-
-Cloning selection lists enables you to copy one selection list into a new selection list. You can maintain both copies of the list, or you can delete the previous list.
-
-. Click Acquisitions -> My Selection Lists.
-. Check the box adjacent to the list that you want to clone.
-. Click Clone Selected.
-. Enter a name into the box that appears, and click Clone.
-
-image::media/acq_selection_clone.png[clone selection list]
-
-Merge selection lists
-^^^^^^^^^^^^^^^^^^^^^
-
-You can merge two or more selection lists into one selection list.
-
-
-. Click Acquisitions -> My Selection Lists.
-. Check the boxes adjacent to the selection lists that you want to merge, and click Merge Selected.
-. Choose the Lead Selection List from the drop down menu. This is the list to which the items on the other list(s) will be transferred.
-. Click Merge.
-
-image::media/acq_selection_merge.png[merge selection list]
-
-Delete selection lists
-^^^^^^^^^^^^^^^^^^^^^^
-
-You can delete selection lists that you do not want to save. You will not be able to retrieve these items through the General Search after you have deleted the list. You must delete all line items from a selection list before you can delete the list.
-
-
-. Click Acquisitions -> My Selection Lists.
-. Check the box adjacent to the selection list(s) that you want to delete.
-. Click Delete Selected.
-
-Mark Ready for Selector
-^^^^^^^^^^^^^^^^^^^^^^^
-
-After an item has been added to a selection list or purchase order, you can mark it ready for selector. This step is optional but may be useful to individual workflows.
-
-
-. If you want to mark part of a selection list ready for selector, then you can check the box(es) of the line item(s) that you wish to mark ready for selector. If you want to mark the entire list ready for selector, then skip to step 2.
-. Click Actions -> Mark Ready for Selector.
-. A pop up box will appear. Choose to mark the selected line items or all line items.
-. Click Go.
-. The screen will refresh. The marked line item(s) will be highlighted pink, and the status changes to selector~ready.
-
-image::media/acq_selection_mark_ready.png[mark ready]
-
-Convert selection list to purchase order
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Use the Actions menu to convert a selection list to a purchase order.
-
-
-. From a selection list, click Actions ~> Create Purchase Order.
-. A pop up box will appear.
-. Select the ordering agency from the drop down menu.
-. Enter the provider.
-. Check the box adjacent to prepayment required if prepayment is required.
-. Choose if you will add All Lineitems or Selected Lineitems to your purchase order.
-. Check the box if you want to Import Bibs and Create Copies in the catalog.
-. Click Submit.
-
-Brief Records
-~~~~~~~~~~~~~
-
-Brief records are short bibliographic records with minimal information that are often used as placeholder records until items are received. Brief records can be added to selection lists or purchase orders and can be imported into the catalog. You can add brief records to new or existing selection lists. You can add brief records to new, pending or on~order purchase orders.
-
-Add brief records to a selection list
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-. Click Acquisitions -> New Brief Record. You can also add brief records to an existing selection list by clicking the Actions menu on the selection list and choosing Add Brief Record.
-. Choose a selection list from the drop down menu, or enter the name of a new selection list.
-. Enter bibliographic information in the desired fields.
-. Click Save Record.
-
-image::media/acq_brief_record.png[]
-
-Add brief records to purchase orders
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-You can add brief records to new or existing purchase orders.
-
-. Open or create a purchase order. See the section on link:03~PO.txt[purchase orders] for more information.
-. Click Add Brief Record.
-. Enter bibliographic information in the desired fields. Notice that the record is added to the purchase order that you just created.
-. Click Save Record.
-
-image::media/acq_brief_record-2.png[]
-
-MARC Federated Search
-~~~~~~~~~~~~~~~~~~~~~
-
-The MARC Federated Search enables you to import bibliographic records into a selection list or purchase order from a Z39.50 source.
-
-. Click Acquisitions -> MARC Federated Search.
-. Check the boxes of Z39.50 services that you want to search. Your local Evergreen Catalog is checked by default. Click Submit.
-+
-----
-image::media/acq_marc_search.png[search form]
-----
-+
-. A list of results will appear. Click the "Copies" link to add copy information to the line item. See the link:line_items.txt[section on Line Items] for more information.
-. Click the Notes link to add notes or line item alerts to the line item. See the link:line_items.txt[section on Line Items] for more information.
-. Enter a price in the "Estimated Price" field.
-. You can save the line item(s) to a selection list by checking the box on the line item and clicking Actions -> Save Items to Selection List. You can also create a purchase order from the line item(s) by checking the box on the line item and clicking Actions ~> Create Purchase Order.
-
-image::media/acq_marc_search-2.png[line item]
+Selection Lists and Purchase Orders
+-----------------------------------
+
+Selection Lists
+~~~~~~~~~~~~~~~
+
+Selection lists allow you to create, manage, and save lists of items that you may want to purchase. To view your selection list, click Acquisitions -> My Selection Lists. Use the general search to view selection lists created by other users.
+
+Create a selection list
+^^^^^^^^^^^^^^^^^^^^^^^
+
+Selection lists can be created in four areas within the module. Selection lists can be created when you link:brief_records.txt[Add Brief Records], Upload MARC Order Records, or find records through the link:federated.txt[MARC Federated Search]. In each of these interfaces, you will find the Add to Selection List field. Enter the name of the selection list that you want to create in that field.
+
+Selection lists can also be created through the My Selection Lists interface:
+
+. Click Acquisitions -> My Selection Lists.
+. Click the New Selection List drop down arrow.
+. Enter the name of the selection list in the box that appears.
+. Click Create.
+
+image::media/acq_selection_create.png[create selection list]
+
+Add items to a selection list
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You can add items to a selection list in one of three ways: link:brief_records.txt[add a brief record]; upload MARC order records; add records through a link:federated.txt[federated search]; or use the link:federated.txt[View/Place Orders] menu item in the catalog.
+
+Clone selection lists
+^^^^^^^^^^^^^^^^^^^^^
+
+Cloning selection lists enables you to copy one selection list into a new selection list. You can maintain both copies of the list, or you can delete the previous list.
+
+. Click Acquisitions -> My Selection Lists.
+. Check the box adjacent to the list that you want to clone.
+. Click Clone Selected.
+. Enter a name into the box that appears, and click Clone.
+
+image::media/acq_selection_clone.png[clone selection list]
+
+Merge selection lists
+^^^^^^^^^^^^^^^^^^^^^
+
+You can merge two or more selection lists into one selection list.
+
+
+. Click Acquisitions -> My Selection Lists.
+. Check the boxes adjacent to the selection lists that you want to merge, and click Merge Selected.
+. Choose the Lead Selection List from the drop down menu. This is the list to which the items on the other list(s) will be transferred.
+. Click Merge.
+
+image::media/acq_selection_merge.png[merge selection list]
+
+Delete selection lists
+^^^^^^^^^^^^^^^^^^^^^^
+
+You can delete selection lists that you do not want to save. You will not be able to retrieve these items through the General Search after you have deleted the list. You must delete all line items from a selection list before you can delete the list.
+
+
+. Click Acquisitions -> My Selection Lists.
+. Check the box adjacent to the selection list(s) that you want to delete.
+. Click Delete Selected.
+
+Mark Ready for Selector
+^^^^^^^^^^^^^^^^^^^^^^^
+
+After an item has been added to a selection list or purchase order, you can mark it ready for selector. This step is optional but may be useful to individual workflows.
+
+
+. If you want to mark part of a selection list ready for selector, then you can check the box(es) of the line item(s) that you wish to mark ready for selector. If you want to mark the entire list ready for selector, then skip to step 2.
+. Click Actions -> Mark Ready for Selector.
+. A pop up box will appear. Choose to mark the selected line items or all line items.
+. Click Go.
+. The screen will refresh. The marked line item(s) will be highlighted pink, and the status changes to selector~ready.
+
+image::media/acq_selection_mark_ready.png[mark ready]
+
+Convert selection list to purchase order
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Use the Actions menu to convert a selection list to a purchase order.
+
+
+. From a selection list, click Actions ~> Create Purchase Order.
+. A pop up box will appear.
+. Select the ordering agency from the drop down menu.
+. Enter the provider.
+. Check the box adjacent to prepayment required if prepayment is required.
+. Choose if you will add All Lineitems or Selected Lineitems to your purchase order.
+. Check the box if you want to Import Bibs and Create Copies in the catalog.
+. Click Submit.
+
+Brief Records
+~~~~~~~~~~~~~
+
+Brief records are short bibliographic records with minimal information that are often used as placeholder records until items are received. Brief records can be added to selection lists or purchase orders and can be imported into the catalog. You can add brief records to new or existing selection lists. You can add brief records to new, pending or on~order purchase orders.
+
+Add brief records to a selection list
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+. Click Acquisitions -> New Brief Record. You can also add brief records to an existing selection list by clicking the Actions menu on the selection list and choosing Add Brief Record.
+. Choose a selection list from the drop down menu, or enter the name of a new selection list.
+. Enter bibliographic information in the desired fields.
+. Click Save Record.
+
+image::media/acq_brief_record.png[]
+
+Add brief records to purchase orders
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You can add brief records to new or existing purchase orders.
+
+. Open or create a purchase order. See the section on link:03~PO.txt[purchase orders] for more information.
+. Click Add Brief Record.
+. Enter bibliographic information in the desired fields. Notice that the record is added to the purchase order that you just created.
+. Click Save Record.
+
+image::media/acq_brief_record-2.png[]
+
+MARC Federated Search
+~~~~~~~~~~~~~~~~~~~~~
+
+The MARC Federated Search enables you to import bibliographic records into a selection list or purchase order from a Z39.50 source.
+
+. Click Acquisitions -> MARC Federated Search.
+. Check the boxes of Z39.50 services that you want to search. Your local Evergreen Catalog is checked by default. Click Submit.
++
+----
+image::media/acq_marc_search.png[search form]
+----
++
+. A list of results will appear. Click the "Copies" link to add copy information to the line item. See the link:line_items.txt[section on Line Items] for more information.
+. Click the Notes link to add notes or line item alerts to the line item. See the link:line_items.txt[section on Line Items] for more information.
+. Enter a price in the "Estimated Price" field.
+. You can save the line item(s) to a selection list by checking the box on the line item and clicking Actions -> Save Items to Selection List. You can also create a purchase order from the line item(s) by checking the box on the line item and clicking Actions ~> Create Purchase Order.
+
+image::media/acq_marc_search-2.png[line item]
diff --git a/docs/acquisitions/vandelay_acquisitions_integration.txt b/docs/acquisitions/vandelay_acquisitions_integration.txt
index 51fc2fa..026d131 100644
--- a/docs/acquisitions/vandelay_acquisitions_integration.txt
+++ b/docs/acquisitions/vandelay_acquisitions_integration.txt
@@ -1,69 +1,69 @@
-Vandelay Integration into Acquisitions
---------------------------------------
-The Acquisitions Load MARC Order Record interface enables you to add MARC records to selection lists and purchase orders and upload the records into the catalog. The Vandelay interface enables you to create specific match points between incoming MARC records and exisiting catalog records. Combining these two features enables you to track on order MARC records through the Acquisitions interface and to utilize the record matching mechanisms available in Vandelay.
-
-The purpose of this documentation is to describe the interaction between Vandelay and the Acquisitions MARC Batch Upload interface. For detailed instructions on
- using the Acquisitions MARC Batch Upload interface, see the Evergreen Documentation Interest Group's Book of Evergreen, 2.1 documentation, Chapter 5, Load MARC
-Order Records. For detailed instructions on using the Vandelay functions for record matching and importing, see the Evergreen Documentation Interest Group's Book of Evergreen,
-2.2 documentation, Chapter 7, Batch Importing MARC Records.
-
-*Use Cases for Vandelay Integration into Acquisitions*
-
-You can add items to a selection list or purchase order and ignore the Vandelay options, or you can use both acquisitions and cataloging functions. In these examples, you will use both functions.
-
-Example 1: Using the Acquisitions MARC Batch Load interface, upload MARC records to a selection list and a Vandelay queue, and match queued records with existing catalog records.
-
-In this example, an acquisitions librarian has received a batch of MARC records from a vendor. She will add the records to a selection list and a Vandelay record queue.
-A cataloger will later view the queue, edit the records, and import them into the catalog.
-
-. Click *Acquisitions -> Load MARC Order Records*
-. Add MARC order records to a *Selection list* and/or a *Purchase Order.* Check the box to create a purchase order if desired.
-. Select a *Provider* from the drop down menu, or begin typing the code for the provider, and the field will auto-fill.
-. Select a *Context Org Unit* from the drop down menu, or begin typing the code for the context org unit, and the field will auto-fill.
-. Select a *Selection List* from the drop down menu, or begin typing the name of the selection list. You can create a new list, or the field will auto-fill.
-. Create a new record queue in Vandelay, or upload the records to an existing queue.
-. Select a *Record Match Set*.
-. Browse your computer to find the MARC file, and click *Upload*.
-+
-image::media/Vandelay_Integration_into_Acquisitions1.jpg[Vandelay_Integration_into_Acquisitions1]
-+
-. The processed items appear at the bottom of the screen.
-+
-image::media/Vandelay_Integration_into_Acquisitions2.jpg[Vandelay_Integration_into_Acquisitions2]
-. You can click the link(s) to access the selection list or the import queue. Click the link to *View Selection List*.
-. Look at the first line item. The line item has not yet been linked to the catalog, but it is linked to a Vandelay record queue. Click the link to the *queue* to examine the MARC record.
-+
-image::media/Vandelay_Integration_into_Acquisitions3.jpg[Vandelay_Integration_into_Acquisitions3]
-. The Vandelay interface opens in a new tab. The bibliographic records appear in the queue. Records that have matches are identified in the queue. You can edit these records and/or import them into the catalog, completing the process.
-
-image::media/Vandelay_Integration_into_Acquisitions4.jpg[Vandelay_Integration_into_Acquisitions4]
-
-Example 2: Using the Acquisitions MARC Batch Load interface, upload MARC records to a selection list, and use the Vandelay options to import the records directly into the catalog. The Vandelay options will enable you to match incoming records with existing catalog records.
-
-In this example, a librarian will add MARC records to a selection list, create criteria for matching incoming and existing records, and import the matching and non-matching records into the catalog.
-
-. Click *Acquisitions* -> *Load MARC Order Records*
-. Add MARC order records to a *Selection list* and/or a *Purchase Order.* Check the box to create a purchase order if desired.
-. Select a *Provider* from the drop down menu, or begin typing the code for the provider, and the field will auto-fill.
-. Select a *Context Org Unit* from the drop down menu, or begin typing the code for the context org unit, and the field will auto-fill.
-. Select a *Selection List* from the drop down menu, or begin typing the name of the selection list. You can create a new list, or the field will auto-fill.
-. Create a new record queue in Vandelay, or upload the records to an existing queue.
-. Select a *Record Match Set*.
-. Select *Merge Profile* -> *Match-Only Merge*.
-. Check the box adjacent to *Merge on Best Match*.
-. Browse your computer to find the MARC file, and click *Upload*.
-+
-image::media/Vandelay_Integration_into_Acquisitions5.jpg[Vandelay_Integration_into_Acquisitions5]
-+
-. Click the link to *View Selection List* Line items that do not match existing catalog records on title and ISBN contain the link, *link to catalog*. This link indicates that you could link the line item to a catalog record, but currently, no match exists between the line item and catalog records. Line items that do have matching records in the catalog contain the link, *catalog*.
-+
-image::/media/Vandelay_Integration_into_Acquisitions6.jpg[Vandelay_Integration_into_Acquisitions6]
-+
-. Click the *catalog* link to view the line item in the catalog.
-
-*Permissions to use this Feature*
-
-IMPORT_MARC - Using Vandelay to create new bib records now requres the IMPORT_MARC
-permission (same as open-ils.cat.biblio.record.xml.import). If the permission fails, the queued record will fail import and be stamped with a new "import.record.perm_failure" vandelay import error
-
-IMPORT_ACQ_LINEITEM_BIB_RECORD_UPLOAD - This allows interfaces leveraging Vandelay, such as Acquisitions, to create a higher barrier to entry. This permission prevents users from creating new bib records directly from the ACQ vendor MARC file upload interface.
+Vandelay Integration into Acquisitions
+--------------------------------------
+The Acquisitions Load MARC Order Record interface enables you to add MARC records to selection lists and purchase orders and upload the records into the catalog. The Vandelay interface enables you to create specific match points between incoming MARC records and exisiting catalog records. Combining these two features enables you to track on order MARC records through the Acquisitions interface and to utilize the record matching mechanisms available in Vandelay.
+
+The purpose of this documentation is to describe the interaction between Vandelay and the Acquisitions MARC Batch Upload interface. For detailed instructions on
+ using the Acquisitions MARC Batch Upload interface, see the Evergreen Documentation Interest Group's Book of Evergreen, 2.1 documentation, Chapter 5, Load MARC
+Order Records. For detailed instructions on using the Vandelay functions for record matching and importing, see the Evergreen Documentation Interest Group's Book of Evergreen,
+2.2 documentation, Chapter 7, Batch Importing MARC Records.
+
+*Use Cases for Vandelay Integration into Acquisitions*
+
+You can add items to a selection list or purchase order and ignore the Vandelay options, or you can use both acquisitions and cataloging functions. In these examples, you will use both functions.
+
+Example 1: Using the Acquisitions MARC Batch Load interface, upload MARC records to a selection list and a Vandelay queue, and match queued records with existing catalog records.
+
+In this example, an acquisitions librarian has received a batch of MARC records from a vendor. She will add the records to a selection list and a Vandelay record queue.
+A cataloger will later view the queue, edit the records, and import them into the catalog.
+
+. Click *Acquisitions -> Load MARC Order Records*
+. Add MARC order records to a *Selection list* and/or a *Purchase Order.* Check the box to create a purchase order if desired.
+. Select a *Provider* from the drop down menu, or begin typing the code for the provider, and the field will auto-fill.
+. Select a *Context Org Unit* from the drop down menu, or begin typing the code for the context org unit, and the field will auto-fill.
+. Select a *Selection List* from the drop down menu, or begin typing the name of the selection list. You can create a new list, or the field will auto-fill.
+. Create a new record queue in Vandelay, or upload the records to an existing queue.
+. Select a *Record Match Set*.
+. Browse your computer to find the MARC file, and click *Upload*.
++
+image::media/Vandelay_Integration_into_Acquisitions1.jpg[Vandelay_Integration_into_Acquisitions1]
++
+. The processed items appear at the bottom of the screen.
++
+image::media/Vandelay_Integration_into_Acquisitions2.jpg[Vandelay_Integration_into_Acquisitions2]
+. You can click the link(s) to access the selection list or the import queue. Click the link to *View Selection List*.
+. Look at the first line item. The line item has not yet been linked to the catalog, but it is linked to a Vandelay record queue. Click the link to the *queue* to examine the MARC record.
++
+image::media/Vandelay_Integration_into_Acquisitions3.jpg[Vandelay_Integration_into_Acquisitions3]
+. The Vandelay interface opens in a new tab. The bibliographic records appear in the queue. Records that have matches are identified in the queue. You can edit these records and/or import them into the catalog, completing the process.
+
+image::media/Vandelay_Integration_into_Acquisitions4.jpg[Vandelay_Integration_into_Acquisitions4]
+
+Example 2: Using the Acquisitions MARC Batch Load interface, upload MARC records to a selection list, and use the Vandelay options to import the records directly into the catalog. The Vandelay options will enable you to match incoming records with existing catalog records.
+
+In this example, a librarian will add MARC records to a selection list, create criteria for matching incoming and existing records, and import the matching and non-matching records into the catalog.
+
+. Click *Acquisitions* -> *Load MARC Order Records*
+. Add MARC order records to a *Selection list* and/or a *Purchase Order.* Check the box to create a purchase order if desired.
+. Select a *Provider* from the drop down menu, or begin typing the code for the provider, and the field will auto-fill.
+. Select a *Context Org Unit* from the drop down menu, or begin typing the code for the context org unit, and the field will auto-fill.
+. Select a *Selection List* from the drop down menu, or begin typing the name of the selection list. You can create a new list, or the field will auto-fill.
+. Create a new record queue in Vandelay, or upload the records to an existing queue.
+. Select a *Record Match Set*.
+. Select *Merge Profile* -> *Match-Only Merge*.
+. Check the box adjacent to *Merge on Best Match*.
+. Browse your computer to find the MARC file, and click *Upload*.
++
+image::media/Vandelay_Integration_into_Acquisitions5.jpg[Vandelay_Integration_into_Acquisitions5]
++
+. Click the link to *View Selection List* Line items that do not match existing catalog records on title and ISBN contain the link, *link to catalog*. This link indicates that you could link the line item to a catalog record, but currently, no match exists between the line item and catalog records. Line items that do have matching records in the catalog contain the link, *catalog*.
++
+image::/media/Vandelay_Integration_into_Acquisitions6.jpg[Vandelay_Integration_into_Acquisitions6]
++
+. Click the *catalog* link to view the line item in the catalog.
+
+*Permissions to use this Feature*
+
+IMPORT_MARC - Using Vandelay to create new bib records now requres the IMPORT_MARC
+permission (same as open-ils.cat.biblio.record.xml.import). If the permission fails, the queued record will fail import and be stamped with a new "import.record.perm_failure" vandelay import error
+
+IMPORT_ACQ_LINEITEM_BIB_RECORD_UPLOAD - This allows interfaces leveraging Vandelay, such as Acquisitions, to create a higher barrier to entry. This permission prevents users from creating new bib records directly from the ACQ vendor MARC file upload interface.
diff --git a/docs/admin/acquisitions_admin.txt b/docs/admin/acquisitions_admin.txt
index 30db442..8f96bcf 100644
--- a/docs/admin/acquisitions_admin.txt
+++ b/docs/admin/acquisitions_admin.txt
@@ -1,490 +1,490 @@
-Acquisitions Administration
----------------------------
-
-Acquisitions Permissions in the Admin module
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Several setting in the Library Settings area of the Admin module pertain to functions in the Acquisitions module. You can access these settings by clicking _Admin -> Local Administration ->Library Settings Editor_.
-
-* CAT: Delete bib if all copies are deleted via Acquisitions lineitem cancellation - If you cancel a line item, then all of the on order copies in the catalog are deleted. If, when you cancel a line item, you also want to delete the bib record, then set this setting to TRUE.
-* Default circulation modifier - This modifier would be applied to items that are created in the acquisitions module
-* Default copy location - This copy location would be applied to items that are created in the acquisitions module
-* Fund Spending Limit for Block - When the amount remaining in the fund, including spent money and encumbrances, goes below this percentage, attempts to spend from the fund will be blocked.
-* Fund Spending Limit for Warning - When the amount remaining in the fund, including spent money and encumbrances, goes below this percentage, attempts to spend from the fund will result in a warning to the staff.
-* Temporary barcode prefix - Temporary barcode prefix for items that are created in the acquisitions module
-* Temporary call number prefix - Temporary call number prefix for items that are created in the acquisitions module
-
-Cancel/Suspend reasons
-~~~~~~~~~~~~~~~~~~~~~~
-
-The Cancel reasons link enables you to predefine the reasons for which a line item or a PO can be cancelled. A default list of reasons appears, but you can add custom reasons to this list. Applying the cancel reason will prevent the item from appearing in a claims list and will allow you to cancel debits associated with the purchase. Cancel reasons also enable you to suspend or delay a purchase. For example, you could create a cancel reason of 'back ordered,' and you could choose to keep the debits associated with the purchase.
-
-Create a cancel/suspend reason
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-. To add a new cancel reason, click _Administration -> Server Administration -> Acquisitions -> Cancel reasons_.
-
-. Click _New Cancel Reason_.
-
-. Select a using library from the drop down menu. The using library indicates the organizational units whose staff can use this cancel reason. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units.)
-
-. Create a label for the cancel reason. This label will appear when you select a cancel reason on an item or a PO.
-
-. Create a description of the cancel reason. This is a free text field and can be comprised of any text of your choosing.
-
-. If you want to retain the debits associated with the cancelled purchase, click the box adjacent to Keep Debits->
-
-. Click _Save_.
-
-Claiming
-~~~~~~~~
-Currently, all claiming is manual, but the admin module enables you to build claim policies and specify the action(s) that users should take to claim items.
-
-Create a claim policy
-^^^^^^^^^^^^^^^^^^^^^
-
-The claim policy link enables you to name the claim policy and specify the organization that owns it.
-
-. To create a claim policy, click _Admin -> Server Administration -> Acquisitions -> Claim Policies_.
-. Create a claim policy name. No limits exist on the number of characters that can be entered in this field.
-. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this claim policy. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
-+
-[NOTE]
-The rule of parental inheritance applies to this list.
-+
-. Enter a description. No limits exist on the number of characters that can be entered in this field.
-. Click _Save_.
-
-Create a claim type
-^^^^^^^^^^^^^^^^^^^
-
-The claim type link enables you to specify the reason for a type of claim.
-
-. To create a claim type, click _Admin -> Server Administration -> Acquisitions -> Claim types_.
-. Create a claim type. No limits exist on the number of characters that can be entered in this field.
-. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this claim type. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
-+
-[NOTE]
-The rule of parental inheritance applies to this list.
-+
-. Enter a description. No limits exist on the number of characters that can be entered in this field.
-. Click _Save_.
-
-Create a claim event type
-^^^^^^^^^^^^^^^^^^^^^^^^^
-
-The claim event type describes the physical action that should occur when an item needs to be claimed. For example, the user should notify the vendor via email that the library is claiming an item.
-
-. To access the claim event types, click _Admin -> Server Administration -> Acquisitions ->Claim event type_.
-. Enter a code for the claim event type. No limits exist on the number of characters that can be entered in this field.
-. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this event type. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
-+
-[NOTE]
-The rule of parental inheritance applies to this list.
-+
-. Enter a description. No limits exist on the number of characters that can be entered in this field.
-. If this claim is initiated by the user, then check the box adjacent to Library Initiated.
-+
-[NOTE]
-Currently, all claims are initiated by a user. The ILS cannot automatically claim an issue.
-+
-. Click _Save_.
-
-Create a claim policy action
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-The claim policy action enables you to specify how long a user should wait before claiming the item.
-
-. To access claim policy actions, click _Admin -> Server Administration -> Acquisitions ->Claim Policy Actions_.
-
-. Select an Action (Event Type) from the drop down menu.
-
-. Enter an action interval. This field indicates how long a user should wait before claiming the item.
-
-. In the Claim Policy ID field, select a claim policy from the drop down menu.
-
-. Click _Save_.
-
-[NOTE]
-You can create claim cycles by adding multiple claim policy actions to a claim policy.
-
-Currency Types
-~~~~~~~~~~~~~~
-
-Currency types can be created and applied to funds in the administrative module. When a fund is applied to a copy or line item for purchase, the item will be purchased in the currency associated with that fund.
-
-Create a currency type
-^^^^^^^^^^^^^^^^^^^^^^
-
-. To create a new currency type, click _Admin -> Server Administration -> Acquisitions -> Currency types_.
-
-. Enter the currency code. No limits exist on the number of characters that can be entered in this field.
-
-. Enter the name of the currency type in Currency Label field. No limits exist on the number of characters that can be entered in this field.
-
-. Click Save.
-
-Edit a currency type
-^^^^^^^^^^^^^^^^^^^^
-
-. To edit a currency type, click your cursor in the row that you want to edit. The row will turn blue.
-
-. Double~click. The pop~up box will appear, and you can edit the fields.
-
-. After making changes, click Save.
-
-[NOTE]
-From the currency types interface, you can delete currencies that have never been applied to funds or used to make purchases.
-
-Distribution Formulas
-~~~~~~~~~~~~~~~~~~~~~
-
-Distribution formulas allow you to specify the number of copies that should be distributed to specific branches. You can create and reuse formulas as needed.
-
-Create a distribution formula
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-. Click _Admin -> Server Administration -> Acquisitions ->Distribution Formulas_.
-. Click _New Formula_.
-. Enter a Formula Name. No limits exist on the number of characters that can be entered in this field.
-. Choose a Formula Owner from the drop down menu. The Formula Owner indicates the organizational units whose staff can use this formula. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
-+
-[NOTE]
-The rule of parental inheritance applies to this list.
-+
-. Ignore the Skip Count field which is currently not used.
-. Click _Save_.
-. Click _New Entry_.
-. Select an Owning Library from the drop down menu. This indicates the branch that will receive the items. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See _Admin -> Server Administration -> Organizational Units_).
-. Select a Shelving Location from the drop down menu.
-. In the Item Count field, enter the number of items that should be distributed to the branch. You can enter the number or use the arrows on the right side of the field.
-. Click _Apply Changes_. The screen will reload.
-. To view the changes to your formula, click Admin -> Server Administration -> Acquisitions -> Distribution Formulas. The item_count will reflect the entries to your distribution formula.
-
-[NOTE]
-To edit the Formula Name, click the hyperlinked name of the formula in the top left corner. A pop up box will enable you to enter a new formula name.
-
-Edit a distribution formula
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-To edit a distribution formula, click the hyperlinked title of the formula.
-
-EDI
-~~~
-Many libraries use Electronic Data Interchange (EDI) accounts to order new acquisitions. Users can set up EDI accounts and manage EDI messages in the admin module. EDI messages and notes can be viewed in the acquisitions module. See also the link:../installation/edi_setup.txt[EDI Installation Instructions] because this is required for use of EDI.
-
-The following fields are required to create an EDI account:
-
-[NOTE]
-host, username, password, path, and incoming directory.
-
-EDI Accounts
-^^^^^^^^^^^^
-
-Create EDI Accounts to communicate electronically with providers.
-
-. Create a label. The label allows you to differentiate between accounts for the same provider. No limits exist on the number of characters that can be entered in this field.
-. Enter a host. Your provider will provide you with the requisite FTP or SCP information.
-. Enter the username that has been supplied by your provider.
-. Enter the password that has been supplied by your provider.
-. Enter account information. This field enables you to add a supplemental password for entry to a remote system after log in has been completed. This field is optional for the ILS but may be required by your provider.
-. Select an owner from the drop down menu. The owner indicates the organizational units whose staff can use this EDI account. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
-+
-[NOTE]
-The rule of parental inheritance applies to this list.
-+
-. The Last Activity updates automatically with any inbound or outbound communication.
-. Select a provider from the drop down menu to whom this account belongs.
-. Enter a path. The path indicates the remote location on the server from which files are pulled in to the ILS.
-. Enter the incoming directory. This directory indicates the location on your local network to which the files download.
-. Enter the vendor account number supplied by your provider.
-. Enter the vendor account code supplied by your provider.
-. Click Save.
-
-EDI Messages
-^^^^^^^^^^^^
-
-The EDI messages screen displays all incoming and outgoing messages between the library and the vendor.
-
-Exchange Rates
-~~~~~~~~~~~~~~
-
-Exchange rates define the rate of exchange between currencies. Evergreen will automatically calculate exchange rates for purchases. Evergreen assumes that the currency of the purchasing fund is identical to the currency of the provider, but it provides for two unique situations: If the currency of the fund that is used for the purchase is different from the currency of the provider as listed in the provider profile, then Evergreen will use the exchange rate to calculate the price of the item in the currency of the fund and debit the fund accordingly. When money is transferred between funds that use different currency types, Evergreen will automatically use the exchange rate to convert the money to the currency of the receiving fund. During such transfers, however, staff can override the automatic conversion by providing an explicit amount to credit to the receiving fund.
-
-Create an exchange rate
-^^^^^^^^^^^^^^^^^^^^^^^
-
-. To create a new exchange rate, click _Admin -> Server Administration -> Acquisitions -> Exchange Rates_.
-
-. Click New Exchange Rate.
-
-. Enter the From Currency from the drop down menu populated by the currency types.
-
-. Enter the To Currency from the drop down menu populated by the currency types.
-
-. Enter the exchange Ratio.
-
-. Click _Save_.
-
-Edit an Exchange Rate
-^^^^^^^^^^^^^^^^^^^^^
-
-Edit an exchange rate just as you would edit a currency type.
-
-MARC Federated Search
-~~~~~~~~~~~~~~~~~~~~~
-
-The MARC Federated Search enables you to import bibliographic records into a selection list or purchase order from a Z39.50 source.
-
-. Click _Acquisitions -> MARC Federated Search_.
-. Check the boxes of Z39.50 services that you want to search. Your local Evergreen Catalog is checked by default. Click Submit.
-+
-image::media/acq_marc_search.png[search form]
-+
-. A list of results will appear. Click the _Copies_ link to add copy information to the line item. See the link:line_items.txt[section on Line Items] for more information.
-. Click the Notes link to add notes or line item alerts to the line item. See the link:line_items.txt[section on Line Items] for more information.
-. Enter a price in the _Estimated Price_ field.
-. You can save the line item(s) to a selection list by checking the box on the line item and clicking _Actions -> Save Items to Selection List_. You can also create a purchase order from the line item(s) by checking the box on the line item and clicking _Actions -> Create Purchase Order_.
-
-image::media/acq_marc_search-2.png[line item]
-
-Fund Tags
-~~~~~~~~~
-
-You can apply tags to funds so that you can group funds for easy reporting. For example, you have three funds for children's materials: Children's Board Books, Children's DVDs, and Children's CDs. Assign a fund tag of 'children's' to each fund. When you need to report on the amount that has been spent on all children's materials, you can run a report on the fund tag to find total expenditures on children's materials rather than reporting on each individual fund.
-
-Create a Fund Tag
-
-. To create a fund tag, click _Admin -> Server Administration -> Acquisitions -> Fund Tags_.
-. Click _New Fund Tag_. No limits exist on the number of characters that can be entered in this field.
-. Select a Fund Tag Owner from the drop down menu. The owner indicates the organizational unit(s) whose staff can use this fund tag. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
-+
-[NOTE]
-The rule of parental inheritance applies to this list.
-+
-. Enter a Fund Tag Name. No limits exist on the number of characters that can be entered in this field.
-. Click _Save_.
-
-Funding Sources
-~~~~~~~~~~~~~~~
-
-Funding sources allow you to specify the sources that contribute monies to your fund(s). You can create as few or as many funding sources as you need. These can be used to track exact amounts for accounts in your general ledger. You can then use funds to track spending and purchases for specific collections.
-
-Create a funding source
-^^^^^^^^^^^^^^^^^^^^^^^
-
-. To create a new funding source, click _Admin -> Server Administration -> Acquisitions -> Funding Source_.
-. Enter a funding source name. No limits exist on the number of characters that can be entered in this field.
-. Select an owner from the drop down menu. The owner indicates the organizational unit(s) whose staff can use this funding source. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
-+
-[NOTE]
-The rule of parental inheritance applies to this list. For example, if a system is made the owner of a funding source, then users with appropriate permissions at the branches within the system could also use the funding source.
-+
-. Create a code for the source. No limits exist on the number of characters that can be entered in this field.
-. Select a currency from the drop down menu. This menu is populated from the choices in the Currency Types interface.
-. Click _Save_.
-
-Allocate Credits to Funding Sources
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-. Apply a credit to this funding source.
-
-. Enter the amount of money that the funding source contributes to the organization. Funding sources are not tied to fiscal or calendar years, so you can continue to add money to the same funding source over multiple years, e.g. County Funding. Alternatively, you can name funding sources by year, e.g. County Funding 2010 and County Funding 2011, and apply credits each year to the matching source.
-
-. To apply a credit, click on the hyperlinked name of the funding source. The Funding Source Details will appear.
-
-. Click _Apply Credit_.
-
-. Enter an amount to apply to this funding source.
-
-. Enter a note. This field is optional.
-
-. Click _Apply_.
-
-Allocate credits to funds
-^^^^^^^^^^^^^^^^^^^^^^^^^
-
-If you have already set up your funds, then you can then click the Allocate to Fund button to apply credits from the funding sources to the funds. If you have not yet set up your funds, or you need to add a new one, you can allocate credits to funds from the funds interface. See section 1.2 for more information.
-
-. To allocate credits to funds, click _Allocate to Fund_.
-
-. Enter the amount that you want to allocate.
-
-. Enter a note. This field is optional.
-
-. Click _Apply_.
-
-Track Debits and Credits
-^^^^^^^^^^^^^^^^^^^^^^^^
-
-You can track credits to and allocations from each funding source. These amounts are updated when credits and allocations are made in the Funding Source Details. Access the Funding Source Details by clicking on the hyperlinked name of the Funding Source.
-
-Funds
-~~~~~
-
-Funds allow you to allocate credits toward specific purchases. In the funds interface, you can create funds; allocate credits from funding sources to funds; transfer money between funds; and apply fund tags to funds. Funds are created for a specific year, either fiscal or calendar. These funds are owned by org units. At the top of the funds interface, you can set a contextual org unit and year. The drop down menu at the top of the screen enables you to focus on funds that are owned by specific organizational units during specific years.
-
-Create a fund
-^^^^^^^^^^^^^
-
-. To create a new fund, click _Admin -> Server Administration -> Acquisitions -> Funds_.
-. Enter a name for the fund. No limits exist on the number of characters that can be entered in this field.
-. Create a code for the fund. No limits exist on the number of characters that can be entered in this field.
-. Enter a year for the fund. This can be a fiscal year or a calendar year. The format of the year is YYYY.
-. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this fund. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
-+
-[NOTE]
-The rule of parental inheritance applies to this list. See section
-+
-. Select a currency type from the drop down menu. This menu is comprised of entries in the currency types menu. When a fund is applied to a line item or copy, the price of the item will be encumbered in the currency associated with the fund.
-. Click the Active box to activate this fund. You cannot make purchases from this fund if it is not active.
-. Enter a Balance Stop Percent. The balance stop percent prevents you from making purchases when only a specified amount of the fund remains. For example, if you want to spend 95 percent of your funds, leaving a five percent balance in the fund, then you would enter 95 in the field. When the fund reaches its balance stop percent, it will appear in red when you apply funds to copies.
-. Enter a Balance Warning Percent. The balance warning percent gives you a warning that the fund is low. You can specify any percent. For example, if you want to spend 90 percent of your funds and be warned when the fund has only 10 percent of its balance remaining, then enter 90 in the field. When the fund reaches its balance warning percent, it will appear in yellow when you apply funds to copies.
-. Check the Propagate box to propagate funds. When you propagate a fund, the ILS will create a new fund for the following fiscal year with the same parameters as your current fund. All of the settings transfer except for the year and the amount of money in the fund. Propagation occurs during the fiscal year close~out operation.
-. Check the Rollover box if you want to roll over remaining funds into the same fund next year.
-. Click _Save_.
-
-Allocate Credits from Funding Sources to Funds
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Credits can be applied to funds from funding sources using the fund interface. The credits that you apply to the fund can be applied later to purchases.
-
-. To access funds, click _Admin -> Server Administration -> Acquisitions -> Funds_.
-
-. Click the hyperlinked name of the fund.
-
-. To add a credit to the fund, click the Create Allocation tab.
-
-. Choose a Funding Source from the drop down menu.
-
-. Enter an amount that you want to apply to the fund from the funding source.
-
-. Enter a note. This field is optional.
-
-. Click _Apply_.
-
-Transfer credits between funds
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-The credits that you allocate to funds can be transferred between funds if desired. In the following example, you can transfer $500.00 from the Young Adult Fiction fund to the Children's DVD fund.
-
-. To access funds, click _Admin -> Server Administration -> Acquisitions -> Funds_.
-
-. Click the hyperlinked name of the originating fund.
-
-. The Fund Details screen appears. Click Transfer Money.
-
-. Enter the amount that you would like to transfer.
-
-. From the drop down menu, select the destination fund.
-
-. Add a note. This field is optional.
-
-. Click _Transfer_.
-
-Track Balances and Expenditures
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-The Fund Details allows you to track the fund's balance, encumbrances, and amount spent. It also allows you to track allocations from the funding source(s), debits, and fund tags.
-
-. To access the fund details, click on the hyperlinked name of the fund that you created.
-
-. The Summary allows you to track the following:
-
-. Balance - The balance is calculated by subtracting both items that have been invoiced and encumbrances from the total allocated to the fund.
-. Total Allocated - This amount is the total amount allocated from the Funding Source.
-. Spent Balance - This balance is calculated by subtracting only the items that have been invoiced from the total allocated to the fund. It does not include encumbrances.
-. Total Debits - The total debits are calculated by adding the cost of items that have been invoiced and encumbrances.
-. Total Spent - The total spent is calculated by adding the cost of items that have been invoiced. It does not include encumbrances.
-. Total Encumbered - The total encumbered is calculated by adding all encumbrances.
-
-Edit a Fund
-^^^^^^^^^^^
-
-Edit a fund just as you would edit a currency type.
-
-Perform Year End Closeout Operation
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-The Year End Closeout Operation allows you to deactivate funds for the current year and create analogous funds for the next year. It transfers encumbrances to the analogous funds, and it rolls over any remaining funds if you checked the rollover box when creating the fund.
-
-. To access the year end closeout of a fund, click Admin -> Server Administration -> Acquisitions -> Funds.
-
-. Click _Fund Propagation and Rollover_.
-
-. Check the box adjacent to _Perform Fiscal Year Close~Out Operation_.
-
-. Notice that the context org unit reflects the context org unit that you selected at the top of the Funds screen.
-
-. If you want to perform the close~out operation on the context org unit and its child units, then check the box adjacent to Include Funds for Descendant Org Units.
-
-. Check the box adjacent to dry run if you want to test changes to the funds before they are enacted. Evergreen will generate a summary of the changes that would occur during the selected operations. No data will be changed.
-
-. Click _Process_.
-
-. Evergreen will begin the propagation process. Evergreen will make a clone of each fund, but it will increment the year by .
-
-Invoice menus
-~~~~~~~~~~~~~
-
-Invoice menus allow you to create drop down menus that appear on invoices. You can create an invoice item type or invoice payment method.
-
-Invoice item type
-^^^^^^^^^^^^^^^^^
-
-The invoice item type allows you to enter the types of additional charges that you can add to an invoice. Examples of additional charge types might include taxes or processing fees. Charges for bibliographic items are listed separately from these additional charges. A default list of charge types displays, but you can add custom charge types to this list. Invoice item types can also be used when adding non~bibliographic items to a purchase order. When invoiced, the invoice item type will copy from the purchase order to the invoice.
-
-. To create a new charge type, click _Admin -> Server Administration -> Acquisitions -> Invoice Item Type_.
-
-. Click _New Invoice Item Type_.
-
-. Create a code for the charge type. No limits exist on the number of characters that can be entered in this field.
-
-. Create a label. No limits exist on the number of characters that can be entered in this field. The text in this field appears in the drop down menu on the invoice.
-
-. If items on the invoice were purchased with the monies in multiple funds, then you can divide the additional charge across funds. Check the box adjacent to Prorate-> if you want to prorate the charge across funds.
-
-. Click _Save_.
-
-Invoice payment method
-^^^^^^^^^^^^^^^^^^^^^^
-
-The invoice payment method allows you to predefine the type(s) of invoices and payment method(s) that you accept. The text that you enter in the admin module will appear as a drop down menu in the invoice type and payment method fields on the invoice.
-
-. To create a new invoice payment method, click _Admin -> Server Administration -> Acquisitions -> Invoice Payment Method_.
-
-. Click _New Invoice Payment Method_.
-
-. Create a code for the invoice payment method. No limits exist on the number of characters that can be entered in this field.
-
-. Create a name for the invoice payment method. No limits exist on the number of characters that can be entered in this field. The text in this field appears in the drop down menu on the invoice.
-
-. Click _Save_.
-
-Payment methods can be deleted from this screen.
-
-Line item features
-~~~~~~~~~~~~~~~~~~
-
-Line item alerts are predefined text that can be added to line items that are on selection lists or purchase orders. You can define the alerts from which staff can choose. Line item alerts appear in a pop up box when the line item, or any of its copies, are marked as received.
-
-Create a line item alert
-^^^^^^^^^^^^^^^^^^^^^^^^
-
-. To create a line item alert, click _Administration -> Server Administration -> Acquisitions -> Line Item Alerts_.
-
-. Click _New Line Item Alert Text_.
-
-. Create a code for the text. No limits exist on the number of characters that can be entered in this field.
-
-. Create a description for the text. No limits exist on the number of characters that can be entered in this field.
-
-. Select an owning library from the drop down menu. The owning library indicates the organizational units whose staff can use this alert. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
-
-. Click _Save_.
-
-Line Item MARC Attribute Definitions
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Line item attributes define the fields that Evergreen needs to extract from the bibliographic records that are in the acquisitions database to display in the catalog. Also, these attributes will appear as fields in the New Brief Record interface. You will be able to enter information for the brief record in the fields where attributes have been defined.
-
+Acquisitions Administration
+---------------------------
+
+Acquisitions Permissions in the Admin module
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Several setting in the Library Settings area of the Admin module pertain to functions in the Acquisitions module. You can access these settings by clicking _Admin -> Local Administration ->Library Settings Editor_.
+
+* CAT: Delete bib if all copies are deleted via Acquisitions lineitem cancellation - If you cancel a line item, then all of the on order copies in the catalog are deleted. If, when you cancel a line item, you also want to delete the bib record, then set this setting to TRUE.
+* Default circulation modifier - This modifier would be applied to items that are created in the acquisitions module
+* Default copy location - This copy location would be applied to items that are created in the acquisitions module
+* Fund Spending Limit for Block - When the amount remaining in the fund, including spent money and encumbrances, goes below this percentage, attempts to spend from the fund will be blocked.
+* Fund Spending Limit for Warning - When the amount remaining in the fund, including spent money and encumbrances, goes below this percentage, attempts to spend from the fund will result in a warning to the staff.
+* Temporary barcode prefix - Temporary barcode prefix for items that are created in the acquisitions module
+* Temporary call number prefix - Temporary call number prefix for items that are created in the acquisitions module
+
+Cancel/Suspend reasons
+~~~~~~~~~~~~~~~~~~~~~~
+
+The Cancel reasons link enables you to predefine the reasons for which a line item or a PO can be cancelled. A default list of reasons appears, but you can add custom reasons to this list. Applying the cancel reason will prevent the item from appearing in a claims list and will allow you to cancel debits associated with the purchase. Cancel reasons also enable you to suspend or delay a purchase. For example, you could create a cancel reason of 'back ordered,' and you could choose to keep the debits associated with the purchase.
+
+Create a cancel/suspend reason
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+. To add a new cancel reason, click _Administration -> Server Administration -> Acquisitions -> Cancel reasons_.
+
+. Click _New Cancel Reason_.
+
+. Select a using library from the drop down menu. The using library indicates the organizational units whose staff can use this cancel reason. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units.)
+
+. Create a label for the cancel reason. This label will appear when you select a cancel reason on an item or a PO.
+
+. Create a description of the cancel reason. This is a free text field and can be comprised of any text of your choosing.
+
+. If you want to retain the debits associated with the cancelled purchase, click the box adjacent to Keep Debits->
+
+. Click _Save_.
+
+Claiming
+~~~~~~~~
+Currently, all claiming is manual, but the admin module enables you to build claim policies and specify the action(s) that users should take to claim items.
+
+Create a claim policy
+^^^^^^^^^^^^^^^^^^^^^
+
+The claim policy link enables you to name the claim policy and specify the organization that owns it.
+
+. To create a claim policy, click _Admin -> Server Administration -> Acquisitions -> Claim Policies_.
+. Create a claim policy name. No limits exist on the number of characters that can be entered in this field.
+. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this claim policy. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
++
+[NOTE]
+The rule of parental inheritance applies to this list.
++
+. Enter a description. No limits exist on the number of characters that can be entered in this field.
+. Click _Save_.
+
+Create a claim type
+^^^^^^^^^^^^^^^^^^^
+
+The claim type link enables you to specify the reason for a type of claim.
+
+. To create a claim type, click _Admin -> Server Administration -> Acquisitions -> Claim types_.
+. Create a claim type. No limits exist on the number of characters that can be entered in this field.
+. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this claim type. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
++
+[NOTE]
+The rule of parental inheritance applies to this list.
++
+. Enter a description. No limits exist on the number of characters that can be entered in this field.
+. Click _Save_.
+
+Create a claim event type
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The claim event type describes the physical action that should occur when an item needs to be claimed. For example, the user should notify the vendor via email that the library is claiming an item.
+
+. To access the claim event types, click _Admin -> Server Administration -> Acquisitions ->Claim event type_.
+. Enter a code for the claim event type. No limits exist on the number of characters that can be entered in this field.
+. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this event type. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
++
+[NOTE]
+The rule of parental inheritance applies to this list.
++
+. Enter a description. No limits exist on the number of characters that can be entered in this field.
+. If this claim is initiated by the user, then check the box adjacent to Library Initiated.
++
+[NOTE]
+Currently, all claims are initiated by a user. The ILS cannot automatically claim an issue.
++
+. Click _Save_.
+
+Create a claim policy action
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The claim policy action enables you to specify how long a user should wait before claiming the item.
+
+. To access claim policy actions, click _Admin -> Server Administration -> Acquisitions ->Claim Policy Actions_.
+
+. Select an Action (Event Type) from the drop down menu.
+
+. Enter an action interval. This field indicates how long a user should wait before claiming the item.
+
+. In the Claim Policy ID field, select a claim policy from the drop down menu.
+
+. Click _Save_.
+
+[NOTE]
+You can create claim cycles by adding multiple claim policy actions to a claim policy.
+
+Currency Types
+~~~~~~~~~~~~~~
+
+Currency types can be created and applied to funds in the administrative module. When a fund is applied to a copy or line item for purchase, the item will be purchased in the currency associated with that fund.
+
+Create a currency type
+^^^^^^^^^^^^^^^^^^^^^^
+
+. To create a new currency type, click _Admin -> Server Administration -> Acquisitions -> Currency types_.
+
+. Enter the currency code. No limits exist on the number of characters that can be entered in this field.
+
+. Enter the name of the currency type in Currency Label field. No limits exist on the number of characters that can be entered in this field.
+
+. Click Save.
+
+Edit a currency type
+^^^^^^^^^^^^^^^^^^^^
+
+. To edit a currency type, click your cursor in the row that you want to edit. The row will turn blue.
+
+. Double~click. The pop~up box will appear, and you can edit the fields.
+
+. After making changes, click Save.
+
+[NOTE]
+From the currency types interface, you can delete currencies that have never been applied to funds or used to make purchases.
+
+Distribution Formulas
+~~~~~~~~~~~~~~~~~~~~~
+
+Distribution formulas allow you to specify the number of copies that should be distributed to specific branches. You can create and reuse formulas as needed.
+
+Create a distribution formula
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+. Click _Admin -> Server Administration -> Acquisitions ->Distribution Formulas_.
+. Click _New Formula_.
+. Enter a Formula Name. No limits exist on the number of characters that can be entered in this field.
+. Choose a Formula Owner from the drop down menu. The Formula Owner indicates the organizational units whose staff can use this formula. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
++
+[NOTE]
+The rule of parental inheritance applies to this list.
++
+. Ignore the Skip Count field which is currently not used.
+. Click _Save_.
+. Click _New Entry_.
+. Select an Owning Library from the drop down menu. This indicates the branch that will receive the items. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See _Admin -> Server Administration -> Organizational Units_).
+. Select a Shelving Location from the drop down menu.
+. In the Item Count field, enter the number of items that should be distributed to the branch. You can enter the number or use the arrows on the right side of the field.
+. Click _Apply Changes_. The screen will reload.
+. To view the changes to your formula, click Admin -> Server Administration -> Acquisitions -> Distribution Formulas. The item_count will reflect the entries to your distribution formula.
+
+[NOTE]
+To edit the Formula Name, click the hyperlinked name of the formula in the top left corner. A pop up box will enable you to enter a new formula name.
+
+Edit a distribution formula
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+To edit a distribution formula, click the hyperlinked title of the formula.
+
+EDI
+~~~
+Many libraries use Electronic Data Interchange (EDI) accounts to order new acquisitions. Users can set up EDI accounts and manage EDI messages in the admin module. EDI messages and notes can be viewed in the acquisitions module. See also the link:../installation/edi_setup.txt[EDI Installation Instructions] because this is required for use of EDI.
+
+The following fields are required to create an EDI account:
+
+[NOTE]
+host, username, password, path, and incoming directory.
+
+EDI Accounts
+^^^^^^^^^^^^
+
+Create EDI Accounts to communicate electronically with providers.
+
+. Create a label. The label allows you to differentiate between accounts for the same provider. No limits exist on the number of characters that can be entered in this field.
+. Enter a host. Your provider will provide you with the requisite FTP or SCP information.
+. Enter the username that has been supplied by your provider.
+. Enter the password that has been supplied by your provider.
+. Enter account information. This field enables you to add a supplemental password for entry to a remote system after log in has been completed. This field is optional for the ILS but may be required by your provider.
+. Select an owner from the drop down menu. The owner indicates the organizational units whose staff can use this EDI account. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
++
+[NOTE]
+The rule of parental inheritance applies to this list.
++
+. The Last Activity updates automatically with any inbound or outbound communication.
+. Select a provider from the drop down menu to whom this account belongs.
+. Enter a path. The path indicates the remote location on the server from which files are pulled in to the ILS.
+. Enter the incoming directory. This directory indicates the location on your local network to which the files download.
+. Enter the vendor account number supplied by your provider.
+. Enter the vendor account code supplied by your provider.
+. Click Save.
+
+EDI Messages
+^^^^^^^^^^^^
+
+The EDI messages screen displays all incoming and outgoing messages between the library and the vendor.
+
+Exchange Rates
+~~~~~~~~~~~~~~
+
+Exchange rates define the rate of exchange between currencies. Evergreen will automatically calculate exchange rates for purchases. Evergreen assumes that the currency of the purchasing fund is identical to the currency of the provider, but it provides for two unique situations: If the currency of the fund that is used for the purchase is different from the currency of the provider as listed in the provider profile, then Evergreen will use the exchange rate to calculate the price of the item in the currency of the fund and debit the fund accordingly. When money is transferred between funds that use different currency types, Evergreen will automatically use the exchange rate to convert the money to the currency of the receiving fund. During such transfers, however, staff can override the automatic conversion by providing an explicit amount to credit to the receiving fund.
+
+Create an exchange rate
+^^^^^^^^^^^^^^^^^^^^^^^
+
+. To create a new exchange rate, click _Admin -> Server Administration -> Acquisitions -> Exchange Rates_.
+
+. Click New Exchange Rate.
+
+. Enter the From Currency from the drop down menu populated by the currency types.
+
+. Enter the To Currency from the drop down menu populated by the currency types.
+
+. Enter the exchange Ratio.
+
+. Click _Save_.
+
+Edit an Exchange Rate
+^^^^^^^^^^^^^^^^^^^^^
+
+Edit an exchange rate just as you would edit a currency type.
+
+MARC Federated Search
+~~~~~~~~~~~~~~~~~~~~~
+
+The MARC Federated Search enables you to import bibliographic records into a selection list or purchase order from a Z39.50 source.
+
+. Click _Acquisitions -> MARC Federated Search_.
+. Check the boxes of Z39.50 services that you want to search. Your local Evergreen Catalog is checked by default. Click Submit.
++
+image::media/acq_marc_search.png[search form]
++
+. A list of results will appear. Click the _Copies_ link to add copy information to the line item. See the link:line_items.txt[section on Line Items] for more information.
+. Click the Notes link to add notes or line item alerts to the line item. See the link:line_items.txt[section on Line Items] for more information.
+. Enter a price in the _Estimated Price_ field.
+. You can save the line item(s) to a selection list by checking the box on the line item and clicking _Actions -> Save Items to Selection List_. You can also create a purchase order from the line item(s) by checking the box on the line item and clicking _Actions -> Create Purchase Order_.
+
+image::media/acq_marc_search-2.png[line item]
+
+Fund Tags
+~~~~~~~~~
+
+You can apply tags to funds so that you can group funds for easy reporting. For example, you have three funds for children's materials: Children's Board Books, Children's DVDs, and Children's CDs. Assign a fund tag of 'children's' to each fund. When you need to report on the amount that has been spent on all children's materials, you can run a report on the fund tag to find total expenditures on children's materials rather than reporting on each individual fund.
+
+Create a Fund Tag
+
+. To create a fund tag, click _Admin -> Server Administration -> Acquisitions -> Fund Tags_.
+. Click _New Fund Tag_. No limits exist on the number of characters that can be entered in this field.
+. Select a Fund Tag Owner from the drop down menu. The owner indicates the organizational unit(s) whose staff can use this fund tag. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
++
+[NOTE]
+The rule of parental inheritance applies to this list.
++
+. Enter a Fund Tag Name. No limits exist on the number of characters that can be entered in this field.
+. Click _Save_.
+
+Funding Sources
+~~~~~~~~~~~~~~~
+
+Funding sources allow you to specify the sources that contribute monies to your fund(s). You can create as few or as many funding sources as you need. These can be used to track exact amounts for accounts in your general ledger. You can then use funds to track spending and purchases for specific collections.
+
+Create a funding source
+^^^^^^^^^^^^^^^^^^^^^^^
+
+. To create a new funding source, click _Admin -> Server Administration -> Acquisitions -> Funding Source_.
+. Enter a funding source name. No limits exist on the number of characters that can be entered in this field.
+. Select an owner from the drop down menu. The owner indicates the organizational unit(s) whose staff can use this funding source. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
++
+[NOTE]
+The rule of parental inheritance applies to this list. For example, if a system is made the owner of a funding source, then users with appropriate permissions at the branches within the system could also use the funding source.
++
+. Create a code for the source. No limits exist on the number of characters that can be entered in this field.
+. Select a currency from the drop down menu. This menu is populated from the choices in the Currency Types interface.
+. Click _Save_.
+
+Allocate Credits to Funding Sources
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+. Apply a credit to this funding source.
+
+. Enter the amount of money that the funding source contributes to the organization. Funding sources are not tied to fiscal or calendar years, so you can continue to add money to the same funding source over multiple years, e.g. County Funding. Alternatively, you can name funding sources by year, e.g. County Funding 2010 and County Funding 2011, and apply credits each year to the matching source.
+
+. To apply a credit, click on the hyperlinked name of the funding source. The Funding Source Details will appear.
+
+. Click _Apply Credit_.
+
+. Enter an amount to apply to this funding source.
+
+. Enter a note. This field is optional.
+
+. Click _Apply_.
+
+Allocate credits to funds
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+If you have already set up your funds, then you can then click the Allocate to Fund button to apply credits from the funding sources to the funds. If you have not yet set up your funds, or you need to add a new one, you can allocate credits to funds from the funds interface. See section 1.2 for more information.
+
+. To allocate credits to funds, click _Allocate to Fund_.
+
+. Enter the amount that you want to allocate.
+
+. Enter a note. This field is optional.
+
+. Click _Apply_.
+
+Track Debits and Credits
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+You can track credits to and allocations from each funding source. These amounts are updated when credits and allocations are made in the Funding Source Details. Access the Funding Source Details by clicking on the hyperlinked name of the Funding Source.
+
+Funds
+~~~~~
+
+Funds allow you to allocate credits toward specific purchases. In the funds interface, you can create funds; allocate credits from funding sources to funds; transfer money between funds; and apply fund tags to funds. Funds are created for a specific year, either fiscal or calendar. These funds are owned by org units. At the top of the funds interface, you can set a contextual org unit and year. The drop down menu at the top of the screen enables you to focus on funds that are owned by specific organizational units during specific years.
+
+Create a fund
+^^^^^^^^^^^^^
+
+. To create a new fund, click _Admin -> Server Administration -> Acquisitions -> Funds_.
+. Enter a name for the fund. No limits exist on the number of characters that can be entered in this field.
+. Create a code for the fund. No limits exist on the number of characters that can be entered in this field.
+. Enter a year for the fund. This can be a fiscal year or a calendar year. The format of the year is YYYY.
+. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this fund. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
++
+[NOTE]
+The rule of parental inheritance applies to this list. See section
++
+. Select a currency type from the drop down menu. This menu is comprised of entries in the currency types menu. When a fund is applied to a line item or copy, the price of the item will be encumbered in the currency associated with the fund.
+. Click the Active box to activate this fund. You cannot make purchases from this fund if it is not active.
+. Enter a Balance Stop Percent. The balance stop percent prevents you from making purchases when only a specified amount of the fund remains. For example, if you want to spend 95 percent of your funds, leaving a five percent balance in the fund, then you would enter 95 in the field. When the fund reaches its balance stop percent, it will appear in red when you apply funds to copies.
+. Enter a Balance Warning Percent. The balance warning percent gives you a warning that the fund is low. You can specify any percent. For example, if you want to spend 90 percent of your funds and be warned when the fund has only 10 percent of its balance remaining, then enter 90 in the field. When the fund reaches its balance warning percent, it will appear in yellow when you apply funds to copies.
+. Check the Propagate box to propagate funds. When you propagate a fund, the ILS will create a new fund for the following fiscal year with the same parameters as your current fund. All of the settings transfer except for the year and the amount of money in the fund. Propagation occurs during the fiscal year close~out operation.
+. Check the Rollover box if you want to roll over remaining funds into the same fund next year.
+. Click _Save_.
+
+Allocate Credits from Funding Sources to Funds
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Credits can be applied to funds from funding sources using the fund interface. The credits that you apply to the fund can be applied later to purchases.
+
+. To access funds, click _Admin -> Server Administration -> Acquisitions -> Funds_.
+
+. Click the hyperlinked name of the fund.
+
+. To add a credit to the fund, click the Create Allocation tab.
+
+. Choose a Funding Source from the drop down menu.
+
+. Enter an amount that you want to apply to the fund from the funding source.
+
+. Enter a note. This field is optional.
+
+. Click _Apply_.
+
+Transfer credits between funds
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The credits that you allocate to funds can be transferred between funds if desired. In the following example, you can transfer $500.00 from the Young Adult Fiction fund to the Children's DVD fund.
+
+. To access funds, click _Admin -> Server Administration -> Acquisitions -> Funds_.
+
+. Click the hyperlinked name of the originating fund.
+
+. The Fund Details screen appears. Click Transfer Money.
+
+. Enter the amount that you would like to transfer.
+
+. From the drop down menu, select the destination fund.
+
+. Add a note. This field is optional.
+
+. Click _Transfer_.
+
+Track Balances and Expenditures
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The Fund Details allows you to track the fund's balance, encumbrances, and amount spent. It also allows you to track allocations from the funding source(s), debits, and fund tags.
+
+. To access the fund details, click on the hyperlinked name of the fund that you created.
+
+. The Summary allows you to track the following:
+
+. Balance - The balance is calculated by subtracting both items that have been invoiced and encumbrances from the total allocated to the fund.
+. Total Allocated - This amount is the total amount allocated from the Funding Source.
+. Spent Balance - This balance is calculated by subtracting only the items that have been invoiced from the total allocated to the fund. It does not include encumbrances.
+. Total Debits - The total debits are calculated by adding the cost of items that have been invoiced and encumbrances.
+. Total Spent - The total spent is calculated by adding the cost of items that have been invoiced. It does not include encumbrances.
+. Total Encumbered - The total encumbered is calculated by adding all encumbrances.
+
+Edit a Fund
+^^^^^^^^^^^
+
+Edit a fund just as you would edit a currency type.
+
+Perform Year End Closeout Operation
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The Year End Closeout Operation allows you to deactivate funds for the current year and create analogous funds for the next year. It transfers encumbrances to the analogous funds, and it rolls over any remaining funds if you checked the rollover box when creating the fund.
+
+. To access the year end closeout of a fund, click Admin -> Server Administration -> Acquisitions -> Funds.
+
+. Click _Fund Propagation and Rollover_.
+
+. Check the box adjacent to _Perform Fiscal Year Close~Out Operation_.
+
+. Notice that the context org unit reflects the context org unit that you selected at the top of the Funds screen.
+
+. If you want to perform the close~out operation on the context org unit and its child units, then check the box adjacent to Include Funds for Descendant Org Units.
+
+. Check the box adjacent to dry run if you want to test changes to the funds before they are enacted. Evergreen will generate a summary of the changes that would occur during the selected operations. No data will be changed.
+
+. Click _Process_.
+
+. Evergreen will begin the propagation process. Evergreen will make a clone of each fund, but it will increment the year by .
+
+Invoice menus
+~~~~~~~~~~~~~
+
+Invoice menus allow you to create drop down menus that appear on invoices. You can create an invoice item type or invoice payment method.
+
+Invoice item type
+^^^^^^^^^^^^^^^^^
+
+The invoice item type allows you to enter the types of additional charges that you can add to an invoice. Examples of additional charge types might include taxes or processing fees. Charges for bibliographic items are listed separately from these additional charges. A default list of charge types displays, but you can add custom charge types to this list. Invoice item types can also be used when adding non~bibliographic items to a purchase order. When invoiced, the invoice item type will copy from the purchase order to the invoice.
+
+. To create a new charge type, click _Admin -> Server Administration -> Acquisitions -> Invoice Item Type_.
+
+. Click _New Invoice Item Type_.
+
+. Create a code for the charge type. No limits exist on the number of characters that can be entered in this field.
+
+. Create a label. No limits exist on the number of characters that can be entered in this field. The text in this field appears in the drop down menu on the invoice.
+
+. If items on the invoice were purchased with the monies in multiple funds, then you can divide the additional charge across funds. Check the box adjacent to Prorate-> if you want to prorate the charge across funds.
+
+. Click _Save_.
+
+Invoice payment method
+^^^^^^^^^^^^^^^^^^^^^^
+
+The invoice payment method allows you to predefine the type(s) of invoices and payment method(s) that you accept. The text that you enter in the admin module will appear as a drop down menu in the invoice type and payment method fields on the invoice.
+
+. To create a new invoice payment method, click _Admin -> Server Administration -> Acquisitions -> Invoice Payment Method_.
+
+. Click _New Invoice Payment Method_.
+
+. Create a code for the invoice payment method. No limits exist on the number of characters that can be entered in this field.
+
+. Create a name for the invoice payment method. No limits exist on the number of characters that can be entered in this field. The text in this field appears in the drop down menu on the invoice.
+
+. Click _Save_.
+
+Payment methods can be deleted from this screen.
+
+Line item features
+~~~~~~~~~~~~~~~~~~
+
+Line item alerts are predefined text that can be added to line items that are on selection lists or purchase orders. You can define the alerts from which staff can choose. Line item alerts appear in a pop up box when the line item, or any of its copies, are marked as received.
+
+Create a line item alert
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+. To create a line item alert, click _Administration -> Server Administration -> Acquisitions -> Line Item Alerts_.
+
+. Click _New Line Item Alert Text_.
+
+. Create a code for the text. No limits exist on the number of characters that can be entered in this field.
+
+. Create a description for the text. No limits exist on the number of characters that can be entered in this field.
+
+. Select an owning library from the drop down menu. The owning library indicates the organizational units whose staff can use this alert. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units).
+
+. Click _Save_.
+
+Line Item MARC Attribute Definitions
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Line item attributes define the fields that Evergreen needs to extract from the bibliographic records that are in the acquisitions database to display in the catalog. Also, these attributes will appear as fields in the New Brief Record interface. You will be able to enter information for the brief record in the fields where attributes have been defined.
+
diff --git a/docs/admin/auto_suggest_search.txt b/docs/admin/auto_suggest_search.txt
index fc01215..4a2dc61 100644
--- a/docs/admin/auto_suggest_search.txt
+++ b/docs/admin/auto_suggest_search.txt
@@ -1,32 +1,32 @@
-Auto Suggest in Catalog Search
-------------------------------
-
-The auto suggest feature suggestions for completing search terms as the user enters his search query. Ten suggestions are the default, but the number of suggestions is configurable at
-the database level. Scroll through suggestions with your mouse, or use the arrow keys to scroll through the suggestions. Select a suggestion to view records that are linked to
-this suggestion. This feature is not turned on by default. You must turn it on in the Admin module.
-
-
-Enabling this Feature
-~~~~~~~~~~~~~~~~~~~~~
-
-. To enable this feature, click *Admin* -> *Server Administration* -> *Global Flags*.
-. Scroll down to item 10, OPAC.
-. Double click anywhere in the row to edit the fields.
-. Check the box adjacent to *Enabled* to turn on the feature.
-. The *Value* field is optional. If you checked *Enabled* in step 4, and you leave this field empty, then Evergreen will only suggest searches for which there are any corresponding MARC records.
-+
-note: If you checked *Enabled* in step 4, and you enter the string, *opac_visible*, into this field, then Evergreen will suggest searches for which
-there are matching MARC records with copies within your search scope. For example, it will suggest MARC records with copies at your branch.
-+
-. Click *Save.*
-
-image::media/Auto_Suggest_in_Catalog_Search2.jpg[Auto_Suggest_in_Catalog_Search2]
-
-Using this Feature
-~~~~~~~~~~~~~~~~~~
-
-. Enter search terms into the basic search field. Evergreen will automatically suggest search terms.
-. Select a suggestion to view records that are linked to this suggestion.
-
-image::media/Auto_Suggest_in_Catalog_Search1.jpg[Auto_Suggest_in_Catalog_Search1]
-
+Auto Suggest in Catalog Search
+------------------------------
+
+The auto suggest feature suggestions for completing search terms as the user enters his search query. Ten suggestions are the default, but the number of suggestions is configurable at
+the database level. Scroll through suggestions with your mouse, or use the arrow keys to scroll through the suggestions. Select a suggestion to view records that are linked to
+this suggestion. This feature is not turned on by default. You must turn it on in the Admin module.
+
+
+Enabling this Feature
+~~~~~~~~~~~~~~~~~~~~~
+
+. To enable this feature, click *Admin* -> *Server Administration* -> *Global Flags*.
+. Scroll down to item 10, OPAC.
+. Double click anywhere in the row to edit the fields.
+. Check the box adjacent to *Enabled* to turn on the feature.
+. The *Value* field is optional. If you checked *Enabled* in step 4, and you leave this field empty, then Evergreen will only suggest searches for which there are any corresponding MARC records.
++
+note: If you checked *Enabled* in step 4, and you enter the string, *opac_visible*, into this field, then Evergreen will suggest searches for which
+there are matching MARC records with copies within your search scope. For example, it will suggest MARC records with copies at your branch.
++
+. Click *Save.*
+
+image::media/Auto_Suggest_in_Catalog_Search2.jpg[Auto_Suggest_in_Catalog_Search2]
+
+Using this Feature
+~~~~~~~~~~~~~~~~~~
+
+. Enter search terms into the basic search field. Evergreen will automatically suggest search terms.
+. Select a suggestion to view records that are linked to this suggestion.
+
+image::media/Auto_Suggest_in_Catalog_Search1.jpg[Auto_Suggest_in_Catalog_Search1]
+
diff --git a/docs/admin/booking-admin.txt b/docs/admin/booking-admin.txt
index 5fc51e5..2a10980 100644
--- a/docs/admin/booking-admin.txt
+++ b/docs/admin/booking-admin.txt
@@ -1,199 +1,199 @@
-Booking Module Administration
------------------------------
-
-Creating Bookable Non-Bibliographic Resources
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Staff with the required permissions (Circulator and above) can create bookable non-bibliographic resources such as laptops, projectors, and meeting rooms.
-
-The following pieces make up a non-bibliographic resource:
-
-* Resource Type
-* Resource Attribute
-* Resource Attribute Values
-* Resource
-* Resource Attribute Map
-
-You need to create resource types and resource attributes (features of the resource types), and add booking items (resources) to individual resource type. Each resource attribute may have multiple values. You need to link the applicable features (resource attributes and values) to individual item (resource) through the Resource Attribute Map. Before you create resources (booking items) you need to have a resource type and associated resource attributes and values, if any, for them.
-
-Create New Resource Type
-^^^^^^^^^^^^^^^^^^^^^^^^
-
-1) Select Admin --> Server Administration --> Booking --> Resource Types.
-
-image::media/booking-create-resourcetype-1.png[]
-
-2) A list of current resource types will appear. Use Back and Next buttons to browse the whole list.
-
-image::media/booking-create-resourcetype-2.png[]
-
-[NOTE]
-You may also see cataloged items in the list. Those items have been marked bookable or booked before.
-
-
-3) To create a new resource type, click New Resource Type in the top right corner, .
-
-image::media/booking-create-resourcetype-3.png[]
-
-4) A box will appear in which you create your new type of resource.
-
-image::media/booking-create-bookable-1.png[]
-
-* Resource Type Name - Give your resource a name.
-* Fine Interval - How often will fines be charged? This period can be input in several ways:
-
-[NOTE]
-====================================================================
-** second(s), minute(s), hour(s), day(s), week(s), month(s), year(s)
-** sec(s), min(s)
-** s, m, h
-** 00:00:30, 00:01:00, 01:00:00
-===================================================================
-
-* Fine Amount - The amount that will be charged at each Fine Interval.
-* Owning Library - The home library of the resource.
-* Catalog Item - (Function not currently available.)
-* Transferable - This allows the item to be transferred between libraries.
-* Inter-booking and Inter-circulation Interval - The amount of time required by your library between the return of a resource and a new reservation for the resource. This interval uses * the same input conventions as the Fine Interval.
-* Max Fine Amount - The amount at which fines will stop generating.
-
-5) Click Save when you have entered the needed information.
-
-image::media/booking-create-resourcetype-4.png[]
-
-6) The new resource type will appear in the list.
-
-image::media/booking-create-resourcetype-5.png[]
-
-Create New Resource Attribute
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-1) Select Server Administration --> Booking --> Resource Attributes.
-
-2) Click New Resource Attribute in the top right corner.
-
-3) A box will appear in which you can add the attributes of the resource. Attributes are categories of descriptive information that are provided to the staff member when the booking request is made. For example, an attribute of a projector may be the type of projector. Other attributes might be the number of seats available in a room, or the computing platform of a laptop.
-
-image::media/booking-create-bookable-2.png[]
-
-* Resource Attribute Name - Give your attribute a name.
-* Owning Library - The home library of the resource.
-* Resource Type - Type in the first letter to list then choose the Resource Type to which the Attribute is applicable.
-* Is Required - (Function not currently available.)
-
-4) Click Save when the necessary information has been entered.
-
-5) The added attribute will appear in the list.
-
-[NOTE]
-One resource type may have multiple attributes. You may repeat the above procedure to add more.
-
-Create New Resource Attribute Value
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-1) One resource attribute may have multiple values. To add new attribute value, select Server Administration → Booking → Resource Attribute Values.
-
-2) Click New Resource Attribute Value in the top right corner.
-
-3) A box will appear in which you assign a value to a particular attribute. Values can be numbers, words, or a combination of them, that describe the particular aspects of the resource that have been defined as Attributes. As all values appear on the same list for selection, values should be as unique as possible. For example, a laptop may have a computing platform that is either PC or Mac.
-
-image::media/booking-create-bookable-3.png[]
-
-* Owning Library - The home library of the resource.
-* Resource Attribute - The attribute you wish to assign the value to.
-* Valid Value - Enter the value for your attribute.
-
-4) Click Save when the required information has been added.
-
-5) The attribute value will appear in the list. Each attribute should have at least two values attached to it; repeat this process for all applicable attribute values.
-
-Create New Resource
-^^^^^^^^^^^^^^^^^^^
-
-1) Add items to a resource type. Click Admin → Server Administration → Booking → Resources.
-
-2) Click New Resource in the top right corner.
-
-3) A box will appear. Add information for the resource.
-
-image::media/booking-create-bookable-4.png[]
-
-* Owning Library - The home library of the resource.
-* Resource Type - Type in the first letter of the resource type's name to list then select the resource type for your item.
-* Barcode - Barcode for the resource.
-* Overbook - This allows a single item to be reserved, picked up, and returned by multiple patrons during overlapping or identical time periods.
-* Is Deposit Required - (Function not currently available.)
-* Deposit Amount - (Function not currently available.)
-* User Fee - (Function not currently available.)
-
-4) Click Save when the required information has been added.
-
-5) The resource will appear in the list.
-
-[NOTE]
-One resource type may have multiple resources attached.
-
-Map Resource Attributes and Values to Resources
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-1) Use Resource Attribute Maps to bring together the resources and their attributes and values. Select Admin → Server Administration → Booking → Resource Attribute Maps.
-
-2) Click New Resource Attribute Map in the right top corner.
-
-3) A box will appear in which you will map your attributes and values to your resources.
-
-image::media/booking-create-bookable-5.png[]
-
-* Resource - Enter the barcode of your resource.
-* Resource Attribute - Select an attribute that belongs to the Resource Type.
-* Attribute Value - Select a value that belongs to your chosen attribute and describes your resource. If your attribute and value do not belong together you will be unable to save.
-
-4) Click Save once you have entered the required information.
-
-[NOTE]
-A resource may have multiple attributes and values. Repeat the above steps to map all.
-
-5) The resource attribute map will appear in the list.
-
-Once all attributes have been mapped your resource will be part of a hierarchy similar to the example below.
-
-image::media/booking-create-bookable-6.png[]
-
-
-Editing Non-Bibliographic Resources
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Staff with the required permissions can edit aspects of existing non-bibliographic resources. For example, resource type can be edited in the event that the fine amount for a laptop changes from $2.00 to $5.00.
-
-Editing Resource Types
-^^^^^^^^^^^^^^^^^^^^^^
-
-1) Bring up your list of resource types. Select Admin --> Server Administration --> Booking --> Resource Types.
-
-2) A list of current resource types will appear.
-
-3) Double click anywhere on the line of the resource type you would like to edit.
-
-4) The resource type box will appear. Make your changes and click Save.
-
-5) Following the same procedure you may edit Resource Attributes, Attributes Values, Resources and Attribute Map by selecting them on Admin --> Server Administration --> Booking menu.
-
-
-
-
-Deleting Non-bibliographic Resources
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-1) To delete a booking resource, go to Admin → Server Administration → Booking → Resources.
-
-2) Select the checkbox in front the resource you want to delete. Click Delete Selected. The resource will disappear from the list.
-
-Following the same procedure you may delete Resource Attributes Maps.
-
-You may also delete Resource Attribute Values, Resource Attributes and Resource Types. But you have to delete them in the reverse order when you create them to make sure the entry is not in use when you try to delete it.
-
-This is the deletion order: Resource Attribut Map/Resources --> Resource Attribute Values --> Resource Attributes --> Resource Types.
-
-
-
-
+Booking Module Administration
+-----------------------------
+
+Creating Bookable Non-Bibliographic Resources
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Staff with the required permissions (Circulator and above) can create bookable non-bibliographic resources such as laptops, projectors, and meeting rooms.
+
+The following pieces make up a non-bibliographic resource:
+
+* Resource Type
+* Resource Attribute
+* Resource Attribute Values
+* Resource
+* Resource Attribute Map
+
+You need to create resource types and resource attributes (features of the resource types), and add booking items (resources) to individual resource type. Each resource attribute may have multiple values. You need to link the applicable features (resource attributes and values) to individual item (resource) through the Resource Attribute Map. Before you create resources (booking items) you need to have a resource type and associated resource attributes and values, if any, for them.
+
+Create New Resource Type
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+1) Select Admin --> Server Administration --> Booking --> Resource Types.
+
+image::media/booking-create-resourcetype-1.png[]
+
+2) A list of current resource types will appear. Use Back and Next buttons to browse the whole list.
+
+image::media/booking-create-resourcetype-2.png[]
+
+[NOTE]
+You may also see cataloged items in the list. Those items have been marked bookable or booked before.
+
+
+3) To create a new resource type, click New Resource Type in the top right corner, .
+
+image::media/booking-create-resourcetype-3.png[]
+
+4) A box will appear in which you create your new type of resource.
+
+image::media/booking-create-bookable-1.png[]
+
+* Resource Type Name - Give your resource a name.
+* Fine Interval - How often will fines be charged? This period can be input in several ways:
+
+[NOTE]
+====================================================================
+** second(s), minute(s), hour(s), day(s), week(s), month(s), year(s)
+** sec(s), min(s)
+** s, m, h
+** 00:00:30, 00:01:00, 01:00:00
+===================================================================
+
+* Fine Amount - The amount that will be charged at each Fine Interval.
+* Owning Library - The home library of the resource.
+* Catalog Item - (Function not currently available.)
+* Transferable - This allows the item to be transferred between libraries.
+* Inter-booking and Inter-circulation Interval - The amount of time required by your library between the return of a resource and a new reservation for the resource. This interval uses * the same input conventions as the Fine Interval.
+* Max Fine Amount - The amount at which fines will stop generating.
+
+5) Click Save when you have entered the needed information.
+
+image::media/booking-create-resourcetype-4.png[]
+
+6) The new resource type will appear in the list.
+
+image::media/booking-create-resourcetype-5.png[]
+
+Create New Resource Attribute
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+1) Select Server Administration --> Booking --> Resource Attributes.
+
+2) Click New Resource Attribute in the top right corner.
+
+3) A box will appear in which you can add the attributes of the resource. Attributes are categories of descriptive information that are provided to the staff member when the booking request is made. For example, an attribute of a projector may be the type of projector. Other attributes might be the number of seats available in a room, or the computing platform of a laptop.
+
+image::media/booking-create-bookable-2.png[]
+
+* Resource Attribute Name - Give your attribute a name.
+* Owning Library - The home library of the resource.
+* Resource Type - Type in the first letter to list then choose the Resource Type to which the Attribute is applicable.
+* Is Required - (Function not currently available.)
+
+4) Click Save when the necessary information has been entered.
+
+5) The added attribute will appear in the list.
+
+[NOTE]
+One resource type may have multiple attributes. You may repeat the above procedure to add more.
+
+Create New Resource Attribute Value
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+1) One resource attribute may have multiple values. To add new attribute value, select Server Administration → Booking → Resource Attribute Values.
+
+2) Click New Resource Attribute Value in the top right corner.
+
+3) A box will appear in which you assign a value to a particular attribute. Values can be numbers, words, or a combination of them, that describe the particular aspects of the resource that have been defined as Attributes. As all values appear on the same list for selection, values should be as unique as possible. For example, a laptop may have a computing platform that is either PC or Mac.
+
+image::media/booking-create-bookable-3.png[]
+
+* Owning Library - The home library of the resource.
+* Resource Attribute - The attribute you wish to assign the value to.
+* Valid Value - Enter the value for your attribute.
+
+4) Click Save when the required information has been added.
+
+5) The attribute value will appear in the list. Each attribute should have at least two values attached to it; repeat this process for all applicable attribute values.
+
+Create New Resource
+^^^^^^^^^^^^^^^^^^^
+
+1) Add items to a resource type. Click Admin → Server Administration → Booking → Resources.
+
+2) Click New Resource in the top right corner.
+
+3) A box will appear. Add information for the resource.
+
+image::media/booking-create-bookable-4.png[]
+
+* Owning Library - The home library of the resource.
+* Resource Type - Type in the first letter of the resource type's name to list then select the resource type for your item.
+* Barcode - Barcode for the resource.
+* Overbook - This allows a single item to be reserved, picked up, and returned by multiple patrons during overlapping or identical time periods.
+* Is Deposit Required - (Function not currently available.)
+* Deposit Amount - (Function not currently available.)
+* User Fee - (Function not currently available.)
+
+4) Click Save when the required information has been added.
+
+5) The resource will appear in the list.
+
+[NOTE]
+One resource type may have multiple resources attached.
+
+Map Resource Attributes and Values to Resources
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+1) Use Resource Attribute Maps to bring together the resources and their attributes and values. Select Admin → Server Administration → Booking → Resource Attribute Maps.
+
+2) Click New Resource Attribute Map in the right top corner.
+
+3) A box will appear in which you will map your attributes and values to your resources.
+
+image::media/booking-create-bookable-5.png[]
+
+* Resource - Enter the barcode of your resource.
+* Resource Attribute - Select an attribute that belongs to the Resource Type.
+* Attribute Value - Select a value that belongs to your chosen attribute and describes your resource. If your attribute and value do not belong together you will be unable to save.
+
+4) Click Save once you have entered the required information.
+
+[NOTE]
+A resource may have multiple attributes and values. Repeat the above steps to map all.
+
+5) The resource attribute map will appear in the list.
+
+Once all attributes have been mapped your resource will be part of a hierarchy similar to the example below.
+
+image::media/booking-create-bookable-6.png[]
+
+
+Editing Non-Bibliographic Resources
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Staff with the required permissions can edit aspects of existing non-bibliographic resources. For example, resource type can be edited in the event that the fine amount for a laptop changes from $2.00 to $5.00.
+
+Editing Resource Types
+^^^^^^^^^^^^^^^^^^^^^^
+
+1) Bring up your list of resource types. Select Admin --> Server Administration --> Booking --> Resource Types.
+
+2) A list of current resource types will appear.
+
+3) Double click anywhere on the line of the resource type you would like to edit.
+
+4) The resource type box will appear. Make your changes and click Save.
+
+5) Following the same procedure you may edit Resource Attributes, Attributes Values, Resources and Attribute Map by selecting them on Admin --> Server Administration --> Booking menu.
+
+
+
+
+Deleting Non-bibliographic Resources
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+1) To delete a booking resource, go to Admin → Server Administration → Booking → Resources.
+
+2) Select the checkbox in front the resource you want to delete. Click Delete Selected. The resource will disappear from the list.
+
+Following the same procedure you may delete Resource Attributes Maps.
+
+You may also delete Resource Attribute Values, Resource Attributes and Resource Types. But you have to delete them in the reverse order when you create them to make sure the entry is not in use when you try to delete it.
+
+This is the deletion order: Resource Attribut Map/Resources --> Resource Attribute Values --> Resource Attributes --> Resource Types.
+
+
+
+
diff --git a/docs/admin/cn_prefixes_and_suffixes.txt b/docs/admin/cn_prefixes_and_suffixes.txt
index 03b11c6..789367e 100644
--- a/docs/admin/cn_prefixes_and_suffixes.txt
+++ b/docs/admin/cn_prefixes_and_suffixes.txt
@@ -1,46 +1,46 @@
-Call Number Prefixes and Suffixes
----------------------------------
-
-You can configure call number prefixes and suffixes in the Admin module. This feature ensures more precise cataloging because each cataloger will have access to an identical drop down menu of call number prefixes and suffixes that are used at his library. In addition, it may streamline cataloging workflow. Catalogers can use a drop down menu to enter call number prefixes and suffixes rather than entering them manually. You can also run reports on call number prefixes and suffixes that would facilitate collection development and maintenance.
-
-
-Configure call number prefixes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Call number prefixes are codes that precede a call number.
-
-To configure call number prefixes:
-
-1. Select *Admin -> Server Administration -> Call Number Prefixes*.
-2. Click *New Prefix*.
-3. Enter the *call number label* that will appear on the item.
-4. Select the *owning library* from the drop down menu. Staff at this library, and its descendant org units, with the appropriate permissions, will be able to apply this call number prefix.
-5. Click *Save*.
-
-
-
-image::media/Call_Number_Prefixes_and_Suffixes_2_21.jpg[Call_Number_Prefixes_and_Suffixes_2_21]
-
-
-
-Configure call number suffixes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Call number suffixes are codes that succeed a call number.
-
-To configure call number suffixes:
-
-1. Select *Admin -> Server Administration -> Call Number Suffixes*.
-2. Click *New Suffix*.
-3. Enter the *call number label* that will appear on the item.
-4. Select the *owning library* from the drop down menu. Staff at this library, and its descendant org units, with the appropriate permissions, will be able to apply this call number suffix.
-5. Click *Save*.
-
-
-image::media/Call_Number_Prefixes_and_Suffixes_2_22.jpg[Call_Number_Prefixes_and_Suffixes_2_22]
-
-
-Apply Call Number Prefixes and Suffixes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-You can apply call number prefixes and suffixes to items from a pre-configured list in the *Unified Volume/Copy Creator*. See the document, Unified Volume/Copy Creator, for an example.
+Call Number Prefixes and Suffixes
+---------------------------------
+
+You can configure call number prefixes and suffixes in the Admin module. This feature ensures more precise cataloging because each cataloger will have access to an identical drop down menu of call number prefixes and suffixes that are used at his library. In addition, it may streamline cataloging workflow. Catalogers can use a drop down menu to enter call number prefixes and suffixes rather than entering them manually. You can also run reports on call number prefixes and suffixes that would facilitate collection development and maintenance.
+
+
+Configure call number prefixes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Call number prefixes are codes that precede a call number.
+
+To configure call number prefixes:
+
+1. Select *Admin -> Server Administration -> Call Number Prefixes*.
+2. Click *New Prefix*.
+3. Enter the *call number label* that will appear on the item.
+4. Select the *owning library* from the drop down menu. Staff at this library, and its descendant org units, with the appropriate permissions, will be able to apply this call number prefix.
+5. Click *Save*.
+
+
+
+image::media/Call_Number_Prefixes_and_Suffixes_2_21.jpg[Call_Number_Prefixes_and_Suffixes_2_21]
+
+
+
+Configure call number suffixes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Call number suffixes are codes that succeed a call number.
+
+To configure call number suffixes:
+
+1. Select *Admin -> Server Administration -> Call Number Suffixes*.
+2. Click *New Suffix*.
+3. Enter the *call number label* that will appear on the item.
+4. Select the *owning library* from the drop down menu. Staff at this library, and its descendant org units, with the appropriate permissions, will be able to apply this call number suffix.
+5. Click *Save*.
+
+
+image::media/Call_Number_Prefixes_and_Suffixes_2_22.jpg[Call_Number_Prefixes_and_Suffixes_2_22]
+
+
+Apply Call Number Prefixes and Suffixes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can apply call number prefixes and suffixes to items from a pre-configured list in the *Unified Volume/Copy Creator*. See the document, Unified Volume/Copy Creator, for an example.
diff --git a/docs/admin/customize_staff_client.txt b/docs/admin/customize_staff_client.txt
index c70ff58..05e805c 100644
--- a/docs/admin/customize_staff_client.txt
+++ b/docs/admin/customize_staff_client.txt
@@ -1,59 +1,59 @@
-Customizing the Staff Client
-----------------------------
-
-Customizable Toolbar
-~~~~~~~~~~~~~~~~~~~~
-
-
-By default, two toolbars are available in the staff client: circulation and
-cataloging. This feature enables you to customize toolbars in the staff client.
-You can create toolbars for specific org unit(s), workstation(s), or login(s).
-
-
-Configure Toolbar
-^^^^^^^^^^^^^^^^^
-
-. Click *Admin* -> *Workstation Administration* -> *Toolbars* -> *Configure
-Toolbars*.
-. Click *New Toolbar*.
-. *Enter label for toolbar*.
-+
-image::media/Customizable_Toolbar1.jpg[Customizable_Toolbar1]
-+
-. Click *Ok*.
-.Select one of the buttons in the *Available* panel. The *Button ID* describes
-that action that the button will take, and the *Label* will display in the
-toolbar.
-. Click the *--> A* button to add the selected function to the
-*Selected* panel on the bottom right side of the screen. To remove a button,
-click the *<--R* button.
-+
-image::media/Customizable_Toolbar2.jpg[Customizable_Toolbar2]
-+
-. Continue adding buttons if desired. The buttons will display in the order that you add
-them. If you want to reorder the buttons, click the *Up* or *Down* buttons.
-. To separate buttons onto left and right sides of the screen on the same
-toolbar, select *toolbarspacer*, and click *--> A*.
-+
-image::media/Customizable_Toolbar3.jpg[Customizable_Toolbar3]
-+
-. To add a dividing line between buttons that appear on the same side of the
-screen, select *toolbarseparator*, and click *-->A*.
-+
-image::media/Customizable_Toolbar4.jpg[Customizable_Toolbar4]
-+
-. At the bottom of the screen, choose the owner of this toolbar.
-If you click *Owning Org Unit*, then the owning org unit that you specify will display this
-toolbar. Select the owning org unit from the drop down menu. The rule of
-parental inheritance applies, so all child units will inherit the toolbars of
-their parental units.
-If you click *Owning Workstation*, then the workstation to which you are logged
-in when you created the toolbar will display this toolbar.
-If you select *Owning User*, then your login has access to that toolbar.
- . When you are finished creating the toolbar, click *Save Toolbar*. Any
-toolbar to which you have access displays under *Admin -> Workstation
-Administration -> Toolbars -> Current*.
-
-*Permissions*
-
-ADMIN_TOOLBAR - Allow a user to create, edit, and delete custom toolbars
+Customizing the Staff Client
+----------------------------
+
+Customizable Toolbar
+~~~~~~~~~~~~~~~~~~~~
+
+
+By default, two toolbars are available in the staff client: circulation and
+cataloging. This feature enables you to customize toolbars in the staff client.
+You can create toolbars for specific org unit(s), workstation(s), or login(s).
+
+
+Configure Toolbar
+^^^^^^^^^^^^^^^^^
+
+. Click *Admin* -> *Workstation Administration* -> *Toolbars* -> *Configure
+Toolbars*.
+. Click *New Toolbar*.
+. *Enter label for toolbar*.
++
+image::media/Customizable_Toolbar1.jpg[Customizable_Toolbar1]
++
+. Click *Ok*.
+.Select one of the buttons in the *Available* panel. The *Button ID* describes
+that action that the button will take, and the *Label* will display in the
+toolbar.
+. Click the *--> A* button to add the selected function to the
+*Selected* panel on the bottom right side of the screen. To remove a button,
+click the *<--R* button.
++
+image::media/Customizable_Toolbar2.jpg[Customizable_Toolbar2]
++
+. Continue adding buttons if desired. The buttons will display in the order that you add
+them. If you want to reorder the buttons, click the *Up* or *Down* buttons.
+. To separate buttons onto left and right sides of the screen on the same
+toolbar, select *toolbarspacer*, and click *--> A*.
++
+image::media/Customizable_Toolbar3.jpg[Customizable_Toolbar3]
++
+. To add a dividing line between buttons that appear on the same side of the
+screen, select *toolbarseparator*, and click *-->A*.
++
+image::media/Customizable_Toolbar4.jpg[Customizable_Toolbar4]
++
+. At the bottom of the screen, choose the owner of this toolbar.
+If you click *Owning Org Unit*, then the owning org unit that you specify will display this
+toolbar. Select the owning org unit from the drop down menu. The rule of
+parental inheritance applies, so all child units will inherit the toolbars of
+their parental units.
+If you click *Owning Workstation*, then the workstation to which you are logged
+in when you created the toolbar will display this toolbar.
+If you select *Owning User*, then your login has access to that toolbar.
+ . When you are finished creating the toolbar, click *Save Toolbar*. Any
+toolbar to which you have access displays under *Admin -> Workstation
+Administration -> Toolbars -> Current*.
+
+*Permissions*
+
+ADMIN_TOOLBAR - Allow a user to create, edit, and delete custom toolbars
diff --git a/docs/admin/recent_staff_searches.txt b/docs/admin/recent_staff_searches.txt
index b297b8d..bd2be10 100644
--- a/docs/admin/recent_staff_searches.txt
+++ b/docs/admin/recent_staff_searches.txt
@@ -1,49 +1,49 @@
-Recent Staff Searches
----------------------
-
-This feature enables you to view your recent searches as you perform them in the staff client. The number of searches that you can view is configurable. This feature is only available through the staff client; it is not available to patrons in the OPAC.
-
-*Administrative Settings*
-
-By default, ten searches will be saved as you search the staff client. If you want to change the number of saved searches, then you can configure the number of searches that you wish to save through the *Library Settings Editor* in the *Admin* module.
-
-To configure the number of recent staff searches:
-
-1. Click *Admin -> Local Administration -> Library Settings Editor.*
-
-2. Scroll to *OPAC: Number of staff client saved searches to display on left side of results and record details pages*
-
-3. Click *Edit*.
-
-4. Select a *Context* from the drop down menu.
-
-5. Enter the number of searches that you wish to save in the *Value* field.
-
-6. Click *Update Setting*
-
-image::media/Saved_Catalog_Searches_2_21.jpg[Saved_Catalog_Searches_2_21]
-
-
-NOTE: To retain this setting, the system administrator must restart the web server.
-
-
-If you do not want to save any searches, then you can turn off this feature.
-
-To deactivate this feature:
-
-1. Follow steps 1-4 (one through four) as listed in the previous section.
-
-2. In the *value* field, enter 0 (zero).
-
-3. Click *Update Setting.* This will prevent you from viewing any saved searches.
-
-
-*Recent Staff Searches*
-
-Evergreen will save staff searches that are entered through either the basic or advanced search fields. To view recent staff searches:
-
-1. Enter a search term in either the basic or advanced search fields.
-
-2. Your search results for the current search will appear in the middle of the screen. The most recent searches will appear on the left side of the screen.
-
-image::media/Saved_Catalog_Searches_2_22.jpg[Saved_Catalog_Searches_2_22]
+Recent Staff Searches
+---------------------
+
+This feature enables you to view your recent searches as you perform them in the staff client. The number of searches that you can view is configurable. This feature is only available through the staff client; it is not available to patrons in the OPAC.
+
+*Administrative Settings*
+
+By default, ten searches will be saved as you search the staff client. If you want to change the number of saved searches, then you can configure the number of searches that you wish to save through the *Library Settings Editor* in the *Admin* module.
+
+To configure the number of recent staff searches:
+
+1. Click *Admin -> Local Administration -> Library Settings Editor.*
+
+2. Scroll to *OPAC: Number of staff client saved searches to display on left side of results and record details pages*
+
+3. Click *Edit*.
+
+4. Select a *Context* from the drop down menu.
+
+5. Enter the number of searches that you wish to save in the *Value* field.
+
+6. Click *Update Setting*
+
+image::media/Saved_Catalog_Searches_2_21.jpg[Saved_Catalog_Searches_2_21]
+
+
+NOTE: To retain this setting, the system administrator must restart the web server.
+
+
+If you do not want to save any searches, then you can turn off this feature.
+
+To deactivate this feature:
+
+1. Follow steps 1-4 (one through four) as listed in the previous section.
+
+2. In the *value* field, enter 0 (zero).
+
+3. Click *Update Setting.* This will prevent you from viewing any saved searches.
+
+
+*Recent Staff Searches*
+
+Evergreen will save staff searches that are entered through either the basic or advanced search fields. To view recent staff searches:
+
+1. Enter a search term in either the basic or advanced search fields.
+
+2. Your search results for the current search will appear in the middle of the screen. The most recent searches will appear on the left side of the screen.
+
+image::media/Saved_Catalog_Searches_2_22.jpg[Saved_Catalog_Searches_2_22]
diff --git a/docs/admin/restrict_Z39.50_sources_by_perm_group.txt b/docs/admin/restrict_Z39.50_sources_by_perm_group.txt
index 2977cc3..c9667ba 100644
--- a/docs/admin/restrict_Z39.50_sources_by_perm_group.txt
+++ b/docs/admin/restrict_Z39.50_sources_by_perm_group.txt
@@ -1,49 +1,49 @@
-Restrict Z39.50 Sources by Permission Group
--------------------------------------------
-
-In Evergreen versions preceeding 2.2, all users with cataloging privileges could view all of the Z39.50 servers that were available for use in the staff client. In Evergreen version 2.2, you can use a permission to restrict users' access to Z39.50 servers. You can apply a permission to the Z39.50 servers to restrict access to that server, and then assign that permission to users or groups so that they can access the restricted servers.
-
-Administrative Settings
-~~~~~~~~~~~~~~~~~~~~~~~
-
-You can add a permission to limit use of Z39.50 servers, or you can use an existing permission.
-
-NOTE: You must be authorized to add permission types at the database level to add a new permission.
-
-Add a new permission:
-
-1) Create a permission at the database level.
-
-2) Click *Admin -> Server Administration -> Permissions* to add a permission to the staff client.
-
-3) In the *New Permission* field, enter the text that describes the new permission.
-
-image::media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg[]
-
-4) Click *Add*.
-
-5) The new permission appears in the list of permissions.
-
-
-
-Restrict Z39.50 Sources by Permission Group
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-1) Click *Admin -> Server Administration -> Z39.50 Servers*
-
-2) Click *New Z39.50 Server*, or double click on an existing Z39.50 server to restrict its use.
-
-3) Select the permission that you added to restrict Z39.50 use from the drop down menu.
-
-image::media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg[]
-
-4) Click *Save*.
-
-5) Add the permission that you created to a user or user group so that they can access the restricted server.
-
-
-image::media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg[]
-
-6) Users that log in to the staff client and have that permission will be able to see the restricted Z39.50 server.
-
-NOTE: As an alternative to creating a new permission to restrict use, you can use a preexisting permission. For example, your library uses a permission group called SuperCat, and only members in this group should have access to a restricted Z39.50 source. Identify a permission that is unique to the SuperCat group (e.g. CREATE_MARC) and apply that permission to the restricted Z39.50 server. Because these users are in the only group with the permission, they will be the only group w/ access to the restricted server.
+Restrict Z39.50 Sources by Permission Group
+-------------------------------------------
+
+In Evergreen versions preceeding 2.2, all users with cataloging privileges could view all of the Z39.50 servers that were available for use in the staff client. In Evergreen version 2.2, you can use a permission to restrict users' access to Z39.50 servers. You can apply a permission to the Z39.50 servers to restrict access to that server, and then assign that permission to users or groups so that they can access the restricted servers.
+
+Administrative Settings
+~~~~~~~~~~~~~~~~~~~~~~~
+
+You can add a permission to limit use of Z39.50 servers, or you can use an existing permission.
+
+NOTE: You must be authorized to add permission types at the database level to add a new permission.
+
+Add a new permission:
+
+1) Create a permission at the database level.
+
+2) Click *Admin -> Server Administration -> Permissions* to add a permission to the staff client.
+
+3) In the *New Permission* field, enter the text that describes the new permission.
+
+image::media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg[]
+
+4) Click *Add*.
+
+5) The new permission appears in the list of permissions.
+
+
+
+Restrict Z39.50 Sources by Permission Group
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+1) Click *Admin -> Server Administration -> Z39.50 Servers*
+
+2) Click *New Z39.50 Server*, or double click on an existing Z39.50 server to restrict its use.
+
+3) Select the permission that you added to restrict Z39.50 use from the drop down menu.
+
+image::media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg[]
+
+4) Click *Save*.
+
+5) Add the permission that you created to a user or user group so that they can access the restricted server.
+
+
+image::media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg[]
+
+6) Users that log in to the staff client and have that permission will be able to see the restricted Z39.50 server.
+
+NOTE: As an alternative to creating a new permission to restrict use, you can use a preexisting permission. For example, your library uses a permission group called SuperCat, and only members in this group should have access to a restricted Z39.50 source. Identify a permission that is unique to the SuperCat group (e.g. CREATE_MARC) and apply that permission to the restricted Z39.50 server. Because these users are in the only group with the permission, they will be the only group w/ access to the restricted server.
diff --git a/docs/admin/staff_client-double_clicking.txt b/docs/admin/staff_client-double_clicking.txt
index f08b009..46dba84 100644
--- a/docs/admin/staff_client-double_clicking.txt
+++ b/docs/admin/staff_client-double_clicking.txt
@@ -1,23 +1,23 @@
-New Options for Double Clicking
--------------------------------
-
-Double Click to Retrieve a Patron's Record
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-. Click *Search -> Search for Patrons* to access a patron's record
-. Enter search terms.
-. Retrieve a list of possible matches. Double click on the record that you want to open.
-
-image::media/Double_Click1.jpg[Double_Click1]
-
-
-Double Click to Retrieve Item Attributes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-. Enter search terms to retrieve a bibliographic record.
-. Click *Actions for this Record* -> *Holdings Maintenance*.
-. Double click on an item.
-+
-image::media/Double_Click3.jpg[Double_Click3]
-+
-. The copy information will appear in a new tab.
+New Options for Double Clicking
+-------------------------------
+
+Double Click to Retrieve a Patron's Record
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+. Click *Search -> Search for Patrons* to access a patron's record
+. Enter search terms.
+. Retrieve a list of possible matches. Double click on the record that you want to open.
+
+image::media/Double_Click1.jpg[Double_Click1]
+
+
+Double Click to Retrieve Item Attributes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+. Enter search terms to retrieve a bibliographic record.
+. Click *Actions for this Record* -> *Holdings Maintenance*.
+. Double click on an item.
++
+image::media/Double_Click3.jpg[Double_Click3]
++
+. The copy information will appear in a new tab.
diff --git a/docs/admin/staff_client-recent_searches.txt b/docs/admin/staff_client-recent_searches.txt
index fd1f87b..d727970 100644
--- a/docs/admin/staff_client-recent_searches.txt
+++ b/docs/admin/staff_client-recent_searches.txt
@@ -1,42 +1,42 @@
-Recent Staff Searches
----------------------
-
-This feature enables you to view your recent searches as you perform them in the staff client. The number of searches that you can view is configurable. This feature is only available through the staff client; it is not available to patrons in the OPAC.
-
-Administrative Settings
-~~~~~~~~~~~~~~~~~~~~~~~
-
-By default, ten searches will be saved as you search the staff client. If you want to change the number of saved searches, then you can configure the number of searches that you wish to save through the *Library Settings Editor* in the *Admin* module.
-
-To configure the number of recent staff searches:
-
-. Click *Admin -> Local Administration -> Library Settings Editor.*
-. Scroll to *OPAC: Number of staff client saved searches to display on left side of results and record details pages*
-. Click *Edit*.
-. Select a *Context* from the drop down menu.
-. Enter the number of searches that you wish to save in the *Value* field.
-. Click *Update Setting*
-
-image::media/Saved_Catalog_Searches_2_21.jpg[Saved_Catalog_Searches_2_21]
-
-
-NOTE: To retain this setting, the system administrator must restart the web server.
-
-If you do not want to save any searches, then you can turn off this feature.
-
-To deactivate this feature:
-
-. Follow steps 1-4 (one through four) as listed in the previous section.
-. In the *value* field, enter 0 (zero).
-. Click *Update Setting.* This will prevent you from viewing any saved searches.
-
-
-Recent Staff Searches
-~~~~~~~~~~~~~~~~~~~~~
-
-Evergreen will save staff searches that are entered through either the basic or advanced search fields. To view recent staff searches:
-
-. Enter a search term in either the basic or advanced search fields.
-. Your search results for the current search will appear in the middle of the screen. The most recent searches will appear on the left side of the screen.
-
-image::media/Saved_Catalog_Searches_2_22.jpg[Saved_Catalog_Searches_2_22]
+Recent Staff Searches
+---------------------
+
+This feature enables you to view your recent searches as you perform them in the staff client. The number of searches that you can view is configurable. This feature is only available through the staff client; it is not available to patrons in the OPAC.
+
+Administrative Settings
+~~~~~~~~~~~~~~~~~~~~~~~
+
+By default, ten searches will be saved as you search the staff client. If you want to change the number of saved searches, then you can configure the number of searches that you wish to save through the *Library Settings Editor* in the *Admin* module.
+
+To configure the number of recent staff searches:
+
+. Click *Admin -> Local Administration -> Library Settings Editor.*
+. Scroll to *OPAC: Number of staff client saved searches to display on left side of results and record details pages*
+. Click *Edit*.
+. Select a *Context* from the drop down menu.
+. Enter the number of searches that you wish to save in the *Value* field.
+. Click *Update Setting*
+
+image::media/Saved_Catalog_Searches_2_21.jpg[Saved_Catalog_Searches_2_21]
+
+
+NOTE: To retain this setting, the system administrator must restart the web server.
+
+If you do not want to save any searches, then you can turn off this feature.
+
+To deactivate this feature:
+
+. Follow steps 1-4 (one through four) as listed in the previous section.
+. In the *value* field, enter 0 (zero).
+. Click *Update Setting.* This will prevent you from viewing any saved searches.
+
+
+Recent Staff Searches
+~~~~~~~~~~~~~~~~~~~~~
+
+Evergreen will save staff searches that are entered through either the basic or advanced search fields. To view recent staff searches:
+
+. Enter a search term in either the basic or advanced search fields.
+. Your search results for the current search will appear in the middle of the screen. The most recent searches will appear on the left side of the screen.
+
+image::media/Saved_Catalog_Searches_2_22.jpg[Saved_Catalog_Searches_2_22]
diff --git a/docs/admin/staff_client-return_to_results_from_marc.txt b/docs/admin/staff_client-return_to_results_from_marc.txt
index 1e6efc5..b54106f 100644
--- a/docs/admin/staff_client-return_to_results_from_marc.txt
+++ b/docs/admin/staff_client-return_to_results_from_marc.txt
@@ -1,6 +1,6 @@
-Return to Search Results from MARC Record
------------------------------------------
-
-This feature enables you to return to your title search results directly from any view of the MARC record, including the OPAC View, MARC Record, MARC Edit, and Holdings Maintenance. You can use this feature to page through records in the MARC Record View or Edit interfaces. You do not have to return to the OPAC View to access title results.
-
-image::media/Search_Results1.jpg[Search_Results1]
+Return to Search Results from MARC Record
+-----------------------------------------
+
+This feature enables you to return to your title search results directly from any view of the MARC record, including the OPAC View, MARC Record, MARC Edit, and Holdings Maintenance. You can use this feature to page through records in the MARC Record View or Edit interfaces. You do not have to return to the OPAC View to access title results.
+
+image::media/Search_Results1.jpg[Search_Results1]
diff --git a/docs/admin/staff_client-sorting_columns.txt b/docs/admin/staff_client-sorting_columns.txt
index 1f0e355..d9f60fa 100644
--- a/docs/admin/staff_client-sorting_columns.txt
+++ b/docs/admin/staff_client-sorting_columns.txt
@@ -1,59 +1,59 @@
-Sorting Columns
----------------
-
-This feature enables you to sort display columns so that you can find easily the
-information that you need on a screen that contains multiple columns. You can
-sort display columns on any screen that is built on a grid, such as the Check In
-screen or the On Shelf Pull List.
-
-You can also sort the columns on the following Administration screens:
-Circulation Policies, Hold Policies, Circulation Limit Sets, Barcode Completion,
-Acquisitions User Request List, and Vandelay Import Errors.
-
-You can sort items in an ascending or descending order, and you can prioritize
-the order in which columns will sort. The following use cases illustrate how to
-sort items within the Circulation and Administration interfaces.
-
-Sorting the On Shelf Pull List
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-You want to capture items that are on the shelf to fill current holds. To
-simplify this process, you will sort the items on the On Shelf Pull List by Copy
-Location and Call Number.
-
-. Click *Circulation* -> *Pull List for Hold Requests*.
-. The first column that you want to sort is the column, Current Copy Location. Right click the column header, Current Copy Location.
-. Click *Sort First (Descending)*.
-+
-image::media/Sorting_Columns3.jpg[Sorting_Columns3]
-+
-. The next column that you want to sort is the column, Call Number. Right click the column header, Call Number.
-. Click *Sort Next (Ascending)*.
-+
-image::media/Sorting_Columns4.jpg[Sorting_Columns4]
-+
-. The pull list has now been sorted by copy location and call number.
-
-image::media/Sorting_Columns5.jpg[Sorting_Columns5]
-
-NOTE: If you wanted to sort more columns, you could continue the process by clicking *Sort Next* for any subsequent columns.
-
-
-Sorting Circulation Policies
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-You want to sort the display of circulation policies in your staff client.
-
-. Click *Administration* -> *Local Administration* -> *Circulation Policies*.
-. Right click on any column header.
-. A pop-up box appears.
-+
-image::media/Sorting_Columns2.jpg[Sorting_Columns2]
-+
-. Check the *Display* box if you want to display a column in the staff client.
-. Check the *Auto Width* box if you want the width of the columns to adjust to fit the staff client.
-. Select a sort priority.
-.. A sort priority of "0" indicates that no sorting has been applied. Columns will display in their default order.
-.. A sort priority of "1" indicates that ascending sorting should be applied to this column first. Subsequent sorts will be applied as you continue to enter increasing numbers.
-.. A sort priority of "-1" indicates that descending sorting should be applied to this column.
-. Click *Save*. The circulation policies will now sort according to your selections each time that you log into the staff client.
+Sorting Columns
+---------------
+
+This feature enables you to sort display columns so that you can find easily the
+information that you need on a screen that contains multiple columns. You can
+sort display columns on any screen that is built on a grid, such as the Check In
+screen or the On Shelf Pull List.
+
+You can also sort the columns on the following Administration screens:
+Circulation Policies, Hold Policies, Circulation Limit Sets, Barcode Completion,
+Acquisitions User Request List, and Vandelay Import Errors.
+
+You can sort items in an ascending or descending order, and you can prioritize
+the order in which columns will sort. The following use cases illustrate how to
+sort items within the Circulation and Administration interfaces.
+
+Sorting the On Shelf Pull List
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You want to capture items that are on the shelf to fill current holds. To
+simplify this process, you will sort the items on the On Shelf Pull List by Copy
+Location and Call Number.
+
+. Click *Circulation* -> *Pull List for Hold Requests*.
+. The first column that you want to sort is the column, Current Copy Location. Right click the column header, Current Copy Location.
+. Click *Sort First (Descending)*.
++
+image::media/Sorting_Columns3.jpg[Sorting_Columns3]
++
+. The next column that you want to sort is the column, Call Number. Right click the column header, Call Number.
+. Click *Sort Next (Ascending)*.
++
+image::media/Sorting_Columns4.jpg[Sorting_Columns4]
++
+. The pull list has now been sorted by copy location and call number.
+
+image::media/Sorting_Columns5.jpg[Sorting_Columns5]
+
+NOTE: If you wanted to sort more columns, you could continue the process by clicking *Sort Next* for any subsequent columns.
+
+
+Sorting Circulation Policies
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You want to sort the display of circulation policies in your staff client.
+
+. Click *Administration* -> *Local Administration* -> *Circulation Policies*.
+. Right click on any column header.
+. A pop-up box appears.
++
+image::media/Sorting_Columns2.jpg[Sorting_Columns2]
++
+. Check the *Display* box if you want to display a column in the staff client.
+. Check the *Auto Width* box if you want the width of the columns to adjust to fit the staff client.
+. Select a sort priority.
+.. A sort priority of "0" indicates that no sorting has been applied. Columns will display in their default order.
+.. A sort priority of "1" indicates that ascending sorting should be applied to this column first. Subsequent sorts will be applied as you continue to enter increasing numbers.
+.. A sort priority of "-1" indicates that descending sorting should be applied to this column.
+. Click *Save*. The circulation policies will now sort according to your selections each time that you log into the staff client.
diff --git a/docs/admin/staff_client-tab_buttons.txt b/docs/admin/staff_client-tab_buttons.txt
index 34797f7..e3daa27 100644
--- a/docs/admin/staff_client-tab_buttons.txt
+++ b/docs/admin/staff_client-tab_buttons.txt
@@ -1,6 +1,6 @@
-Tab Buttons
------------
-
-This feature enables you to add a new tab to the Evergreen staff client by clicking the + sign adjacent to the tab that you currently have opened. As in previous versions, you can also add new tabs by clicking *File -> New Tab*, or use the hotkey, Ctrl+T.
-
-image::media/New_Tab_Button1.jpg[New_Tab_Button1]
+Tab Buttons
+-----------
+
+This feature enables you to add a new tab to the Evergreen staff client by clicking the + sign adjacent to the tab that you currently have opened. As in previous versions, you can also add new tabs by clicking *File -> New Tab*, or use the hotkey, Ctrl+T.
+
+image::media/New_Tab_Button1.jpg[New_Tab_Button1]
diff --git a/docs/admin/user_activity_type.txt b/docs/admin/user_activity_type.txt
index 979f479..162cb57 100644
--- a/docs/admin/user_activity_type.txt
+++ b/docs/admin/user_activity_type.txt
@@ -1,32 +1,32 @@
-User Activity Types
--------------------
-
-The User Activity Types feature enables you to specify the user activity that you want to record in the database. You can use this feature for reporting purposes. This function will also display a last activity date in a user's account.
-
-Enabling this Feature
-~~~~~~~~~~~~~~~~~~~~~
-
-Click *Admin* -> *Server Administration* -> *User Activity Types* to access the default set of user activity types and to add new ones. The default set of user activity types records user logins to the Evergreen ILS and to third party products that communicate with Evergreen.
-
-The *Label* is a free text field that enables you to describe the activity that you are tracking.
-
-The *Event Caller* describes the third party software or Evergreen interface that interacts with the Evergreen database and is responsible for managing the communication between the parties.
-
-The *Event Type* describes the type of activity that Evergreen is tracking. Currently, this feature only tracks user authentication.
-
-The *Event Mechanism* describes the framework for communication between the third party software or OPAC and the database. Enter an event mechanism if you want to track the means by which the software communicates with the database. If you do not want to track how the softwares communicate, then leave this field empty.
-
-The *Enabled* field allows you to specify which types of user activity that you would like to track.
-
-The *Transient* column enables you to decide how many actions you want to track. If you want to track only the last activity, then enter *True.* If you want to trace all activity by the user, enter *False*.
-
-image::media/User_Activity_Types1A.jpg[User_Activity_Types1A]
-
-
-Using this Feature
-~~~~~~~~~~~~~~~~~~
-
-The last activty date for user logins appears in the patron's summary.
-
-image::media/User_Activity_Types2A.jpg[User_Activity_Types2A]
-
+User Activity Types
+-------------------
+
+The User Activity Types feature enables you to specify the user activity that you want to record in the database. You can use this feature for reporting purposes. This function will also display a last activity date in a user's account.
+
+Enabling this Feature
+~~~~~~~~~~~~~~~~~~~~~
+
+Click *Admin* -> *Server Administration* -> *User Activity Types* to access the default set of user activity types and to add new ones. The default set of user activity types records user logins to the Evergreen ILS and to third party products that communicate with Evergreen.
+
+The *Label* is a free text field that enables you to describe the activity that you are tracking.
+
+The *Event Caller* describes the third party software or Evergreen interface that interacts with the Evergreen database and is responsible for managing the communication between the parties.
+
+The *Event Type* describes the type of activity that Evergreen is tracking. Currently, this feature only tracks user authentication.
+
+The *Event Mechanism* describes the framework for communication between the third party software or OPAC and the database. Enter an event mechanism if you want to track the means by which the software communicates with the database. If you do not want to track how the softwares communicate, then leave this field empty.
+
+The *Enabled* field allows you to specify which types of user activity that you would like to track.
+
+The *Transient* column enables you to decide how many actions you want to track. If you want to track only the last activity, then enter *True.* If you want to trace all activity by the user, enter *False*.
+
+image::media/User_Activity_Types1A.jpg[User_Activity_Types1A]
+
+
+Using this Feature
+~~~~~~~~~~~~~~~~~~
+
+The last activty date for user logins appears in the patron's summary.
+
+image::media/User_Activity_Types2A.jpg[User_Activity_Types2A]
+
diff --git a/docs/cataloging/batch_importing_MARC.txt b/docs/cataloging/batch_importing_MARC.txt
index 906af8c..f58e82d 100644
--- a/docs/cataloging/batch_importing_MARC.txt
+++ b/docs/cataloging/batch_importing_MARC.txt
@@ -1,214 +1,214 @@
-Batch Importing MARC Records
-----------------------------
-
-The cataloging module in version 2.2 includes an enhanced MARC Batch Import interface. This interface features improved matching of records and managing of your import queue. In 2.2, you will be able to specify match points between incoming and existing records. You will also be able to apply filters to your queue that enable you to generate any errors that may have occurred during import. You will also be able to print your queue, email your queue, or export your queue as a CSV file.
-
-Permissions
-~~~~~~~~~~~
-
-To use match sets to import records, you will need the following permission:
-
-ADMIN_IMPORT_MATCH_SET
-
-
-Record Display Attributes
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
-This feature enables you to specify the tags and subfields that will display in records that appear in the import queue.
-
-
-*Record Match Sets*
-
-This feature enables you to create custom match points that you can use to accurately match incoming records with existing catalog records.
-
-
-In this example, to demonstrate matching on record attributes and MARC tags and subfields, we will create a record match set that defines a match based on the title of the record, in either the 240 or 245, and the fixed field, Lang. You can add multiple record attributes and MARC tags to customize a record match set.
-
-
-1) Click *Cataloging -> MARC Batch Import/Export*.
-
-2) Create a new record match set. Click *Record Match Sets -> New Match Set*.
-
-3) Enter a name for the record match set.
-
-4) Select an *Owning Library* from the drop down menu. Staff with permissions at this location will be able to use this record match set.
-
-5) Select a *Match Set Type* from the drop down menu. You can create a match set for authority records or bibliographic records.
-
-6) Click *Save*.
-
-
-image::media/Batch_Importing_MARC_Records1.jpg[Batch_Importing_MARC_Records1]
-
-
-7) The screen will refresh to list the record match set that you created. Click the link to the record match set.
-
-8) Create an expression that will define the match points for the incoming record. You can choose from two areas to create a match: *Record Attribute* or *MARC Tag and Subfield*. You can use the Boolean operators AND and OR to combine these elements to create a match set.
-
-9) Select a *Record Attribute* from the drop-down menu.
-
-10) Enter a *Match Score.* The *Match Score* indicates the relative importance of that match point as Evergreen evaluates an incoming record against an existing record. You can enter any integer into this field. The number that you enter is only important as it relates to other match points. Recommended practice is that you create a match score of one (1) for the least important match point and assign increasing match points to the power of 2 to working points in increasing importance.
-
-11) Check the *Negate?* box if you want to negate the match point. Checking this box would be the equivalent of applying a Boolean operator of NOT to the match point.
-
-
-
-image::media/Batch_Importing_MARC_Records2.jpg[Batch_Importing_MARC_Records2]
-
-
-
-12) Click *Ok.*
-
-13) Drag the completed match point under the folder with the appropriately-named Boolean folder under the Expression tree.
-
-
-
-image::media/Batch_Importing_MARC_Records3.jpg[Batch_Importing_MARC_Records3]
-
-
-The match point will nest underneath the folder in the Expression tree.
-
-
-image::media/Batch_Importing_MARC_Records4.jpg[Batch_Importing_MARC_Records4]
-
-
-14) Enter another *Boolean Operator* to further refine your match set.
-
-15) Click *Boolean Operator*.
-
-16) Select the *OR* operator from the drop down menu.
-
-17) Click *Ok*.
-
-18) Drag the operator to the expression tree.
-
-
-image::media/Batch_Importing_MARC_Records5.jpg[Batch_Importing_MARC_Records5]
-
-
-19) Click *MARC Tag and Subfield*.
-
-20) Enter a *MARC tag* on which you want the records to match.
-
-21) Enter a *subfield* on which you want the records to match.
-
-22) Enter a *Match Score.* The *Match Score* indicates the relative importance of that match point as Evergreen evaluates an incoming record against an existing record. You can enter any integer into this field. The number that you enter is only important as it relates to other match points. Recommended practice is that you create a match score of one (1) for the least important match point and assign increasing match points to the power of 2 to working points in increasing importance.
-
-23) Check the *Negate?* box if you want to negate the match point. Checking this box would be the equivalent of applying a Boolean operator of NOT to the match point.
-
-
-24) Click *Ok.*
-
-
-image::media/Batch_Importing_MARC_Records6.jpg[Batch_Importing_MARC_Records6]
-
-
-25) Drag the completed match point under the folder with the appropriately-named Boolean folder under the Expression tree. The Expression will build across the top of the screen.
-
-26) Add additional MARC tags or record attributes to build the expression tree.
-
-27) Click *Save Changes to Expression*.
-
-
-image::media/Batch_Importing_MARC_Records7.jpg[Batch_Importing_MARC_Records7]
-
-
-*Replace Mode*
-
-Replace Mode enables you to replace an existing part of the expression tree with a new record attribute, MARC tag, or Boolean operator. For example, if the top of the tree is AND, in replace mode, you could change that to an OR.
-
-
-1) Create a working match point.
-
-2) Click *Enter replace mode*.
-
-3) Highlight the piece of the tree that you want to replace.
-
-4) Drag the replacement piece over the highlighted piece.
-
-5) Click *Exit Replace Mode*.
-
-
-*Quality Metrics*
-
-
-1) Set the *Quality Metrics for this Match Set*. Quality metrics are used to determine the overall quality of a record. Each metric is given a weight and the total quality value for a record is equal to the sum of all metrics that apply to that record. For example, a record that has been cataloged thoroughly and contains accurate data would be more valuable than one of poor quality. You may want to ensure that the incoming record is of the same or better quality than the record that currently exists in your catalog; otherwise, you may want the match to fail. The quality metric is optional.
-
-2) You can create quality metrics based on the record attribute or the MARC Tag and Subfield.
-
-3) Click *Record Attribute.*
-
-4) Select an attribute from the drop down menu.
-
-5) Enter a value for the attribute.
-
-6.) Enter a match score. You can enter any integer into this field. The number that you enter is only important as it relates to other quality values for the current configuration. Higher scores would indicate increasing quality of incoming records. You can, as in the expression match score, increase the quality points by increasing subsequent records by a power of 2 (two).
-
-7) Click *Ok*.
-
-
-image::media/Batch_Importing_MARC_Records8.jpg[Batch_Importing_MARC_Records8]
-
-
-
-*Import Records*
-
-The *Import Records* interface incorporates record match sets, quality metrics, more merging options, and improved ways to manage your queue. In this example, we will import a batch of records. One of the records in the queue will contain a matching record in the catalog that is of lower quality than the incoming record. We will import the record according to the guidelines set by our record match set, quality metrics, and merge/overlay choices that we will select.
-
-
-1) Select a *Record Type* from the drop down menu.
-
-2) Create a queue to which you can upload your records, or add you records to an existing queue. Queues are linked to match sets and a holdings import profile. You cannot change a holdings import or record match set for a queue.
-
-3) Select a *Record Match Set* from the drop down menu.
-
-4) Select a *Holdings Import Profile* if you want to import holdings that are attached to your records.
-
-5) Select a *Record Source* from the drop down menu.
-
-6) Select a *Merge Profile*. Merge profiles enable you to specify which tags should be removed or preserved in incoming records.
-
-7) Choose one of the following import options if you want to auto-import records:
-
-a. *Merge on Single Match* - Using the Record Match Set, Evergreen will only attempt to perform the merge/overlay action if only one match was found in the catalog.
-
-b. *Merge on Best Match* - If more than one match is found in the catalog for a given record, Evergreen will attempt to perform the merge/overlay action with the best match as defined by the match score and quality metric.
-
-NOTE: Quality ratio affects only the *Merge on Single Match* and *Merge on Best Match* options.
-
-8) Enter a *Best/Single Match Minimum Quality Ratio.* Divide the incoming record quality score by the record quality score of the best match that might exist in the catalog. By default, Evergreen will assign any record a quality score of 1 (one). If you want to ensure that the inbound record is only imported when it has a higher quality than the best match, then you must enter a ratio that is higher than 1. For example, if you want the incoming record to have twice the quality of an existing record, then you should enter a 2 (two) in this field. If you want to bypass all quality restraints, enter a 0 (zero) in this field.
-
-
-9) Select an *Insufficient Quality Fall-Through Profile* if desired. This field enables you to indicate that if the inbound record doees not meet the configured quality standards, then you may still import the record using an alternate merge profile. This field is typically used for selecting a merge profile that allows
-the user to import holdings attached to a lower quality record without replacing the existing (target) record with the incoming record. This field is optional.
-
-10) *Browse* to find the appropriate file, and click *Upload*. The files will be uploaded to a queue.
-
-
-image::media/Batch_Importing_MARC_Records9.jpg[Batch_Importing_MARC_Records9]
-
-11) The screen will display records that have been uploaded to your queue.
-
-image::media/Batch_Importing_MARC_Records15.jpg[Batch_Importing_MARC_Records15]
-
-
-12) If Evergreen indicates that matching records exist, then click the *Matches* link to view the matching records. Check the box adjacent to the existing record that you want to merge with the incoming record.
-
-image::media/Batch_Importing_MARC_Records10.jpg[Batch_Importing_MARC_Records10]
-
-13) Click *Back to Import Queue*.
-
-14) Check the boxes of the records that you want to import, and click *Import Selected Records*, or click *Import All Records*.
-
-15) A pop up window will offer you the same import choices that were present on the *Import Records* screen. You can choose one of the import options, or click *Import*.
-
-image::media/Batch_Importing_MARC_Records9.jpg[Batch_Importing_MARC_Records9]
-
-16) The screen will refresh. The *Queue Summary* indicates that the record was imported. The *Import Time* column records the date that the record was imported.
-
-image::media/Batch_Importing_MARC_Records12.jpg[Batch_Importing_MARC_Records12]
-
-17) Search the catalog to confirm that the record was imported.
-
-image::media/Batch_Importing_MARC_Records14.jpg[Batch_Importing_MARC_Records14]
-
+Batch Importing MARC Records
+----------------------------
+
+The cataloging module in version 2.2 includes an enhanced MARC Batch Import interface. This interface features improved matching of records and managing of your import queue. In 2.2, you will be able to specify match points between incoming and existing records. You will also be able to apply filters to your queue that enable you to generate any errors that may have occurred during import. You will also be able to print your queue, email your queue, or export your queue as a CSV file.
+
+Permissions
+~~~~~~~~~~~
+
+To use match sets to import records, you will need the following permission:
+
+ADMIN_IMPORT_MATCH_SET
+
+
+Record Display Attributes
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This feature enables you to specify the tags and subfields that will display in records that appear in the import queue.
+
+
+*Record Match Sets*
+
+This feature enables you to create custom match points that you can use to accurately match incoming records with existing catalog records.
+
+
+In this example, to demonstrate matching on record attributes and MARC tags and subfields, we will create a record match set that defines a match based on the title of the record, in either the 240 or 245, and the fixed field, Lang. You can add multiple record attributes and MARC tags to customize a record match set.
+
+
+1) Click *Cataloging -> MARC Batch Import/Export*.
+
+2) Create a new record match set. Click *Record Match Sets -> New Match Set*.
+
+3) Enter a name for the record match set.
+
+4) Select an *Owning Library* from the drop down menu. Staff with permissions at this location will be able to use this record match set.
+
+5) Select a *Match Set Type* from the drop down menu. You can create a match set for authority records or bibliographic records.
+
+6) Click *Save*.
+
+
+image::media/Batch_Importing_MARC_Records1.jpg[Batch_Importing_MARC_Records1]
+
+
+7) The screen will refresh to list the record match set that you created. Click the link to the record match set.
+
+8) Create an expression that will define the match points for the incoming record. You can choose from two areas to create a match: *Record Attribute* or *MARC Tag and Subfield*. You can use the Boolean operators AND and OR to combine these elements to create a match set.
+
+9) Select a *Record Attribute* from the drop-down menu.
+
+10) Enter a *Match Score.* The *Match Score* indicates the relative importance of that match point as Evergreen evaluates an incoming record against an existing record. You can enter any integer into this field. The number that you enter is only important as it relates to other match points. Recommended practice is that you create a match score of one (1) for the least important match point and assign increasing match points to the power of 2 to working points in increasing importance.
+
+11) Check the *Negate?* box if you want to negate the match point. Checking this box would be the equivalent of applying a Boolean operator of NOT to the match point.
+
+
+
+image::media/Batch_Importing_MARC_Records2.jpg[Batch_Importing_MARC_Records2]
+
+
+
+12) Click *Ok.*
+
+13) Drag the completed match point under the folder with the appropriately-named Boolean folder under the Expression tree.
+
+
+
+image::media/Batch_Importing_MARC_Records3.jpg[Batch_Importing_MARC_Records3]
+
+
+The match point will nest underneath the folder in the Expression tree.
+
+
+image::media/Batch_Importing_MARC_Records4.jpg[Batch_Importing_MARC_Records4]
+
+
+14) Enter another *Boolean Operator* to further refine your match set.
+
+15) Click *Boolean Operator*.
+
+16) Select the *OR* operator from the drop down menu.
+
+17) Click *Ok*.
+
+18) Drag the operator to the expression tree.
+
+
+image::media/Batch_Importing_MARC_Records5.jpg[Batch_Importing_MARC_Records5]
+
+
+19) Click *MARC Tag and Subfield*.
+
+20) Enter a *MARC tag* on which you want the records to match.
+
+21) Enter a *subfield* on which you want the records to match.
+
+22) Enter a *Match Score.* The *Match Score* indicates the relative importance of that match point as Evergreen evaluates an incoming record against an existing record. You can enter any integer into this field. The number that you enter is only important as it relates to other match points. Recommended practice is that you create a match score of one (1) for the least important match point and assign increasing match points to the power of 2 to working points in increasing importance.
+
+23) Check the *Negate?* box if you want to negate the match point. Checking this box would be the equivalent of applying a Boolean operator of NOT to the match point.
+
+
+24) Click *Ok.*
+
+
+image::media/Batch_Importing_MARC_Records6.jpg[Batch_Importing_MARC_Records6]
+
+
+25) Drag the completed match point under the folder with the appropriately-named Boolean folder under the Expression tree. The Expression will build across the top of the screen.
+
+26) Add additional MARC tags or record attributes to build the expression tree.
+
+27) Click *Save Changes to Expression*.
+
+
+image::media/Batch_Importing_MARC_Records7.jpg[Batch_Importing_MARC_Records7]
+
+
+*Replace Mode*
+
+Replace Mode enables you to replace an existing part of the expression tree with a new record attribute, MARC tag, or Boolean operator. For example, if the top of the tree is AND, in replace mode, you could change that to an OR.
+
+
+1) Create a working match point.
+
+2) Click *Enter replace mode*.
+
+3) Highlight the piece of the tree that you want to replace.
+
+4) Drag the replacement piece over the highlighted piece.
+
+5) Click *Exit Replace Mode*.
+
+
+*Quality Metrics*
+
+
+1) Set the *Quality Metrics for this Match Set*. Quality metrics are used to determine the overall quality of a record. Each metric is given a weight and the total quality value for a record is equal to the sum of all metrics that apply to that record. For example, a record that has been cataloged thoroughly and contains accurate data would be more valuable than one of poor quality. You may want to ensure that the incoming record is of the same or better quality than the record that currently exists in your catalog; otherwise, you may want the match to fail. The quality metric is optional.
+
+2) You can create quality metrics based on the record attribute or the MARC Tag and Subfield.
+
+3) Click *Record Attribute.*
+
+4) Select an attribute from the drop down menu.
+
+5) Enter a value for the attribute.
+
+6.) Enter a match score. You can enter any integer into this field. The number that you enter is only important as it relates to other quality values for the current configuration. Higher scores would indicate increasing quality of incoming records. You can, as in the expression match score, increase the quality points by increasing subsequent records by a power of 2 (two).
+
+7) Click *Ok*.
+
+
+image::media/Batch_Importing_MARC_Records8.jpg[Batch_Importing_MARC_Records8]
+
+
+
+*Import Records*
+
+The *Import Records* interface incorporates record match sets, quality metrics, more merging options, and improved ways to manage your queue. In this example, we will import a batch of records. One of the records in the queue will contain a matching record in the catalog that is of lower quality than the incoming record. We will import the record according to the guidelines set by our record match set, quality metrics, and merge/overlay choices that we will select.
+
+
+1) Select a *Record Type* from the drop down menu.
+
+2) Create a queue to which you can upload your records, or add you records to an existing queue. Queues are linked to match sets and a holdings import profile. You cannot change a holdings import or record match set for a queue.
+
+3) Select a *Record Match Set* from the drop down menu.
+
+4) Select a *Holdings Import Profile* if you want to import holdings that are attached to your records.
+
+5) Select a *Record Source* from the drop down menu.
+
+6) Select a *Merge Profile*. Merge profiles enable you to specify which tags should be removed or preserved in incoming records.
+
+7) Choose one of the following import options if you want to auto-import records:
+
+a. *Merge on Single Match* - Using the Record Match Set, Evergreen will only attempt to perform the merge/overlay action if only one match was found in the catalog.
+
+b. *Merge on Best Match* - If more than one match is found in the catalog for a given record, Evergreen will attempt to perform the merge/overlay action with the best match as defined by the match score and quality metric.
+
+NOTE: Quality ratio affects only the *Merge on Single Match* and *Merge on Best Match* options.
+
+8) Enter a *Best/Single Match Minimum Quality Ratio.* Divide the incoming record quality score by the record quality score of the best match that might exist in the catalog. By default, Evergreen will assign any record a quality score of 1 (one). If you want to ensure that the inbound record is only imported when it has a higher quality than the best match, then you must enter a ratio that is higher than 1. For example, if you want the incoming record to have twice the quality of an existing record, then you should enter a 2 (two) in this field. If you want to bypass all quality restraints, enter a 0 (zero) in this field.
+
+
+9) Select an *Insufficient Quality Fall-Through Profile* if desired. This field enables you to indicate that if the inbound record doees not meet the configured quality standards, then you may still import the record using an alternate merge profile. This field is typically used for selecting a merge profile that allows
+the user to import holdings attached to a lower quality record without replacing the existing (target) record with the incoming record. This field is optional.
+
+10) *Browse* to find the appropriate file, and click *Upload*. The files will be uploaded to a queue.
+
+
+image::media/Batch_Importing_MARC_Records9.jpg[Batch_Importing_MARC_Records9]
+
+11) The screen will display records that have been uploaded to your queue.
+
+image::media/Batch_Importing_MARC_Records15.jpg[Batch_Importing_MARC_Records15]
+
+
+12) If Evergreen indicates that matching records exist, then click the *Matches* link to view the matching records. Check the box adjacent to the existing record that you want to merge with the incoming record.
+
+image::media/Batch_Importing_MARC_Records10.jpg[Batch_Importing_MARC_Records10]
+
+13) Click *Back to Import Queue*.
+
+14) Check the boxes of the records that you want to import, and click *Import Selected Records*, or click *Import All Records*.
+
+15) A pop up window will offer you the same import choices that were present on the *Import Records* screen. You can choose one of the import options, or click *Import*.
+
+image::media/Batch_Importing_MARC_Records9.jpg[Batch_Importing_MARC_Records9]
+
+16) The screen will refresh. The *Queue Summary* indicates that the record was imported. The *Import Time* column records the date that the record was imported.
+
+image::media/Batch_Importing_MARC_Records12.jpg[Batch_Importing_MARC_Records12]
+
+17) Search the catalog to confirm that the record was imported.
+
+image::media/Batch_Importing_MARC_Records14.jpg[Batch_Importing_MARC_Records14]
+
diff --git a/docs/cataloging/monograph_parts.txt b/docs/cataloging/monograph_parts.txt
index 122fcae..8f9780d 100644
--- a/docs/cataloging/monograph_parts.txt
+++ b/docs/cataloging/monograph_parts.txt
@@ -1,57 +1,57 @@
-Monograph Parts
----------------
-
-*Monograph Parts* enables you to differentiate between parts of monographs or other multi-part items. This feature enables catalogers to describe items more precisely by labeling the parts of an item. For example, catalogers might identify the parts of a monograph or the discs of a DVD set. This feature also allows patrons more flexibility when placing holds on multi-part items. A patron could place a hold on a specific disc of a DVD set if they want to access a specific season or episode rather than an entire series.
-
-Four new permissions are used by this functionality: CREATE_MONOGRAPH_PART, UPDATE_MONOGRAPH_PART, DELETE_MONOGRAPH_PART and MAP_MONOGRAPH_PART. Thes
-e permissions should be assigned at the consorial level to those groups or users that will make use of the features described below.
-
-
-Add a monograph part to an existing record
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To add a monograph part to an existing record in the catalog:
-
-1) Retrieve a record.
-
-2) Click *Actions for this Record -> Manage Parts*
-
-
-image::media/monograph_parts1.jpg[monograph_parts1]
-
-
-3) Click *New Monograph Part*
-
-4) Enter the *label* that you want to appear to the user in the catalog, and click *Save*. This will create a list of monograph parts from which you can choose when you create a volume and copy.
-
-
-image::media/monograph_parts2.jpg[monograph_parts2]
-
-
-5) Add a volume and copy. To add a volume and copy to your workstation library, click the *Add Volumes* link in the *Record Summary* at the top of the bibliographic record, or click *Actions for this Record -> Add Volumes*.
-
-To add a volume and copy to your workstation library or other libraries, click *Actions for this Record -> Holdings Maintenance -> Add Volumes*.
-
-
-image::media/monograph_parts3.jpg[monograph_parts3]
-
-
-6) The *Unified Volume/Copy Creator* opens. Enter the number of volumes that you want to add to the catalog and the volume description.
-
-7) Enter the number of copies and barcode(s) of each item.
-
-8) Select the *part designation* from the drop down menu adjacent to the barcode field.
-
-9) Apply a template to the copies, or edit fields in the *Copy Editor*.
-
-
-image::media/monograph_parts4.jpg[monograph_parts4]
-
-
-10) Click *Create Volumes/Items*.
-
-11) The *Holdings Maintenance* screen will refresh to demonstrate the addition of the volume, copy, and part. These fields also appear in the OPAC View.
-
-
-image::media/monograph_parts5.jpg[monograph_parts5]
-
+Monograph Parts
+---------------
+
+*Monograph Parts* enables you to differentiate between parts of monographs or other multi-part items. This feature enables catalogers to describe items more precisely by labeling the parts of an item. For example, catalogers might identify the parts of a monograph or the discs of a DVD set. This feature also allows patrons more flexibility when placing holds on multi-part items. A patron could place a hold on a specific disc of a DVD set if they want to access a specific season or episode rather than an entire series.
+
+Four new permissions are used by this functionality: CREATE_MONOGRAPH_PART, UPDATE_MONOGRAPH_PART, DELETE_MONOGRAPH_PART and MAP_MONOGRAPH_PART. Thes
+e permissions should be assigned at the consorial level to those groups or users that will make use of the features described below.
+
+
+Add a monograph part to an existing record
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To add a monograph part to an existing record in the catalog:
+
+1) Retrieve a record.
+
+2) Click *Actions for this Record -> Manage Parts*
+
+
+image::media/monograph_parts1.jpg[monograph_parts1]
+
+
+3) Click *New Monograph Part*
+
+4) Enter the *label* that you want to appear to the user in the catalog, and click *Save*. This will create a list of monograph parts from which you can choose when you create a volume and copy.
+
+
+image::media/monograph_parts2.jpg[monograph_parts2]
+
+
+5) Add a volume and copy. To add a volume and copy to your workstation library, click the *Add Volumes* link in the *Record Summary* at the top of the bibliographic record, or click *Actions for this Record -> Add Volumes*.
+
+To add a volume and copy to your workstation library or other libraries, click *Actions for this Record -> Holdings Maintenance -> Add Volumes*.
+
+
+image::media/monograph_parts3.jpg[monograph_parts3]
+
+
+6) The *Unified Volume/Copy Creator* opens. Enter the number of volumes that you want to add to the catalog and the volume description.
+
+7) Enter the number of copies and barcode(s) of each item.
+
+8) Select the *part designation* from the drop down menu adjacent to the barcode field.
+
+9) Apply a template to the copies, or edit fields in the *Copy Editor*.
+
+
+image::media/monograph_parts4.jpg[monograph_parts4]
+
+
+10) Click *Create Volumes/Items*.
+
+11) The *Holdings Maintenance* screen will refresh to demonstrate the addition of the volume, copy, and part. These fields also appear in the OPAC View.
+
+
+image::media/monograph_parts5.jpg[monograph_parts5]
+
diff --git a/docs/cataloging/overlay_record_3950_import.txt b/docs/cataloging/overlay_record_3950_import.txt
index 73c63f1..733b47a 100644
--- a/docs/cataloging/overlay_record_3950_import.txt
+++ b/docs/cataloging/overlay_record_3950_import.txt
@@ -1,55 +1,55 @@
-Overlay Existing Catalog Record via Z39.50 Import
--------------------------------------------------
-
-This feature enables you to replace a catalog record with a record obtained through a Z39.50 search. No new permissions or administrative settings are needed to use this feature.
-
-*To Overlay an Existing Record via Z39.50 Import:*
-
-1) Click *Cataloging -> Import Record from Z39.50*
-
-2) Select at least one *Service* in addition to the *Local Catalog* in the *Service and Credentials* window in the top right panel.
-
-3) Enter search terms in the *Query* window in the top left panel.
-
-4) Click *Search*.
-
-image::media/Overlay_Existing_Record_via_Z39_50_Import1.jpg[]
-
-5) The results will appear in the lower window.
-
-6) Select the record in the local catalog that you wish to overlay.
-
-7) Click *Mark Local Result as Overlay Target*
-
-
-image::media/Overlay_Existing_Record_via_Z39_50_Import2.jpg[]
-
-
-8) A confirmation message appears. Click *OK*.
-
-9) Select the record that you want to replace the existing catalog record.
-
-10) Click *Overlay.*
-
-
-image::media/Overlay_Existing_Record_via_Z39_50_Import3.jpg[]
-
-
-11) The record that you selected will open in the MARC Editor. Make any desired changes to the record, and click *Overlay Record*.
-
-image::media/Overlay_Existing_Record_via_Z39_50_Import4.jpg[]
-
-
-12) The catalog record that you want to overlay will appear in a new window. Review the MARC record to verify that you are overlaying the correct catalog record.
-
-13) If the correct record appears, click *Overlay*.
-
-
-image::media/Overlay_Existing_Record_via_Z39_50_Import5.jpg[]
-
-14) A confirmation message will appear to confirm that you have overlaid the record. Click *Ok*.
-
-15) The screen will refresh in the OPAC View to show that the record has been overlaid.
-
-
-image::media/Overlay_Existing_Record_via_Z39_50_Import6.jpg[]
+Overlay Existing Catalog Record via Z39.50 Import
+-------------------------------------------------
+
+This feature enables you to replace a catalog record with a record obtained through a Z39.50 search. No new permissions or administrative settings are needed to use this feature.
+
+*To Overlay an Existing Record via Z39.50 Import:*
+
+1) Click *Cataloging -> Import Record from Z39.50*
+
+2) Select at least one *Service* in addition to the *Local Catalog* in the *Service and Credentials* window in the top right panel.
+
+3) Enter search terms in the *Query* window in the top left panel.
+
+4) Click *Search*.
+
+image::media/Overlay_Existing_Record_via_Z39_50_Import1.jpg[]
+
+5) The results will appear in the lower window.
+
+6) Select the record in the local catalog that you wish to overlay.
+
+7) Click *Mark Local Result as Overlay Target*
+
+
+image::media/Overlay_Existing_Record_via_Z39_50_Import2.jpg[]
+
+
+8) A confirmation message appears. Click *OK*.
+
+9) Select the record that you want to replace the existing catalog record.
+
+10) Click *Overlay.*
+
+
+image::media/Overlay_Existing_Record_via_Z39_50_Import3.jpg[]
+
+
+11) The record that you selected will open in the MARC Editor. Make any desired changes to the record, and click *Overlay Record*.
+
+image::media/Overlay_Existing_Record_via_Z39_50_Import4.jpg[]
+
+
+12) The catalog record that you want to overlay will appear in a new window. Review the MARC record to verify that you are overlaying the correct catalog record.
+
+13) If the correct record appears, click *Overlay*.
+
+
+image::media/Overlay_Existing_Record_via_Z39_50_Import5.jpg[]
+
+14) A confirmation message will appear to confirm that you have overlaid the record. Click *Ok*.
+
+15) The screen will refresh in the OPAC View to show that the record has been overlaid.
+
+
+image::media/Overlay_Existing_Record_via_Z39_50_Import6.jpg[]
diff --git a/docs/circulation/booking.txt b/docs/circulation/booking.txt
index 730b890..880b796 100644
--- a/docs/circulation/booking.txt
+++ b/docs/circulation/booking.txt
@@ -1,272 +1,272 @@
-Booking Module
---------------
-
-Creating a Booking Reservation
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Only staff members may create reservations. A reservation can be started from a patron record, or a booking resource. To reserve catalogued items, you may start from searching the catalogue, if you do not know the booking item's barcode.
-
-To create a reservation from a patron record
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-1) Retrieve the patron’s record.
-
-2) Select Other --> Booking --> Create or Cancel Reservations. This takes you to the Reservations Screen.
-
-image::media/booking-create-1.png[]
-
-3) For non-catalogued items, choose a Bookable Resource Type and click Next. For catalogued items, enter the barcode in Enter the barcode of a catalogued, bookable resource box, then click Next beside the box.
-
-image::media/booking-create-2.png[]
-
-4) For non-catalogued resources, the Bookable Resource Type and the items associated with the type will appear.
-
-image::media/booking-create-3.png[]
-
-For catalogued items, the title and the item will display in the box.
-
-5) Select the date and time for the reservation in I need this resource... area. Click the date field. A calendar widget will be displayed for you to choose a date. Click the time field to choose time from the dropdown list.
-
-image::media/booking-create-4.png[]
-
-[NOTE]
-If incorrect date and time is selected, the date/time boxes will appear in red. For example, if the time for which the reservation is set has already passed, the boxes will appear in red. There must be at least 15 minutes between the creation of the reservation and the start time of the reservation.
-
-6) For non-catalogued resources, patrons may specify special feature(s), if any, of the resource. With these attributes: allows you to do so. For example, if a patron is booking a laptop he/she can choose between PC and Mac and even choose a specific operating system if they need to. Click the drop down arrow to select your option from the list.
-
-image::media/booking-create-5.png[]
-
-7) Select the pickup location from the dropdown list.
-
-image::media/booking-create-6.png[]
-
-8) If there are multiple copies of the resource and any item listed is acceptable, click Reserve Any. To choose a specific item, select it
-and then click Reserve Selected.
-
-image::media/booking-create-7.png[]
-
-9) A message will confirm that the action succeeded. Click OK on the prompt.
-
-10) The screen will refresh and the reservation will appear below the patron’s name at the bottom of the screen.
-
-image::media/booking-create-9.png[]
-
-To create a reservation from a booking resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-You need to know the barcode of the patron when you create a reservation for him/her from a booking resource.
-
-1) From the Booking menu, select Create Reservations
-
-image::media/booking-create-module-1.png[]
-
-2) Choose a Bookable Resource Type and click Next or enter the barcode of a catalogued resource and click Next.
-
-image::media/booking-create-module-2.png[]
-
-3) For non-catalogued resources, a screen showing the Bookable Resource Type and the items associated with the type will appear.
-
-image::media/booking-create-module-3.png[]
-
-For catalogued resources, the title and item will appear.
-
-4) Enter the user’s barcode in the Reserve to patron barcode box. The user’s existing reservations, if any, will appear at the bottom of the screen.
-
-image::media/booking-create-module-4.png[]
-
-5) Select the date and time for the reservation in I need this resource... area. Click the date field. A calendar widget will be displayed for you to choose a date. Click the time field to choose time from the dropdown list.
-
-image::media/booking-create-4.png[]
-
-[NOTE]
-If incorrect date and time is selected, the date/time boxes will appear in red. For example, if the time for which the reservation is set has already passed, the boxes will appear in red. The times must be set correctly for the reservation to be created. There must be at least 15 minutes between the creation of the reservation and the start time of the reservation.
-
-
-6) For non-catalogued resources, patrons may specify special feature(s), if any, of the resource. The With these attributes: allows you to do so. For example, if a patron is booking a laptop they can choose between PC and Mac and even choose a specific operating system if they need to. Click the dropdown arrow to select your option from the list.
-
-image::media/booking-create-5.png[]
-
-7) Select the pickup location from the dropdown list.
-
-image::media/booking-create-6.png[]
-
-8) If there are multiple copies of the resource and any item listed is acceptable, click Reserve Any. To choose a specific item, select it and then click Reserve Selected.
-
-image::media/booking-create-7.png[]
-
-9) A message will confirm that the action succeeded. Click OK on the prompt.
-
-10) The screen will refresh and the reservation will appear below the patron’s name at the bottom of the screen.
-
-image::media/booking-create-9.png[]
-
-
-Search the catalogue to create a reservation
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-If you would like to reserve a catalogued item but do not know the item barcode, you may start with a catalogue search.
-
-1) In the staff client, select Cataloguing --> Search the Catalogue or keyboard shortcut F3 to search for the item you wish to reserve. You may search by any bibliographic information.
-
-2) Click the title to display the record summary. In the Copy Summary, select Copy Details in Actions column.
-
-3) The Copy Details will appear in a new row. In the barcode column, click the book now link.
-
-4) A screen showing the title and barcodes of available copies will appear.
-
-5) Enter the user’s barcode in the Reserve to patron barcode box. The user’s existing reservations, if any, will appear at the bottom of the screen.
-
-6) Select the date and time in I need this resource... section. If the date and time set is incorrect the boxes appear in red. For example, if the time for which the reservation is set has already passed, the boxes will appear in red.
-
-7) Select pickup location. If there are multiple copies and any of the listed items is acceptable, click Reserve Any. To choose a specific item, select it and then click Reserve Selected.
-
-8) A message will confirm that the action succeeded. Click OK on the prompt.
-
-9) The screen will refresh, and the reservation will appear below the user’s name.
-
-[NOTE]
-Reservations on catalogued items can be created on Item Status (F5) screen. Select the item, then Actions for Selected Items → Book Item Now.
-
-Reservation Pull List
-~~~~~~~~~~~~~~~~~~~~~
-
-Reservation pull list can be generated dynamically on the Staff Client.
-
-1) To create a pull list, select Booking --> Pull List.
-
-image::media/booking-pull-1.png[]
-
-2) You can decide how many days in advance you would like to pull reserved items. Enter the number of days in the box adjacent to Generate list for this many days hence. For example, if you would like to pull items that are needed today, you can enter 1 in the box, and you will retrieve items that need to be pulled today.
-
-3) Click Fetch to retrieve the pull list.
-
-image::media/booking-pull-2.png[]
-
-4) The pull list will appear. Click Print to print the pull list.
-
-image::media/booking-pull-3.png[]
-
-Capturing Items for Reservations
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Reservations must be captured before they are ready to be picked up by the patron.
-
-[CAUTION]
-Always capture reservations in Booking Module. Check In function in Circulation does not function the same as Capture Resources.
-
-1) In the staff client, select Booking --> Capture Resources.
-
-image::media/booking-capture-1.png[]
-
-2) Scan the item barcode or type the barcode then click Capture.
-
-image::media/booking-capture-2.png[]
-
-3) The message Capture succeeded will appear to the right. Information about the item will appear below the message. Click Print button to print a slip for the reservation.
-
-image::media/booking-capture-3.png[]
-
-
-Picking Up Reservations
-~~~~~~~~~~~~~~~~~~~~~~~
-
-[CAUTION]
-Always use the dedicated Booking Module interfaces for tasks related to reservations. Items that have been captured for a reservation cannot be checked out using the Check Out interface, even if the patron is the reservation recipient.
-
-1) Ready-for-pickup reservations can be listed from Other --> Booking --> Pick Up Reservations within a patron record or Booking --> Pick Up Reservations.
-
-
-image::media/booking-pickup-1.png[]
-
-image::media/booking-pickup-module-1.png[]
-
-
-2) Scan the patron barcode if using Booking --> Pick Up Reservations.
-
-3) The reservation(s) available for pickup will display. Select those you want to pick up and click Pick Up.
-
-image::media/booking-pickup-2.png[]
-
-4) The screen will refresh to show that the patron has picked up the reservation(s).
-
-image::media/booking-pickup-3.png[]
-
-
-Returning Reservations
-~~~~~~~~~~~~~~~~~~~~~~
-
-[CAUTION]
-When a reserved item is brought back, staff must use the Booking Module to return the reservation.
-
-1) To return reservations, select Booking --> Return Reservations
-
-image::media/booking-return-module-1.png[]
-
-2) You can return the item by patron or item barcode. Here we choose Resource to return by item barcode. Scan or enter the barcode, and click Go.
-
-image::media/booking-return-module-2.png[]
-
-3) A pop up box will tell you that the item was returned. Click OK on the prompt.
-
-4) If we select Patron on the above screen, after scanning the patron's barcode, reservations currently out to that patron are displayed. Highlight the reservations you want to return, and click Return.
-
-image::media/booking-return-2.png[]
-
-5) The screen will refresh to show any resources that remain out and the reservations that have been returned.
-
-image::media/booking-return-module-4.png[]
-
-[NOTE]
-Reservations can be returned from within patron records by selecting Other --> Booking --> Return Reservations
-
-Cancelling a Reservation
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-A reservation can be cancelled in a patron’s record or reservation creation screen.
-
-Cancel a reservation from the patron record
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-1) Retrieve the patron's record.
-
-2) Select Other --> Booking --> Create or Cancel Reservations.
-
-image::media/booking-create-1.png[]
-
-3) The existing reservations will appear at the bottom of the screen.
-
-image::media/booking-cancel-1.png[]
-
-4) Highlight the reservation that you want to cancel. Click Cancel Selected.
-
-image::media/booking-cancel-2.png[]
-
-[NOTE]
-Use Shift or Ctrl on keyboard and mouse click to select multiple reservations if needed.
-
-5) A pop-up window will confirm the cancellation. Click OK on the prompt.
-
-6) The screen will refresh, and the cancelled reservation(s) will disappear.
-
-image::media/booking-cancel-4.png[]
-
-Cancel a reservation on reservation creation screen
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-1) Access the reservation creation screen by selecting Booking --> Create Reservations.
-
-2) Select any Bookable Resource Type, then click Next.
-
-3) Scan or type in the patron barcode in Reserve to Patron box then hit Enter.
-
-4) Patron's existing reservations will display at the bottom of the screen.
-
-5) Select those that you want to cancel, then click Cancel Selected.
-
-
-
-
-
-
-
-
+Booking Module
+--------------
+
+Creating a Booking Reservation
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Only staff members may create reservations. A reservation can be started from a patron record, or a booking resource. To reserve catalogued items, you may start from searching the catalogue, if you do not know the booking item's barcode.
+
+To create a reservation from a patron record
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+1) Retrieve the patron’s record.
+
+2) Select Other --> Booking --> Create or Cancel Reservations. This takes you to the Reservations Screen.
+
+image::media/booking-create-1.png[]
+
+3) For non-catalogued items, choose a Bookable Resource Type and click Next. For catalogued items, enter the barcode in Enter the barcode of a catalogued, bookable resource box, then click Next beside the box.
+
+image::media/booking-create-2.png[]
+
+4) For non-catalogued resources, the Bookable Resource Type and the items associated with the type will appear.
+
+image::media/booking-create-3.png[]
+
+For catalogued items, the title and the item will display in the box.
+
+5) Select the date and time for the reservation in I need this resource... area. Click the date field. A calendar widget will be displayed for you to choose a date. Click the time field to choose time from the dropdown list.
+
+image::media/booking-create-4.png[]
+
+[NOTE]
+If incorrect date and time is selected, the date/time boxes will appear in red. For example, if the time for which the reservation is set has already passed, the boxes will appear in red. There must be at least 15 minutes between the creation of the reservation and the start time of the reservation.
+
+6) For non-catalogued resources, patrons may specify special feature(s), if any, of the resource. With these attributes: allows you to do so. For example, if a patron is booking a laptop he/she can choose between PC and Mac and even choose a specific operating system if they need to. Click the drop down arrow to select your option from the list.
+
+image::media/booking-create-5.png[]
+
+7) Select the pickup location from the dropdown list.
+
+image::media/booking-create-6.png[]
+
+8) If there are multiple copies of the resource and any item listed is acceptable, click Reserve Any. To choose a specific item, select it
+and then click Reserve Selected.
+
+image::media/booking-create-7.png[]
+
+9) A message will confirm that the action succeeded. Click OK on the prompt.
+
+10) The screen will refresh and the reservation will appear below the patron’s name at the bottom of the screen.
+
+image::media/booking-create-9.png[]
+
+To create a reservation from a booking resource
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You need to know the barcode of the patron when you create a reservation for him/her from a booking resource.
+
+1) From the Booking menu, select Create Reservations
+
+image::media/booking-create-module-1.png[]
+
+2) Choose a Bookable Resource Type and click Next or enter the barcode of a catalogued resource and click Next.
+
+image::media/booking-create-module-2.png[]
+
+3) For non-catalogued resources, a screen showing the Bookable Resource Type and the items associated with the type will appear.
+
+image::media/booking-create-module-3.png[]
+
+For catalogued resources, the title and item will appear.
+
+4) Enter the user’s barcode in the Reserve to patron barcode box. The user’s existing reservations, if any, will appear at the bottom of the screen.
+
+image::media/booking-create-module-4.png[]
+
+5) Select the date and time for the reservation in I need this resource... area. Click the date field. A calendar widget will be displayed for you to choose a date. Click the time field to choose time from the dropdown list.
+
+image::media/booking-create-4.png[]
+
+[NOTE]
+If incorrect date and time is selected, the date/time boxes will appear in red. For example, if the time for which the reservation is set has already passed, the boxes will appear in red. The times must be set correctly for the reservation to be created. There must be at least 15 minutes between the creation of the reservation and the start time of the reservation.
+
+
+6) For non-catalogued resources, patrons may specify special feature(s), if any, of the resource. The With these attributes: allows you to do so. For example, if a patron is booking a laptop they can choose between PC and Mac and even choose a specific operating system if they need to. Click the dropdown arrow to select your option from the list.
+
+image::media/booking-create-5.png[]
+
+7) Select the pickup location from the dropdown list.
+
+image::media/booking-create-6.png[]
+
+8) If there are multiple copies of the resource and any item listed is acceptable, click Reserve Any. To choose a specific item, select it and then click Reserve Selected.
+
+image::media/booking-create-7.png[]
+
+9) A message will confirm that the action succeeded. Click OK on the prompt.
+
+10) The screen will refresh and the reservation will appear below the patron’s name at the bottom of the screen.
+
+image::media/booking-create-9.png[]
+
+
+Search the catalogue to create a reservation
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+If you would like to reserve a catalogued item but do not know the item barcode, you may start with a catalogue search.
+
+1) In the staff client, select Cataloguing --> Search the Catalogue or keyboard shortcut F3 to search for the item you wish to reserve. You may search by any bibliographic information.
+
+2) Click the title to display the record summary. In the Copy Summary, select Copy Details in Actions column.
+
+3) The Copy Details will appear in a new row. In the barcode column, click the book now link.
+
+4) A screen showing the title and barcodes of available copies will appear.
+
+5) Enter the user’s barcode in the Reserve to patron barcode box. The user’s existing reservations, if any, will appear at the bottom of the screen.
+
+6) Select the date and time in I need this resource... section. If the date and time set is incorrect the boxes appear in red. For example, if the time for which the reservation is set has already passed, the boxes will appear in red.
+
+7) Select pickup location. If there are multiple copies and any of the listed items is acceptable, click Reserve Any. To choose a specific item, select it and then click Reserve Selected.
+
+8) A message will confirm that the action succeeded. Click OK on the prompt.
+
+9) The screen will refresh, and the reservation will appear below the user’s name.
+
+[NOTE]
+Reservations on catalogued items can be created on Item Status (F5) screen. Select the item, then Actions for Selected Items → Book Item Now.
+
+Reservation Pull List
+~~~~~~~~~~~~~~~~~~~~~
+
+Reservation pull list can be generated dynamically on the Staff Client.
+
+1) To create a pull list, select Booking --> Pull List.
+
+image::media/booking-pull-1.png[]
+
+2) You can decide how many days in advance you would like to pull reserved items. Enter the number of days in the box adjacent to Generate list for this many days hence. For example, if you would like to pull items that are needed today, you can enter 1 in the box, and you will retrieve items that need to be pulled today.
+
+3) Click Fetch to retrieve the pull list.
+
+image::media/booking-pull-2.png[]
+
+4) The pull list will appear. Click Print to print the pull list.
+
+image::media/booking-pull-3.png[]
+
+Capturing Items for Reservations
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Reservations must be captured before they are ready to be picked up by the patron.
+
+[CAUTION]
+Always capture reservations in Booking Module. Check In function in Circulation does not function the same as Capture Resources.
+
+1) In the staff client, select Booking --> Capture Resources.
+
+image::media/booking-capture-1.png[]
+
+2) Scan the item barcode or type the barcode then click Capture.
+
+image::media/booking-capture-2.png[]
+
+3) The message Capture succeeded will appear to the right. Information about the item will appear below the message. Click Print button to print a slip for the reservation.
+
+image::media/booking-capture-3.png[]
+
+
+Picking Up Reservations
+~~~~~~~~~~~~~~~~~~~~~~~
+
+[CAUTION]
+Always use the dedicated Booking Module interfaces for tasks related to reservations. Items that have been captured for a reservation cannot be checked out using the Check Out interface, even if the patron is the reservation recipient.
+
+1) Ready-for-pickup reservations can be listed from Other --> Booking --> Pick Up Reservations within a patron record or Booking --> Pick Up Reservations.
+
+
+image::media/booking-pickup-1.png[]
+
+image::media/booking-pickup-module-1.png[]
+
+
+2) Scan the patron barcode if using Booking --> Pick Up Reservations.
+
+3) The reservation(s) available for pickup will display. Select those you want to pick up and click Pick Up.
+
+image::media/booking-pickup-2.png[]
+
+4) The screen will refresh to show that the patron has picked up the reservation(s).
+
+image::media/booking-pickup-3.png[]
+
+
+Returning Reservations
+~~~~~~~~~~~~~~~~~~~~~~
+
+[CAUTION]
+When a reserved item is brought back, staff must use the Booking Module to return the reservation.
+
+1) To return reservations, select Booking --> Return Reservations
+
+image::media/booking-return-module-1.png[]
+
+2) You can return the item by patron or item barcode. Here we choose Resource to return by item barcode. Scan or enter the barcode, and click Go.
+
+image::media/booking-return-module-2.png[]
+
+3) A pop up box will tell you that the item was returned. Click OK on the prompt.
+
+4) If we select Patron on the above screen, after scanning the patron's barcode, reservations currently out to that patron are displayed. Highlight the reservations you want to return, and click Return.
+
+image::media/booking-return-2.png[]
+
+5) The screen will refresh to show any resources that remain out and the reservations that have been returned.
+
+image::media/booking-return-module-4.png[]
+
+[NOTE]
+Reservations can be returned from within patron records by selecting Other --> Booking --> Return Reservations
+
+Cancelling a Reservation
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+A reservation can be cancelled in a patron’s record or reservation creation screen.
+
+Cancel a reservation from the patron record
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+1) Retrieve the patron's record.
+
+2) Select Other --> Booking --> Create or Cancel Reservations.
+
+image::media/booking-create-1.png[]
+
+3) The existing reservations will appear at the bottom of the screen.
+
+image::media/booking-cancel-1.png[]
+
+4) Highlight the reservation that you want to cancel. Click Cancel Selected.
+
+image::media/booking-cancel-2.png[]
+
+[NOTE]
+Use Shift or Ctrl on keyboard and mouse click to select multiple reservations if needed.
+
+5) A pop-up window will confirm the cancellation. Click OK on the prompt.
+
+6) The screen will refresh, and the cancelled reservation(s) will disappear.
+
+image::media/booking-cancel-4.png[]
+
+Cancel a reservation on reservation creation screen
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+1) Access the reservation creation screen by selecting Booking --> Create Reservations.
+
+2) Select any Bookable Resource Type, then click Next.
+
+3) Scan or type in the patron barcode in Reserve to Patron box then hit Enter.
+
+4) Patron's existing reservations will display at the bottom of the screen.
+
+5) Select those that you want to cancel, then click Cancel Selected.
+
+
+
+
+
+
+
+
diff --git a/docs/circulation/circulating_items.txt b/docs/circulation/circulating_items.txt
index 51d653e..c41b1ac 100644
--- a/docs/circulation/circulating_items.txt
+++ b/docs/circulation/circulating_items.txt
@@ -1,327 +1,327 @@
-Circulating Items
------------------
-
-Check Out (F1)
-~~~~~~~~~~~~~~
-
-Regular Items
-^^^^^^^^^^^^^
-
-1) To check out an item press *F1*, click *Check Out* on the Circulation toolbar, or select *Circulation* -> *Check Out Items*.
-
-image::media/checkout_menu.png[]
-
-2) Scan or enter patron's barcode and click *Submit* if entering barcode manually. If scanning, number is submitted automatically.
-
-image::media/retrieve_patron.png[]
-
-3) Scan or enter item barcode manually, clicking *Submit* if manual.
-
-image::media/checkout_item_barcode.png[]
-
-4) Due date is now displayed.
-
-image::media/due_date_display.png[]
-
-5) When all items are scanned, hit the *F1* key or click the *Check Out* button on the Circulation toolbar to generate slip receipt or to exit patron record if not printing slip receipts.
-
-Pre-cataloged Items
-^^^^^^^^^^^^^^^^^^^
-
-1) Go to patron's *Check Out* screen by clicking *Circulation* -> *Check Out Items*.
-
-2) Scan the item barcode.
-
-3) At prompt, click *Pre-Cataloged*.
-
-image::media/pre_cat_alert.png[]
-
-4) Enter required information and click *Check Out*.
-
-image::media/precat.png[]
-
-[TIP]
-On check-in, Evergreen will prompt staff to re-route the item to cataloging.
-
-Due Dates
-^^^^^^^^^
-
-Circulation periods are pre-set. When items are checked out, due dates are automatically calculated and inserted into circulation records if the *Specific Due Date* checkbox is not selected on the Check Out screen. The *Specific Due Date* checkbox allows you to set a different due date to override the pre-set loan period.
-
-Before you scan the item, select the *Specific Due Date* checkbox. Use the calendar widget to select a date. Or click in day, month or year, then use the up or down arrows to make the change or simply delete the data, then enter again. Time is used for hourly loan only. This date applies to all items until you change the date, de-select the *Specific Due Date* checkbox, or quit the patron record.
-
-image::media/specify_due_date1.png[]
-
-image::media/specify_due_date2.png[]
-
-Check In (F2)
-~~~~~~~~~~~~~
-
-Regular check in
-^^^^^^^^^^^^^^^^
-
-1) To check in an item, select *Circulation -> Check In Items*, click *Check In* on the Circulation toolbar, or press *F2*.
-
-image::media/check_in_menu.png[]
-
-2) Scan item barcode or enter manually and click *Submit*.
-
-image::media/checkin_barcode.png[]
-
-3) If there is an overdue fine associated with the checkin, an alert will appear at the top of the screen with a fine tally for the current checkin session. To immediately handle fine payment, click the alert to jump to the patron's bill record.
-
-image::media/overdue_checkin.png[]
-
-Backdated check in
-^^^^^^^^^^^^^^^^^^
-
-This is useful for clearing a book drop.
-
-1) To change effective check-in date, select *Circulation* -> *Check In Items*, or press *F2*. Use the calendar widget to choose the effective date.
-
-image::media/backdate_checkin.png[]
-
-2) The top green bar changes to red. The new effective date is now displayed in the header.
-
-image::media/backdate_red.png[]
-
-3) Move the cursor to the *Barcode* field. Scan the items. When finishing backdated check-in, change the *Effective Date* back to today's date.
-
-Backdate Post-Checkin
-^^^^^^^^^^^^^^^^^^^^^
-
-After an item has been checked in, you may use the Backdate Post-Checkin function to backdate the check-in date.
-
-1) Select the item on the Check In screen, click Actions for Selected Items -> Backdate Post-Checkin.
-
-image::media/backdate_post_checkin.png[]
-
-2) Use the calendar widget to select an effective check-in date. Click Apply. Overdue fines, if any, will be adjusted according to the new effective check-in date.
-
-image::media/backdate_post_date.png[]
-
-[TIP]
-Checkin Modifiers
-===================================================
-At the right bottom corner there is a *Checkin Modifiers* pop-up list. The options are:
-
-- Ignore Pre-cat Items: no prompt when checking in a pre-cat item. Item will be routed to Cataloging with Cataloging status.
-- Suppress Holds and Transit: item will not be used to fill holds or sent in transit. Item has Reshelving status.
-- Amnesty Mode/Forgive Fines: overdue fines will be voided if already created or not be inserted if not yet created (e.g. hourly loans).
-- Auto-Print Hold and Transit Slips: slips will be automatically printed without prompt for confirmation.
-
-These options may be selected simultaneously. The selected option is displayed in the header area.
-
-image::media/checkin_options.png[]
-
-====================================================
-
-Renewal and Editing the Item's Due Date
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Checked-out items can be renewed if your library's policy allows it. The new due date is calculated from the renewal date. Existing loans can also be extended to a specific date by editing the due date or renewing with a specific due date.
-
-Renewing via a Patron's Account
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-1) Retrieve the patron record and go to the *Items Out* screen.
-
-image::media/items_out_click.png[]
-
-2) Select the item you want to renew. *Click on Actions for Selected Items* -> *Renew*. If you want to renew all items in the account, click *Renew All* instead.
-
-image::media/renew_action.png[]
-
-3) If you want to specify the due date, click *Renew with Specific Due Date*. You will be prompted to select a due date. Once done, click *Apply*.
-
-image::media/renew_specific_date.png[]
-
-[TIP]
-Renewal can also be done on the *Item Status* screen. See the section called <<itemstatus,Item Status (F5)>> for more information.
-
-Renewing by Item Barcode
-^^^^^^^^^^^^^^^^^^^^^^^^
-1) To renew items by barcode, select *Circulation* -> *Renew Items* or press *CTRL-F2*.
-
-2) Scan or manually entire the item barcode.
-
-image::media/renew_item.png[]
-
-3) If you want to specify the due date, click *Specific Due Date* and select a new due date from the calendar.
-
-image::media/renew_item_calendar.png[]
-
-Editing Due Date
-^^^^^^^^^^^^^^^^
-
-1) Retrieve the patron record and go to the *Items Out* screen.
-
-2) Select the item you want to renew. Click on *Actions for Selected Items* -> *Edit Due Date*.
-
-image::media/edit_due_date_action.png[]
-
-3) Select a new due date in the pop-up window, then click *Apply*.
-
-[TIP]
-You can select multiple items by pressing down the CTRL key on your keyboard and clicking each items you want to edit.
-
-[NOTE]
-Editing a due date is not included in the renewal count.
-
-Marking Items Lost and Claimed Returned
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Lost Items
-^^^^^^^^^^
-1) To mark items Lost, retrieve patron record and click *Items Out*.
-
-2) Select the item. Click on *Actions for Selected Items* -> *Mark Lost (by Patron)*.
-
-image::media/mark_lost.png[]
-
-3) The lost item now displays in the *Lost/Claimed Returned/Long Overdue, Has Unpaid Billings* section of the patron record.
-
-image::media/lost_cr_section.png[]
-
-4) The lost item also adds to the count of *Lost* items in the patron summary on the left (or top) of the screen.
-
-image::media/patron_summary_checkouts.jpg[]
-
-[NOTE]
-Lost Item Billing
-========================
-- Marking an item Lost will automatically bill the patron the replacement cost of the item as recorded in the price field in the item record, and a processing fee as determined by your local policy. If the lost item has overdue charges, the overdue charges may be voided or retained based on local policy.
-- A lost-then-returned item will disappear from the Items Out screen only when all bills linked to this particular circulation have been resolved. Bills may include replacement charges, processing fees, and manual charges added to the existing bills.
-- The replacement fee and processing fee for lost-then-returned items may be voided if set by local policy. Overdue fines may be reinstated on lost-then-returned items if set by local policy.
-==========================
-
-Refunds for Lost Items
-^^^^^^^^^^^^^^^^^^^^^^^
-
-If an item is returned after a lost bill has been paid and the library's policy is to void the replacement fee for lost-then-returned items, there will be a negative balance in the bill. A refund needs to be made to close the bill and the circulation record. Once the outstanding amount has been refunded, the bill and circulation record will be closed and the item will disappear from the Items Out screen.
-
-If you need to balance a bill with a negative amount and close the linked lost circulation record without making a refund (removing the item from the *Lost, Claimed Returned, Long Overdue, Has Unpaid Bills* panel on the *Items Out* screen), you need to add two dummy bills to the existing bills. The first one can be of any amount (e.g. $0.01), while the second should be of the absolute value of the negative amount. Then you need to void the first dummy bill. The reason for using a dummy bill is that Evergreen will check and close the circulation record only when payment is applied or bills are voided.
-
-Claimed Returned Items
-^^^^^^^^^^^^^^^^^^^^^^^
-
-1) To mark an item Claimed Returned, retrieve the patron record and go to the *Items Out* screen.
-
-2) Select the item, then select *Actions for Selected Items* -> *Mark Claimed Returned* from the dropdown menu.
-
-image::media/mark_claims_returned.png[]
-
-3) Select a date and click *Apply*.
-
-image::media/claimed_date.png[]
-
-4) The Claimed Returned item now displays in the *Lost/Claimed Returned/Long Overdue, Has Unpaid Billings* section of the patron record.
-
-image::media/lost_cr_section.png[]
-
-5) The Claimed Returned item adds to the count of Check Outs that are Claimed Returned in the patron summary on the left (or top) of the screen. It also adds to the total *Claims-returned Count* (including those that are current Check Outs and those that have since been returned) that is displayed when editing the patron's record.
-
-image::media/patron_summary_checkouts.jpg[]
-
-[NOTE]
-More on Claimed Returned Items
-====================================
-- The date entered for a Claimed Returned item establishes the fine. If the date given has passed, bills will be adjusted accordingly.
-- When a Claimed Returned item is returned, if there is an outstanding bill associated with it, the item will not disappear from the *Items Out* screen. It will disappear when the outstanding bills are resolved.
-- When an item is marked Claimed Returned, the value in *Claims-returned Count* field in the patron record is automatically increased. Staff can manually adjust this count by editing the patron record.
-====================================
-
-In-house Use (F6)
-~~~~~~~~~~~~~~~~~
-1) To record in-house use, select *Circulation* -> *Record-In House Use*, click *Check Out* -> *Record In-House Use* on the circulation toolbar , or press *F6*.
-
-image::media/record_in_house_action.png[]
-
-2) To record in-house use for cataloged items, enter number of uses, scan barcode or type barcode and click *Submit*.
-
-image::media/in_house_use.png[]
-
-[NOTE]
-The statistics of in-house use are separated from circulation statistics. The in-house use count of cataloged items is not included in the items' total use count.
-
-[[itemstatus]]
-Item Status (F5)
-~~~~~~~~~~~~~~~~
-
-The Item Status screen is very useful. Many actions can be taken by either circulation staff or catalogers on this screen. Here we will cover some circulation-related functions, namely checking item status, viewing past circulations, inserting item alert messages, marking items missing or damaged, etc.
-
-Checking item status
-^^^^^^^^^^^^^^^^^^^^
-
-1) To check the status of an item, select *Search* -> *Search for copies by Barcode* or *Circulation* -> *Show Item Status by Barcode*; click the *Item Status button* on the circulation or cataloging toolbar; or press *F5*.
-
-image::media/item_status_menu.png[]
-
-2) Scan the barcode or type it and click *Submit*. The current status of the item is displayed with selected other fields. You can use the column picker to select more fields to view.
-
-image::media/item_status_barcode.png[]
-
-3) Click the *Alternate View* button, and the item summary and circulation history will be displayed.
-
-image::media/item_status_altview.png[]
-
-4) Click *List View* to go back.
-
-image::media/item_status_list_view.png[]
-
-[NOTE]
-If the item's status is "Available", the displayed due date refers to the previous circulation's due date.
-
-[TIP]
-Upload From File allows you to load multiple items saved in a file on your local computer. The file contains a list of the barcodes in text format. To ensure smooth uploading and further processing on the items, it is recommended that the list contains no more than 100 items.
-
-Viewing past circulations
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-1) To view past circulations, retrieve the item on the *Item Status* screen as described above.
-
-2) Select *Actions for Selected Items* -> *Show Last Few Circulations*.
-
-image::media/last_few_circs_action.png[]
-
-3) The item's recent circulation history is displayed.
-
-image::media/last_few_circs_display.png[]
-
-4) To retrieve the patron(s) of the last circulations, click the *Retrieve Last Patron* or the *Retrieve All These Patrons* button at the bottom of the above screen. Patron record(s) will be displayed in new tab(s).
-
-[TIP]
-The number of items that displays in the circulation history can be set in Local *Administration* -> *Library Settings Editor*.
-
-[NOTE]
-You can also retrieve the past circulations on the patron's Items Out screen and from the Check In screen.
-
-Marking items damaged or missing and other functions
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-1) To mark items damaged or missing, retrieve the item on the *Item Status* screen.
-
-2) Select the item. Click on *Actions for Selected Items* -> *Mark Item Damaged* or *Mark Item Missing*.
-
-image::media/mark_missing_damaged.png[]
-
-[NOTE}
-Depending on the library's policy, when marking an item damaged, bills (cost and/or processing fee) may be inserted into the last borrower's account.
-
-3) Following the above procedure, you can check in and renew items by using the *Check in Items* and *Renew Items* on the dropdown menu.
-
-Item alerts
-^^^^^^^^^^^
-
-The *Edit Item Attributes* function on the *Actions for Selected Items* dropdown list allows you to edit item records. Here, we will show you how to insert item alert messages by this function. See cataloging instructions for more information on item editing.
-1) Retrieve record on *Item Status* screen.
-
-2) Once item is displayed, highlight it and select *Actions for Selected Items* -> *Edit Item Attributes*.
-
-3) The item record is displayed in the *Copy Editor*.
-
-image::media/copy_edit_alert.png[]
-
-4) Click *Alert Message* in the *Miscellaneous* column. The background color of the box changes. Type in the message then click *Apply*.
-
-image::media/copy_alert_message.png[]
-
-5) Click *Modify Copies*, then confirm the action.
+Circulating Items
+-----------------
+
+Check Out (F1)
+~~~~~~~~~~~~~~
+
+Regular Items
+^^^^^^^^^^^^^
+
+1) To check out an item press *F1*, click *Check Out* on the Circulation toolbar, or select *Circulation* -> *Check Out Items*.
+
+image::media/checkout_menu.png[]
+
+2) Scan or enter patron's barcode and click *Submit* if entering barcode manually. If scanning, number is submitted automatically.
+
+image::media/retrieve_patron.png[]
+
+3) Scan or enter item barcode manually, clicking *Submit* if manual.
+
+image::media/checkout_item_barcode.png[]
+
+4) Due date is now displayed.
+
+image::media/due_date_display.png[]
+
+5) When all items are scanned, hit the *F1* key or click the *Check Out* button on the Circulation toolbar to generate slip receipt or to exit patron record if not printing slip receipts.
+
+Pre-cataloged Items
+^^^^^^^^^^^^^^^^^^^
+
+1) Go to patron's *Check Out* screen by clicking *Circulation* -> *Check Out Items*.
+
+2) Scan the item barcode.
+
+3) At prompt, click *Pre-Cataloged*.
+
+image::media/pre_cat_alert.png[]
+
+4) Enter required information and click *Check Out*.
+
+image::media/precat.png[]
+
+[TIP]
+On check-in, Evergreen will prompt staff to re-route the item to cataloging.
+
+Due Dates
+^^^^^^^^^
+
+Circulation periods are pre-set. When items are checked out, due dates are automatically calculated and inserted into circulation records if the *Specific Due Date* checkbox is not selected on the Check Out screen. The *Specific Due Date* checkbox allows you to set a different due date to override the pre-set loan period.
+
+Before you scan the item, select the *Specific Due Date* checkbox. Use the calendar widget to select a date. Or click in day, month or year, then use the up or down arrows to make the change or simply delete the data, then enter again. Time is used for hourly loan only. This date applies to all items until you change the date, de-select the *Specific Due Date* checkbox, or quit the patron record.
+
+image::media/specify_due_date1.png[]
+
+image::media/specify_due_date2.png[]
+
+Check In (F2)
+~~~~~~~~~~~~~
+
+Regular check in
+^^^^^^^^^^^^^^^^
+
+1) To check in an item, select *Circulation -> Check In Items*, click *Check In* on the Circulation toolbar, or press *F2*.
+
+image::media/check_in_menu.png[]
+
+2) Scan item barcode or enter manually and click *Submit*.
+
+image::media/checkin_barcode.png[]
+
+3) If there is an overdue fine associated with the checkin, an alert will appear at the top of the screen with a fine tally for the current checkin session. To immediately handle fine payment, click the alert to jump to the patron's bill record.
+
+image::media/overdue_checkin.png[]
+
+Backdated check in
+^^^^^^^^^^^^^^^^^^
+
+This is useful for clearing a book drop.
+
+1) To change effective check-in date, select *Circulation* -> *Check In Items*, or press *F2*. Use the calendar widget to choose the effective date.
+
+image::media/backdate_checkin.png[]
+
+2) The top green bar changes to red. The new effective date is now displayed in the header.
+
+image::media/backdate_red.png[]
+
+3) Move the cursor to the *Barcode* field. Scan the items. When finishing backdated check-in, change the *Effective Date* back to today's date.
+
+Backdate Post-Checkin
+^^^^^^^^^^^^^^^^^^^^^
+
+After an item has been checked in, you may use the Backdate Post-Checkin function to backdate the check-in date.
+
+1) Select the item on the Check In screen, click Actions for Selected Items -> Backdate Post-Checkin.
+
+image::media/backdate_post_checkin.png[]
+
+2) Use the calendar widget to select an effective check-in date. Click Apply. Overdue fines, if any, will be adjusted according to the new effective check-in date.
+
+image::media/backdate_post_date.png[]
+
+[TIP]
+Checkin Modifiers
+===================================================
+At the right bottom corner there is a *Checkin Modifiers* pop-up list. The options are:
+
+- Ignore Pre-cat Items: no prompt when checking in a pre-cat item. Item will be routed to Cataloging with Cataloging status.
+- Suppress Holds and Transit: item will not be used to fill holds or sent in transit. Item has Reshelving status.
+- Amnesty Mode/Forgive Fines: overdue fines will be voided if already created or not be inserted if not yet created (e.g. hourly loans).
+- Auto-Print Hold and Transit Slips: slips will be automatically printed without prompt for confirmation.
+
+These options may be selected simultaneously. The selected option is displayed in the header area.
+
+image::media/checkin_options.png[]
+
+====================================================
+
+Renewal and Editing the Item's Due Date
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Checked-out items can be renewed if your library's policy allows it. The new due date is calculated from the renewal date. Existing loans can also be extended to a specific date by editing the due date or renewing with a specific due date.
+
+Renewing via a Patron's Account
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+1) Retrieve the patron record and go to the *Items Out* screen.
+
+image::media/items_out_click.png[]
+
+2) Select the item you want to renew. *Click on Actions for Selected Items* -> *Renew*. If you want to renew all items in the account, click *Renew All* instead.
+
+image::media/renew_action.png[]
+
+3) If you want to specify the due date, click *Renew with Specific Due Date*. You will be prompted to select a due date. Once done, click *Apply*.
+
+image::media/renew_specific_date.png[]
+
+[TIP]
+Renewal can also be done on the *Item Status* screen. See the section called <<itemstatus,Item Status (F5)>> for more information.
+
+Renewing by Item Barcode
+^^^^^^^^^^^^^^^^^^^^^^^^
+1) To renew items by barcode, select *Circulation* -> *Renew Items* or press *CTRL-F2*.
+
+2) Scan or manually entire the item barcode.
+
+image::media/renew_item.png[]
+
+3) If you want to specify the due date, click *Specific Due Date* and select a new due date from the calendar.
+
+image::media/renew_item_calendar.png[]
+
+Editing Due Date
+^^^^^^^^^^^^^^^^
+
+1) Retrieve the patron record and go to the *Items Out* screen.
+
+2) Select the item you want to renew. Click on *Actions for Selected Items* -> *Edit Due Date*.
+
+image::media/edit_due_date_action.png[]
+
+3) Select a new due date in the pop-up window, then click *Apply*.
+
+[TIP]
+You can select multiple items by pressing down the CTRL key on your keyboard and clicking each items you want to edit.
+
+[NOTE]
+Editing a due date is not included in the renewal count.
+
+Marking Items Lost and Claimed Returned
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Lost Items
+^^^^^^^^^^
+1) To mark items Lost, retrieve patron record and click *Items Out*.
+
+2) Select the item. Click on *Actions for Selected Items* -> *Mark Lost (by Patron)*.
+
+image::media/mark_lost.png[]
+
+3) The lost item now displays in the *Lost/Claimed Returned/Long Overdue, Has Unpaid Billings* section of the patron record.
+
+image::media/lost_cr_section.png[]
+
+4) The lost item also adds to the count of *Lost* items in the patron summary on the left (or top) of the screen.
+
+image::media/patron_summary_checkouts.jpg[]
+
+[NOTE]
+Lost Item Billing
+========================
+- Marking an item Lost will automatically bill the patron the replacement cost of the item as recorded in the price field in the item record, and a processing fee as determined by your local policy. If the lost item has overdue charges, the overdue charges may be voided or retained based on local policy.
+- A lost-then-returned item will disappear from the Items Out screen only when all bills linked to this particular circulation have been resolved. Bills may include replacement charges, processing fees, and manual charges added to the existing bills.
+- The replacement fee and processing fee for lost-then-returned items may be voided if set by local policy. Overdue fines may be reinstated on lost-then-returned items if set by local policy.
+==========================
+
+Refunds for Lost Items
+^^^^^^^^^^^^^^^^^^^^^^^
+
+If an item is returned after a lost bill has been paid and the library's policy is to void the replacement fee for lost-then-returned items, there will be a negative balance in the bill. A refund needs to be made to close the bill and the circulation record. Once the outstanding amount has been refunded, the bill and circulation record will be closed and the item will disappear from the Items Out screen.
+
+If you need to balance a bill with a negative amount and close the linked lost circulation record without making a refund (removing the item from the *Lost, Claimed Returned, Long Overdue, Has Unpaid Bills* panel on the *Items Out* screen), you need to add two dummy bills to the existing bills. The first one can be of any amount (e.g. $0.01), while the second should be of the absolute value of the negative amount. Then you need to void the first dummy bill. The reason for using a dummy bill is that Evergreen will check and close the circulation record only when payment is applied or bills are voided.
+
+Claimed Returned Items
+^^^^^^^^^^^^^^^^^^^^^^^
+
+1) To mark an item Claimed Returned, retrieve the patron record and go to the *Items Out* screen.
+
+2) Select the item, then select *Actions for Selected Items* -> *Mark Claimed Returned* from the dropdown menu.
+
+image::media/mark_claims_returned.png[]
+
+3) Select a date and click *Apply*.
+
+image::media/claimed_date.png[]
+
+4) The Claimed Returned item now displays in the *Lost/Claimed Returned/Long Overdue, Has Unpaid Billings* section of the patron record.
+
+image::media/lost_cr_section.png[]
+
+5) The Claimed Returned item adds to the count of Check Outs that are Claimed Returned in the patron summary on the left (or top) of the screen. It also adds to the total *Claims-returned Count* (including those that are current Check Outs and those that have since been returned) that is displayed when editing the patron's record.
+
+image::media/patron_summary_checkouts.jpg[]
+
+[NOTE]
+More on Claimed Returned Items
+====================================
+- The date entered for a Claimed Returned item establishes the fine. If the date given has passed, bills will be adjusted accordingly.
+- When a Claimed Returned item is returned, if there is an outstanding bill associated with it, the item will not disappear from the *Items Out* screen. It will disappear when the outstanding bills are resolved.
+- When an item is marked Claimed Returned, the value in *Claims-returned Count* field in the patron record is automatically increased. Staff can manually adjust this count by editing the patron record.
+====================================
+
+In-house Use (F6)
+~~~~~~~~~~~~~~~~~
+1) To record in-house use, select *Circulation* -> *Record-In House Use*, click *Check Out* -> *Record In-House Use* on the circulation toolbar , or press *F6*.
+
+image::media/record_in_house_action.png[]
+
+2) To record in-house use for cataloged items, enter number of uses, scan barcode or type barcode and click *Submit*.
+
+image::media/in_house_use.png[]
+
+[NOTE]
+The statistics of in-house use are separated from circulation statistics. The in-house use count of cataloged items is not included in the items' total use count.
+
+[[itemstatus]]
+Item Status (F5)
+~~~~~~~~~~~~~~~~
+
+The Item Status screen is very useful. Many actions can be taken by either circulation staff or catalogers on this screen. Here we will cover some circulation-related functions, namely checking item status, viewing past circulations, inserting item alert messages, marking items missing or damaged, etc.
+
+Checking item status
+^^^^^^^^^^^^^^^^^^^^
+
+1) To check the status of an item, select *Search* -> *Search for copies by Barcode* or *Circulation* -> *Show Item Status by Barcode*; click the *Item Status button* on the circulation or cataloging toolbar; or press *F5*.
+
+image::media/item_status_menu.png[]
+
+2) Scan the barcode or type it and click *Submit*. The current status of the item is displayed with selected other fields. You can use the column picker to select more fields to view.
+
+image::media/item_status_barcode.png[]
+
+3) Click the *Alternate View* button, and the item summary and circulation history will be displayed.
+
+image::media/item_status_altview.png[]
+
+4) Click *List View* to go back.
+
+image::media/item_status_list_view.png[]
+
+[NOTE]
+If the item's status is "Available", the displayed due date refers to the previous circulation's due date.
+
+[TIP]
+Upload From File allows you to load multiple items saved in a file on your local computer. The file contains a list of the barcodes in text format. To ensure smooth uploading and further processing on the items, it is recommended that the list contains no more than 100 items.
+
+Viewing past circulations
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+1) To view past circulations, retrieve the item on the *Item Status* screen as described above.
+
+2) Select *Actions for Selected Items* -> *Show Last Few Circulations*.
+
+image::media/last_few_circs_action.png[]
+
+3) The item's recent circulation history is displayed.
+
+image::media/last_few_circs_display.png[]
+
+4) To retrieve the patron(s) of the last circulations, click the *Retrieve Last Patron* or the *Retrieve All These Patrons* button at the bottom of the above screen. Patron record(s) will be displayed in new tab(s).
+
+[TIP]
+The number of items that displays in the circulation history can be set in Local *Administration* -> *Library Settings Editor*.
+
+[NOTE]
+You can also retrieve the past circulations on the patron's Items Out screen and from the Check In screen.
+
+Marking items damaged or missing and other functions
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+1) To mark items damaged or missing, retrieve the item on the *Item Status* screen.
+
+2) Select the item. Click on *Actions for Selected Items* -> *Mark Item Damaged* or *Mark Item Missing*.
+
+image::media/mark_missing_damaged.png[]
+
+[NOTE}
+Depending on the library's policy, when marking an item damaged, bills (cost and/or processing fee) may be inserted into the last borrower's account.
+
+3) Following the above procedure, you can check in and renew items by using the *Check in Items* and *Renew Items* on the dropdown menu.
+
+Item alerts
+^^^^^^^^^^^
+
+The *Edit Item Attributes* function on the *Actions for Selected Items* dropdown list allows you to edit item records. Here, we will show you how to insert item alert messages by this function. See cataloging instructions for more information on item editing.
+1) Retrieve record on *Item Status* screen.
+
+2) Once item is displayed, highlight it and select *Actions for Selected Items* -> *Edit Item Attributes*.
+
+3) The item record is displayed in the *Copy Editor*.
+
+image::media/copy_edit_alert.png[]
+
+4) Click *Alert Message* in the *Miscellaneous* column. The background color of the box changes. Type in the message then click *Apply*.
+
+image::media/copy_alert_message.png[]
+
+5) Click *Modify Copies*, then confirm the action.
diff --git a/docs/installation/edi_setup.txt b/docs/installation/edi_setup.txt
index ececa15..61f2b91 100644
--- a/docs/installation/edi_setup.txt
+++ b/docs/installation/edi_setup.txt
@@ -1,212 +1,212 @@
-Setting Up EDI Acquisitions
----------------------------
-
-Introduction
-~~~~~~~~~~~~
-
-Electronic Data Interchange (EDI) is used to exchange information between
-participating vendors and Evergreen. This chapter contains technical
-information for installation and configuration of the components necessary
-to run EDI Acquisitions for Evergreen.
-
-Installation
-~~~~~~~~~~~~
-
-Install EDI Translator
-^^^^^^^^^^^^^^^^^^^^^^
-
-The EDI Translator is used to convert data into EDI format. It runs
-on localhost and listens on port 9191 by default. This is controlled via
-the edi_webrick.cnf file located in the edi_translator directory. It should
-not be necessary to edit this configuration if you install EDI Translator
-on the same server used for running Action/Triggers events.
-
-[NOTE]
-If you are running Evergreen with a multi-server configuration, make sure
-to install EDI Translator on the same server used for Action/Trigger event
-generation.
-
-.Steps for Installing
-
-1. As the *opensrf* user, copy the EDI Translator code found in
- Open-ILS/src/edi_translator to somewhere accessible
- (for example, /openils/var/edi):
-+
-[source, bash]
---------------------------------------------------
-cp -r Open-ILS/src/edi_translator /openils/var/edi
---------------------------------------------------
-2. Navigate to where you have saved the code to begin next step:
-+
-[source, bash]
--------------------
-cd /openils/var/edi
--------------------
-3. Next, as the *root* user (or a user with sudo rights), install the
- dependencies, via "install.sh". This will perform some apt-get routines
- to install the code needed for the EDI translator to function.
- (Note: subversion must be installed first)
-+
-[source, bash]
------------
-./install.sh
------------
-4. Now, we're ready to start "edi_webrick.bash" which is the script that calls
- the "Ruby" code to translate EDI. This script needs to be started in
- order for EDI to function so please take appropriate measures to ensure this
- starts following reboots/upgrades/etc. As the *opensrf* user:
-+
-[source, bash]
------------------
-./edi_webrick.bash
------------------
-5. You can check to see if EDI translator is running.
- * Using the command "ps aux | grep edi" should show you something similar
- if the script is running properly:
-+
-[source, bash]
-------------------------------------------------------------------------------------------
-root 30349 0.8 0.1 52620 10824 pts/0 S 13:04 0:00 ruby ./edi_webrick.rb
-------------------------------------------------------------------------------------------
- * To shutdown EDI Translator you can use something like pkill (assuming
- no other ruby processes are running on that server):
-+
-[source, bash]
------------------------
-kill -INT $(pgrep ruby)
------------------------
-
-Install EDI Scripts
-^^^^^^^^^^^^^^^^^^^
-
-The EDI scripts are "edi_pusher.pl" and "edi_fetcher.pl" and are used to
-"push" and "fetch" EDI messages for configured EDI accounts.
-
-1. As the *opensrf* user, copy edi_pusher.pl and edi_fetcher.pl from
- Open-ILS/src/support-scripts into /openils/bin:
-+
-[source, bash]
---------------------------------------------------
-cp Open-ILS/src/support-scripts/edi_pusher.pl /openils/bin
-cp Open-ILS/src/support-scripts/edi_fetcher.pl /openils/bin
---------------------------------------------------
-2. Setup the edi_pusher.pl and edi_fetcher.pl scripts to run as cron jobs
- in order to regularly push and receive EDI messages.
- * Add to the opensrf user's crontab the following entries:
-+
-[source, bash]
------------------------------------------------------------------------
-10 * * * * cd /openils/bin && /usr/bin/perl ./edi_pusher.pl > /dev/null
-0 1 * * * cd /openils/bin && /usr/bin/perl ./edi_fetcher.pl > /dev/null
------------------------------------------------------------------------
- * The example for edi_pusher.pl sets the script to run at
- 10 minutes past the hour, every hour.
- * The example for edi_fetcher.pl sets the script to run at
- 1 AM every night.
-
-[NOTE]
-You may choose to run the EDI scripts more or less frequently based on the
-necessary response times from your vendors.
-
-Configuration
-~~~~~~~~~~~~~
-
-Configuring Providers
-^^^^^^^^^^^^^^^^^^^^^
-
-Look in Admin > Server Administration > Acquisitions > Providers
-
-[options="header"]
-|======================================================================================
-|Column |Description/Notes
-|Provider Name |A unique name to identify the provider
-|Code |A unique code to identify the provider
-|Owner |The org unit who will "own" the provider.
-|Currency |The currency format the provider accepts
-|Active |Whether or not the Provider is "active" for use
-|Default Claim Policy|??
-|EDI Default |The default "EDI Account" to use (see EDI Accounts Configuration)
-|Email |The email address for the provider
-|Fax Phone |A fax number for the provider
-|Holdings Tag |The holdings tag to be utilized (usually 852, for Evergreen)
-|Phone |A phone number for the provider
-|Prepayment Required |Whether or not prepayment is required
-|SAN |The vendor provided, org unit specific SAN code
-|URL |The vendor website
-|======================================================================================
-
-Configuring EDI Accounts
-^^^^^^^^^^^^^^^^^^^^^^^^
-
-Look in Admin > Server Administration > Acquisitions > EDI Accounts
-
-[options="header"]
-|===============================================================================================================
-|Column |Description/Notes
-|Label |A unique name to identify the provider
-|Host |FTP/SFTP/SSH hostname - vendor assigned
-|Username |FTP/SFTP/SSH username - vendor assigned
-|Password |FTP/SFTP/SSH password - vendor assigned
-|Account |Vendor assigned account number associated with your organization
-|Owner |The organizational unit who owns the EDI account
-|Last Activity |The date of last activity for the account
-|Provider |This is a link to one of the "codes" in the "Providers" interface
-|Path |The path on the vendor's server where Evergreen will send it's outgoing .epo files
-|Incoming Directory |The path on the vendor's server where "incoming" .epo files are stored
-|Vendor Account Number|Vendor assigned account number.
-|Vendor Assigned Code |Usually a sub-account designation. Can be used with or without the Vendor Account Number.
-|===============================================================================================================
-
-Configuring Organizational Unit SAN code
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Look in Admin > Server Settings > Organizational Units
-
-This interface allows a library to configure their SAN, alongside
-their address, phone, etc.
-
-Troubleshooting
-~~~~~~~~~~~~~~~
-
-PO JEDI Template Issues
-^^^^^^^^^^^^^^^^^^^^^^^
-
-Some libraries may run into issues with the action/trigger (PO JEDI).
-The template has to be modified to handle different vendor codes that
-may be used. For instance, if you use "ingra" instead of INGRAM this
-may cause a problem because they are hardcoded in the template. The
-following is an example of one modification that seems to work.
-
-.Original template has:
-
-[source, bash]
-----------------------------------------------------------------------------------------------------------------------------------------------
-"buyer":[
- [% IF target.provider.edi_default.vendcode && (target.provider.code == 'BT' || target.provider.name.match('(?i)^BAKER & TAYLOR')) -%]
- {"id-qualifier": 91, "id":"[% target.ordering_agency.mailing_address.san _ ' ' _ target.provider.edi_default.vendcode %]"}
- [%- ELSIF target.provider.edi_default.vendcode && target.provider.code == 'INGRAM' -%]
- {"id":"[% target.ordering_agency.mailing_address.san %]"},
- {"id-qualifier": 91, "id":"[% target.provider.edi_default.vendcode %]"}
- [%- ELSE -%]
- {"id":"[% target.ordering_agency.mailing_address.san %]"}
- [%- END -%]
-],
-----------------------------------------------------------------------------------------------------------------------------------------------
-
-.Modified template has the following where it matches on provider SAN instead of code:
-
-[source, bash]
-------------------------------------------------------------------------------------------------------------------------------------------
-"buyer":[
- [% IF target.provider.edi_default.vendcode && (target.provider.san == '1556150') -%]
- {"id-qualifier": 91, "id":"[% target.ordering_agency.mailing_address.san _ ' ' _ target.provider.edi_default.vendcode %]"}
- {"id-qualifier": 91, "id":"[% target.ordering_agency.mailing_address.san _ ' ' _ target.provider.edi_default.vendcode %]"}
- [%- ELSIF target.provider.edi_default.vendcode && (target.provider.san == '1697978') -%]
- {"id":"[% target.ordering_agency.mailing_address.san %]"},
- {"id-qualifier": 91, "id":"[% target.provider.edi_default.vendcode %]"}
- [%- ELSE -%]
- {"id":"[% target.ordering_agency.mailing_address.san %]"}
- [%- END -%]
-],
-------------------------------------------------------------------------------------------------------------------------------------------
-
+Setting Up EDI Acquisitions
+---------------------------
+
+Introduction
+~~~~~~~~~~~~
+
+Electronic Data Interchange (EDI) is used to exchange information between
+participating vendors and Evergreen. This chapter contains technical
+information for installation and configuration of the components necessary
+to run EDI Acquisitions for Evergreen.
+
+Installation
+~~~~~~~~~~~~
+
+Install EDI Translator
+^^^^^^^^^^^^^^^^^^^^^^
+
+The EDI Translator is used to convert data into EDI format. It runs
+on localhost and listens on port 9191 by default. This is controlled via
+the edi_webrick.cnf file located in the edi_translator directory. It should
+not be necessary to edit this configuration if you install EDI Translator
+on the same server used for running Action/Triggers events.
+
+[NOTE]
+If you are running Evergreen with a multi-server configuration, make sure
+to install EDI Translator on the same server used for Action/Trigger event
+generation.
+
+.Steps for Installing
+
+1. As the *opensrf* user, copy the EDI Translator code found in
+ Open-ILS/src/edi_translator to somewhere accessible
+ (for example, /openils/var/edi):
++
+[source, bash]
+--------------------------------------------------
+cp -r Open-ILS/src/edi_translator /openils/var/edi
+--------------------------------------------------
+2. Navigate to where you have saved the code to begin next step:
++
+[source, bash]
+-------------------
+cd /openils/var/edi
+-------------------
+3. Next, as the *root* user (or a user with sudo rights), install the
+ dependencies, via "install.sh". This will perform some apt-get routines
+ to install the code needed for the EDI translator to function.
+ (Note: subversion must be installed first)
++
+[source, bash]
+-----------
+./install.sh
+-----------
+4. Now, we're ready to start "edi_webrick.bash" which is the script that calls
+ the "Ruby" code to translate EDI. This script needs to be started in
+ order for EDI to function so please take appropriate measures to ensure this
+ starts following reboots/upgrades/etc. As the *opensrf* user:
++
+[source, bash]
+-----------------
+./edi_webrick.bash
+-----------------
+5. You can check to see if EDI translator is running.
+ * Using the command "ps aux | grep edi" should show you something similar
+ if the script is running properly:
++
+[source, bash]
+------------------------------------------------------------------------------------------
+root 30349 0.8 0.1 52620 10824 pts/0 S 13:04 0:00 ruby ./edi_webrick.rb
+------------------------------------------------------------------------------------------
+ * To shutdown EDI Translator you can use something like pkill (assuming
+ no other ruby processes are running on that server):
++
+[source, bash]
+-----------------------
+kill -INT $(pgrep ruby)
+-----------------------
+
+Install EDI Scripts
+^^^^^^^^^^^^^^^^^^^
+
+The EDI scripts are "edi_pusher.pl" and "edi_fetcher.pl" and are used to
+"push" and "fetch" EDI messages for configured EDI accounts.
+
+1. As the *opensrf* user, copy edi_pusher.pl and edi_fetcher.pl from
+ Open-ILS/src/support-scripts into /openils/bin:
++
+[source, bash]
+--------------------------------------------------
+cp Open-ILS/src/support-scripts/edi_pusher.pl /openils/bin
+cp Open-ILS/src/support-scripts/edi_fetcher.pl /openils/bin
+--------------------------------------------------
+2. Setup the edi_pusher.pl and edi_fetcher.pl scripts to run as cron jobs
+ in order to regularly push and receive EDI messages.
+ * Add to the opensrf user's crontab the following entries:
++
+[source, bash]
+-----------------------------------------------------------------------
+10 * * * * cd /openils/bin && /usr/bin/perl ./edi_pusher.pl > /dev/null
+0 1 * * * cd /openils/bin && /usr/bin/perl ./edi_fetcher.pl > /dev/null
+-----------------------------------------------------------------------
+ * The example for edi_pusher.pl sets the script to run at
+ 10 minutes past the hour, every hour.
+ * The example for edi_fetcher.pl sets the script to run at
+ 1 AM every night.
+
+[NOTE]
+You may choose to run the EDI scripts more or less frequently based on the
+necessary response times from your vendors.
+
+Configuration
+~~~~~~~~~~~~~
+
+Configuring Providers
+^^^^^^^^^^^^^^^^^^^^^
+
+Look in Admin > Server Administration > Acquisitions > Providers
+
+[options="header"]
+|======================================================================================
+|Column |Description/Notes
+|Provider Name |A unique name to identify the provider
+|Code |A unique code to identify the provider
+|Owner |The org unit who will "own" the provider.
+|Currency |The currency format the provider accepts
+|Active |Whether or not the Provider is "active" for use
+|Default Claim Policy|??
+|EDI Default |The default "EDI Account" to use (see EDI Accounts Configuration)
+|Email |The email address for the provider
+|Fax Phone |A fax number for the provider
+|Holdings Tag |The holdings tag to be utilized (usually 852, for Evergreen)
+|Phone |A phone number for the provider
+|Prepayment Required |Whether or not prepayment is required
+|SAN |The vendor provided, org unit specific SAN code
+|URL |The vendor website
+|======================================================================================
+
+Configuring EDI Accounts
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+Look in Admin > Server Administration > Acquisitions > EDI Accounts
+
+[options="header"]
+|===============================================================================================================
+|Column |Description/Notes
+|Label |A unique name to identify the provider
+|Host |FTP/SFTP/SSH hostname - vendor assigned
+|Username |FTP/SFTP/SSH username - vendor assigned
+|Password |FTP/SFTP/SSH password - vendor assigned
+|Account |Vendor assigned account number associated with your organization
+|Owner |The organizational unit who owns the EDI account
+|Last Activity |The date of last activity for the account
+|Provider |This is a link to one of the "codes" in the "Providers" interface
+|Path |The path on the vendor's server where Evergreen will send it's outgoing .epo files
+|Incoming Directory |The path on the vendor's server where "incoming" .epo files are stored
+|Vendor Account Number|Vendor assigned account number.
+|Vendor Assigned Code |Usually a sub-account designation. Can be used with or without the Vendor Account Number.
+|===============================================================================================================
+
+Configuring Organizational Unit SAN code
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Look in Admin > Server Settings > Organizational Units
+
+This interface allows a library to configure their SAN, alongside
+their address, phone, etc.
+
+Troubleshooting
+~~~~~~~~~~~~~~~
+
+PO JEDI Template Issues
+^^^^^^^^^^^^^^^^^^^^^^^
+
+Some libraries may run into issues with the action/trigger (PO JEDI).
+The template has to be modified to handle different vendor codes that
+may be used. For instance, if you use "ingra" instead of INGRAM this
+may cause a problem because they are hardcoded in the template. The
+following is an example of one modification that seems to work.
+
+.Original template has:
+
+[source, bash]
+----------------------------------------------------------------------------------------------------------------------------------------------
+"buyer":[
+ [% IF target.provider.edi_default.vendcode && (target.provider.code == 'BT' || target.provider.name.match('(?i)^BAKER & TAYLOR')) -%]
+ {"id-qualifier": 91, "id":"[% target.ordering_agency.mailing_address.san _ ' ' _ target.provider.edi_default.vendcode %]"}
+ [%- ELSIF target.provider.edi_default.vendcode && target.provider.code == 'INGRAM' -%]
+ {"id":"[% target.ordering_agency.mailing_address.san %]"},
+ {"id-qualifier": 91, "id":"[% target.provider.edi_default.vendcode %]"}
+ [%- ELSE -%]
+ {"id":"[% target.ordering_agency.mailing_address.san %]"}
+ [%- END -%]
+],
+----------------------------------------------------------------------------------------------------------------------------------------------
+
+.Modified template has the following where it matches on provider SAN instead of code:
+
+[source, bash]
+------------------------------------------------------------------------------------------------------------------------------------------
+"buyer":[
+ [% IF target.provider.edi_default.vendcode && (target.provider.san == '1556150') -%]
+ {"id-qualifier": 91, "id":"[% target.ordering_agency.mailing_address.san _ ' ' _ target.provider.edi_default.vendcode %]"}
+ {"id-qualifier": 91, "id":"[% target.ordering_agency.mailing_address.san _ ' ' _ target.provider.edi_default.vendcode %]"}
+ [%- ELSIF target.provider.edi_default.vendcode && (target.provider.san == '1697978') -%]
+ {"id":"[% target.ordering_agency.mailing_address.san %]"},
+ {"id-qualifier": 91, "id":"[% target.provider.edi_default.vendcode %]"}
+ [%- ELSE -%]
+ {"id":"[% target.ordering_agency.mailing_address.san %]"}
+ [%- END -%]
+],
+------------------------------------------------------------------------------------------------------------------------------------------
+
diff --git a/docs/opac/my_lists.txt b/docs/opac/my_lists.txt
index c6b848e..0e018e3 100644
--- a/docs/opac/my_lists.txt
+++ b/docs/opac/my_lists.txt
@@ -1,63 +1,63 @@
-My Lists 2.2
-------------
-
-The *My Lists* feature replaces the bookbag feature that was available in versions proior to 2.2. The *My Lists* feature is a part of the Template Toolkit OPAC that is available in version 2.2. This feature enables you to create temporary and permanent lists; create and edit notes for items in lists; place holds on items in lists; and share lists via RSS feeds and CSV files.
-
-
-*Create New Lists*
-
-1) Log in to your account in the OPAC.
-
-2) Search for titles.
-
-3) Choose a title to add to your list. Click *Add to My List*.
-
-image::media/My_Lists1.jpg[My_Lists1]
-
-4) Scroll up to the gray row on top of the *Search Results*. Click *View My List*
-
-5) Items are added to a temporary list. Your temporary list appears at the bottom of the screen.
-
-6) The *Actions for these items* menu on the right side of the screen demonstrates the actions that you can apply to this list. You can place holds on items in your temporary list; remove items from the list; or move selected items to a permanent list.
-
-To place a hold or remove items from the list, check the box adjacent to the title of the item, and select the desired function.
-
-To move selected items into an existing list, check the box adjacent to the title, and highlight the list in which you will store the item.
-
-image::media/My_Lists3.jpg[My_Lists3]
-
-7) If you do not want to place the item into an existing list, you can create a new list to contain the item. Enter the name of the new list, and, if desired, enter a description.
-
-image::media/My_Lists4.jpg[My_Lists4]
-
-8) Click *Submit*.
-
-9) The new list appears beneath the temporary list.
-
-10) Select the title(s) of the items that you want to add to the list, and click *Actions for these items*. Select the permanent list that you created from the drop down menu.
-
-image::media/My_Lists5.jpg[My_Lists5]
-
-11) Click *Go*.
-
-12) Your existing lists appear. Click on a list to view the items in the list. You can sort the items in the permanent list. You can also add, edit, and remove notes.
-
-13) Click *Edit* to add or edit a note.
-
-14). Enter desired notes, and click *Save Notes*.
-
-image::media/My_Lists6.jpg[My_Lists6]
-
-15) You can keep your list private, or you can share it. To share your list, click *Share*, and click the orange RSS icon to share through an RSS reader. You can also click *HTML View* to share your list as an HTML link.
-
-You can also download your list into a CSV file by clicking *Download CSV*.
-
-image::media/My_Lists7.jpg[My_Lists7]
-
-
-16) When you no longer need a list, click *Delete List*.
-
-
-
-
-
+My Lists 2.2
+------------
+
+The *My Lists* feature replaces the bookbag feature that was available in versions proior to 2.2. The *My Lists* feature is a part of the Template Toolkit OPAC that is available in version 2.2. This feature enables you to create temporary and permanent lists; create and edit notes for items in lists; place holds on items in lists; and share lists via RSS feeds and CSV files.
+
+
+*Create New Lists*
+
+1) Log in to your account in the OPAC.
+
+2) Search for titles.
+
+3) Choose a title to add to your list. Click *Add to My List*.
+
+image::media/My_Lists1.jpg[My_Lists1]
+
+4) Scroll up to the gray row on top of the *Search Results*. Click *View My List*
+
+5) Items are added to a temporary list. Your temporary list appears at the bottom of the screen.
+
+6) The *Actions for these items* menu on the right side of the screen demonstrates the actions that you can apply to this list. You can place holds on items in your temporary list; remove items from the list; or move selected items to a permanent list.
+
+To place a hold or remove items from the list, check the box adjacent to the title of the item, and select the desired function.
+
+To move selected items into an existing list, check the box adjacent to the title, and highlight the list in which you will store the item.
+
+image::media/My_Lists3.jpg[My_Lists3]
+
+7) If you do not want to place the item into an existing list, you can create a new list to contain the item. Enter the name of the new list, and, if desired, enter a description.
+
+image::media/My_Lists4.jpg[My_Lists4]
+
+8) Click *Submit*.
+
+9) The new list appears beneath the temporary list.
+
+10) Select the title(s) of the items that you want to add to the list, and click *Actions for these items*. Select the permanent list that you created from the drop down menu.
+
+image::media/My_Lists5.jpg[My_Lists5]
+
+11) Click *Go*.
+
+12) Your existing lists appear. Click on a list to view the items in the list. You can sort the items in the permanent list. You can also add, edit, and remove notes.
+
+13) Click *Edit* to add or edit a note.
+
+14). Enter desired notes, and click *Save Notes*.
+
+image::media/My_Lists6.jpg[My_Lists6]
+
+15) You can keep your list private, or you can share it. To share your list, click *Share*, and click the orange RSS icon to share through an RSS reader. You can also click *HTML View* to share your list as an HTML link.
+
+You can also download your list into a CSV file by clicking *Download CSV*.
+
+image::media/My_Lists7.jpg[My_Lists7]
+
+
+16) When you no longer need a list, click *Delete List*.
+
+
+
+
+
diff --git a/docs/root.txt b/docs/root.txt
index 5c03084..a60641b 100644
--- a/docs/root.txt
+++ b/docs/root.txt
@@ -1,320 +1,320 @@
-Evergreen Documentation
-=======================
-Documentation Interest Group
-:doctype: book
-:toc:
-:numbered:
-
-Introduction
-============
-
-About This Documentation
-------------------------
-
-This guide was produced by the Evergreen Documentation Interest Group (DIG),
-consisting of numerous volunteers from many different organizations. The DIG
-has drawn together, edited, and supplemented pre-existing documentation
-contributed by libraries and consortia running Evergreen that were kind enough
-to release their documentation into the creative commons. Please see the
-<<attributions,Attributions>> section for a full list of authors and
-contributing organizations. Just like the software it describes, this guide is
-a work in progress, continually revised to meet the needs of its users, so if
-you find errors or omissions, please let us know, by contacting the DIG
-facilitators at docs at evergreen-ils.org.
-
-This guide to Evergreen is intended to meet the needs of front-line library
-staff, catalogers, library administrators, system administrators, and software
-developers. It is organized into Parts, Chapters, and Sections addressing key
-aspects of the software, beginning with the topics of broadest interest to the
-largest groups of users and progressing to some of the more specialized and
-technical topics of interest to smaller numbers of users.
-
-Copies of this guide can be accessed in PDF and HTML formats from http://docs.evergreen-ils.org/.
-
-About Evergreen
----------------
-
-Evergreen is an open source library automation software designed to meet the
-needs of the very smallest to the very largest libraries and consortia. Through
-its staff interface, it facilitates the management, cataloging, and circulation
-of library materials, and through its online public access interface it helps
-patrons find those materials.
-
-The Evergreen software is freely licensed under the GNU General Public License,
-meaning that it is free to download, use, view, modify, and share. It has an
-active development and user community, as well as several companies offering
-migration, support, hosting, and development services.
-
-The community’s development requirements state that Evergreen must be:
-
-* Stable, even under extreme load.
-* Robust, and capable of handling a high volume of transactions and simultaneous users.
-* Flexible, to accommodate the varied needs of libraries.
-* Secure, to protect our patrons’ privacy and data.
-* User-friendly, to facilitate patron and staff use of the system.
-
-Evergreen, which first launched in 2006 now powers over 544 libraries of every
-type – public, academic, special, school, and even tribal and home libraries –
-in over a dozen countries worldwide.
-
-// Push titles down one level.
-:leveloffset: 1
-
-include::RELEASE_NOTES_2_2.txt[]
-
-// Return to normal title levels.
-:leveloffset: 0
-
-Software Installation
-=====================
-
-
-Introduction
-------------
-
-This part will guide you through the installation steps installation or
-upgrading your Evergreen system. It is intended for system administrators.
-
-
-include::installation/system_requirements.txt[]
-
-// Push titles down one level.
-:leveloffset: 1
-
-include::installation/server_installation.txt[]
-
-// Return to normal title levels.
-:leveloffset: 0
-
-include::installation/server_upgrade.txt[]
-
-include::installation/edi_setup.txt[]
-
-// include::staff_client_installation.txt[]
-// include::org_unit_structure_initialization.txt[]
-// include::loading_data.txt[]
-
-
-System Configuration and Customization
-======================================
-
-Introduction
-------------
-
-The Evergreen system allows a free range of customizations to every aspect of
-the system. Use this part of the documentation to become familiar with the tools
-for configuring the system as well as customizing the OPAC and staff client.
-
-// include::global_system_configuration.txt[]
-// include::opac_customization.txt[]
-
-include::admin/template_toolkit.txt[]
-
-include::admin/auto_suggest_search.txt[]
-
-include::admin/customize_staff_client.txt[]
-
-// include::backing_up.txt[]
-
-
-
-Using the Staff Client
-======================
-
-
-Introduction
-------------
-
-This part of the documentation deals with general Staff Client usage including
-logging in, navigation and shortcuts.
-
-
-include::admin/staff_client-tab_buttons.txt[]
-
-include::admin/staff_client-double_clicking.txt[]
-
-include::admin/staff_client-sorting_columns.txt[]
-
-include::admin/staff_client-recent_searches.txt[]
-
-include::admin/staff_client-return_to_results_from_marc.txt[]
-
-System Administration From the Staff Client
-===========================================
-
-Introduction
-------------
-
-This part deals with the options in the Server Administration menu found in the
-staff client.
-
-// Follow structure from staff client system admin menu.
-
-include::admin/acquisitions_admin.txt[]
-
-include::admin/authorities.txt[]
-
-include::admin/cn_prefixes_and_suffixes.txt[]
-
-include::admin/restrict_Z39.50_sources_by_perm_group.txt[]
-
-include::admin/booking-admin.txt[]
-
-include::admin/SMS_messaging.txt[]
-
-include::admin/user_activity_type.txt[]
-
-
-Local Administration
-====================
-
-Introduction
-------------
-
-This part covers the options in the Local Administration menu found in the staff
-client.
-
-// Follow structure from staff client local admin menu.
-
-// Push titles down one level.
-:leveloffset: 1
-
-include::admin/hold_driven_recalls.txt[]
-
-// Return to normal title levels.
-:leveloffset: 0
-
-include::admin/recent_staff_searches.txt[]
-
-include::admin/lsa-library_settings_editor.txt[]
-
-include::admin/lsa-statcat.txt[]
-
-
-Acquisitions
-===========
-
-include::acquisitions/introduction.txt[]
-
-include::acquisitions/selection_lists_po.txt[]
-
-include::acquisitions/receive_items_from_invoice.txt[]
-
-include::acquisitions/vandelay_acquisitions_integration.txt[]
-
-
-Cataloging
-==========
-
-Introduction
-------------
-
-Cataloguers should use this part for understanding the cataloguing procedures
-used in Evergreen.
-
-include::cataloging/batch_importing_MARC.txt[]
-
-include::cataloging/overlay_record_3950_import.txt[]
-
-include::cataloging/monograph_parts.txt[]
-
-include::cataloging/conjoined_items.txt[]
-
-
-Serials
-=======
-
-include::serials/A-intro.txt[]
-
-include::serials/B-copy_template.txt[]
-
-include::serials/C-subscription-SCV.txt[]
-
-include::serials/D-subscription-ASCV.txt[]
-
-include::serials/E-edit_subscriptions.txt[]
-
-include::serials/F-Receiving.txt[]
-
-include::serials/G-Special_issue.txt[]
-
-include::serials/H-holdings_statements.txt[]
-
-
-Circulation
-===========
-
-Introduction
-------------
-
-Use this section for understanding the circulation procedures in the Evergreen
-system.
-
-include::circulation/circulating_items.txt[]
-
-include::circulation/booking.txt[]
-
-Reports
-=======
-
-Introduction
-------------
-
-Learn how to create and use reports in Evergreen.
-
-Using the Public Access Catalog
-===============================
-
-Introduction
-------------
-
-Use this part for information about searching the Evergreen public access catalog.
-
-include::opac/my_lists.txt[]
-
-Developer Resources
-===================
-
-Introduction
-------------
-
-Developers can use this part to learn more about the programming languages,
-communication protocols and standards used in Evergreen.
-
-// Push titles down one level.
-:leveloffset: 1
-
-include::development/updating_translations_launchpad.txt[]
-
-// Return to normal title levels.
-:leveloffset: 0
-
-[appendix]
-
-include::attributions.txt[]
-
-include::licensing.txt[]
-
-Admonitions
-===========
-
-Images used for Admonitions
----------------------------
-
-* Note
-
-image::media/note.png[]
-
-* warning
-
-image::media/warning.png[]
-
-* caution
-
-image::media/caution.png[]
-
-* tip
-
-image::media/tip.png[]
-
-
+Evergreen Documentation
+=======================
+Documentation Interest Group
+:doctype: book
+:toc:
+:numbered:
+
+Introduction
+============
+
+About This Documentation
+------------------------
+
+This guide was produced by the Evergreen Documentation Interest Group (DIG),
+consisting of numerous volunteers from many different organizations. The DIG
+has drawn together, edited, and supplemented pre-existing documentation
+contributed by libraries and consortia running Evergreen that were kind enough
+to release their documentation into the creative commons. Please see the
+<<attributions,Attributions>> section for a full list of authors and
+contributing organizations. Just like the software it describes, this guide is
+a work in progress, continually revised to meet the needs of its users, so if
+you find errors or omissions, please let us know, by contacting the DIG
+facilitators at docs at evergreen-ils.org.
+
+This guide to Evergreen is intended to meet the needs of front-line library
+staff, catalogers, library administrators, system administrators, and software
+developers. It is organized into Parts, Chapters, and Sections addressing key
+aspects of the software, beginning with the topics of broadest interest to the
+largest groups of users and progressing to some of the more specialized and
+technical topics of interest to smaller numbers of users.
+
+Copies of this guide can be accessed in PDF and HTML formats from http://docs.evergreen-ils.org/.
+
+About Evergreen
+---------------
+
+Evergreen is an open source library automation software designed to meet the
+needs of the very smallest to the very largest libraries and consortia. Through
+its staff interface, it facilitates the management, cataloging, and circulation
+of library materials, and through its online public access interface it helps
+patrons find those materials.
+
+The Evergreen software is freely licensed under the GNU General Public License,
+meaning that it is free to download, use, view, modify, and share. It has an
+active development and user community, as well as several companies offering
+migration, support, hosting, and development services.
+
+The community’s development requirements state that Evergreen must be:
+
+* Stable, even under extreme load.
+* Robust, and capable of handling a high volume of transactions and simultaneous users.
+* Flexible, to accommodate the varied needs of libraries.
+* Secure, to protect our patrons’ privacy and data.
+* User-friendly, to facilitate patron and staff use of the system.
+
+Evergreen, which first launched in 2006 now powers over 544 libraries of every
+type – public, academic, special, school, and even tribal and home libraries –
+in over a dozen countries worldwide.
+
+// Push titles down one level.
+:leveloffset: 1
+
+include::RELEASE_NOTES_2_2.txt[]
+
+// Return to normal title levels.
+:leveloffset: 0
+
+Software Installation
+=====================
+
+
+Introduction
+------------
+
+This part will guide you through the installation steps installation or
+upgrading your Evergreen system. It is intended for system administrators.
+
+
+include::installation/system_requirements.txt[]
+
+// Push titles down one level.
+:leveloffset: 1
+
+include::installation/server_installation.txt[]
+
+// Return to normal title levels.
+:leveloffset: 0
+
+include::installation/server_upgrade.txt[]
+
+include::installation/edi_setup.txt[]
+
+// include::staff_client_installation.txt[]
+// include::org_unit_structure_initialization.txt[]
+// include::loading_data.txt[]
+
+
+System Configuration and Customization
+======================================
+
+Introduction
+------------
+
+The Evergreen system allows a free range of customizations to every aspect of
+the system. Use this part of the documentation to become familiar with the tools
+for configuring the system as well as customizing the OPAC and staff client.
+
+// include::global_system_configuration.txt[]
+// include::opac_customization.txt[]
+
+include::admin/template_toolkit.txt[]
+
+include::admin/auto_suggest_search.txt[]
+
+include::admin/customize_staff_client.txt[]
+
+// include::backing_up.txt[]
+
+
+
+Using the Staff Client
+======================
+
+
+Introduction
+------------
+
+This part of the documentation deals with general Staff Client usage including
+logging in, navigation and shortcuts.
+
+
+include::admin/staff_client-tab_buttons.txt[]
+
+include::admin/staff_client-double_clicking.txt[]
+
+include::admin/staff_client-sorting_columns.txt[]
+
+include::admin/staff_client-recent_searches.txt[]
+
+include::admin/staff_client-return_to_results_from_marc.txt[]
+
+System Administration From the Staff Client
+===========================================
+
+Introduction
+------------
+
+This part deals with the options in the Server Administration menu found in the
+staff client.
+
+// Follow structure from staff client system admin menu.
+
+include::admin/acquisitions_admin.txt[]
+
+include::admin/authorities.txt[]
+
+include::admin/cn_prefixes_and_suffixes.txt[]
+
+include::admin/restrict_Z39.50_sources_by_perm_group.txt[]
+
+include::admin/booking-admin.txt[]
+
+include::admin/SMS_messaging.txt[]
+
+include::admin/user_activity_type.txt[]
+
+
+Local Administration
+====================
+
+Introduction
+------------
+
+This part covers the options in the Local Administration menu found in the staff
+client.
+
+// Follow structure from staff client local admin menu.
+
+// Push titles down one level.
+:leveloffset: 1
+
+include::admin/hold_driven_recalls.txt[]
+
+// Return to normal title levels.
+:leveloffset: 0
+
+include::admin/recent_staff_searches.txt[]
+
+include::admin/lsa-library_settings_editor.txt[]
+
+include::admin/lsa-statcat.txt[]
+
+
+Acquisitions
+===========
+
+include::acquisitions/introduction.txt[]
+
+include::acquisitions/selection_lists_po.txt[]
+
+include::acquisitions/receive_items_from_invoice.txt[]
+
+include::acquisitions/vandelay_acquisitions_integration.txt[]
+
+
+Cataloging
+==========
+
+Introduction
+------------
+
+Cataloguers should use this part for understanding the cataloguing procedures
+used in Evergreen.
+
+include::cataloging/batch_importing_MARC.txt[]
+
+include::cataloging/overlay_record_3950_import.txt[]
+
+include::cataloging/monograph_parts.txt[]
+
+include::cataloging/conjoined_items.txt[]
+
+
+Serials
+=======
+
+include::serials/A-intro.txt[]
+
+include::serials/B-copy_template.txt[]
+
+include::serials/C-subscription-SCV.txt[]
+
+include::serials/D-subscription-ASCV.txt[]
+
+include::serials/E-edit_subscriptions.txt[]
+
+include::serials/F-Receiving.txt[]
+
+include::serials/G-Special_issue.txt[]
+
+include::serials/H-holdings_statements.txt[]
+
+
+Circulation
+===========
+
+Introduction
+------------
+
+Use this section for understanding the circulation procedures in the Evergreen
+system.
+
+include::circulation/circulating_items.txt[]
+
+include::circulation/booking.txt[]
+
+Reports
+=======
+
+Introduction
+------------
+
+Learn how to create and use reports in Evergreen.
+
+Using the Public Access Catalog
+===============================
+
+Introduction
+------------
+
+Use this part for information about searching the Evergreen public access catalog.
+
+include::opac/my_lists.txt[]
+
+Developer Resources
+===================
+
+Introduction
+------------
+
+Developers can use this part to learn more about the programming languages,
+communication protocols and standards used in Evergreen.
+
+// Push titles down one level.
+:leveloffset: 1
+
+include::development/updating_translations_launchpad.txt[]
+
+// Return to normal title levels.
+:leveloffset: 0
+
+[appendix]
+
+include::attributions.txt[]
+
+include::licensing.txt[]
+
+Admonitions
+===========
+
+Images used for Admonitions
+---------------------------
+
+* Note
+
+image::media/note.png[]
+
+* warning
+
+image::media/warning.png[]
+
+* caution
+
+image::media/caution.png[]
+
+* tip
+
+image::media/tip.png[]
+
+
commit 1e8c1b810f34f4fccda11f0d88120320c3a4d0ce
Author: Dan Scott <dan at coffeecode.net>
Date: Sun Jun 3 01:09:26 2012 -0400
Improve Fedora prereqs and instructions
Fedora 16 and 17 need the makensis package.
As well, make the Makefile.install target "fedora" to match the OpenSRF
target, and adjust the docs accordingly. This should lead to fewer
changes in the future as Fedora 18, 19, etc roll out.
Signed-off-by: Dan Scott <dan at coffeecode.net>
diff --git a/Open-ILS/src/extras/Makefile.install b/Open-ILS/src/extras/Makefile.install
index aeb84f3..9d9c6c3 100644
--- a/Open-ILS/src/extras/Makefile.install
+++ b/Open-ILS/src/extras/Makefile.install
@@ -4,7 +4,9 @@
#
# Makefile to install prerequisites for OpenSRF and Evergreen
#
-# Currently supports Debian (squeeze), Ubuntu (10.04), Ubuntu (12.04) and Fedora (16).
+# Currently supports Debian (squeeze), Ubuntu (10.04), Ubuntu (12.04) and
+# Fedora (16 and 17).
+#
# Installs Perl prereqs, libjs with Perl wrapper, libdbi, libdbi-drivers, and libyaz
#
# usage:
@@ -14,7 +16,7 @@
# - or -
# make -f Makefile.install ubuntu-precise
# - or -
-# make -f Makefile.install fedora16
+# make -f Makefile.install fedora
#
# ---------------------------------------------------------------------
@@ -122,6 +124,7 @@ FEDORA_RPMS = \
libssh2-devel \
libyaz \
libyaz-devel \
+ mingw32-nsiswrapper \
mod_ssl \
ncurses-devel \
ncurses-libs \
@@ -152,7 +155,7 @@ FEDORA_RPMS = \
# Note: B:O:AuthorizeNet 3.21 fails with https://rt.cpan.org/Public/Bug/Display.html?id=55172
# Should be fixed in 3.22
-# MARC::Record 2.0.1 is required but only 2.0.0 is packaged
+# MARC::Record 2.0.1+ is required but only 2.0.0 is packaged
FEDORA_CPAN = \
Business::OnlinePayment \
Business::OnlinePayment::AuthorizeNet \
@@ -261,7 +264,7 @@ all:
# these should be the same for any distro
install: install_cpan install_js_sm install_cpan_force
-fedora16: install_fedora_rpms install_cpan_fedora install_cpan_marc install
+fedora: install_fedora_rpms install_cpan_fedora install_cpan_marc install
debian-squeeze: squeeze generic_debian
squeeze: install_pgsql_client_backport_debs_91 install_extra_debs_squeeze
diff --git a/docs/installation/server_installation.txt b/docs/installation/server_installation.txt
index c7585c0..991eece 100644
--- a/docs/installation/server_installation.txt
+++ b/docs/installation/server_installation.txt
@@ -103,13 +103,13 @@ add-apt-repository ppa:pitti/postgresql
+
* Ubuntu Precise comes with PostgreSQL 9, so no additional steps are required.
+
- * Fedora 16 comes with PostgreSQL 9, so no additional steps are required.
+ * Fedora comes with PostgreSQL 9, so no additional steps are required.
+
3. On Debian and Ubuntu, run `aptitude update` as the *root* Linux account to
retrieve the new packages from the backports repository.
4. Issue the following commands as the *root* Linux account to install
prerequisites using the `Makefile.install` prerequisite installer,
- substituting `debian-squeeze`, `fedora16`, `ubuntu-lucid`, or
+ substituting `debian-squeeze`, `fedora`, `ubuntu-lucid`, or
`ubuntu-precise` for <osname> below:
+
[source, bash]
@@ -329,7 +329,7 @@ make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_91
You can install the packages required by Fedora on the machine of your choice
using the following commands as the *root* Linux account:
-.(Fedora 16) Installing PostgreSQL server packages
+.(Fedora) Installing PostgreSQL server packages
[source, bash]
------------------------------------------------------------------------------
make -f Open-ILS/src/extras/Makefile.install install_fedora_pgsql_server
@@ -351,7 +351,7 @@ cpan MARC::File::XML
cpan UUID::Tiny
------------------------------------------------------------------------------
-.(Fedora 16) Installing additional Perl modules on a standalone PostgreSQL 9 server
+.(Fedora) Installing additional Perl modules on a standalone PostgreSQL 9 server
[source, bash]
------------------------------------------------------------------------------
yum install gcc perl-XML-LibXML perl-XML-LibXSLT perl-Business-ISBN
commit 7753dd6b1722320b8a1c9034a82293e9a0102c1f
Author: Galen Charlton <gmc at esilibrary.com>
Date: Sat May 26 12:17:58 2012 -0400
DOC: fix a couple typos
Signed-off-by: Galen Charlton <gmc at esilibrary.com>
diff --git a/docs/admin/acquisitions_admin.txt b/docs/admin/acquisitions_admin.txt
index de4e329..30db442 100644
--- a/docs/admin/acquisitions_admin.txt
+++ b/docs/admin/acquisitions_admin.txt
@@ -268,7 +268,7 @@ The rule of parental inheritance applies to this list.
Funding Sources
~~~~~~~~~~~~~~~
-Funding sources allow you to specify the sources that contribute monies to your fund(s). You can create as few or as many funding sources as you need. These can be used to track exact ammounts for accounts in your general ledger. You can then use funds to track spending and purchases for specific collections.
+Funding sources allow you to specify the sources that contribute monies to your fund(s). You can create as few or as many funding sources as you need. These can be used to track exact amounts for accounts in your general ledger. You can then use funds to track spending and purchases for specific collections.
Create a funding source
^^^^^^^^^^^^^^^^^^^^^^^
@@ -340,7 +340,7 @@ The rule of parental inheritance applies to this list. See section
. Click the Active box to activate this fund. You cannot make purchases from this fund if it is not active.
. Enter a Balance Stop Percent. The balance stop percent prevents you from making purchases when only a specified amount of the fund remains. For example, if you want to spend 95 percent of your funds, leaving a five percent balance in the fund, then you would enter 95 in the field. When the fund reaches its balance stop percent, it will appear in red when you apply funds to copies.
. Enter a Balance Warning Percent. The balance warning percent gives you a warning that the fund is low. You can specify any percent. For example, if you want to spend 90 percent of your funds and be warned when the fund has only 10 percent of its balance remaining, then enter 90 in the field. When the fund reaches its balance warning percent, it will appear in yellow when you apply funds to copies.
-. Check the Propagate box to propagate funds. When you propagate a fund, the ILS will create a new fund for the following fisca year with the same parameters as your current fund. All of the settings transfer except for the year and the amount of money in the fund. Propagation occurs during the fiscal year close~out operation.
+. Check the Propagate box to propagate funds. When you propagate a fund, the ILS will create a new fund for the following fiscal year with the same parameters as your current fund. All of the settings transfer except for the year and the amount of money in the fund. Propagation occurs during the fiscal year close~out operation.
. Check the Rollover box if you want to roll over remaining funds into the same fund next year.
. Click _Save_.
commit 6891ac8b8e5b1b0257e5f32b7016eb1587f25335
Author: Dan Scott <dan at coffeecode.net>
Date: Fri May 25 03:14:46 2012 -0400
README: Bump OpenSRF prerequisite to 2.1 for Evergreen 2.2+
Also use a title that fits into the DIG documentation more smoothly, and
be consistent about sentence-style capitalization of sub-headings.
Signed-off-by: Dan Scott <dan at coffeecode.net>
diff --git a/docs/installation/server_installation.txt b/docs/installation/server_installation.txt
index 5888c1c..c7585c0 100644
--- a/docs/installation/server_installation.txt
+++ b/docs/installation/server_installation.txt
@@ -1,5 +1,5 @@
-README for Evergreen master
-===========================
+Installing the Evergreen server
+===============================
:toc:
:numbered:
@@ -32,7 +32,7 @@ follows:
Evergreen that you will use to test connectivity and configure your
Evergreen instance.
-Preamble: Developer instructions
+Preamble: developer instructions
--------------------------------
[NOTE]
@@ -76,7 +76,7 @@ Installing prerequisites
Evergreen has a number of prerequisite packages that must be installed
before you can successfully configure, compile, and install Evergreen.
-1. Begin by installing the most recent version of OpenSRF (2.0 or later).
+1. Begin by installing the most recent version of OpenSRF (2.1 or later).
You can download OpenSRF releases from http://evergreen-ils.org/opensrf.php
2. On many distributions, it is necessary to install PostgreSQL 9 from external
repositories.
commit 15769b7f63de1143f69a00f26c1f17360406dc10
Author: Dan Scott <dscott at laurentian.ca>
Date: Sun May 20 23:02:09 2012 -0400
Further integration: link README to server install docs
We will now have the INSTALL file linking to the README file which in
turn leads to the docs/installation/server_installation.text file. But
it all works!
Signed-off-by: Dan Scott <dscott at laurentian.ca>
Conflicts:
README
Signed-off-by: Dan Scott <dscott at laurentian.ca>
diff --git a/README b/README
deleted file mode 100644
index b1c7bba..0000000
--- a/README
+++ /dev/null
@@ -1,549 +0,0 @@
-Installing the Evergreen server
-===============================
-:toc:
-:numbered:
-
-Preamble: referenced user accounts
-----------------------------------
-
-In subsequent sections, we will refer to a number of different accounts, as
-follows:
-
- * Linux user accounts:
- ** The *user* Linux account is the account that you use to log onto the
- Linux system as a regular user.
- ** The *root* Linux account is an account that has system administrator
- privileges. On Debian and Fedora you can switch to this account from
- your *user* account by issuing the `su -` command and entering the
- password for the *root* account when prompted. On Ubuntu you can switch
- to this account from your *user* account using the `sudo su -` command
- and entering the password for your *user* account when prompted.
- ** The *opensrf* Linux account is an account that you create when installing
- OpenSRF. You can switch to this account from the *root* account by
- issuing the `su - opensrf` command.
- ** The *postgres* Linux account is created automatically when you install
- the PostgreSQL database server. You can switch to this account from the
- *root* account by issuing the `su - postgres` command.
- * PostgreSQL user accounts:
- ** The *evergreen* PostgreSQL account is a superuser account that you will
- create to connect to the PostgreSQL database server.
- * Evergreen administrator account:
- ** The *egadmin* Evergreen account is an administrator account for
- Evergreen that you will use to test connectivity and configure your
- Evergreen instance.
-
-Preamble: developer instructions
---------------------------------
-
-[NOTE]
-Skip this section if you are using an official release tarball downloaded
-from http://evergreen-ils.org/downloads
-
-Developers working directly with the source code from the Git repository,
-rather than an official release tarball, must install some extra packages
-and perform one step before they can proceed with the `./configure` step.
-
-As the *root* Linux account, install the following packages:
-
- * autoconf
- * automake
- * libtool
-
-As the *user* Linux account, issue the following command in the Evergreen
-source directory to generate the configure script and Makefiles:
-
-[source, bash]
-------------------------------------------------------------------------------
-autoreconf -i
-------------------------------------------------------------------------------
-
-After running `make install`, developers also need to install the Dojo Toolkit
-set of JavaScript libraries. The appropriate version of Dojo is included
-in Evergreen release tarballs. Developers should install the Dojo 1.3.3
-version of Dojo by issuing the following commands as the *opensrf* Linux
-account:
-
-[source, bash]
-------------------------------------------------------------------------------
-wget http://download.dojotoolkit.org/release-1.3.3/dojo-release-1.3.3.tar.gz
-tar -C /openils/var/web/js -xzf dojo-release-1.3.3.tar.gz
-cp -r /openils/var/web/js/dojo-release-1.3.3/* /openils/var/web/js/dojo/.
-------------------------------------------------------------------------------
-
-Installing prerequisites
-------------------------
-
-Evergreen has a number of prerequisite packages that must be installed
-before you can successfully configure, compile, and install Evergreen.
-
-1. Begin by installing the most recent version of OpenSRF (2.1 or later).
- You can download OpenSRF releases from http://evergreen-ils.org/opensrf.php
-2. On many distributions, it is necessary to install PostgreSQL 9 from external
- repositories.
-+
- * On Debian Squeeze, open `/etc/apt/sources.list` in a text editor as the
- *root* Linux account and add the following line:
-+
-[source, bash]
-------------------------------------------------------------------------------
-deb http://backports.debian.org/debian-backports squeeze-backports main contrib
-------------------------------------------------------------------------------
-+
- * On Ubuntu Lucid, you can use a PPA (personal package archive), which are
- package sources hosted on Launchpad. The one most commonly used by Evergreen
- Community members is maintained by Martin Pitt, who also maintains the
- official PostgreSQL packages for Ubuntu. As the *root* Linux account, issue
- the following commands to add the PPA source:
-+
-[source, bash]
-------------------------------------------------------------------------------
-apt-get install python-software-properties
-add-apt-repository ppa:pitti/postgresql
-------------------------------------------------------------------------------
-+
- * Ubuntu Precise comes with PostgreSQL 9, so no additional steps are required.
-+
- * Fedora 16 comes with PostgreSQL 9, so no additional steps are required.
-+
-3. On Debian and Ubuntu, run `aptitude update` as the *root* Linux account to
- retrieve the new packages from the backports repository.
-4. Issue the following commands as the *root* Linux account to install
- prerequisites using the `Makefile.install` prerequisite installer,
- substituting `debian-squeeze`, `fedora16`, `ubuntu-lucid`, or
- `ubuntu-precise` for <osname> below:
-+
-[source, bash]
-------------------------------------------------------------------------------
-make -f Open-ILS/src/extras/Makefile.install <osname>
-------------------------------------------------------------------------------
-+
-5. Add the libdbi-libdbd libraries to the system dynamic library path by
- issuing the following commands as the *root* Linux account:
-+
-[NOTE]
-You should skip this step if installing on Ubuntu Precise. The ubuntu-precise
-target uses libdbd-pgsql from packages.
-+
-.Debian / Ubuntu Lucid
-[source, bash]
-------------------------------------------------------------------------------
-echo "/usr/local/lib/dbd" > /etc/ld.so.conf.d/eg.conf
-ldconfig
-------------------------------------------------------------------------------
-+
-.Fedora
-[source, bash]
-------------------------------------------------------------------------------
-echo "/usr/lib64/dbd" > /etc/ld.so.conf.d/eg.conf
-ldconfig
-------------------------------------------------------------------------------
-
-Configuration and compilation instructions
-------------------------------------------
-
-For the time being, we are still installing everything in the `/openils/`
-directory. From the Evergreen source directory, issue the following commands as
-the *user* Linux account to configure and build Evergreen:
-
-[source, bash]
-------------------------------------------------------------------------------
-./configure --prefix=/openils --sysconfdir=/openils/conf
-make
-------------------------------------------------------------------------------
-
-Installation instructions
--------------------------
-
-1. Once you have configured and compiled Evergreen, issue the following
- command as the *root* Linux account to install Evergreen, build the server
- portion of the staff client, and copy example configuration files to
- `/openils/conf`.
- Change the value of the `STAFF_CLIENT_STAMP_ID` variable to match the version
- of the staff client that you will use to connect to the Evergreen server.
-+
-[source, bash]
-------------------------------------------------------------------------------
-make STAFF_CLIENT_STAMP_ID=rel_2_2 install
-------------------------------------------------------------------------------
-+
-2. The server portion of the staff client expects `http://hostname/xul/server`
- to resolve. Issue the following commands as the *root* Linux account to
- create a symbolic link pointing to the `server` subdirectory of the server
- portion of the staff client that we just built using the staff client ID
- 'rel_name':
-+
-[source, bash]
-------------------------------------------------------------------------------
-cd /openils/var/web/xul
-ln -sf rel_name/server server
-------------------------------------------------------------------------------
-
-Change ownership of the Evergreen files
----------------------------------------
-
-All files in the `/openils/` directory and subdirectories must be owned by the
-`opensrf` user. Issue the following command as the *root* Linux account to
-change the ownership on the files:
-
-[source, bash]
-------------------------------------------------------------------------------
-chown -R opensrf:opensrf /openils
-------------------------------------------------------------------------------
-
-Configure the Apache Web server
--------------------------------
-
-1. Use the example configuration files in `Open-ILS/examples/apache/` to
-configure your Web server for the Evergreen catalog, staff client, Web
-services, and administration interfaces. Issue the following commands as the
-*root* Linux account:
-+
-.Debian and Ubuntu
-[source,bash]
-------------------------------------------------------------------------------
-cp Open-ILS/examples/apache/eg.conf /etc/apache2/sites-available/
-cp Open-ILS/examples/apache/eg_vhost.conf /etc/apache2/
-cp Open-ILS/examples/apache/startup.pl /etc/apache2/
-# Now set up SSL
-mkdir /etc/apache2/ssl
-cd /etc/apache2/ssl
-------------------------------------------------------------------------------
-+
-.Fedora
-[source,bash]
-------------------------------------------------------------------------------
-cp Open-ILS/examples/apache/eg.conf /etc/httpd/conf.d/
-cp Open-ILS/examples/apache/eg_vhost.conf /etc/httpd/
-cp Open-ILS/examples/apache/startup.pl /etc/httpd/
-# Now set up SSL
-mkdir /etc/httpd/ssl
-cd /etc/httpd/ssl
-------------------------------------------------------------------------------
-+
-2. The `openssl` command cuts a new SSL key for your Apache server. For a
-production server, you should purchase a signed SSL certificate, but you can
-just use a self-signed certificate and accept the warnings in the staff client
-and browser during testing and development. Create an SSL key for the Apache
-server by issuing the following command as the *root* Linux account:
-+
-[source,bash]
-------------------------------------------------------------------------------
-openssl req -new -x509 -days 365 -nodes -out server.crt -keyout server.key
-------------------------------------------------------------------------------
-+
-3. As the *root* Linux account, edit the `eg.conf` file that you copied into
-place.
- a. Replace `Allow from 10.0.0.0/8` with `Allow from all` (to enable
- access to the offline upload / execute interface from any workstation on
- any network - note that you must secure this for a production instance)
- b. (Fedora): Change references from the non-existent `/etc/apache2/` directory
- to `/etc/httpd/`.
-4. Change the user for the Apache server.
- * (Debian and Ubuntu): As the *root* Linux account, edit
- `/etc/apache2/envvars`. Change `export APACHE_RUN_USER=www-data` to
- `export APACHE_RUN_USER=opensrf`.
- * (Fedora): As the *root* Linux account , edit `/etc/httpd/conf/httpd.conf`.
- Change `User apache` to `User opensrf`.
-5. Configure Apache with performance settings appropriate for Evergreen:
- * (Debian and Ubuntu): As the *root* Linux account, edit
- `/etc/apache2/apache2.conf`:
- * (Fedora): As the *root* Linux account, edit `/etc/httpd/conf/httpd.conf`:
- a. Change `KeepAliveTimeout` to `1`. Higher values reduce the chance of
- a request timing out unexpectedly, but increase the risk of using up
- all available Apache child processes.
- b. 'Optional': Change `MaxKeepAliveRequests` to `100`
- c. Update the prefork configuration section to suit your environment. The
- following settings apply to a busy system:
-+
-[source,bash]
-------------------------------------------------------------------------------
-<IfModule mpm_prefork_module>
- StartServers 20
- MinSpareServers 5
- MaxSpareServers 15
- MaxClients 150
- MaxRequestsPerChild 10000
-</IfModule>
-------------------------------------------------------------------------------
-+
-6. (Fedora): As the *root* Linux account, edit the `/etc/httpd/eg_vhost.conf`
- file to change references from the non-existent `/etc/apache2/` directory
- to `/etc/httpd/`.
-7. (Debian and Ubuntu): As the *root* Linux account, enable the Evergreen site:
-+
-[source,bash]
-------------------------------------------------------------------------------
-a2dissite default # OPTIONAL: disable the default site (the "It Works" page)
-a2ensite eg.conf
-------------------------------------------------------------------------------
-
-Configure OpenSRF for the Evergreen application
------------------------------------------------
-There are a number of example OpenSRF configuration files in `/openils/conf/`
-that you can use as a template for your Evergreen installation. Issue the
-following commands as the *opensrf* Linux account:
-
-[source, bash]
-------------------------------------------------------------------------------
-cp -b /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml
-cp -b /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml
-------------------------------------------------------------------------------
-
-When you installed OpenSRF, you created four Jabber users on two
-separate domains and edited the `opensrf_core.xml` file accordingly. Please
-refer back to the OpenSRF README and, as the *opensrf* Linux account, edit the
-Evergreen version of the `opensrf_core.xml` file using the same Jabber users
-and domains as you used while installing and testing OpenSRF.
-
-[NOTE]
-The `-b` flag tells the `cp` command to create a backup version of the
-destination file. The backup version of the destination file has a tilde (`~`)
-appended to the file name, so if you have forgotten the Jabber users and
-domains, you can retrieve the settings from the backup version of the files.
-
-`eg_db_config.pl`, described in the following section, sets the database
-connection information in `opensrf.xml` for you.
-
-Creating the Evergreen database
--------------------------------
-
-By default, the `Makefile.install` prerequisite installer does not install
-the PostgreSQL 9 database server required by every Evergreen system;
-for production use, most libraries install the PostgreSQL database server on a
-dedicated machine. You can install the packages required by Debian or Ubuntu Lucid
-on the machine of your choice using the following commands as the *root*
-Linux account:
-
-.(Debian and Ubuntu Lucid) Installing PostgreSQL 9.1 server packages
-[source, bash]
-------------------------------------------------------------------------------
-make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_backport_debs_91
-------------------------------------------------------------------------------
-
-.(Ubuntu Precise) Installing PostgreSQL 9.1 server packages
-[source, bash]
-------------------------------------------------------------------------------
-make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_91
-------------------------------------------------------------------------------
-
-You can install the packages required by Fedora on the machine of your choice
-using the following commands as the *root* Linux account:
-
-.(Fedora 16) Installing PostgreSQL server packages
-[source, bash]
-------------------------------------------------------------------------------
-make -f Open-ILS/src/extras/Makefile.install install_fedora_pgsql_server
-postgresql-setup initdb
-------------------------------------------------------------------------------
-
-For a standalone PostgreSQL server, install the following Perl modules as the
-*root* Linux account:
-
-.(Debian / Ubuntu) Installing additional Perl modules on a standalone PostgreSQL 9 server
-[source, bash]
-------------------------------------------------------------------------------
-aptitude install gcc libxml-libxml-perl libxml-libxslt-perl
-cpan Business::ISBN
-cpan JSON::XS
-cpan Library::CallNumber::LC
-cpan MARC::Record
-cpan MARC::File::XML
-cpan UUID::Tiny
-------------------------------------------------------------------------------
-
-.(Fedora 16) Installing additional Perl modules on a standalone PostgreSQL 9 server
-[source, bash]
-------------------------------------------------------------------------------
-yum install gcc perl-XML-LibXML perl-XML-LibXSLT perl-Business-ISBN
-cpan Library::CallNumber::LC
-cpan MARC::Record
-cpan MARC::File::XML
-cpan UUID::Tiny
-------------------------------------------------------------------------------
-
-You need to create a PostgreSQL superuser to create and access the database.
-Issue the following command as the *postgres* Linux account to create a new
-PostgreSQL superuser named `evergreen`. When prompted, enter the new user's
-password:
-
-[source, bash]
-------------------------------------------------------------------------------
-createuser -s -P evergreen
-------------------------------------------------------------------------------
-
-Once you have created the *evergreen* PostgreSQL account, you also need to
-create the database and schema, and configure your configuration files to point
-at the database server. Issue the following command as the *root* Linux account
-from inside the Evergreen source directory, replacing <user>, <password>,
-<hostname>, <port>, and <dbname> with the appropriate values for your
-PostgreSQL database (where <user> and <password> are for the *evergreen*
-PostgreSQL account you just created), and replace <admin-user> and <admin-pass>
-with the values you want for the *egadmin* Evergreen administrator account:
-
-[source, bash]
-------------------------------------------------------------------------------
-perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config \
- --service all --create-database --create-schema --create-offline \
- --user <user> --password <password> --hostname <hostname> --port <port> \
- --database <dbname> --admin-user <admin-user> --admin-pass <admin-pass>
-------------------------------------------------------------------------------
-
-This creates the database and schema and configures all of the services in
-your `/openils/conf/opensrf.xml` configuration file to point to that database.
-It also creates the configuration files required by the Evergreen `cgi-bin`
-administration scripts, and sets the user name and password for the *egadmin*
-Evergreen administrator account to your requested values.
-
-Creating the database on a remote server
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-In a production instance of Evergreen, your PostgreSQL server should be
-installed on a dedicated server.
-
-PostgreSQL 9.1 and later
-^^^^^^^^^^^^^^^^^^^^^^^^
-To create the database instance on a remote database server running PostgreSQL
-9.1 or later, simply use the `--create-database` flag on `eg_db_config.pl`.
-
-For PostgreSQL 9.0
-^^^^^^^^^^^^^^^^^^
-To create the database instance on a remote database server running PostgreSQL
-9.0, you can either:
-
- * Install the PostgreSQL contrib modules on the machine on which you
- are installing the Evergreen code, and use the `--create-database`
- option from that machine, or
- * Copy the `Open-ILS/src/sql/Pg/create_database.sql` script to your
- PostgreSQL server and invoke it as the *postgres* Linux account:
-+
-[source, bash]
-------------------------------------------------------------------------------
-psql -vdb_name=<dbname> -vcontrib_dir=`pg_config --sharedir`/contrib -f create_database.sql
-------------------------------------------------------------------------------
-
-Then you can issue the `eg_db_config.pl` command as above _without_ the
-`--create-database` argument to create your schema and configure your
-configuration files.
-
-Starting Evergreen
-------------------
-1. As the *root* Linux account, start the `memcached` and `ejabberd` services
-(if they aren't already running):
-+
-[source, bash]
-------------------------------------------------------------------------------
-/etc/init.d/ejabberd start
-/etc/init.d/memcached start
-------------------------------------------------------------------------------
-+
-2. As the *opensrf* Linux account, start Evergreen. The `-l` flag in the
-following command is only necessary if you want to force Evergreen to treat the
-hostname as `localhost`; if you configured `opensrf.xml` using the real
-hostname of your machine as returned by `perl -ENet::Domain 'print
-Net::Domain::hostfqdn() . "\n";'`, you should not use the `-l` flag.
-+
-[source, bash]
-------------------------------------------------------------------------------
-osrf_ctl.sh -l -a start_all
-------------------------------------------------------------------------------
-+
- ** If you receive the error message `bash: osrf_ctl.sh: command not found`,
- then your environment variable `PATH` does not include the `/openils/bin`
- directory; this should have been set in the *opensrf* Linux account's
- `.bashrc` configuration file. To manually set the `PATH` variable, edit the
- configuration file `~/.bashrc` as the *opensrf* Linux account and add the
- following line:
-+
-[source, bash]
-------------------------------------------------------------------------------
-export PATH=$PATH:/openils/bin
-------------------------------------------------------------------------------
-+
-3. As the *opensrf* Linux account, generate the Web files needed by the staff
- client and catalogue and update the organization unit proximity (you need to do
- this the first time you start Evergreen, and after that each time you change
- the library hierarchy in `config.cgi`):
-+
-[source, bash]
-------------------------------------------------------------------------------
-autogen.sh -u
-------------------------------------------------------------------------------
-+
-4. As the *root* Linux account, restart the Apache Web server:
-+
-[source, bash]
-------------------------------------------------------------------------------
-/etc/init.d/apache2 restart
-------------------------------------------------------------------------------
-+
-If the Apache Web server was running when you started the OpenSRF services, you
-might not be able to successfully log in to the OPAC or staff client until the
-Apache Web server is restarted.
-
-Testing connections to Evergreen
---------------------------------
-
-Once you have installed and started Evergreen, test your connection to
-Evergreen via `srfsh`. As the *opensrf* Linux account, issue the following
-commands to start `srfsh` and try to log onto the Evergreen server using the
-*egadmin* Evergreen administrator user name and password that you set using the
-`eg_db_config.pl` command:
-
-[source, bash]
-------------------------------------------------------------------------------
-/openils/bin/srfsh
-srfsh% login <admin-user> <admin-pass>
-------------------------------------------------------------------------------
-
-You should see a result like:
-
- Received Data: "250bf1518c7527a03249858687714376"
- ------------------------------------
- Request Completed Successfully
- Request Time in seconds: 0.045286
- ------------------------------------
-
- Received Data: {
- "ilsevent":0,
- "textcode":"SUCCESS",
- "desc":" ",
- "pid":21616,
- "stacktrace":"oils_auth.c:304",
- "payload":{
- "authtoken":"e5f9827cc0f93b503a1cc66bee6bdd1a",
- "authtime":420
- }
-
- }
-
- ------------------------------------
- Request Completed Successfully
- Request Time in seconds: 1.336568
- ------------------------------------
-
-If this does not work, it's time to do some troubleshooting.
-
- * As the *opensrf* Linux acccount, run the `settings-tester.pl` script to see
- if it finds any system configuration problems. The script is found at
- `Open-ILS/src/support-scripts/settings-tester.pl` in the Evergreen source
- tree.
- * Follow the steps in the http://evergreen-ils.org/dokuwiki/doku.php?id=troubleshooting:checking_for_errors[troubleshooting guide].
- * If you have faithfully followed the entire set of installation steps
- listed here, you are probably extremely close to a working system.
- Gather your configuration files and log files and contact the
- http://open-ils.org/listserv.php[Evergreen development mailing list]
- for assistance before making any drastic changes to your system
- configuration.
-
-Getting help
-------------
-
-Need help installing or using Evergreen? Join the mailing lists at
-http://evergreen-ils.org/listserv.php or contact us on the Freenode
-IRC network on the #evergreen channel.
-
-License
--------
-This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
-Unported License. To view a copy of this license, visit
-http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative
-Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.
diff --git a/README b/README
new file mode 120000
index 0000000..b57451a
--- /dev/null
+++ b/README
@@ -0,0 +1 @@
+docs/installation/server_installation.txt
\ No newline at end of file
diff --git a/docs/installation/server_installation.txt b/docs/installation/server_installation.txt
index 0f52df4..5888c1c 100644
--- a/docs/installation/server_installation.txt
+++ b/docs/installation/server_installation.txt
@@ -1,5 +1,5 @@
-README for Evergreen 2.2
-========================
+README for Evergreen master
+===========================
:toc:
:numbered:
@@ -76,7 +76,7 @@ Installing prerequisites
Evergreen has a number of prerequisite packages that must be installed
before you can successfully configure, compile, and install Evergreen.
-1. Begin by installing the most recent version of OpenSRF (2.1 or later).
+1. Begin by installing the most recent version of OpenSRF (2.0 or later).
You can download OpenSRF releases from http://evergreen-ils.org/opensrf.php
2. On many distributions, it is necessary to install PostgreSQL 9 from external
repositories.
@@ -163,7 +163,7 @@ Installation instructions
+
[source, bash]
------------------------------------------------------------------------------
-make STAFF_CLIENT_STAMP_ID=rel_2_2 install
+make STAFF_CLIENT_STAMP_ID=rel_name install
------------------------------------------------------------------------------
+
2. The server portion of the staff client expects `http://hostname/xul/server`
commit 4ea6279c37a5035472879281ae251aff9259554d
Author: Dan Scott <dscott at laurentian.ca>
Date: Sun May 20 22:51:52 2012 -0400
Merge the Evergreen docs into the code repository
Rather than maintaining two separate repositories, with dual maintenance
of what are essentially single-sourced files in the release notes and
the install instructions, make better use of the docs/ subfolder of the
Evergreen repository. If this crazy scheme works, DIG can commit to the
docs/ subfolder, and devs can commit there too.
Signed-off-by: Dan Scott <dscott at laurentian.ca>
diff --git a/.gitignore b/.gitignore
index d9e24bf..8b5efd3 100644
--- a/.gitignore
+++ b/.gitignore
@@ -15,6 +15,8 @@ config.sub
configure
depcomp
docs/RELEASE_NOTES_2_2.html
+docs/root.html
+docs/root.pdf
install-sh
libtool
ltmain.sh
diff --git a/docs/RELEASE_NOTES_2_2.txt b/docs/RELEASE_NOTES_2_2.txt
index 7d1c3f3..e382742 100644
--- a/docs/RELEASE_NOTES_2_2.txt
+++ b/docs/RELEASE_NOTES_2_2.txt
@@ -102,8 +102,10 @@ and deprecate the use of the JSPAC.
Auto Suggest in Catalog Search
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The auto suggest feature suggests the completion of search terms as the user
-enters his query. By default, the user will see ten suggestions although this
+The
+http://docs.evergreen-ils.org/2.2/_auto_suggest_in_catalog_search_2.html[auto
+suggest feature] suggests the completion of search terms as the user enters his
+query. By default, the user will see ten suggestions although this
number is configurable at the database level. Scroll through suggestions with
your mouse, or use the arrow keys to scroll through the suggestions. Select a
suggestion to view records that are linked to this suggestion.
@@ -111,9 +113,6 @@ suggestion to view records that are linked to this suggestion.
This feature is not turned on by default. You must turn it on in the Admin
module.
-Documentation for this feature is available in the Book of Evergreen
-at http://docs.evergreen-ils.org/2.2/
-
Copy Location Groups
^^^^^^^^^^^^^^^^^^^^
This feature allows staff to create and name sets of copy locations to use as
diff --git a/acquisitions/introduction.txt b/docs/acquisitions/introduction.txt
similarity index 100%
rename from acquisitions/introduction.txt
rename to docs/acquisitions/introduction.txt
diff --git a/acquisitions/receive_items_from_invoice.txt b/docs/acquisitions/receive_items_from_invoice.txt
similarity index 100%
rename from acquisitions/receive_items_from_invoice.txt
rename to docs/acquisitions/receive_items_from_invoice.txt
diff --git a/acquisitions/selection_lists_po.txt b/docs/acquisitions/selection_lists_po.txt
similarity index 100%
rename from acquisitions/selection_lists_po.txt
rename to docs/acquisitions/selection_lists_po.txt
diff --git a/acquisitions/vandelay_acquisitions_integration.txt b/docs/acquisitions/vandelay_acquisitions_integration.txt
similarity index 100%
rename from acquisitions/vandelay_acquisitions_integration.txt
rename to docs/acquisitions/vandelay_acquisitions_integration.txt
diff --git a/admin/SMS_messaging.txt b/docs/admin/SMS_messaging.txt
similarity index 100%
rename from admin/SMS_messaging.txt
rename to docs/admin/SMS_messaging.txt
diff --git a/admin/acquisitions_admin.txt b/docs/admin/acquisitions_admin.txt
similarity index 100%
rename from admin/acquisitions_admin.txt
rename to docs/admin/acquisitions_admin.txt
diff --git a/admin/authorities.txt b/docs/admin/authorities.txt
similarity index 100%
rename from admin/authorities.txt
rename to docs/admin/authorities.txt
diff --git a/admin/auto_suggest_search.txt b/docs/admin/auto_suggest_search.txt
similarity index 100%
rename from admin/auto_suggest_search.txt
rename to docs/admin/auto_suggest_search.txt
diff --git a/admin/booking-admin.txt b/docs/admin/booking-admin.txt
similarity index 100%
rename from admin/booking-admin.txt
rename to docs/admin/booking-admin.txt
diff --git a/admin/cn_prefixes_and_suffixes.txt b/docs/admin/cn_prefixes_and_suffixes.txt
similarity index 100%
rename from admin/cn_prefixes_and_suffixes.txt
rename to docs/admin/cn_prefixes_and_suffixes.txt
diff --git a/admin/customize_staff_client.txt b/docs/admin/customize_staff_client.txt
similarity index 100%
rename from admin/customize_staff_client.txt
rename to docs/admin/customize_staff_client.txt
diff --git a/admin/hold_driven_recalls.txt b/docs/admin/hold_driven_recalls.txt
similarity index 100%
rename from admin/hold_driven_recalls.txt
rename to docs/admin/hold_driven_recalls.txt
diff --git a/admin/lsa-library_settings_editor.txt b/docs/admin/lsa-library_settings_editor.txt
similarity index 100%
rename from admin/lsa-library_settings_editor.txt
rename to docs/admin/lsa-library_settings_editor.txt
diff --git a/admin/lsa-statcat.txt b/docs/admin/lsa-statcat.txt
similarity index 100%
rename from admin/lsa-statcat.txt
rename to docs/admin/lsa-statcat.txt
diff --git a/admin/recent_staff_searches.txt b/docs/admin/recent_staff_searches.txt
similarity index 100%
rename from admin/recent_staff_searches.txt
rename to docs/admin/recent_staff_searches.txt
diff --git a/admin/restrict_Z39.50_sources_by_perm_group.txt b/docs/admin/restrict_Z39.50_sources_by_perm_group.txt
similarity index 100%
rename from admin/restrict_Z39.50_sources_by_perm_group.txt
rename to docs/admin/restrict_Z39.50_sources_by_perm_group.txt
diff --git a/admin/staff_client-double_clicking.txt b/docs/admin/staff_client-double_clicking.txt
similarity index 100%
rename from admin/staff_client-double_clicking.txt
rename to docs/admin/staff_client-double_clicking.txt
diff --git a/admin/staff_client-recent_searches.txt b/docs/admin/staff_client-recent_searches.txt
similarity index 100%
rename from admin/staff_client-recent_searches.txt
rename to docs/admin/staff_client-recent_searches.txt
diff --git a/admin/staff_client-return_to_results_from_marc.txt b/docs/admin/staff_client-return_to_results_from_marc.txt
similarity index 100%
rename from admin/staff_client-return_to_results_from_marc.txt
rename to docs/admin/staff_client-return_to_results_from_marc.txt
diff --git a/admin/staff_client-sorting_columns.txt b/docs/admin/staff_client-sorting_columns.txt
similarity index 100%
rename from admin/staff_client-sorting_columns.txt
rename to docs/admin/staff_client-sorting_columns.txt
diff --git a/admin/staff_client-tab_buttons.txt b/docs/admin/staff_client-tab_buttons.txt
similarity index 100%
rename from admin/staff_client-tab_buttons.txt
rename to docs/admin/staff_client-tab_buttons.txt
diff --git a/admin/template_toolkit.txt b/docs/admin/template_toolkit.txt
similarity index 100%
rename from admin/template_toolkit.txt
rename to docs/admin/template_toolkit.txt
diff --git a/admin/user_activity_type.txt b/docs/admin/user_activity_type.txt
similarity index 100%
rename from admin/user_activity_type.txt
rename to docs/admin/user_activity_type.txt
diff --git a/attributions.txt b/docs/attributions.txt
similarity index 100%
rename from attributions.txt
rename to docs/attributions.txt
diff --git a/cataloging/batch_importing_MARC.txt b/docs/cataloging/batch_importing_MARC.txt
similarity index 100%
rename from cataloging/batch_importing_MARC.txt
rename to docs/cataloging/batch_importing_MARC.txt
diff --git a/cataloging/conjoined_items.txt b/docs/cataloging/conjoined_items.txt
similarity index 100%
rename from cataloging/conjoined_items.txt
rename to docs/cataloging/conjoined_items.txt
diff --git a/cataloging/monograph_parts.txt b/docs/cataloging/monograph_parts.txt
similarity index 100%
rename from cataloging/monograph_parts.txt
rename to docs/cataloging/monograph_parts.txt
diff --git a/cataloging/overlay_record_3950_import.txt b/docs/cataloging/overlay_record_3950_import.txt
similarity index 100%
rename from cataloging/overlay_record_3950_import.txt
rename to docs/cataloging/overlay_record_3950_import.txt
diff --git a/circulation/README b/docs/circulation/README
similarity index 100%
rename from circulation/README
rename to docs/circulation/README
diff --git a/circulation/booking.txt b/docs/circulation/booking.txt
similarity index 100%
rename from circulation/booking.txt
rename to docs/circulation/booking.txt
diff --git a/circulation/circulating_items.txt b/docs/circulation/circulating_items.txt
similarity index 100%
rename from circulation/circulating_items.txt
rename to docs/circulation/circulating_items.txt
diff --git a/development/README b/docs/development/README
similarity index 100%
rename from development/README
rename to docs/development/README
diff --git a/development/updating_translations_launchpad.txt b/docs/development/updating_translations_launchpad.txt
similarity index 100%
rename from development/updating_translations_launchpad.txt
rename to docs/development/updating_translations_launchpad.txt
diff --git a/installation/edi_setup.txt b/docs/installation/edi_setup.txt
similarity index 100%
rename from installation/edi_setup.txt
rename to docs/installation/edi_setup.txt
diff --git a/installation/server_installation.txt b/docs/installation/server_installation.txt
similarity index 100%
rename from installation/server_installation.txt
rename to docs/installation/server_installation.txt
diff --git a/installation/server_upgrade.txt b/docs/installation/server_upgrade.txt
similarity index 100%
rename from installation/server_upgrade.txt
rename to docs/installation/server_upgrade.txt
diff --git a/installation/system_requirements.txt b/docs/installation/system_requirements.txt
similarity index 100%
rename from installation/system_requirements.txt
rename to docs/installation/system_requirements.txt
diff --git a/licensing.txt b/docs/licensing.txt
similarity index 100%
rename from licensing.txt
rename to docs/licensing.txt
diff --git a/media/1.png b/docs/media/1.png
similarity index 100%
rename from media/1.png
rename to docs/media/1.png
diff --git a/media/10.png b/docs/media/10.png
similarity index 100%
rename from media/10.png
rename to docs/media/10.png
diff --git a/media/11.png b/docs/media/11.png
similarity index 100%
rename from media/11.png
rename to docs/media/11.png
diff --git a/media/12.png b/docs/media/12.png
similarity index 100%
rename from media/12.png
rename to docs/media/12.png
diff --git a/media/13.png b/docs/media/13.png
similarity index 100%
rename from media/13.png
rename to docs/media/13.png
diff --git a/media/14.png b/docs/media/14.png
similarity index 100%
rename from media/14.png
rename to docs/media/14.png
diff --git a/media/15.png b/docs/media/15.png
similarity index 100%
rename from media/15.png
rename to docs/media/15.png
diff --git a/media/2.png b/docs/media/2.png
similarity index 100%
rename from media/2.png
rename to docs/media/2.png
diff --git a/media/3.png b/docs/media/3.png
similarity index 100%
rename from media/3.png
rename to docs/media/3.png
diff --git a/media/4.png b/docs/media/4.png
similarity index 100%
rename from media/4.png
rename to docs/media/4.png
diff --git a/media/5.png b/docs/media/5.png
similarity index 100%
rename from media/5.png
rename to docs/media/5.png
diff --git a/media/6.png b/docs/media/6.png
similarity index 100%
rename from media/6.png
rename to docs/media/6.png
diff --git a/media/7.png b/docs/media/7.png
similarity index 100%
rename from media/7.png
rename to docs/media/7.png
diff --git a/media/8.png b/docs/media/8.png
similarity index 100%
rename from media/8.png
rename to docs/media/8.png
diff --git a/media/9.png b/docs/media/9.png
similarity index 100%
rename from media/9.png
rename to docs/media/9.png
diff --git a/media/Authority_Control_Sets1.jpg b/docs/media/Authority_Control_Sets1.jpg
similarity index 100%
rename from media/Authority_Control_Sets1.jpg
rename to docs/media/Authority_Control_Sets1.jpg
diff --git a/media/Authority_Control_Sets1.jpg.1 b/docs/media/Authority_Control_Sets1.jpg.1
similarity index 100%
rename from media/Authority_Control_Sets1.jpg.1
rename to docs/media/Authority_Control_Sets1.jpg.1
diff --git a/media/Authority_Control_Sets2.jpg b/docs/media/Authority_Control_Sets2.jpg
similarity index 100%
rename from media/Authority_Control_Sets2.jpg
rename to docs/media/Authority_Control_Sets2.jpg
diff --git a/media/Authority_Control_Sets2.jpg.1 b/docs/media/Authority_Control_Sets2.jpg.1
similarity index 100%
rename from media/Authority_Control_Sets2.jpg.1
rename to docs/media/Authority_Control_Sets2.jpg.1
diff --git a/media/Authority_Control_Sets3.jpg b/docs/media/Authority_Control_Sets3.jpg
similarity index 100%
rename from media/Authority_Control_Sets3.jpg
rename to docs/media/Authority_Control_Sets3.jpg
diff --git a/media/Authority_Control_Sets3.jpg.1 b/docs/media/Authority_Control_Sets3.jpg.1
similarity index 100%
rename from media/Authority_Control_Sets3.jpg.1
rename to docs/media/Authority_Control_Sets3.jpg.1
diff --git a/media/Authority_Control_Sets4.jpg b/docs/media/Authority_Control_Sets4.jpg
similarity index 100%
rename from media/Authority_Control_Sets4.jpg
rename to docs/media/Authority_Control_Sets4.jpg
diff --git a/media/Authority_Control_Sets4.jpg.1 b/docs/media/Authority_Control_Sets4.jpg.1
similarity index 100%
rename from media/Authority_Control_Sets4.jpg.1
rename to docs/media/Authority_Control_Sets4.jpg.1
diff --git a/media/Authority_Control_Sets5.jpg b/docs/media/Authority_Control_Sets5.jpg
similarity index 100%
rename from media/Authority_Control_Sets5.jpg
rename to docs/media/Authority_Control_Sets5.jpg
diff --git a/media/Authority_Control_Sets5.jpg.1 b/docs/media/Authority_Control_Sets5.jpg.1
similarity index 100%
rename from media/Authority_Control_Sets5.jpg.1
rename to docs/media/Authority_Control_Sets5.jpg.1
diff --git a/media/Authority_Control_Sets6.jpg b/docs/media/Authority_Control_Sets6.jpg
similarity index 100%
rename from media/Authority_Control_Sets6.jpg
rename to docs/media/Authority_Control_Sets6.jpg
diff --git a/media/Authority_Control_Sets6.jpg.1 b/docs/media/Authority_Control_Sets6.jpg.1
similarity index 100%
rename from media/Authority_Control_Sets6.jpg.1
rename to docs/media/Authority_Control_Sets6.jpg.1
diff --git a/media/Authority_Control_Sets7.jpg b/docs/media/Authority_Control_Sets7.jpg
similarity index 100%
rename from media/Authority_Control_Sets7.jpg
rename to docs/media/Authority_Control_Sets7.jpg
diff --git a/media/Authority_Control_Sets7.jpg.1 b/docs/media/Authority_Control_Sets7.jpg.1
similarity index 100%
rename from media/Authority_Control_Sets7.jpg.1
rename to docs/media/Authority_Control_Sets7.jpg.1
diff --git a/media/Authority_Control_Sets8.jpg b/docs/media/Authority_Control_Sets8.jpg
similarity index 100%
rename from media/Authority_Control_Sets8.jpg
rename to docs/media/Authority_Control_Sets8.jpg
diff --git a/media/Authority_Control_Sets8.jpg.1 b/docs/media/Authority_Control_Sets8.jpg.1
similarity index 100%
rename from media/Authority_Control_Sets8.jpg.1
rename to docs/media/Authority_Control_Sets8.jpg.1
diff --git a/media/Authority_Control_Sets9.jpg b/docs/media/Authority_Control_Sets9.jpg
similarity index 100%
rename from media/Authority_Control_Sets9.jpg
rename to docs/media/Authority_Control_Sets9.jpg
diff --git a/media/Authority_Control_Sets9.jpg.1 b/docs/media/Authority_Control_Sets9.jpg.1
similarity index 100%
rename from media/Authority_Control_Sets9.jpg.1
rename to docs/media/Authority_Control_Sets9.jpg.1
diff --git a/media/Auto_Suggest_in_Catalog_Search1.jpg b/docs/media/Auto_Suggest_in_Catalog_Search1.jpg
similarity index 100%
rename from media/Auto_Suggest_in_Catalog_Search1.jpg
rename to docs/media/Auto_Suggest_in_Catalog_Search1.jpg
diff --git a/media/Auto_Suggest_in_Catalog_Search2.jpg b/docs/media/Auto_Suggest_in_Catalog_Search2.jpg
similarity index 100%
rename from media/Auto_Suggest_in_Catalog_Search2.jpg
rename to docs/media/Auto_Suggest_in_Catalog_Search2.jpg
diff --git a/media/Batch_Importing_MARC_Records1.jpg b/docs/media/Batch_Importing_MARC_Records1.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records1.jpg
rename to docs/media/Batch_Importing_MARC_Records1.jpg
diff --git a/media/Batch_Importing_MARC_Records10.jpg b/docs/media/Batch_Importing_MARC_Records10.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records10.jpg
rename to docs/media/Batch_Importing_MARC_Records10.jpg
diff --git a/media/Batch_Importing_MARC_Records11.jpg b/docs/media/Batch_Importing_MARC_Records11.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records11.jpg
rename to docs/media/Batch_Importing_MARC_Records11.jpg
diff --git a/media/Batch_Importing_MARC_Records12.jpg b/docs/media/Batch_Importing_MARC_Records12.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records12.jpg
rename to docs/media/Batch_Importing_MARC_Records12.jpg
diff --git a/media/Batch_Importing_MARC_Records13.jpg b/docs/media/Batch_Importing_MARC_Records13.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records13.jpg
rename to docs/media/Batch_Importing_MARC_Records13.jpg
diff --git a/media/Batch_Importing_MARC_Records14.jpg b/docs/media/Batch_Importing_MARC_Records14.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records14.jpg
rename to docs/media/Batch_Importing_MARC_Records14.jpg
diff --git a/media/Batch_Importing_MARC_Records15.jpg b/docs/media/Batch_Importing_MARC_Records15.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records15.jpg
rename to docs/media/Batch_Importing_MARC_Records15.jpg
diff --git a/media/Batch_Importing_MARC_Records2.jpg b/docs/media/Batch_Importing_MARC_Records2.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records2.jpg
rename to docs/media/Batch_Importing_MARC_Records2.jpg
diff --git a/media/Batch_Importing_MARC_Records3.jpg b/docs/media/Batch_Importing_MARC_Records3.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records3.jpg
rename to docs/media/Batch_Importing_MARC_Records3.jpg
diff --git a/media/Batch_Importing_MARC_Records4.jpg b/docs/media/Batch_Importing_MARC_Records4.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records4.jpg
rename to docs/media/Batch_Importing_MARC_Records4.jpg
diff --git a/media/Batch_Importing_MARC_Records5.jpg b/docs/media/Batch_Importing_MARC_Records5.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records5.jpg
rename to docs/media/Batch_Importing_MARC_Records5.jpg
diff --git a/media/Batch_Importing_MARC_Records6.jpg b/docs/media/Batch_Importing_MARC_Records6.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records6.jpg
rename to docs/media/Batch_Importing_MARC_Records6.jpg
diff --git a/media/Batch_Importing_MARC_Records7.jpg b/docs/media/Batch_Importing_MARC_Records7.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records7.jpg
rename to docs/media/Batch_Importing_MARC_Records7.jpg
diff --git a/media/Batch_Importing_MARC_Records8.jpg b/docs/media/Batch_Importing_MARC_Records8.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records8.jpg
rename to docs/media/Batch_Importing_MARC_Records8.jpg
diff --git a/media/Batch_Importing_MARC_Records9.jpg b/docs/media/Batch_Importing_MARC_Records9.jpg
similarity index 100%
rename from media/Batch_Importing_MARC_Records9.jpg
rename to docs/media/Batch_Importing_MARC_Records9.jpg
diff --git a/media/Call_Number_Prefixes_and_Suffixes_2_21.jpg b/docs/media/Call_Number_Prefixes_and_Suffixes_2_21.jpg
similarity index 100%
rename from media/Call_Number_Prefixes_and_Suffixes_2_21.jpg
rename to docs/media/Call_Number_Prefixes_and_Suffixes_2_21.jpg
diff --git a/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg b/docs/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg
similarity index 100%
rename from media/Call_Number_Prefixes_and_Suffixes_2_22.jpg
rename to docs/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg
diff --git a/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg.1 b/docs/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg.1
similarity index 100%
rename from media/Call_Number_Prefixes_and_Suffixes_2_22.jpg.1
rename to docs/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg.1
diff --git a/media/Customizable_Toolbar1.jpg b/docs/media/Customizable_Toolbar1.jpg
similarity index 100%
rename from media/Customizable_Toolbar1.jpg
rename to docs/media/Customizable_Toolbar1.jpg
diff --git a/media/Customizable_Toolbar2.jpg b/docs/media/Customizable_Toolbar2.jpg
similarity index 100%
rename from media/Customizable_Toolbar2.jpg
rename to docs/media/Customizable_Toolbar2.jpg
diff --git a/media/Customizable_Toolbar3.jpg b/docs/media/Customizable_Toolbar3.jpg
similarity index 100%
rename from media/Customizable_Toolbar3.jpg
rename to docs/media/Customizable_Toolbar3.jpg
diff --git a/media/Customizable_Toolbar4.jpg b/docs/media/Customizable_Toolbar4.jpg
similarity index 100%
rename from media/Customizable_Toolbar4.jpg
rename to docs/media/Customizable_Toolbar4.jpg
diff --git a/media/Double_Click1.jpg b/docs/media/Double_Click1.jpg
similarity index 100%
rename from media/Double_Click1.jpg
rename to docs/media/Double_Click1.jpg
diff --git a/media/Double_Click2.jpg b/docs/media/Double_Click2.jpg
similarity index 100%
rename from media/Double_Click2.jpg
rename to docs/media/Double_Click2.jpg
diff --git a/media/Double_Click3.jpg b/docs/media/Double_Click3.jpg
similarity index 100%
rename from media/Double_Click3.jpg
rename to docs/media/Double_Click3.jpg
diff --git a/media/My_Lists1.jpg b/docs/media/My_Lists1.jpg
similarity index 100%
rename from media/My_Lists1.jpg
rename to docs/media/My_Lists1.jpg
diff --git a/media/My_Lists3.jpg b/docs/media/My_Lists3.jpg
similarity index 100%
rename from media/My_Lists3.jpg
rename to docs/media/My_Lists3.jpg
diff --git a/media/My_Lists4.jpg b/docs/media/My_Lists4.jpg
similarity index 100%
rename from media/My_Lists4.jpg
rename to docs/media/My_Lists4.jpg
diff --git a/media/My_Lists5.jpg b/docs/media/My_Lists5.jpg
similarity index 100%
rename from media/My_Lists5.jpg
rename to docs/media/My_Lists5.jpg
diff --git a/media/My_Lists6.jpg b/docs/media/My_Lists6.jpg
similarity index 100%
rename from media/My_Lists6.jpg
rename to docs/media/My_Lists6.jpg
diff --git a/media/My_Lists7.jpg b/docs/media/My_Lists7.jpg
similarity index 100%
rename from media/My_Lists7.jpg
rename to docs/media/My_Lists7.jpg
diff --git a/media/New_Tab_Button1.jpg b/docs/media/New_Tab_Button1.jpg
similarity index 100%
rename from media/New_Tab_Button1.jpg
rename to docs/media/New_Tab_Button1.jpg
diff --git a/media/Overlay_Existing_Record_via_Z39_50_Import1.jpg b/docs/media/Overlay_Existing_Record_via_Z39_50_Import1.jpg
similarity index 100%
rename from media/Overlay_Existing_Record_via_Z39_50_Import1.jpg
rename to docs/media/Overlay_Existing_Record_via_Z39_50_Import1.jpg
diff --git a/media/Overlay_Existing_Record_via_Z39_50_Import2.jpg b/docs/media/Overlay_Existing_Record_via_Z39_50_Import2.jpg
similarity index 100%
rename from media/Overlay_Existing_Record_via_Z39_50_Import2.jpg
rename to docs/media/Overlay_Existing_Record_via_Z39_50_Import2.jpg
diff --git a/media/Overlay_Existing_Record_via_Z39_50_Import3.jpg b/docs/media/Overlay_Existing_Record_via_Z39_50_Import3.jpg
similarity index 100%
rename from media/Overlay_Existing_Record_via_Z39_50_Import3.jpg
rename to docs/media/Overlay_Existing_Record_via_Z39_50_Import3.jpg
diff --git a/media/Overlay_Existing_Record_via_Z39_50_Import4.jpg b/docs/media/Overlay_Existing_Record_via_Z39_50_Import4.jpg
similarity index 100%
rename from media/Overlay_Existing_Record_via_Z39_50_Import4.jpg
rename to docs/media/Overlay_Existing_Record_via_Z39_50_Import4.jpg
diff --git a/media/Overlay_Existing_Record_via_Z39_50_Import5.jpg b/docs/media/Overlay_Existing_Record_via_Z39_50_Import5.jpg
similarity index 100%
rename from media/Overlay_Existing_Record_via_Z39_50_Import5.jpg
rename to docs/media/Overlay_Existing_Record_via_Z39_50_Import5.jpg
diff --git a/media/Overlay_Existing_Record_via_Z39_50_Import6.jpg b/docs/media/Overlay_Existing_Record_via_Z39_50_Import6.jpg
similarity index 100%
rename from media/Overlay_Existing_Record_via_Z39_50_Import6.jpg
rename to docs/media/Overlay_Existing_Record_via_Z39_50_Import6.jpg
diff --git a/media/Receive_Items_From_an_Invoice1.jpg b/docs/media/Receive_Items_From_an_Invoice1.jpg
similarity index 100%
rename from media/Receive_Items_From_an_Invoice1.jpg
rename to docs/media/Receive_Items_From_an_Invoice1.jpg
diff --git a/media/Receive_Items_From_an_Invoice2.jpg b/docs/media/Receive_Items_From_an_Invoice2.jpg
similarity index 100%
rename from media/Receive_Items_From_an_Invoice2.jpg
rename to docs/media/Receive_Items_From_an_Invoice2.jpg
diff --git a/media/Receive_Items_From_an_Invoice3.jpg b/docs/media/Receive_Items_From_an_Invoice3.jpg
similarity index 100%
rename from media/Receive_Items_From_an_Invoice3.jpg
rename to docs/media/Receive_Items_From_an_Invoice3.jpg
diff --git a/media/Receive_Items_From_an_Invoice4.jpg b/docs/media/Receive_Items_From_an_Invoice4.jpg
similarity index 100%
rename from media/Receive_Items_From_an_Invoice4.jpg
rename to docs/media/Receive_Items_From_an_Invoice4.jpg
diff --git a/media/Receive_Items_From_an_Invoice5.jpg b/docs/media/Receive_Items_From_an_Invoice5.jpg
similarity index 100%
rename from media/Receive_Items_From_an_Invoice5.jpg
rename to docs/media/Receive_Items_From_an_Invoice5.jpg
diff --git a/media/Receive_Items_From_an_Invoice6.jpg b/docs/media/Receive_Items_From_an_Invoice6.jpg
similarity index 100%
rename from media/Receive_Items_From_an_Invoice6.jpg
rename to docs/media/Receive_Items_From_an_Invoice6.jpg
diff --git a/media/Receive_Items_From_an_Invoice7.jpg b/docs/media/Receive_Items_From_an_Invoice7.jpg
similarity index 100%
rename from media/Receive_Items_From_an_Invoice7.jpg
rename to docs/media/Receive_Items_From_an_Invoice7.jpg
diff --git a/media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg b/docs/media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg
similarity index 100%
rename from media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg
rename to docs/media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg
diff --git a/media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg b/docs/media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg
similarity index 100%
rename from media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg
rename to docs/media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg
diff --git a/media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg b/docs/media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg
similarity index 100%
rename from media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg
rename to docs/media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg
diff --git a/media/SMS_Text_Messaging1.jpg b/docs/media/SMS_Text_Messaging1.jpg
similarity index 100%
rename from media/SMS_Text_Messaging1.jpg
rename to docs/media/SMS_Text_Messaging1.jpg
diff --git a/media/SMS_Text_Messaging10.jpg b/docs/media/SMS_Text_Messaging10.jpg
similarity index 100%
rename from media/SMS_Text_Messaging10.jpg
rename to docs/media/SMS_Text_Messaging10.jpg
diff --git a/media/SMS_Text_Messaging11.jpg b/docs/media/SMS_Text_Messaging11.jpg
similarity index 100%
rename from media/SMS_Text_Messaging11.jpg
rename to docs/media/SMS_Text_Messaging11.jpg
diff --git a/media/SMS_Text_Messaging12.jpg b/docs/media/SMS_Text_Messaging12.jpg
similarity index 100%
rename from media/SMS_Text_Messaging12.jpg
rename to docs/media/SMS_Text_Messaging12.jpg
diff --git a/media/SMS_Text_Messaging13.jpg b/docs/media/SMS_Text_Messaging13.jpg
similarity index 100%
rename from media/SMS_Text_Messaging13.jpg
rename to docs/media/SMS_Text_Messaging13.jpg
diff --git a/media/SMS_Text_Messaging2.jpg b/docs/media/SMS_Text_Messaging2.jpg
similarity index 100%
rename from media/SMS_Text_Messaging2.jpg
rename to docs/media/SMS_Text_Messaging2.jpg
diff --git a/media/SMS_Text_Messaging3.jpg b/docs/media/SMS_Text_Messaging3.jpg
similarity index 100%
rename from media/SMS_Text_Messaging3.jpg
rename to docs/media/SMS_Text_Messaging3.jpg
diff --git a/media/SMS_Text_Messaging4.jpg b/docs/media/SMS_Text_Messaging4.jpg
similarity index 100%
rename from media/SMS_Text_Messaging4.jpg
rename to docs/media/SMS_Text_Messaging4.jpg
diff --git a/media/SMS_Text_Messaging5.jpg b/docs/media/SMS_Text_Messaging5.jpg
similarity index 100%
rename from media/SMS_Text_Messaging5.jpg
rename to docs/media/SMS_Text_Messaging5.jpg
diff --git a/media/SMS_Text_Messaging6.jpg b/docs/media/SMS_Text_Messaging6.jpg
similarity index 100%
rename from media/SMS_Text_Messaging6.jpg
rename to docs/media/SMS_Text_Messaging6.jpg
diff --git a/media/SMS_Text_Messaging7.jpg b/docs/media/SMS_Text_Messaging7.jpg
similarity index 100%
rename from media/SMS_Text_Messaging7.jpg
rename to docs/media/SMS_Text_Messaging7.jpg
diff --git a/media/SMS_Text_Messaging8.jpg b/docs/media/SMS_Text_Messaging8.jpg
similarity index 100%
rename from media/SMS_Text_Messaging8.jpg
rename to docs/media/SMS_Text_Messaging8.jpg
diff --git a/media/SMS_Text_Messaging9.jpg b/docs/media/SMS_Text_Messaging9.jpg
similarity index 100%
rename from media/SMS_Text_Messaging9.jpg
rename to docs/media/SMS_Text_Messaging9.jpg
diff --git a/media/Saved_Catalog_Searches_2_21.jpg b/docs/media/Saved_Catalog_Searches_2_21.jpg
similarity index 100%
rename from media/Saved_Catalog_Searches_2_21.jpg
rename to docs/media/Saved_Catalog_Searches_2_21.jpg
diff --git a/media/Saved_Catalog_Searches_2_21.jpg.1 b/docs/media/Saved_Catalog_Searches_2_21.jpg.1
similarity index 100%
rename from media/Saved_Catalog_Searches_2_21.jpg.1
rename to docs/media/Saved_Catalog_Searches_2_21.jpg.1
diff --git a/media/Saved_Catalog_Searches_2_22.jpg b/docs/media/Saved_Catalog_Searches_2_22.jpg
similarity index 100%
rename from media/Saved_Catalog_Searches_2_22.jpg
rename to docs/media/Saved_Catalog_Searches_2_22.jpg
diff --git a/media/Saved_Catalog_Searches_2_22.jpg.1 b/docs/media/Saved_Catalog_Searches_2_22.jpg.1
similarity index 100%
rename from media/Saved_Catalog_Searches_2_22.jpg.1
rename to docs/media/Saved_Catalog_Searches_2_22.jpg.1
diff --git a/media/Search_Results1.jpg b/docs/media/Search_Results1.jpg
similarity index 100%
rename from media/Search_Results1.jpg
rename to docs/media/Search_Results1.jpg
diff --git a/media/Sorting_Columns2.jpg b/docs/media/Sorting_Columns2.jpg
similarity index 100%
rename from media/Sorting_Columns2.jpg
rename to docs/media/Sorting_Columns2.jpg
diff --git a/media/Sorting_Columns3.jpg b/docs/media/Sorting_Columns3.jpg
similarity index 100%
rename from media/Sorting_Columns3.jpg
rename to docs/media/Sorting_Columns3.jpg
diff --git a/media/Sorting_Columns3.jpg.1 b/docs/media/Sorting_Columns3.jpg.1
similarity index 100%
rename from media/Sorting_Columns3.jpg.1
rename to docs/media/Sorting_Columns3.jpg.1
diff --git a/media/Sorting_Columns4.jpg b/docs/media/Sorting_Columns4.jpg
similarity index 100%
rename from media/Sorting_Columns4.jpg
rename to docs/media/Sorting_Columns4.jpg
diff --git a/media/Sorting_Columns5.jpg b/docs/media/Sorting_Columns5.jpg
similarity index 100%
rename from media/Sorting_Columns5.jpg
rename to docs/media/Sorting_Columns5.jpg
diff --git a/media/Target_Pickup_Lib1.jpg b/docs/media/Target_Pickup_Lib1.jpg
similarity index 100%
rename from media/Target_Pickup_Lib1.jpg
rename to docs/media/Target_Pickup_Lib1.jpg
diff --git a/media/Target_Pickup_Lib2.jpg b/docs/media/Target_Pickup_Lib2.jpg
similarity index 100%
rename from media/Target_Pickup_Lib2.jpg
rename to docs/media/Target_Pickup_Lib2.jpg
diff --git a/media/User_Activity_Types1A.jpg b/docs/media/User_Activity_Types1A.jpg
similarity index 100%
rename from media/User_Activity_Types1A.jpg
rename to docs/media/User_Activity_Types1A.jpg
diff --git a/media/User_Activity_Types2A.jpg b/docs/media/User_Activity_Types2A.jpg
similarity index 100%
rename from media/User_Activity_Types2A.jpg
rename to docs/media/User_Activity_Types2A.jpg
diff --git a/media/Vandelay_Integration_into_Acquisitions1.jpg b/docs/media/Vandelay_Integration_into_Acquisitions1.jpg
similarity index 100%
rename from media/Vandelay_Integration_into_Acquisitions1.jpg
rename to docs/media/Vandelay_Integration_into_Acquisitions1.jpg
diff --git a/media/Vandelay_Integration_into_Acquisitions2.jpg b/docs/media/Vandelay_Integration_into_Acquisitions2.jpg
similarity index 100%
rename from media/Vandelay_Integration_into_Acquisitions2.jpg
rename to docs/media/Vandelay_Integration_into_Acquisitions2.jpg
diff --git a/media/Vandelay_Integration_into_Acquisitions3.jpg b/docs/media/Vandelay_Integration_into_Acquisitions3.jpg
similarity index 100%
rename from media/Vandelay_Integration_into_Acquisitions3.jpg
rename to docs/media/Vandelay_Integration_into_Acquisitions3.jpg
diff --git a/media/Vandelay_Integration_into_Acquisitions4.jpg b/docs/media/Vandelay_Integration_into_Acquisitions4.jpg
similarity index 100%
rename from media/Vandelay_Integration_into_Acquisitions4.jpg
rename to docs/media/Vandelay_Integration_into_Acquisitions4.jpg
diff --git a/media/Vandelay_Integration_into_Acquisitions5.jpg b/docs/media/Vandelay_Integration_into_Acquisitions5.jpg
similarity index 100%
rename from media/Vandelay_Integration_into_Acquisitions5.jpg
rename to docs/media/Vandelay_Integration_into_Acquisitions5.jpg
diff --git a/media/Vandelay_Integration_into_Acquisitions6.jpg b/docs/media/Vandelay_Integration_into_Acquisitions6.jpg
similarity index 100%
rename from media/Vandelay_Integration_into_Acquisitions6.jpg
rename to docs/media/Vandelay_Integration_into_Acquisitions6.jpg
diff --git a/media/acq_activate.png b/docs/media/acq_activate.png
similarity index 100%
rename from media/acq_activate.png
rename to docs/media/acq_activate.png
diff --git a/media/acq_apply_claim_policy.png b/docs/media/acq_apply_claim_policy.png
similarity index 100%
rename from media/acq_apply_claim_policy.png
rename to docs/media/acq_apply_claim_policy.png
diff --git a/media/acq_brief_record-2.png b/docs/media/acq_brief_record-2.png
similarity index 100%
rename from media/acq_brief_record-2.png
rename to docs/media/acq_brief_record-2.png
diff --git a/media/acq_brief_record.png b/docs/media/acq_brief_record.png
similarity index 100%
rename from media/acq_brief_record.png
rename to docs/media/acq_brief_record.png
diff --git a/media/acq_cancel_copy.png b/docs/media/acq_cancel_copy.png
similarity index 100%
rename from media/acq_cancel_copy.png
rename to docs/media/acq_cancel_copy.png
diff --git a/media/acq_cancel_line_items.png b/docs/media/acq_cancel_line_items.png
similarity index 100%
rename from media/acq_cancel_line_items.png
rename to docs/media/acq_cancel_line_items.png
diff --git a/media/acq_claim_item-2.png b/docs/media/acq_claim_item-2.png
similarity index 100%
rename from media/acq_claim_item-2.png
rename to docs/media/acq_claim_item-2.png
diff --git a/media/acq_claim_item-3.png b/docs/media/acq_claim_item-3.png
similarity index 100%
rename from media/acq_claim_item-3.png
rename to docs/media/acq_claim_item-3.png
diff --git a/media/acq_claim_item-4.png b/docs/media/acq_claim_item-4.png
similarity index 100%
rename from media/acq_claim_item-4.png
rename to docs/media/acq_claim_item-4.png
diff --git a/media/acq_claim_item-5.png b/docs/media/acq_claim_item-5.png
similarity index 100%
rename from media/acq_claim_item-5.png
rename to docs/media/acq_claim_item-5.png
diff --git a/media/acq_claim_item.png b/docs/media/acq_claim_item.png
similarity index 100%
rename from media/acq_claim_item.png
rename to docs/media/acq_claim_item.png
diff --git a/media/acq_export_list.png b/docs/media/acq_export_list.png
similarity index 100%
rename from media/acq_export_list.png
rename to docs/media/acq_export_list.png
diff --git a/media/acq_funds-2.png b/docs/media/acq_funds-2.png
similarity index 100%
rename from media/acq_funds-2.png
rename to docs/media/acq_funds-2.png
diff --git a/media/acq_funds.png b/docs/media/acq_funds.png
similarity index 100%
rename from media/acq_funds.png
rename to docs/media/acq_funds.png
diff --git a/media/acq_invoice_blanket.png b/docs/media/acq_invoice_blanket.png
similarity index 100%
rename from media/acq_invoice_blanket.png
rename to docs/media/acq_invoice_blanket.png
diff --git a/media/acq_invoice_line_items.png b/docs/media/acq_invoice_line_items.png
similarity index 100%
rename from media/acq_invoice_line_items.png
rename to docs/media/acq_invoice_line_items.png
diff --git a/media/acq_invoice_link.png b/docs/media/acq_invoice_link.png
similarity index 100%
rename from media/acq_invoice_link.png
rename to docs/media/acq_invoice_link.png
diff --git a/media/acq_invoice_purchase_order.png b/docs/media/acq_invoice_purchase_order.png
similarity index 100%
rename from media/acq_invoice_purchase_order.png
rename to docs/media/acq_invoice_purchase_order.png
diff --git a/media/acq_invoice_view-2.png b/docs/media/acq_invoice_view-2.png
similarity index 100%
rename from media/acq_invoice_view-2.png
rename to docs/media/acq_invoice_view-2.png
diff --git a/media/acq_invoice_view.png b/docs/media/acq_invoice_view.png
similarity index 100%
rename from media/acq_invoice_view.png
rename to docs/media/acq_invoice_view.png
diff --git a/media/acq_line_items_add_copies-2.png b/docs/media/acq_line_items_add_copies-2.png
similarity index 100%
rename from media/acq_line_items_add_copies-2.png
rename to docs/media/acq_line_items_add_copies-2.png
diff --git a/media/acq_line_items_add_copies-3.png b/docs/media/acq_line_items_add_copies-3.png
similarity index 100%
rename from media/acq_line_items_add_copies-3.png
rename to docs/media/acq_line_items_add_copies-3.png
diff --git a/media/acq_line_items_add_copies.png b/docs/media/acq_line_items_add_copies.png
similarity index 100%
rename from media/acq_line_items_add_copies.png
rename to docs/media/acq_line_items_add_copies.png
diff --git a/media/acq_line_items_add_notes.png b/docs/media/acq_line_items_add_notes.png
similarity index 100%
rename from media/acq_line_items_add_notes.png
rename to docs/media/acq_line_items_add_notes.png
diff --git a/media/acq_line_items_alerts-2.png b/docs/media/acq_line_items_alerts-2.png
similarity index 100%
rename from media/acq_line_items_alerts-2.png
rename to docs/media/acq_line_items_alerts-2.png
diff --git a/media/acq_line_items_alerts.png b/docs/media/acq_line_items_alerts.png
similarity index 100%
rename from media/acq_line_items_alerts.png
rename to docs/media/acq_line_items_alerts.png
diff --git a/media/acq_line_items_link-2.png b/docs/media/acq_line_items_link-2.png
similarity index 100%
rename from media/acq_line_items_link-2.png
rename to docs/media/acq_line_items_link-2.png
diff --git a/media/acq_line_items_link.png b/docs/media/acq_line_items_link.png
similarity index 100%
rename from media/acq_line_items_link.png
rename to docs/media/acq_line_items_link.png
diff --git a/media/acq_line_items_update_barcodes.png b/docs/media/acq_line_items_update_barcodes.png
similarity index 100%
rename from media/acq_line_items_update_barcodes.png
rename to docs/media/acq_line_items_update_barcodes.png
diff --git a/media/acq_line_items_view_history.png b/docs/media/acq_line_items_view_history.png
similarity index 100%
rename from media/acq_line_items_view_history.png
rename to docs/media/acq_line_items_view_history.png
diff --git a/media/acq_line_items_worksheet.png b/docs/media/acq_line_items_worksheet.png
similarity index 100%
rename from media/acq_line_items_worksheet.png
rename to docs/media/acq_line_items_worksheet.png
diff --git a/media/acq_load_records.png b/docs/media/acq_load_records.png
similarity index 100%
rename from media/acq_load_records.png
rename to docs/media/acq_load_records.png
diff --git a/media/acq_marc_search-2.png b/docs/media/acq_marc_search-2.png
similarity index 100%
rename from media/acq_marc_search-2.png
rename to docs/media/acq_marc_search-2.png
diff --git a/media/acq_marc_search.png b/docs/media/acq_marc_search.png
similarity index 100%
rename from media/acq_marc_search.png
rename to docs/media/acq_marc_search.png
diff --git a/media/acq_purchase_order_add_charges.png b/docs/media/acq_purchase_order_add_charges.png
similarity index 100%
rename from media/acq_purchase_order_add_charges.png
rename to docs/media/acq_purchase_order_add_charges.png
diff --git a/media/acq_purchase_order_add_note.png b/docs/media/acq_purchase_order_add_note.png
similarity index 100%
rename from media/acq_purchase_order_add_note.png
rename to docs/media/acq_purchase_order_add_note.png
diff --git a/media/acq_purchase_order_create.png b/docs/media/acq_purchase_order_create.png
similarity index 100%
rename from media/acq_purchase_order_create.png
rename to docs/media/acq_purchase_order_create.png
diff --git a/media/acq_purchase_order_history.png b/docs/media/acq_purchase_order_history.png
similarity index 100%
rename from media/acq_purchase_order_history.png
rename to docs/media/acq_purchase_order_history.png
diff --git a/media/acq_purchase_order_name.png b/docs/media/acq_purchase_order_name.png
similarity index 100%
rename from media/acq_purchase_order_name.png
rename to docs/media/acq_purchase_order_name.png
diff --git a/media/acq_purchase_order_print.png b/docs/media/acq_purchase_order_print.png
similarity index 100%
rename from media/acq_purchase_order_print.png
rename to docs/media/acq_purchase_order_print.png
diff --git a/media/acq_purchase_order_split-2.png b/docs/media/acq_purchase_order_split-2.png
similarity index 100%
rename from media/acq_purchase_order_split-2.png
rename to docs/media/acq_purchase_order_split-2.png
diff --git a/media/acq_purchase_order_split.png b/docs/media/acq_purchase_order_split.png
similarity index 100%
rename from media/acq_purchase_order_split.png
rename to docs/media/acq_purchase_order_split.png
diff --git a/media/acq_purchase_order_view-2.png b/docs/media/acq_purchase_order_view-2.png
similarity index 100%
rename from media/acq_purchase_order_view-2.png
rename to docs/media/acq_purchase_order_view-2.png
diff --git a/media/acq_purchase_order_view.png b/docs/media/acq_purchase_order_view.png
similarity index 100%
rename from media/acq_purchase_order_view.png
rename to docs/media/acq_purchase_order_view.png
diff --git a/media/acq_search.png b/docs/media/acq_search.png
similarity index 100%
rename from media/acq_search.png
rename to docs/media/acq_search.png
diff --git a/media/acq_selection_clone.png b/docs/media/acq_selection_clone.png
similarity index 100%
rename from media/acq_selection_clone.png
rename to docs/media/acq_selection_clone.png
diff --git a/media/acq_selection_create.png b/docs/media/acq_selection_create.png
similarity index 100%
rename from media/acq_selection_create.png
rename to docs/media/acq_selection_create.png
diff --git a/media/acq_selection_mark_ready-2.png b/docs/media/acq_selection_mark_ready-2.png
similarity index 100%
rename from media/acq_selection_mark_ready-2.png
rename to docs/media/acq_selection_mark_ready-2.png
diff --git a/media/acq_selection_mark_ready.png b/docs/media/acq_selection_mark_ready.png
similarity index 100%
rename from media/acq_selection_mark_ready.png
rename to docs/media/acq_selection_mark_ready.png
diff --git a/media/acq_selection_merge.png b/docs/media/acq_selection_merge.png
similarity index 100%
rename from media/acq_selection_merge.png
rename to docs/media/acq_selection_merge.png
diff --git a/media/acq_workflow.jpg b/docs/media/acq_workflow.jpg
similarity index 100%
rename from media/acq_workflow.jpg
rename to docs/media/acq_workflow.jpg
diff --git a/media/add_holdings-1.png b/docs/media/add_holdings-1.png
similarity index 100%
rename from media/add_holdings-1.png
rename to docs/media/add_holdings-1.png
diff --git a/media/add_holdings-2.png b/docs/media/add_holdings-2.png
similarity index 100%
rename from media/add_holdings-2.png
rename to docs/media/add_holdings-2.png
diff --git a/media/add_holdings-3.png b/docs/media/add_holdings-3.png
similarity index 100%
rename from media/add_holdings-3.png
rename to docs/media/add_holdings-3.png
diff --git a/media/add_holdings-4.png b/docs/media/add_holdings-4.png
similarity index 100%
rename from media/add_holdings-4.png
rename to docs/media/add_holdings-4.png
diff --git a/media/add_holdings-5.png b/docs/media/add_holdings-5.png
similarity index 100%
rename from media/add_holdings-5.png
rename to docs/media/add_holdings-5.png
diff --git a/media/application-pdf.png b/docs/media/application-pdf.png
similarity index 100%
rename from media/application-pdf.png
rename to docs/media/application-pdf.png
diff --git a/media/ascv-distr.jpg b/docs/media/ascv-distr.jpg
similarity index 100%
rename from media/ascv-distr.jpg
rename to docs/media/ascv-distr.jpg
diff --git a/media/ascv-issues.jpg b/docs/media/ascv-issues.jpg
similarity index 100%
rename from media/ascv-issues.jpg
rename to docs/media/ascv-issues.jpg
diff --git a/media/ascv-sub.jpg b/docs/media/ascv-sub.jpg
similarity index 100%
rename from media/ascv-sub.jpg
rename to docs/media/ascv-sub.jpg
diff --git a/media/backdate_checkin.png b/docs/media/backdate_checkin.png
similarity index 100%
rename from media/backdate_checkin.png
rename to docs/media/backdate_checkin.png
diff --git a/media/backdate_post_checkin.png b/docs/media/backdate_post_checkin.png
similarity index 100%
rename from media/backdate_post_checkin.png
rename to docs/media/backdate_post_checkin.png
diff --git a/media/backdate_post_date.png b/docs/media/backdate_post_date.png
similarity index 100%
rename from media/backdate_post_date.png
rename to docs/media/backdate_post_date.png
diff --git a/media/backdate_red.png b/docs/media/backdate_red.png
similarity index 100%
rename from media/backdate_red.png
rename to docs/media/backdate_red.png
diff --git a/media/bills-1.png b/docs/media/bills-1.png
similarity index 100%
rename from media/bills-1.png
rename to docs/media/bills-1.png
diff --git a/media/bills-10.png b/docs/media/bills-10.png
similarity index 100%
rename from media/bills-10.png
rename to docs/media/bills-10.png
diff --git a/media/bills-11.png b/docs/media/bills-11.png
similarity index 100%
rename from media/bills-11.png
rename to docs/media/bills-11.png
diff --git a/media/bills-12.png b/docs/media/bills-12.png
similarity index 100%
rename from media/bills-12.png
rename to docs/media/bills-12.png
diff --git a/media/bills-13.png b/docs/media/bills-13.png
similarity index 100%
rename from media/bills-13.png
rename to docs/media/bills-13.png
diff --git a/media/bills-14.png b/docs/media/bills-14.png
similarity index 100%
rename from media/bills-14.png
rename to docs/media/bills-14.png
diff --git a/media/bills-15.png b/docs/media/bills-15.png
similarity index 100%
rename from media/bills-15.png
rename to docs/media/bills-15.png
diff --git a/media/bills-16.png b/docs/media/bills-16.png
similarity index 100%
rename from media/bills-16.png
rename to docs/media/bills-16.png
diff --git a/media/bills-17.png b/docs/media/bills-17.png
similarity index 100%
rename from media/bills-17.png
rename to docs/media/bills-17.png
diff --git a/media/bills-18.png b/docs/media/bills-18.png
similarity index 100%
rename from media/bills-18.png
rename to docs/media/bills-18.png
diff --git a/media/bills-19.png b/docs/media/bills-19.png
similarity index 100%
rename from media/bills-19.png
rename to docs/media/bills-19.png
diff --git a/media/bills-2.png b/docs/media/bills-2.png
similarity index 100%
rename from media/bills-2.png
rename to docs/media/bills-2.png
diff --git a/media/bills-20.png b/docs/media/bills-20.png
similarity index 100%
rename from media/bills-20.png
rename to docs/media/bills-20.png
diff --git a/media/bills-3.png b/docs/media/bills-3.png
similarity index 100%
rename from media/bills-3.png
rename to docs/media/bills-3.png
diff --git a/media/bills-4.png b/docs/media/bills-4.png
similarity index 100%
rename from media/bills-4.png
rename to docs/media/bills-4.png
diff --git a/media/bills-5.png b/docs/media/bills-5.png
similarity index 100%
rename from media/bills-5.png
rename to docs/media/bills-5.png
diff --git a/media/bills-6.png b/docs/media/bills-6.png
similarity index 100%
rename from media/bills-6.png
rename to docs/media/bills-6.png
diff --git a/media/bills-7.png b/docs/media/bills-7.png
similarity index 100%
rename from media/bills-7.png
rename to docs/media/bills-7.png
diff --git a/media/bills-8.png b/docs/media/bills-8.png
similarity index 100%
rename from media/bills-8.png
rename to docs/media/bills-8.png
diff --git a/media/bills-9.png b/docs/media/bills-9.png
similarity index 100%
rename from media/bills-9.png
rename to docs/media/bills-9.png
diff --git a/media/booking-cancel-1.png b/docs/media/booking-cancel-1.png
similarity index 100%
rename from media/booking-cancel-1.png
rename to docs/media/booking-cancel-1.png
diff --git a/media/booking-cancel-2.png b/docs/media/booking-cancel-2.png
similarity index 100%
rename from media/booking-cancel-2.png
rename to docs/media/booking-cancel-2.png
diff --git a/media/booking-cancel-3.png b/docs/media/booking-cancel-3.png
similarity index 100%
rename from media/booking-cancel-3.png
rename to docs/media/booking-cancel-3.png
diff --git a/media/booking-cancel-4.png b/docs/media/booking-cancel-4.png
similarity index 100%
rename from media/booking-cancel-4.png
rename to docs/media/booking-cancel-4.png
diff --git a/media/booking-capture-1.png b/docs/media/booking-capture-1.png
similarity index 100%
rename from media/booking-capture-1.png
rename to docs/media/booking-capture-1.png
diff --git a/media/booking-capture-2.png b/docs/media/booking-capture-2.png
similarity index 100%
rename from media/booking-capture-2.png
rename to docs/media/booking-capture-2.png
diff --git a/media/booking-capture-3.png b/docs/media/booking-capture-3.png
similarity index 100%
rename from media/booking-capture-3.png
rename to docs/media/booking-capture-3.png
diff --git a/media/booking-create-1.png b/docs/media/booking-create-1.png
similarity index 100%
rename from media/booking-create-1.png
rename to docs/media/booking-create-1.png
diff --git a/media/booking-create-2.png b/docs/media/booking-create-2.png
similarity index 100%
rename from media/booking-create-2.png
rename to docs/media/booking-create-2.png
diff --git a/media/booking-create-3.png b/docs/media/booking-create-3.png
similarity index 100%
rename from media/booking-create-3.png
rename to docs/media/booking-create-3.png
diff --git a/media/booking-create-4.png b/docs/media/booking-create-4.png
similarity index 100%
rename from media/booking-create-4.png
rename to docs/media/booking-create-4.png
diff --git a/media/booking-create-5.png b/docs/media/booking-create-5.png
similarity index 100%
rename from media/booking-create-5.png
rename to docs/media/booking-create-5.png
diff --git a/media/booking-create-6.png b/docs/media/booking-create-6.png
similarity index 100%
rename from media/booking-create-6.png
rename to docs/media/booking-create-6.png
diff --git a/media/booking-create-7.png b/docs/media/booking-create-7.png
similarity index 100%
rename from media/booking-create-7.png
rename to docs/media/booking-create-7.png
diff --git a/media/booking-create-8.png b/docs/media/booking-create-8.png
similarity index 100%
rename from media/booking-create-8.png
rename to docs/media/booking-create-8.png
diff --git a/media/booking-create-9.png b/docs/media/booking-create-9.png
similarity index 100%
rename from media/booking-create-9.png
rename to docs/media/booking-create-9.png
diff --git a/media/booking-create-bookable-1.png b/docs/media/booking-create-bookable-1.png
similarity index 100%
rename from media/booking-create-bookable-1.png
rename to docs/media/booking-create-bookable-1.png
diff --git a/media/booking-create-bookable-2.png b/docs/media/booking-create-bookable-2.png
similarity index 100%
rename from media/booking-create-bookable-2.png
rename to docs/media/booking-create-bookable-2.png
diff --git a/media/booking-create-bookable-3.png b/docs/media/booking-create-bookable-3.png
similarity index 100%
rename from media/booking-create-bookable-3.png
rename to docs/media/booking-create-bookable-3.png
diff --git a/media/booking-create-bookable-4.png b/docs/media/booking-create-bookable-4.png
similarity index 100%
rename from media/booking-create-bookable-4.png
rename to docs/media/booking-create-bookable-4.png
diff --git a/media/booking-create-bookable-5.png b/docs/media/booking-create-bookable-5.png
similarity index 100%
rename from media/booking-create-bookable-5.png
rename to docs/media/booking-create-bookable-5.png
diff --git a/media/booking-create-bookable-6.png b/docs/media/booking-create-bookable-6.png
similarity index 100%
rename from media/booking-create-bookable-6.png
rename to docs/media/booking-create-bookable-6.png
diff --git a/media/booking-create-module-1.png b/docs/media/booking-create-module-1.png
similarity index 100%
rename from media/booking-create-module-1.png
rename to docs/media/booking-create-module-1.png
diff --git a/media/booking-create-module-2.png b/docs/media/booking-create-module-2.png
similarity index 100%
rename from media/booking-create-module-2.png
rename to docs/media/booking-create-module-2.png
diff --git a/media/booking-create-module-3.png b/docs/media/booking-create-module-3.png
similarity index 100%
rename from media/booking-create-module-3.png
rename to docs/media/booking-create-module-3.png
diff --git a/media/booking-create-module-4.png b/docs/media/booking-create-module-4.png
similarity index 100%
rename from media/booking-create-module-4.png
rename to docs/media/booking-create-module-4.png
diff --git a/media/booking-create-resourcetype-1.png b/docs/media/booking-create-resourcetype-1.png
similarity index 100%
rename from media/booking-create-resourcetype-1.png
rename to docs/media/booking-create-resourcetype-1.png
diff --git a/media/booking-create-resourcetype-2.png b/docs/media/booking-create-resourcetype-2.png
similarity index 100%
rename from media/booking-create-resourcetype-2.png
rename to docs/media/booking-create-resourcetype-2.png
diff --git a/media/booking-create-resourcetype-3.png b/docs/media/booking-create-resourcetype-3.png
similarity index 100%
rename from media/booking-create-resourcetype-3.png
rename to docs/media/booking-create-resourcetype-3.png
diff --git a/media/booking-create-resourcetype-4.png b/docs/media/booking-create-resourcetype-4.png
similarity index 100%
rename from media/booking-create-resourcetype-4.png
rename to docs/media/booking-create-resourcetype-4.png
diff --git a/media/booking-create-resourcetype-5.png b/docs/media/booking-create-resourcetype-5.png
similarity index 100%
rename from media/booking-create-resourcetype-5.png
rename to docs/media/booking-create-resourcetype-5.png
diff --git a/media/booking-pickup-1.png b/docs/media/booking-pickup-1.png
similarity index 100%
rename from media/booking-pickup-1.png
rename to docs/media/booking-pickup-1.png
diff --git a/media/booking-pickup-2.png b/docs/media/booking-pickup-2.png
similarity index 100%
rename from media/booking-pickup-2.png
rename to docs/media/booking-pickup-2.png
diff --git a/media/booking-pickup-3.png b/docs/media/booking-pickup-3.png
similarity index 100%
rename from media/booking-pickup-3.png
rename to docs/media/booking-pickup-3.png
diff --git a/media/booking-pickup-module-1.png b/docs/media/booking-pickup-module-1.png
similarity index 100%
rename from media/booking-pickup-module-1.png
rename to docs/media/booking-pickup-module-1.png
diff --git a/media/booking-pull-1.png b/docs/media/booking-pull-1.png
similarity index 100%
rename from media/booking-pull-1.png
rename to docs/media/booking-pull-1.png
diff --git a/media/booking-pull-2.png b/docs/media/booking-pull-2.png
similarity index 100%
rename from media/booking-pull-2.png
rename to docs/media/booking-pull-2.png
diff --git a/media/booking-pull-3.png b/docs/media/booking-pull-3.png
similarity index 100%
rename from media/booking-pull-3.png
rename to docs/media/booking-pull-3.png
diff --git a/media/booking-return-2.png b/docs/media/booking-return-2.png
similarity index 100%
rename from media/booking-return-2.png
rename to docs/media/booking-return-2.png
diff --git a/media/booking-return-module-1.png b/docs/media/booking-return-module-1.png
similarity index 100%
rename from media/booking-return-module-1.png
rename to docs/media/booking-return-module-1.png
diff --git a/media/booking-return-module-2.png b/docs/media/booking-return-module-2.png
similarity index 100%
rename from media/booking-return-module-2.png
rename to docs/media/booking-return-module-2.png
diff --git a/media/booking-return-module-4.png b/docs/media/booking-return-module-4.png
similarity index 100%
rename from media/booking-return-module-4.png
rename to docs/media/booking-return-module-4.png
diff --git a/media/cap-wiz-cal.jpg b/docs/media/cap-wiz-cal.jpg
similarity index 100%
rename from media/cap-wiz-cal.jpg
rename to docs/media/cap-wiz-cal.jpg
diff --git a/media/cap-wiz-chan.jpg b/docs/media/cap-wiz-chan.jpg
similarity index 100%
rename from media/cap-wiz-chan.jpg
rename to docs/media/cap-wiz-chan.jpg
diff --git a/media/cap-wiz-chron.jpg b/docs/media/cap-wiz-chron.jpg
similarity index 100%
rename from media/cap-wiz-chron.jpg
rename to docs/media/cap-wiz-chron.jpg
diff --git a/media/cap-wiz-freq.jpg b/docs/media/cap-wiz-freq.jpg
similarity index 100%
rename from media/cap-wiz-freq.jpg
rename to docs/media/cap-wiz-freq.jpg
diff --git a/media/cap-wiz-num.jpg b/docs/media/cap-wiz-num.jpg
similarity index 100%
rename from media/cap-wiz-num.jpg
rename to docs/media/cap-wiz-num.jpg
diff --git a/media/catalogue-10.png b/docs/media/catalogue-10.png
similarity index 100%
rename from media/catalogue-10.png
rename to docs/media/catalogue-10.png
diff --git a/media/catalogue-11.png b/docs/media/catalogue-11.png
similarity index 100%
rename from media/catalogue-11.png
rename to docs/media/catalogue-11.png
diff --git a/media/catalogue-3.png b/docs/media/catalogue-3.png
similarity index 100%
rename from media/catalogue-3.png
rename to docs/media/catalogue-3.png
diff --git a/media/catalogue-4.png b/docs/media/catalogue-4.png
similarity index 100%
rename from media/catalogue-4.png
rename to docs/media/catalogue-4.png
diff --git a/media/catalogue-5.png b/docs/media/catalogue-5.png
similarity index 100%
rename from media/catalogue-5.png
rename to docs/media/catalogue-5.png
diff --git a/media/catalogue-6.png b/docs/media/catalogue-6.png
similarity index 100%
rename from media/catalogue-6.png
rename to docs/media/catalogue-6.png
diff --git a/media/catalogue-7.png b/docs/media/catalogue-7.png
similarity index 100%
rename from media/catalogue-7.png
rename to docs/media/catalogue-7.png
diff --git a/media/catalogue-8.png b/docs/media/catalogue-8.png
similarity index 100%
rename from media/catalogue-8.png
rename to docs/media/catalogue-8.png
diff --git a/media/catalogue-9.png b/docs/media/catalogue-9.png
similarity index 100%
rename from media/catalogue-9.png
rename to docs/media/catalogue-9.png
diff --git a/media/caution.png b/docs/media/caution.png
similarity index 100%
rename from media/caution.png
rename to docs/media/caution.png
diff --git a/media/ccbysa.png b/docs/media/ccbysa.png
similarity index 100%
rename from media/ccbysa.png
rename to docs/media/ccbysa.png
diff --git a/media/check_in_menu.png b/docs/media/check_in_menu.png
similarity index 100%
rename from media/check_in_menu.png
rename to docs/media/check_in_menu.png
diff --git a/media/checkin_barcode.png b/docs/media/checkin_barcode.png
similarity index 100%
rename from media/checkin_barcode.png
rename to docs/media/checkin_barcode.png
diff --git a/media/checkin_options.png b/docs/media/checkin_options.png
similarity index 100%
rename from media/checkin_options.png
rename to docs/media/checkin_options.png
diff --git a/media/checkout_item_barcode.png b/docs/media/checkout_item_barcode.png
similarity index 100%
rename from media/checkout_item_barcode.png
rename to docs/media/checkout_item_barcode.png
diff --git a/media/checkout_menu.png b/docs/media/checkout_menu.png
similarity index 100%
rename from media/checkout_menu.png
rename to docs/media/checkout_menu.png
diff --git a/media/circulation-1.png b/docs/media/circulation-1.png
similarity index 100%
rename from media/circulation-1.png
rename to docs/media/circulation-1.png
diff --git a/media/circulation-10.png b/docs/media/circulation-10.png
similarity index 100%
rename from media/circulation-10.png
rename to docs/media/circulation-10.png
diff --git a/media/circulation-11.png b/docs/media/circulation-11.png
similarity index 100%
rename from media/circulation-11.png
rename to docs/media/circulation-11.png
diff --git a/media/circulation-12.png b/docs/media/circulation-12.png
similarity index 100%
rename from media/circulation-12.png
rename to docs/media/circulation-12.png
diff --git a/media/circulation-13.png b/docs/media/circulation-13.png
similarity index 100%
rename from media/circulation-13.png
rename to docs/media/circulation-13.png
diff --git a/media/circulation-14.png b/docs/media/circulation-14.png
similarity index 100%
rename from media/circulation-14.png
rename to docs/media/circulation-14.png
diff --git a/media/circulation-15.png b/docs/media/circulation-15.png
similarity index 100%
rename from media/circulation-15.png
rename to docs/media/circulation-15.png
diff --git a/media/circulation-16.png b/docs/media/circulation-16.png
similarity index 100%
rename from media/circulation-16.png
rename to docs/media/circulation-16.png
diff --git a/media/circulation-17.png b/docs/media/circulation-17.png
similarity index 100%
rename from media/circulation-17.png
rename to docs/media/circulation-17.png
diff --git a/media/circulation-18.png b/docs/media/circulation-18.png
similarity index 100%
rename from media/circulation-18.png
rename to docs/media/circulation-18.png
diff --git a/media/circulation-19.png b/docs/media/circulation-19.png
similarity index 100%
rename from media/circulation-19.png
rename to docs/media/circulation-19.png
diff --git a/media/circulation-2.png b/docs/media/circulation-2.png
similarity index 100%
rename from media/circulation-2.png
rename to docs/media/circulation-2.png
diff --git a/media/circulation-20.png b/docs/media/circulation-20.png
similarity index 100%
rename from media/circulation-20.png
rename to docs/media/circulation-20.png
diff --git a/media/circulation-21.png b/docs/media/circulation-21.png
similarity index 100%
rename from media/circulation-21.png
rename to docs/media/circulation-21.png
diff --git a/media/circulation-22.png b/docs/media/circulation-22.png
similarity index 100%
rename from media/circulation-22.png
rename to docs/media/circulation-22.png
diff --git a/media/circulation-23.png b/docs/media/circulation-23.png
similarity index 100%
rename from media/circulation-23.png
rename to docs/media/circulation-23.png
diff --git a/media/circulation-24.png b/docs/media/circulation-24.png
similarity index 100%
rename from media/circulation-24.png
rename to docs/media/circulation-24.png
diff --git a/media/circulation-25.png b/docs/media/circulation-25.png
similarity index 100%
rename from media/circulation-25.png
rename to docs/media/circulation-25.png
diff --git a/media/circulation-26.png b/docs/media/circulation-26.png
similarity index 100%
rename from media/circulation-26.png
rename to docs/media/circulation-26.png
diff --git a/media/circulation-27.png b/docs/media/circulation-27.png
similarity index 100%
rename from media/circulation-27.png
rename to docs/media/circulation-27.png
diff --git a/media/circulation-28.png b/docs/media/circulation-28.png
similarity index 100%
rename from media/circulation-28.png
rename to docs/media/circulation-28.png
diff --git a/media/circulation-29.png b/docs/media/circulation-29.png
similarity index 100%
rename from media/circulation-29.png
rename to docs/media/circulation-29.png
diff --git a/media/circulation-3.png b/docs/media/circulation-3.png
similarity index 100%
rename from media/circulation-3.png
rename to docs/media/circulation-3.png
diff --git a/media/circulation-30.png b/docs/media/circulation-30.png
similarity index 100%
rename from media/circulation-30.png
rename to docs/media/circulation-30.png
diff --git a/media/circulation-31.png b/docs/media/circulation-31.png
similarity index 100%
rename from media/circulation-31.png
rename to docs/media/circulation-31.png
diff --git a/media/circulation-32.png b/docs/media/circulation-32.png
similarity index 100%
rename from media/circulation-32.png
rename to docs/media/circulation-32.png
diff --git a/media/circulation-33.png b/docs/media/circulation-33.png
similarity index 100%
rename from media/circulation-33.png
rename to docs/media/circulation-33.png
diff --git a/media/circulation-34.png b/docs/media/circulation-34.png
similarity index 100%
rename from media/circulation-34.png
rename to docs/media/circulation-34.png
diff --git a/media/circulation-35.png b/docs/media/circulation-35.png
similarity index 100%
rename from media/circulation-35.png
rename to docs/media/circulation-35.png
diff --git a/media/circulation-36.png b/docs/media/circulation-36.png
similarity index 100%
rename from media/circulation-36.png
rename to docs/media/circulation-36.png
diff --git a/media/circulation-4.png b/docs/media/circulation-4.png
similarity index 100%
rename from media/circulation-4.png
rename to docs/media/circulation-4.png
diff --git a/media/circulation-5.png b/docs/media/circulation-5.png
similarity index 100%
rename from media/circulation-5.png
rename to docs/media/circulation-5.png
diff --git a/media/circulation-6.png b/docs/media/circulation-6.png
similarity index 100%
rename from media/circulation-6.png
rename to docs/media/circulation-6.png
diff --git a/media/circulation-7.png b/docs/media/circulation-7.png
similarity index 100%
rename from media/circulation-7.png
rename to docs/media/circulation-7.png
diff --git a/media/circulation-8.png b/docs/media/circulation-8.png
similarity index 100%
rename from media/circulation-8.png
rename to docs/media/circulation-8.png
diff --git a/media/circulation-9.png b/docs/media/circulation-9.png
similarity index 100%
rename from media/circulation-9.png
rename to docs/media/circulation-9.png
diff --git a/media/claimed_date.png b/docs/media/claimed_date.png
similarity index 100%
rename from media/claimed_date.png
rename to docs/media/claimed_date.png
diff --git a/media/conj1.jpg b/docs/media/conj1.jpg
similarity index 100%
rename from media/conj1.jpg
rename to docs/media/conj1.jpg
diff --git a/media/conj10.jpg b/docs/media/conj10.jpg
similarity index 100%
rename from media/conj10.jpg
rename to docs/media/conj10.jpg
diff --git a/media/conj2.jpg b/docs/media/conj2.jpg
similarity index 100%
rename from media/conj2.jpg
rename to docs/media/conj2.jpg
diff --git a/media/conj3.jpg b/docs/media/conj3.jpg
similarity index 100%
rename from media/conj3.jpg
rename to docs/media/conj3.jpg
diff --git a/media/conj4.jpg b/docs/media/conj4.jpg
similarity index 100%
rename from media/conj4.jpg
rename to docs/media/conj4.jpg
diff --git a/media/conj5.jpg b/docs/media/conj5.jpg
similarity index 100%
rename from media/conj5.jpg
rename to docs/media/conj5.jpg
diff --git a/media/conj6.jpg b/docs/media/conj6.jpg
similarity index 100%
rename from media/conj6.jpg
rename to docs/media/conj6.jpg
diff --git a/media/conj7.jpg b/docs/media/conj7.jpg
similarity index 100%
rename from media/conj7.jpg
rename to docs/media/conj7.jpg
diff --git a/media/conj8.jpg b/docs/media/conj8.jpg
similarity index 100%
rename from media/conj8.jpg
rename to docs/media/conj8.jpg
diff --git a/media/conj9.jpg b/docs/media/conj9.jpg
similarity index 100%
rename from media/conj9.jpg
rename to docs/media/conj9.jpg
diff --git a/media/copy_alert_message.png b/docs/media/copy_alert_message.png
similarity index 100%
rename from media/copy_alert_message.png
rename to docs/media/copy_alert_message.png
diff --git a/media/copy_edit_alert.png b/docs/media/copy_edit_alert.png
similarity index 100%
rename from media/copy_edit_alert.png
rename to docs/media/copy_edit_alert.png
diff --git a/media/create-template-1.png b/docs/media/create-template-1.png
similarity index 100%
rename from media/create-template-1.png
rename to docs/media/create-template-1.png
diff --git a/media/create-template-10.png b/docs/media/create-template-10.png
similarity index 100%
rename from media/create-template-10.png
rename to docs/media/create-template-10.png
diff --git a/media/create-template-11.png b/docs/media/create-template-11.png
similarity index 100%
rename from media/create-template-11.png
rename to docs/media/create-template-11.png
diff --git a/media/create-template-12.png b/docs/media/create-template-12.png
similarity index 100%
rename from media/create-template-12.png
rename to docs/media/create-template-12.png
diff --git a/media/create-template-13.png b/docs/media/create-template-13.png
similarity index 100%
rename from media/create-template-13.png
rename to docs/media/create-template-13.png
diff --git a/media/create-template-15.png b/docs/media/create-template-15.png
similarity index 100%
rename from media/create-template-15.png
rename to docs/media/create-template-15.png
diff --git a/media/create-template-16.png b/docs/media/create-template-16.png
similarity index 100%
rename from media/create-template-16.png
rename to docs/media/create-template-16.png
diff --git a/media/create-template-17.png b/docs/media/create-template-17.png
similarity index 100%
rename from media/create-template-17.png
rename to docs/media/create-template-17.png
diff --git a/media/create-template-19.png b/docs/media/create-template-19.png
similarity index 100%
rename from media/create-template-19.png
rename to docs/media/create-template-19.png
diff --git a/media/create-template-2.png b/docs/media/create-template-2.png
similarity index 100%
rename from media/create-template-2.png
rename to docs/media/create-template-2.png
diff --git a/media/create-template-20.png b/docs/media/create-template-20.png
similarity index 100%
rename from media/create-template-20.png
rename to docs/media/create-template-20.png
diff --git a/media/create-template-21.png b/docs/media/create-template-21.png
similarity index 100%
rename from media/create-template-21.png
rename to docs/media/create-template-21.png
diff --git a/media/create-template-22.png b/docs/media/create-template-22.png
similarity index 100%
rename from media/create-template-22.png
rename to docs/media/create-template-22.png
diff --git a/media/create-template-23.png b/docs/media/create-template-23.png
similarity index 100%
rename from media/create-template-23.png
rename to docs/media/create-template-23.png
diff --git a/media/create-template-24.png b/docs/media/create-template-24.png
similarity index 100%
rename from media/create-template-24.png
rename to docs/media/create-template-24.png
diff --git a/media/create-template-25.png b/docs/media/create-template-25.png
similarity index 100%
rename from media/create-template-25.png
rename to docs/media/create-template-25.png
diff --git a/media/create-template-26.png b/docs/media/create-template-26.png
similarity index 100%
rename from media/create-template-26.png
rename to docs/media/create-template-26.png
diff --git a/media/create-template-27.png b/docs/media/create-template-27.png
similarity index 100%
rename from media/create-template-27.png
rename to docs/media/create-template-27.png
diff --git a/media/create-template-28.png b/docs/media/create-template-28.png
similarity index 100%
rename from media/create-template-28.png
rename to docs/media/create-template-28.png
diff --git a/media/create-template-29.png b/docs/media/create-template-29.png
similarity index 100%
rename from media/create-template-29.png
rename to docs/media/create-template-29.png
diff --git a/media/create-template-3.png b/docs/media/create-template-3.png
similarity index 100%
rename from media/create-template-3.png
rename to docs/media/create-template-3.png
diff --git a/media/create-template-30.png b/docs/media/create-template-30.png
similarity index 100%
rename from media/create-template-30.png
rename to docs/media/create-template-30.png
diff --git a/media/create-template-31.png b/docs/media/create-template-31.png
similarity index 100%
rename from media/create-template-31.png
rename to docs/media/create-template-31.png
diff --git a/media/create-template-32.png b/docs/media/create-template-32.png
similarity index 100%
rename from media/create-template-32.png
rename to docs/media/create-template-32.png
diff --git a/media/create-template-33.png b/docs/media/create-template-33.png
similarity index 100%
rename from media/create-template-33.png
rename to docs/media/create-template-33.png
diff --git a/media/create-template-34.png b/docs/media/create-template-34.png
similarity index 100%
rename from media/create-template-34.png
rename to docs/media/create-template-34.png
diff --git a/media/create-template-35.png b/docs/media/create-template-35.png
similarity index 100%
rename from media/create-template-35.png
rename to docs/media/create-template-35.png
diff --git a/media/create-template-4.png b/docs/media/create-template-4.png
similarity index 100%
rename from media/create-template-4.png
rename to docs/media/create-template-4.png
diff --git a/media/create-template-5.png b/docs/media/create-template-5.png
similarity index 100%
rename from media/create-template-5.png
rename to docs/media/create-template-5.png
diff --git a/media/create-template-6.png b/docs/media/create-template-6.png
similarity index 100%
rename from media/create-template-6.png
rename to docs/media/create-template-6.png
diff --git a/media/create-template-7.png b/docs/media/create-template-7.png
similarity index 100%
rename from media/create-template-7.png
rename to docs/media/create-template-7.png
diff --git a/media/create-template-8.png b/docs/media/create-template-8.png
similarity index 100%
rename from media/create-template-8.png
rename to docs/media/create-template-8.png
diff --git a/media/create-template-9.png b/docs/media/create-template-9.png
similarity index 100%
rename from media/create-template-9.png
rename to docs/media/create-template-9.png
diff --git a/media/due_date_display.png b/docs/media/due_date_display.png
similarity index 100%
rename from media/due_date_display.png
rename to docs/media/due_date_display.png
diff --git a/media/edit_due_date_action.png b/docs/media/edit_due_date_action.png
similarity index 100%
rename from media/edit_due_date_action.png
rename to docs/media/edit_due_date_action.png
diff --git a/media/epub_logo_color_ht39.gif b/docs/media/epub_logo_color_ht39.gif
similarity index 100%
rename from media/epub_logo_color_ht39.gif
rename to docs/media/epub_logo_color_ht39.gif
diff --git a/media/evergreen_logo.gif b/docs/media/evergreen_logo.gif
similarity index 100%
rename from media/evergreen_logo.gif
rename to docs/media/evergreen_logo.gif
diff --git a/media/folder-1.png b/docs/media/folder-1.png
similarity index 100%
rename from media/folder-1.png
rename to docs/media/folder-1.png
diff --git a/media/folder-10.png b/docs/media/folder-10.png
similarity index 100%
rename from media/folder-10.png
rename to docs/media/folder-10.png
diff --git a/media/folder-11.png b/docs/media/folder-11.png
similarity index 100%
rename from media/folder-11.png
rename to docs/media/folder-11.png
diff --git a/media/folder-12.png b/docs/media/folder-12.png
similarity index 100%
rename from media/folder-12.png
rename to docs/media/folder-12.png
diff --git a/media/folder-13.png b/docs/media/folder-13.png
similarity index 100%
rename from media/folder-13.png
rename to docs/media/folder-13.png
diff --git a/media/folder-14.png b/docs/media/folder-14.png
similarity index 100%
rename from media/folder-14.png
rename to docs/media/folder-14.png
diff --git a/media/folder-7a.png b/docs/media/folder-7a.png
similarity index 100%
rename from media/folder-7a.png
rename to docs/media/folder-7a.png
diff --git a/media/generate-report-1.png b/docs/media/generate-report-1.png
similarity index 100%
rename from media/generate-report-1.png
rename to docs/media/generate-report-1.png
diff --git a/media/generate-report-10.png b/docs/media/generate-report-10.png
similarity index 100%
rename from media/generate-report-10.png
rename to docs/media/generate-report-10.png
diff --git a/media/generate-report-14.png b/docs/media/generate-report-14.png
similarity index 100%
rename from media/generate-report-14.png
rename to docs/media/generate-report-14.png
diff --git a/media/generate-report-2.png b/docs/media/generate-report-2.png
similarity index 100%
rename from media/generate-report-2.png
rename to docs/media/generate-report-2.png
diff --git a/media/generate-report-3.png b/docs/media/generate-report-3.png
similarity index 100%
rename from media/generate-report-3.png
rename to docs/media/generate-report-3.png
diff --git a/media/generate-report-8.png b/docs/media/generate-report-8.png
similarity index 100%
rename from media/generate-report-8.png
rename to docs/media/generate-report-8.png
diff --git a/media/generate-report-9.png b/docs/media/generate-report-9.png
similarity index 100%
rename from media/generate-report-9.png
rename to docs/media/generate-report-9.png
diff --git a/media/hold-1.png b/docs/media/hold-1.png
similarity index 100%
rename from media/hold-1.png
rename to docs/media/hold-1.png
diff --git a/media/hold-10.png b/docs/media/hold-10.png
similarity index 100%
rename from media/hold-10.png
rename to docs/media/hold-10.png
diff --git a/media/hold-11.png b/docs/media/hold-11.png
similarity index 100%
rename from media/hold-11.png
rename to docs/media/hold-11.png
diff --git a/media/hold-12.png b/docs/media/hold-12.png
similarity index 100%
rename from media/hold-12.png
rename to docs/media/hold-12.png
diff --git a/media/hold-14.png b/docs/media/hold-14.png
similarity index 100%
rename from media/hold-14.png
rename to docs/media/hold-14.png
diff --git a/media/hold-15.png b/docs/media/hold-15.png
similarity index 100%
rename from media/hold-15.png
rename to docs/media/hold-15.png
diff --git a/media/hold-16.png b/docs/media/hold-16.png
similarity index 100%
rename from media/hold-16.png
rename to docs/media/hold-16.png
diff --git a/media/hold-17.png b/docs/media/hold-17.png
similarity index 100%
rename from media/hold-17.png
rename to docs/media/hold-17.png
diff --git a/media/hold-18.png b/docs/media/hold-18.png
similarity index 100%
rename from media/hold-18.png
rename to docs/media/hold-18.png
diff --git a/media/hold-19.png b/docs/media/hold-19.png
similarity index 100%
rename from media/hold-19.png
rename to docs/media/hold-19.png
diff --git a/media/hold-2.png b/docs/media/hold-2.png
similarity index 100%
rename from media/hold-2.png
rename to docs/media/hold-2.png
diff --git a/media/hold-20.png b/docs/media/hold-20.png
similarity index 100%
rename from media/hold-20.png
rename to docs/media/hold-20.png
diff --git a/media/hold-21.png b/docs/media/hold-21.png
similarity index 100%
rename from media/hold-21.png
rename to docs/media/hold-21.png
diff --git a/media/hold-22.png b/docs/media/hold-22.png
similarity index 100%
rename from media/hold-22.png
rename to docs/media/hold-22.png
diff --git a/media/hold-23.png b/docs/media/hold-23.png
similarity index 100%
rename from media/hold-23.png
rename to docs/media/hold-23.png
diff --git a/media/hold-24.png b/docs/media/hold-24.png
similarity index 100%
rename from media/hold-24.png
rename to docs/media/hold-24.png
diff --git a/media/hold-25.png b/docs/media/hold-25.png
similarity index 100%
rename from media/hold-25.png
rename to docs/media/hold-25.png
diff --git a/media/hold-26.png b/docs/media/hold-26.png
similarity index 100%
rename from media/hold-26.png
rename to docs/media/hold-26.png
diff --git a/media/hold-27.png b/docs/media/hold-27.png
similarity index 100%
rename from media/hold-27.png
rename to docs/media/hold-27.png
diff --git a/media/hold-28.png b/docs/media/hold-28.png
similarity index 100%
rename from media/hold-28.png
rename to docs/media/hold-28.png
diff --git a/media/hold-29.png b/docs/media/hold-29.png
similarity index 100%
rename from media/hold-29.png
rename to docs/media/hold-29.png
diff --git a/media/hold-4.png b/docs/media/hold-4.png
similarity index 100%
rename from media/hold-4.png
rename to docs/media/hold-4.png
diff --git a/media/hold-5.png b/docs/media/hold-5.png
similarity index 100%
rename from media/hold-5.png
rename to docs/media/hold-5.png
diff --git a/media/hold-6.png b/docs/media/hold-6.png
similarity index 100%
rename from media/hold-6.png
rename to docs/media/hold-6.png
diff --git a/media/hold-7.png b/docs/media/hold-7.png
similarity index 100%
rename from media/hold-7.png
rename to docs/media/hold-7.png
diff --git a/media/hold-8.png b/docs/media/hold-8.png
similarity index 100%
rename from media/hold-8.png
rename to docs/media/hold-8.png
diff --git a/media/hold-9.png b/docs/media/hold-9.png
similarity index 100%
rename from media/hold-9.png
rename to docs/media/hold-9.png
diff --git a/media/holds-clearing-1.png b/docs/media/holds-clearing-1.png
similarity index 100%
rename from media/holds-clearing-1.png
rename to docs/media/holds-clearing-1.png
diff --git a/media/holds-clearing-2.png b/docs/media/holds-clearing-2.png
similarity index 100%
rename from media/holds-clearing-2.png
rename to docs/media/holds-clearing-2.png
diff --git a/media/holds-clearing-3.png b/docs/media/holds-clearing-3.png
similarity index 100%
rename from media/holds-clearing-3.png
rename to docs/media/holds-clearing-3.png
diff --git a/media/holds-clearing-4.png b/docs/media/holds-clearing-4.png
similarity index 100%
rename from media/holds-clearing-4.png
rename to docs/media/holds-clearing-4.png
diff --git a/media/holds-managing-1.png b/docs/media/holds-managing-1.png
similarity index 100%
rename from media/holds-managing-1.png
rename to docs/media/holds-managing-1.png
diff --git a/media/holds-managing-10.png b/docs/media/holds-managing-10.png
similarity index 100%
rename from media/holds-managing-10.png
rename to docs/media/holds-managing-10.png
diff --git a/media/holds-managing-11.png b/docs/media/holds-managing-11.png
similarity index 100%
rename from media/holds-managing-11.png
rename to docs/media/holds-managing-11.png
diff --git a/media/holds-managing-12.png b/docs/media/holds-managing-12.png
similarity index 100%
rename from media/holds-managing-12.png
rename to docs/media/holds-managing-12.png
diff --git a/media/holds-managing-13.png b/docs/media/holds-managing-13.png
similarity index 100%
rename from media/holds-managing-13.png
rename to docs/media/holds-managing-13.png
diff --git a/media/holds-managing-14.png b/docs/media/holds-managing-14.png
similarity index 100%
rename from media/holds-managing-14.png
rename to docs/media/holds-managing-14.png
diff --git a/media/holds-managing-15.png b/docs/media/holds-managing-15.png
similarity index 100%
rename from media/holds-managing-15.png
rename to docs/media/holds-managing-15.png
diff --git a/media/holds-managing-16.png b/docs/media/holds-managing-16.png
similarity index 100%
rename from media/holds-managing-16.png
rename to docs/media/holds-managing-16.png
diff --git a/media/holds-managing-17.png b/docs/media/holds-managing-17.png
similarity index 100%
rename from media/holds-managing-17.png
rename to docs/media/holds-managing-17.png
diff --git a/media/holds-managing-18.png b/docs/media/holds-managing-18.png
similarity index 100%
rename from media/holds-managing-18.png
rename to docs/media/holds-managing-18.png
diff --git a/media/holds-managing-19.png b/docs/media/holds-managing-19.png
similarity index 100%
rename from media/holds-managing-19.png
rename to docs/media/holds-managing-19.png
diff --git a/media/holds-managing-2.png b/docs/media/holds-managing-2.png
similarity index 100%
rename from media/holds-managing-2.png
rename to docs/media/holds-managing-2.png
diff --git a/media/holds-managing-3.png b/docs/media/holds-managing-3.png
similarity index 100%
rename from media/holds-managing-3.png
rename to docs/media/holds-managing-3.png
diff --git a/media/holds-managing-4.png b/docs/media/holds-managing-4.png
similarity index 100%
rename from media/holds-managing-4.png
rename to docs/media/holds-managing-4.png
diff --git a/media/holds-managing-5.png b/docs/media/holds-managing-5.png
similarity index 100%
rename from media/holds-managing-5.png
rename to docs/media/holds-managing-5.png
diff --git a/media/holds-managing-6.png b/docs/media/holds-managing-6.png
similarity index 100%
rename from media/holds-managing-6.png
rename to docs/media/holds-managing-6.png
diff --git a/media/holds-managing-7.png b/docs/media/holds-managing-7.png
similarity index 100%
rename from media/holds-managing-7.png
rename to docs/media/holds-managing-7.png
diff --git a/media/holds-managing-8.png b/docs/media/holds-managing-8.png
similarity index 100%
rename from media/holds-managing-8.png
rename to docs/media/holds-managing-8.png
diff --git a/media/holds-managing-9.png b/docs/media/holds-managing-9.png
similarity index 100%
rename from media/holds-managing-9.png
rename to docs/media/holds-managing-9.png
diff --git a/media/holds-notifications-1.png b/docs/media/holds-notifications-1.png
similarity index 100%
rename from media/holds-notifications-1.png
rename to docs/media/holds-notifications-1.png
diff --git a/media/holds-notifications-2.png b/docs/media/holds-notifications-2.png
similarity index 100%
rename from media/holds-notifications-2.png
rename to docs/media/holds-notifications-2.png
diff --git a/media/holds-notifications-3.png b/docs/media/holds-notifications-3.png
similarity index 100%
rename from media/holds-notifications-3.png
rename to docs/media/holds-notifications-3.png
diff --git a/media/holds-notifications-4.png b/docs/media/holds-notifications-4.png
similarity index 100%
rename from media/holds-notifications-4.png
rename to docs/media/holds-notifications-4.png
diff --git a/media/holds-placing-1.png b/docs/media/holds-placing-1.png
similarity index 100%
rename from media/holds-placing-1.png
rename to docs/media/holds-placing-1.png
diff --git a/media/holds-placing-10.png b/docs/media/holds-placing-10.png
similarity index 100%
rename from media/holds-placing-10.png
rename to docs/media/holds-placing-10.png
diff --git a/media/holds-placing-11.png b/docs/media/holds-placing-11.png
similarity index 100%
rename from media/holds-placing-11.png
rename to docs/media/holds-placing-11.png
diff --git a/media/holds-placing-2.png b/docs/media/holds-placing-2.png
similarity index 100%
rename from media/holds-placing-2.png
rename to docs/media/holds-placing-2.png
diff --git a/media/holds-placing-3.png b/docs/media/holds-placing-3.png
similarity index 100%
rename from media/holds-placing-3.png
rename to docs/media/holds-placing-3.png
diff --git a/media/holds-placing-4.png b/docs/media/holds-placing-4.png
similarity index 100%
rename from media/holds-placing-4.png
rename to docs/media/holds-placing-4.png
diff --git a/media/holds-placing-5.png b/docs/media/holds-placing-5.png
similarity index 100%
rename from media/holds-placing-5.png
rename to docs/media/holds-placing-5.png
diff --git a/media/holds-placing-6.png b/docs/media/holds-placing-6.png
similarity index 100%
rename from media/holds-placing-6.png
rename to docs/media/holds-placing-6.png
diff --git a/media/holds-placing-7.png b/docs/media/holds-placing-7.png
similarity index 100%
rename from media/holds-placing-7.png
rename to docs/media/holds-placing-7.png
diff --git a/media/holds-placing-8.png b/docs/media/holds-placing-8.png
similarity index 100%
rename from media/holds-placing-8.png
rename to docs/media/holds-placing-8.png
diff --git a/media/holds-placing-9.png b/docs/media/holds-placing-9.png
similarity index 100%
rename from media/holds-placing-9.png
rename to docs/media/holds-placing-9.png
diff --git a/media/holds-pull-1.png b/docs/media/holds-pull-1.png
similarity index 100%
rename from media/holds-pull-1.png
rename to docs/media/holds-pull-1.png
diff --git a/media/holds-pull-2.png b/docs/media/holds-pull-2.png
similarity index 100%
rename from media/holds-pull-2.png
rename to docs/media/holds-pull-2.png
diff --git a/media/holds-pull-3.png b/docs/media/holds-pull-3.png
similarity index 100%
rename from media/holds-pull-3.png
rename to docs/media/holds-pull-3.png
diff --git a/media/holds-pull-4.png b/docs/media/holds-pull-4.png
similarity index 100%
rename from media/holds-pull-4.png
rename to docs/media/holds-pull-4.png
diff --git a/media/holds-pull-5.png b/docs/media/holds-pull-5.png
similarity index 100%
rename from media/holds-pull-5.png
rename to docs/media/holds-pull-5.png
diff --git a/media/holds-pull-5a.png b/docs/media/holds-pull-5a.png
similarity index 100%
rename from media/holds-pull-5a.png
rename to docs/media/holds-pull-5a.png
diff --git a/media/holds-pull-6.png b/docs/media/holds-pull-6.png
similarity index 100%
rename from media/holds-pull-6.png
rename to docs/media/holds-pull-6.png
diff --git a/media/holds-pull-7.png b/docs/media/holds-pull-7.png
similarity index 100%
rename from media/holds-pull-7.png
rename to docs/media/holds-pull-7.png
diff --git a/media/holds-pull-8.png b/docs/media/holds-pull-8.png
similarity index 100%
rename from media/holds-pull-8.png
rename to docs/media/holds-pull-8.png
diff --git a/media/holds-pull-9.png b/docs/media/holds-pull-9.png
similarity index 100%
rename from media/holds-pull-9.png
rename to docs/media/holds-pull-9.png
diff --git a/media/in_house_use.png b/docs/media/in_house_use.png
similarity index 100%
rename from media/in_house_use.png
rename to docs/media/in_house_use.png
diff --git a/media/item_status_altview.png b/docs/media/item_status_altview.png
similarity index 100%
rename from media/item_status_altview.png
rename to docs/media/item_status_altview.png
diff --git a/media/item_status_barcode.png b/docs/media/item_status_barcode.png
similarity index 100%
rename from media/item_status_barcode.png
rename to docs/media/item_status_barcode.png
diff --git a/media/item_status_list_view.png b/docs/media/item_status_list_view.png
similarity index 100%
rename from media/item_status_list_view.png
rename to docs/media/item_status_list_view.png
diff --git a/media/item_status_menu.png b/docs/media/item_status_menu.png
similarity index 100%
rename from media/item_status_menu.png
rename to docs/media/item_status_menu.png
diff --git a/media/items_out_click.png b/docs/media/items_out_click.png
similarity index 100%
rename from media/items_out_click.png
rename to docs/media/items_out_click.png
diff --git a/media/k_book_record.png b/docs/media/k_book_record.png
similarity index 100%
rename from media/k_book_record.png
rename to docs/media/k_book_record.png
diff --git a/media/last_few_circs_action.png b/docs/media/last_few_circs_action.png
similarity index 100%
rename from media/last_few_circs_action.png
rename to docs/media/last_few_circs_action.png
diff --git a/media/last_few_circs_display.png b/docs/media/last_few_circs_display.png
similarity index 100%
rename from media/last_few_circs_display.png
rename to docs/media/last_few_circs_display.png
diff --git a/media/lost_cr_section.png b/docs/media/lost_cr_section.png
similarity index 100%
rename from media/lost_cr_section.png
rename to docs/media/lost_cr_section.png
diff --git a/media/lsa-1.png b/docs/media/lsa-1.png
similarity index 100%
rename from media/lsa-1.png
rename to docs/media/lsa-1.png
diff --git a/media/lsa-10.jpg b/docs/media/lsa-10.jpg
similarity index 100%
rename from media/lsa-10.jpg
rename to docs/media/lsa-10.jpg
diff --git a/media/lsa-11.jpg b/docs/media/lsa-11.jpg
similarity index 100%
rename from media/lsa-11.jpg
rename to docs/media/lsa-11.jpg
diff --git a/media/lsa-12.jpg b/docs/media/lsa-12.jpg
similarity index 100%
rename from media/lsa-12.jpg
rename to docs/media/lsa-12.jpg
diff --git a/media/lsa-14.jpg b/docs/media/lsa-14.jpg
similarity index 100%
rename from media/lsa-14.jpg
rename to docs/media/lsa-14.jpg
diff --git a/media/lsa-16.jpg b/docs/media/lsa-16.jpg
similarity index 100%
rename from media/lsa-16.jpg
rename to docs/media/lsa-16.jpg
diff --git a/media/lsa-17.jpg b/docs/media/lsa-17.jpg
similarity index 100%
rename from media/lsa-17.jpg
rename to docs/media/lsa-17.jpg
diff --git a/media/lsa-18.jpg b/docs/media/lsa-18.jpg
similarity index 100%
rename from media/lsa-18.jpg
rename to docs/media/lsa-18.jpg
diff --git a/media/lsa-2.jpg b/docs/media/lsa-2.jpg
similarity index 100%
rename from media/lsa-2.jpg
rename to docs/media/lsa-2.jpg
diff --git a/media/lsa-22.png b/docs/media/lsa-22.png
similarity index 100%
rename from media/lsa-22.png
rename to docs/media/lsa-22.png
diff --git a/media/lsa-23.jpg b/docs/media/lsa-23.jpg
similarity index 100%
rename from media/lsa-23.jpg
rename to docs/media/lsa-23.jpg
diff --git a/media/lsa-25.jpg b/docs/media/lsa-25.jpg
similarity index 100%
rename from media/lsa-25.jpg
rename to docs/media/lsa-25.jpg
diff --git a/media/lsa-26.jpg b/docs/media/lsa-26.jpg
similarity index 100%
rename from media/lsa-26.jpg
rename to docs/media/lsa-26.jpg
diff --git a/media/lsa-27.jpg b/docs/media/lsa-27.jpg
similarity index 100%
rename from media/lsa-27.jpg
rename to docs/media/lsa-27.jpg
diff --git a/media/lsa-28.jpg b/docs/media/lsa-28.jpg
similarity index 100%
rename from media/lsa-28.jpg
rename to docs/media/lsa-28.jpg
diff --git a/media/lsa-32.jpg b/docs/media/lsa-32.jpg
similarity index 100%
rename from media/lsa-32.jpg
rename to docs/media/lsa-32.jpg
diff --git a/media/lsa-33.jpg b/docs/media/lsa-33.jpg
similarity index 100%
rename from media/lsa-33.jpg
rename to docs/media/lsa-33.jpg
diff --git a/media/lsa-4.jpg b/docs/media/lsa-4.jpg
similarity index 100%
rename from media/lsa-4.jpg
rename to docs/media/lsa-4.jpg
diff --git a/media/lsa-5.jpg b/docs/media/lsa-5.jpg
similarity index 100%
rename from media/lsa-5.jpg
rename to docs/media/lsa-5.jpg
diff --git a/media/lsa-7.jpg b/docs/media/lsa-7.jpg
similarity index 100%
rename from media/lsa-7.jpg
rename to docs/media/lsa-7.jpg
diff --git a/media/lsa-8.jpg b/docs/media/lsa-8.jpg
similarity index 100%
rename from media/lsa-8.jpg
rename to docs/media/lsa-8.jpg
diff --git a/media/lsa-closed-mountain-1.png b/docs/media/lsa-closed-mountain-1.png
similarity index 100%
rename from media/lsa-closed-mountain-1.png
rename to docs/media/lsa-closed-mountain-1.png
diff --git a/media/lsa-closed-mountain-2.png b/docs/media/lsa-closed-mountain-2.png
similarity index 100%
rename from media/lsa-closed-mountain-2.png
rename to docs/media/lsa-closed-mountain-2.png
diff --git a/media/lsa-group-0.png b/docs/media/lsa-group-0.png
similarity index 100%
rename from media/lsa-group-0.png
rename to docs/media/lsa-group-0.png
diff --git a/media/lsa-group-1.png b/docs/media/lsa-group-1.png
similarity index 100%
rename from media/lsa-group-1.png
rename to docs/media/lsa-group-1.png
diff --git a/media/lsa-group-1a.png b/docs/media/lsa-group-1a.png
similarity index 100%
rename from media/lsa-group-1a.png
rename to docs/media/lsa-group-1a.png
diff --git a/media/lsa-group-2.png b/docs/media/lsa-group-2.png
similarity index 100%
rename from media/lsa-group-2.png
rename to docs/media/lsa-group-2.png
diff --git a/media/lsa-group-3.png b/docs/media/lsa-group-3.png
similarity index 100%
rename from media/lsa-group-3.png
rename to docs/media/lsa-group-3.png
diff --git a/media/lsa-group-4.png b/docs/media/lsa-group-4.png
similarity index 100%
rename from media/lsa-group-4.png
rename to docs/media/lsa-group-4.png
diff --git a/media/lsa-group-5.png b/docs/media/lsa-group-5.png
similarity index 100%
rename from media/lsa-group-5.png
rename to docs/media/lsa-group-5.png
diff --git a/media/lsa-group-6.png b/docs/media/lsa-group-6.png
similarity index 100%
rename from media/lsa-group-6.png
rename to docs/media/lsa-group-6.png
diff --git a/media/lsa-statcat-1.png b/docs/media/lsa-statcat-1.png
similarity index 100%
rename from media/lsa-statcat-1.png
rename to docs/media/lsa-statcat-1.png
diff --git a/media/lsa-statcat-2.png b/docs/media/lsa-statcat-2.png
similarity index 100%
rename from media/lsa-statcat-2.png
rename to docs/media/lsa-statcat-2.png
diff --git a/media/lsa-statcat-3.png b/docs/media/lsa-statcat-3.png
similarity index 100%
rename from media/lsa-statcat-3.png
rename to docs/media/lsa-statcat-3.png
diff --git a/media/lsa-statcat-4.png b/docs/media/lsa-statcat-4.png
similarity index 100%
rename from media/lsa-statcat-4.png
rename to docs/media/lsa-statcat-4.png
diff --git a/media/lsa-statcat-5.png b/docs/media/lsa-statcat-5.png
similarity index 100%
rename from media/lsa-statcat-5.png
rename to docs/media/lsa-statcat-5.png
diff --git a/media/lsa-statcat-6.png b/docs/media/lsa-statcat-6.png
similarity index 100%
rename from media/lsa-statcat-6.png
rename to docs/media/lsa-statcat-6.png
diff --git a/media/lsa-statcat-7.png b/docs/media/lsa-statcat-7.png
similarity index 100%
rename from media/lsa-statcat-7.png
rename to docs/media/lsa-statcat-7.png
diff --git a/media/lsa-statcat-8.png b/docs/media/lsa-statcat-8.png
similarity index 100%
rename from media/lsa-statcat-8.png
rename to docs/media/lsa-statcat-8.png
diff --git a/media/main_logo.jpg b/docs/media/main_logo.jpg
similarity index 100%
rename from media/main_logo.jpg
rename to docs/media/main_logo.jpg
diff --git a/media/mark_claims_returned.png b/docs/media/mark_claims_returned.png
similarity index 100%
rename from media/mark_claims_returned.png
rename to docs/media/mark_claims_returned.png
diff --git a/media/mark_lost.png b/docs/media/mark_lost.png
similarity index 100%
rename from media/mark_lost.png
rename to docs/media/mark_lost.png
diff --git a/media/mark_missing_damaged.png b/docs/media/mark_missing_damaged.png
similarity index 100%
rename from media/mark_missing_damaged.png
rename to docs/media/mark_missing_damaged.png
diff --git a/media/monograph_parts1.jpg b/docs/media/monograph_parts1.jpg
similarity index 100%
rename from media/monograph_parts1.jpg
rename to docs/media/monograph_parts1.jpg
diff --git a/media/monograph_parts2.jpg b/docs/media/monograph_parts2.jpg
similarity index 100%
rename from media/monograph_parts2.jpg
rename to docs/media/monograph_parts2.jpg
diff --git a/media/monograph_parts3.jpg b/docs/media/monograph_parts3.jpg
similarity index 100%
rename from media/monograph_parts3.jpg
rename to docs/media/monograph_parts3.jpg
diff --git a/media/monograph_parts4.jpg b/docs/media/monograph_parts4.jpg
similarity index 100%
rename from media/monograph_parts4.jpg
rename to docs/media/monograph_parts4.jpg
diff --git a/media/monograph_parts5.jpg b/docs/media/monograph_parts5.jpg
similarity index 100%
rename from media/monograph_parts5.jpg
rename to docs/media/monograph_parts5.jpg
diff --git a/media/myaccount-bookbags.png b/docs/media/myaccount-bookbags.png
similarity index 100%
rename from media/myaccount-bookbags.png
rename to docs/media/myaccount-bookbags.png
diff --git a/media/myaccount-itemrenew.png b/docs/media/myaccount-itemrenew.png
similarity index 100%
rename from media/myaccount-itemrenew.png
rename to docs/media/myaccount-itemrenew.png
diff --git a/media/myaccount-itemscheckedout.png b/docs/media/myaccount-itemscheckedout.png
similarity index 100%
rename from media/myaccount-itemscheckedout.png
rename to docs/media/myaccount-itemscheckedout.png
diff --git a/media/myaccount-itemsonhold.png b/docs/media/myaccount-itemsonhold.png
similarity index 100%
rename from media/myaccount-itemsonhold.png
rename to docs/media/myaccount-itemsonhold.png
diff --git a/media/myaccount-login-arrow.png b/docs/media/myaccount-login-arrow.png
similarity index 100%
rename from media/myaccount-login-arrow.png
rename to docs/media/myaccount-login-arrow.png
diff --git a/media/myaccount-login-info.png b/docs/media/myaccount-login-info.png
similarity index 100%
rename from media/myaccount-login-info.png
rename to docs/media/myaccount-login-info.png
diff --git a/media/myaccount-login.png b/docs/media/myaccount-login.png
similarity index 100%
rename from media/myaccount-login.png
rename to docs/media/myaccount-login.png
diff --git a/media/myaccount-loginpasswordupdate.png b/docs/media/myaccount-loginpasswordupdate.png
similarity index 100%
rename from media/myaccount-loginpasswordupdate.png
rename to docs/media/myaccount-loginpasswordupdate.png
diff --git a/media/myaccount-summary.png b/docs/media/myaccount-summary.png
similarity index 100%
rename from media/myaccount-summary.png
rename to docs/media/myaccount-summary.png
diff --git a/media/note.png b/docs/media/note.png
similarity index 100%
rename from media/note.png
rename to docs/media/note.png
diff --git a/media/offline-1.png b/docs/media/offline-1.png
similarity index 100%
rename from media/offline-1.png
rename to docs/media/offline-1.png
diff --git a/media/offline-10.png b/docs/media/offline-10.png
similarity index 100%
rename from media/offline-10.png
rename to docs/media/offline-10.png
diff --git a/media/offline-11.png b/docs/media/offline-11.png
similarity index 100%
rename from media/offline-11.png
rename to docs/media/offline-11.png
diff --git a/media/offline-12.png b/docs/media/offline-12.png
similarity index 100%
rename from media/offline-12.png
rename to docs/media/offline-12.png
diff --git a/media/offline-13.png b/docs/media/offline-13.png
similarity index 100%
rename from media/offline-13.png
rename to docs/media/offline-13.png
diff --git a/media/offline-14.png b/docs/media/offline-14.png
similarity index 100%
rename from media/offline-14.png
rename to docs/media/offline-14.png
diff --git a/media/offline-15.png b/docs/media/offline-15.png
similarity index 100%
rename from media/offline-15.png
rename to docs/media/offline-15.png
diff --git a/media/offline-16.png b/docs/media/offline-16.png
similarity index 100%
rename from media/offline-16.png
rename to docs/media/offline-16.png
diff --git a/media/offline-17.png b/docs/media/offline-17.png
similarity index 100%
rename from media/offline-17.png
rename to docs/media/offline-17.png
diff --git a/media/offline-18.png b/docs/media/offline-18.png
similarity index 100%
rename from media/offline-18.png
rename to docs/media/offline-18.png
diff --git a/media/offline-19.png b/docs/media/offline-19.png
similarity index 100%
rename from media/offline-19.png
rename to docs/media/offline-19.png
diff --git a/media/offline-2.png b/docs/media/offline-2.png
similarity index 100%
rename from media/offline-2.png
rename to docs/media/offline-2.png
diff --git a/media/offline-20.png b/docs/media/offline-20.png
similarity index 100%
rename from media/offline-20.png
rename to docs/media/offline-20.png
diff --git a/media/offline-21.png b/docs/media/offline-21.png
similarity index 100%
rename from media/offline-21.png
rename to docs/media/offline-21.png
diff --git a/media/offline-22.png b/docs/media/offline-22.png
similarity index 100%
rename from media/offline-22.png
rename to docs/media/offline-22.png
diff --git a/media/offline-23.png b/docs/media/offline-23.png
similarity index 100%
rename from media/offline-23.png
rename to docs/media/offline-23.png
diff --git a/media/offline-24.png b/docs/media/offline-24.png
similarity index 100%
rename from media/offline-24.png
rename to docs/media/offline-24.png
diff --git a/media/offline-25.png b/docs/media/offline-25.png
similarity index 100%
rename from media/offline-25.png
rename to docs/media/offline-25.png
diff --git a/media/offline-26.png b/docs/media/offline-26.png
similarity index 100%
rename from media/offline-26.png
rename to docs/media/offline-26.png
diff --git a/media/offline-27.png b/docs/media/offline-27.png
similarity index 100%
rename from media/offline-27.png
rename to docs/media/offline-27.png
diff --git a/media/offline-28.png b/docs/media/offline-28.png
similarity index 100%
rename from media/offline-28.png
rename to docs/media/offline-28.png
diff --git a/media/offline-29.png b/docs/media/offline-29.png
similarity index 100%
rename from media/offline-29.png
rename to docs/media/offline-29.png
diff --git a/media/offline-3.png b/docs/media/offline-3.png
similarity index 100%
rename from media/offline-3.png
rename to docs/media/offline-3.png
diff --git a/media/offline-30.png b/docs/media/offline-30.png
similarity index 100%
rename from media/offline-30.png
rename to docs/media/offline-30.png
diff --git a/media/offline-31.png b/docs/media/offline-31.png
similarity index 100%
rename from media/offline-31.png
rename to docs/media/offline-31.png
diff --git a/media/offline-32.png b/docs/media/offline-32.png
similarity index 100%
rename from media/offline-32.png
rename to docs/media/offline-32.png
diff --git a/media/offline-33.png b/docs/media/offline-33.png
similarity index 100%
rename from media/offline-33.png
rename to docs/media/offline-33.png
diff --git a/media/offline-34.png b/docs/media/offline-34.png
similarity index 100%
rename from media/offline-34.png
rename to docs/media/offline-34.png
diff --git a/media/offline-35.png b/docs/media/offline-35.png
similarity index 100%
rename from media/offline-35.png
rename to docs/media/offline-35.png
diff --git a/media/offline-36.png b/docs/media/offline-36.png
similarity index 100%
rename from media/offline-36.png
rename to docs/media/offline-36.png
diff --git a/media/offline-4.png b/docs/media/offline-4.png
similarity index 100%
rename from media/offline-4.png
rename to docs/media/offline-4.png
diff --git a/media/offline-5.png b/docs/media/offline-5.png
similarity index 100%
rename from media/offline-5.png
rename to docs/media/offline-5.png
diff --git a/media/offline-6.png b/docs/media/offline-6.png
similarity index 100%
rename from media/offline-6.png
rename to docs/media/offline-6.png
diff --git a/media/offline-7.png b/docs/media/offline-7.png
similarity index 100%
rename from media/offline-7.png
rename to docs/media/offline-7.png
diff --git a/media/offline-8.png b/docs/media/offline-8.png
similarity index 100%
rename from media/offline-8.png
rename to docs/media/offline-8.png
diff --git a/media/offline-9.png b/docs/media/offline-9.png
similarity index 100%
rename from media/offline-9.png
rename to docs/media/offline-9.png
diff --git a/media/overdue_checkin.png b/docs/media/overdue_checkin.png
similarity index 100%
rename from media/overdue_checkin.png
rename to docs/media/overdue_checkin.png
diff --git a/media/passwordresetmessage.png b/docs/media/passwordresetmessage.png
similarity index 100%
rename from media/passwordresetmessage.png
rename to docs/media/passwordresetmessage.png
diff --git a/media/patron-1.png b/docs/media/patron-1.png
similarity index 100%
rename from media/patron-1.png
rename to docs/media/patron-1.png
diff --git a/media/patron-10.png b/docs/media/patron-10.png
similarity index 100%
rename from media/patron-10.png
rename to docs/media/patron-10.png
diff --git a/media/patron-11.png b/docs/media/patron-11.png
similarity index 100%
rename from media/patron-11.png
rename to docs/media/patron-11.png
diff --git a/media/patron-12.png b/docs/media/patron-12.png
similarity index 100%
rename from media/patron-12.png
rename to docs/media/patron-12.png
diff --git a/media/patron-13.png b/docs/media/patron-13.png
similarity index 100%
rename from media/patron-13.png
rename to docs/media/patron-13.png
diff --git a/media/patron-14.png b/docs/media/patron-14.png
similarity index 100%
rename from media/patron-14.png
rename to docs/media/patron-14.png
diff --git a/media/patron-15.png b/docs/media/patron-15.png
similarity index 100%
rename from media/patron-15.png
rename to docs/media/patron-15.png
diff --git a/media/patron-16.png b/docs/media/patron-16.png
similarity index 100%
rename from media/patron-16.png
rename to docs/media/patron-16.png
diff --git a/media/patron-17.png b/docs/media/patron-17.png
similarity index 100%
rename from media/patron-17.png
rename to docs/media/patron-17.png
diff --git a/media/patron-18.png b/docs/media/patron-18.png
similarity index 100%
rename from media/patron-18.png
rename to docs/media/patron-18.png
diff --git a/media/patron-19.png b/docs/media/patron-19.png
similarity index 100%
rename from media/patron-19.png
rename to docs/media/patron-19.png
diff --git a/media/patron-2.png b/docs/media/patron-2.png
similarity index 100%
rename from media/patron-2.png
rename to docs/media/patron-2.png
diff --git a/media/patron-20.png b/docs/media/patron-20.png
similarity index 100%
rename from media/patron-20.png
rename to docs/media/patron-20.png
diff --git a/media/patron-21.png b/docs/media/patron-21.png
similarity index 100%
rename from media/patron-21.png
rename to docs/media/patron-21.png
diff --git a/media/patron-22.png b/docs/media/patron-22.png
similarity index 100%
rename from media/patron-22.png
rename to docs/media/patron-22.png
diff --git a/media/patron-23.png b/docs/media/patron-23.png
similarity index 100%
rename from media/patron-23.png
rename to docs/media/patron-23.png
diff --git a/media/patron-24.png b/docs/media/patron-24.png
similarity index 100%
rename from media/patron-24.png
rename to docs/media/patron-24.png
diff --git a/media/patron-25.png b/docs/media/patron-25.png
similarity index 100%
rename from media/patron-25.png
rename to docs/media/patron-25.png
diff --git a/media/patron-26.png b/docs/media/patron-26.png
similarity index 100%
rename from media/patron-26.png
rename to docs/media/patron-26.png
diff --git a/media/patron-27.png b/docs/media/patron-27.png
similarity index 100%
rename from media/patron-27.png
rename to docs/media/patron-27.png
diff --git a/media/patron-28.png b/docs/media/patron-28.png
similarity index 100%
rename from media/patron-28.png
rename to docs/media/patron-28.png
diff --git a/media/patron-29.png b/docs/media/patron-29.png
similarity index 100%
rename from media/patron-29.png
rename to docs/media/patron-29.png
diff --git a/media/patron-3.png b/docs/media/patron-3.png
similarity index 100%
rename from media/patron-3.png
rename to docs/media/patron-3.png
diff --git a/media/patron-30.png b/docs/media/patron-30.png
similarity index 100%
rename from media/patron-30.png
rename to docs/media/patron-30.png
diff --git a/media/patron-31.png b/docs/media/patron-31.png
similarity index 100%
rename from media/patron-31.png
rename to docs/media/patron-31.png
diff --git a/media/patron-32.png b/docs/media/patron-32.png
similarity index 100%
rename from media/patron-32.png
rename to docs/media/patron-32.png
diff --git a/media/patron-3a.png b/docs/media/patron-3a.png
similarity index 100%
rename from media/patron-3a.png
rename to docs/media/patron-3a.png
diff --git a/media/patron-4.png b/docs/media/patron-4.png
similarity index 100%
rename from media/patron-4.png
rename to docs/media/patron-4.png
diff --git a/media/patron-5.png b/docs/media/patron-5.png
similarity index 100%
rename from media/patron-5.png
rename to docs/media/patron-5.png
diff --git a/media/patron-6.png b/docs/media/patron-6.png
similarity index 100%
rename from media/patron-6.png
rename to docs/media/patron-6.png
diff --git a/media/patron-7.png b/docs/media/patron-7.png
similarity index 100%
rename from media/patron-7.png
rename to docs/media/patron-7.png
diff --git a/media/patron-8.png b/docs/media/patron-8.png
similarity index 100%
rename from media/patron-8.png
rename to docs/media/patron-8.png
diff --git a/media/patron-9.png b/docs/media/patron-9.png
similarity index 100%
rename from media/patron-9.png
rename to docs/media/patron-9.png
diff --git a/media/patron-record-status-1.png b/docs/media/patron-record-status-1.png
similarity index 100%
rename from media/patron-record-status-1.png
rename to docs/media/patron-record-status-1.png
diff --git a/media/patron-record-status-dark-grey.png b/docs/media/patron-record-status-dark-grey.png
similarity index 100%
rename from media/patron-record-status-dark-grey.png
rename to docs/media/patron-record-status-dark-grey.png
diff --git a/media/patron-record-status-green.png b/docs/media/patron-record-status-green.png
similarity index 100%
rename from media/patron-record-status-green.png
rename to docs/media/patron-record-status-green.png
diff --git a/media/patron-record-status-light-grey.png b/docs/media/patron-record-status-light-grey.png
similarity index 100%
rename from media/patron-record-status-light-grey.png
rename to docs/media/patron-record-status-light-grey.png
diff --git a/media/patron-record-status-orange.png b/docs/media/patron-record-status-orange.png
similarity index 100%
rename from media/patron-record-status-orange.png
rename to docs/media/patron-record-status-orange.png
diff --git a/media/patron-record-status-purple.png b/docs/media/patron-record-status-purple.png
similarity index 100%
rename from media/patron-record-status-purple.png
rename to docs/media/patron-record-status-purple.png
diff --git a/media/patron-record-status-red.png b/docs/media/patron-record-status-red.png
similarity index 100%
rename from media/patron-record-status-red.png
rename to docs/media/patron-record-status-red.png
diff --git a/media/patron-record-status-yellow.png b/docs/media/patron-record-status-yellow.png
similarity index 100%
rename from media/patron-record-status-yellow.png
rename to docs/media/patron-record-status-yellow.png
diff --git a/media/patron_summary_checkouts.jpg b/docs/media/patron_summary_checkouts.jpg
similarity index 100%
rename from media/patron_summary_checkouts.jpg
rename to docs/media/patron_summary_checkouts.jpg
diff --git a/media/pdf_icon.gif b/docs/media/pdf_icon.gif
similarity index 100%
rename from media/pdf_icon.gif
rename to docs/media/pdf_icon.gif
diff --git a/media/pre_cat_alert.png b/docs/media/pre_cat_alert.png
similarity index 100%
rename from media/pre_cat_alert.png
rename to docs/media/pre_cat_alert.png
diff --git a/media/precat.png b/docs/media/precat.png
similarity index 100%
rename from media/precat.png
rename to docs/media/precat.png
diff --git a/media/profile-5.png b/docs/media/profile-5.png
similarity index 100%
rename from media/profile-5.png
rename to docs/media/profile-5.png
diff --git a/media/profile-6.png b/docs/media/profile-6.png
similarity index 100%
rename from media/profile-6.png
rename to docs/media/profile-6.png
diff --git a/media/profile-7.png b/docs/media/profile-7.png
similarity index 100%
rename from media/profile-7.png
rename to docs/media/profile-7.png
diff --git a/media/receipt-10.jpg b/docs/media/receipt-10.jpg
similarity index 100%
rename from media/receipt-10.jpg
rename to docs/media/receipt-10.jpg
diff --git a/media/receipt-11.jpg b/docs/media/receipt-11.jpg
similarity index 100%
rename from media/receipt-11.jpg
rename to docs/media/receipt-11.jpg
diff --git a/media/receipt-12.jpg b/docs/media/receipt-12.jpg
similarity index 100%
rename from media/receipt-12.jpg
rename to docs/media/receipt-12.jpg
diff --git a/media/receipt-13.jpg b/docs/media/receipt-13.jpg
similarity index 100%
rename from media/receipt-13.jpg
rename to docs/media/receipt-13.jpg
diff --git a/media/receipt-14.jpg b/docs/media/receipt-14.jpg
similarity index 100%
rename from media/receipt-14.jpg
rename to docs/media/receipt-14.jpg
diff --git a/media/receipt-15.jpg b/docs/media/receipt-15.jpg
similarity index 100%
rename from media/receipt-15.jpg
rename to docs/media/receipt-15.jpg
diff --git a/media/receipt-16.png b/docs/media/receipt-16.png
similarity index 100%
rename from media/receipt-16.png
rename to docs/media/receipt-16.png
diff --git a/media/receipt-17.jpg b/docs/media/receipt-17.jpg
similarity index 100%
rename from media/receipt-17.jpg
rename to docs/media/receipt-17.jpg
diff --git a/media/receipt-18.jpg b/docs/media/receipt-18.jpg
similarity index 100%
rename from media/receipt-18.jpg
rename to docs/media/receipt-18.jpg
diff --git a/media/receipt-19.jpg b/docs/media/receipt-19.jpg
similarity index 100%
rename from media/receipt-19.jpg
rename to docs/media/receipt-19.jpg
diff --git a/media/receipt-2.jpg b/docs/media/receipt-2.jpg
similarity index 100%
rename from media/receipt-2.jpg
rename to docs/media/receipt-2.jpg
diff --git a/media/receipt-20.jpg b/docs/media/receipt-20.jpg
similarity index 100%
rename from media/receipt-20.jpg
rename to docs/media/receipt-20.jpg
diff --git a/media/receipt-21.jpg b/docs/media/receipt-21.jpg
similarity index 100%
rename from media/receipt-21.jpg
rename to docs/media/receipt-21.jpg
diff --git a/media/receipt-22.jpg b/docs/media/receipt-22.jpg
similarity index 100%
rename from media/receipt-22.jpg
rename to docs/media/receipt-22.jpg
diff --git a/media/receipt-23.jpg b/docs/media/receipt-23.jpg
similarity index 100%
rename from media/receipt-23.jpg
rename to docs/media/receipt-23.jpg
diff --git a/media/receipt-24.jpg b/docs/media/receipt-24.jpg
similarity index 100%
rename from media/receipt-24.jpg
rename to docs/media/receipt-24.jpg
diff --git a/media/receipt-3.jpg b/docs/media/receipt-3.jpg
similarity index 100%
rename from media/receipt-3.jpg
rename to docs/media/receipt-3.jpg
diff --git a/media/receipt-4.jpg b/docs/media/receipt-4.jpg
similarity index 100%
rename from media/receipt-4.jpg
rename to docs/media/receipt-4.jpg
diff --git a/media/receipt-5.jpg b/docs/media/receipt-5.jpg
similarity index 100%
rename from media/receipt-5.jpg
rename to docs/media/receipt-5.jpg
diff --git a/media/receipt-6.jpg b/docs/media/receipt-6.jpg
similarity index 100%
rename from media/receipt-6.jpg
rename to docs/media/receipt-6.jpg
diff --git a/media/receipt-7.jpg b/docs/media/receipt-7.jpg
similarity index 100%
rename from media/receipt-7.jpg
rename to docs/media/receipt-7.jpg
diff --git a/media/receipt-8.jpg b/docs/media/receipt-8.jpg
similarity index 100%
rename from media/receipt-8.jpg
rename to docs/media/receipt-8.jpg
diff --git a/media/receipt-9.jpg b/docs/media/receipt-9.jpg
similarity index 100%
rename from media/receipt-9.jpg
rename to docs/media/receipt-9.jpg
diff --git a/media/record_in_house_action.png b/docs/media/record_in_house_action.png
similarity index 100%
rename from media/record_in_house_action.png
rename to docs/media/record_in_house_action.png
diff --git a/media/renew_action.png b/docs/media/renew_action.png
similarity index 100%
rename from media/renew_action.png
rename to docs/media/renew_action.png
diff --git a/media/renew_item.png b/docs/media/renew_item.png
similarity index 100%
rename from media/renew_item.png
rename to docs/media/renew_item.png
diff --git a/media/renew_item_calendar.png b/docs/media/renew_item_calendar.png
similarity index 100%
rename from media/renew_item_calendar.png
rename to docs/media/renew_item_calendar.png
diff --git a/media/renew_specific_date.png b/docs/media/renew_specific_date.png
similarity index 100%
rename from media/renew_specific_date.png
rename to docs/media/renew_specific_date.png
diff --git a/media/retrieve_patron.png b/docs/media/retrieve_patron.png
similarity index 100%
rename from media/retrieve_patron.png
rename to docs/media/retrieve_patron.png
diff --git a/media/scv-crec.jpg b/docs/media/scv-crec.jpg
similarity index 100%
rename from media/scv-crec.jpg
rename to docs/media/scv-crec.jpg
diff --git a/media/scv-distr.jpg b/docs/media/scv-distr.jpg
similarity index 100%
rename from media/scv-distr.jpg
rename to docs/media/scv-distr.jpg
diff --git a/media/scv-iss.jpg b/docs/media/scv-iss.jpg
similarity index 100%
rename from media/scv-iss.jpg
rename to docs/media/scv-iss.jpg
diff --git a/media/scv-rec.jpg b/docs/media/scv-rec.jpg
similarity index 100%
rename from media/scv-rec.jpg
rename to docs/media/scv-rec.jpg
diff --git a/media/scv-srec.jpg b/docs/media/scv-srec.jpg
similarity index 100%
rename from media/scv-srec.jpg
rename to docs/media/scv-srec.jpg
diff --git a/media/scv-sub.jpg b/docs/media/scv-sub.jpg
similarity index 100%
rename from media/scv-sub.jpg
rename to docs/media/scv-sub.jpg
diff --git a/media/server-3.png b/docs/media/server-3.png
similarity index 100%
rename from media/server-3.png
rename to docs/media/server-3.png
diff --git a/media/server-4.png b/docs/media/server-4.png
similarity index 100%
rename from media/server-4.png
rename to docs/media/server-4.png
diff --git a/media/server-5.png b/docs/media/server-5.png
similarity index 100%
rename from media/server-5.png
rename to docs/media/server-5.png
diff --git a/media/server-6.png b/docs/media/server-6.png
similarity index 100%
rename from media/server-6.png
rename to docs/media/server-6.png
diff --git a/media/shared-template-6.png b/docs/media/shared-template-6.png
similarity index 100%
rename from media/shared-template-6.png
rename to docs/media/shared-template-6.png
diff --git a/media/shared-template-7.png b/docs/media/shared-template-7.png
similarity index 100%
rename from media/shared-template-7.png
rename to docs/media/shared-template-7.png
diff --git a/media/shared-template-9.png b/docs/media/shared-template-9.png
similarity index 100%
rename from media/shared-template-9.png
rename to docs/media/shared-template-9.png
diff --git a/media/small_logo_white.jpg b/docs/media/small_logo_white.jpg
similarity index 100%
rename from media/small_logo_white.jpg
rename to docs/media/small_logo_white.jpg
diff --git a/media/specify_due_date1.png b/docs/media/specify_due_date1.png
similarity index 100%
rename from media/specify_due_date1.png
rename to docs/media/specify_due_date1.png
diff --git a/media/specify_due_date2.png b/docs/media/specify_due_date2.png
similarity index 100%
rename from media/specify_due_date2.png
rename to docs/media/specify_due_date2.png
diff --git a/media/staffclient-1.png b/docs/media/staffclient-1.png
similarity index 100%
rename from media/staffclient-1.png
rename to docs/media/staffclient-1.png
diff --git a/media/staffclient-2.png b/docs/media/staffclient-2.png
similarity index 100%
rename from media/staffclient-2.png
rename to docs/media/staffclient-2.png
diff --git a/media/staffclient-3.png b/docs/media/staffclient-3.png
similarity index 100%
rename from media/staffclient-3.png
rename to docs/media/staffclient-3.png
diff --git a/media/staffclient-4.png b/docs/media/staffclient-4.png
similarity index 100%
rename from media/staffclient-4.png
rename to docs/media/staffclient-4.png
diff --git a/media/staffclient-5.png b/docs/media/staffclient-5.png
similarity index 100%
rename from media/staffclient-5.png
rename to docs/media/staffclient-5.png
diff --git a/media/staffclient-6.png b/docs/media/staffclient-6.png
similarity index 100%
rename from media/staffclient-6.png
rename to docs/media/staffclient-6.png
diff --git a/media/staffclient-6a.png b/docs/media/staffclient-6a.png
similarity index 100%
rename from media/staffclient-6a.png
rename to docs/media/staffclient-6a.png
diff --git a/media/staffclient-6b.png b/docs/media/staffclient-6b.png
similarity index 100%
rename from media/staffclient-6b.png
rename to docs/media/staffclient-6b.png
diff --git a/media/staffclient-6c.png b/docs/media/staffclient-6c.png
similarity index 100%
rename from media/staffclient-6c.png
rename to docs/media/staffclient-6c.png
diff --git a/media/staffclient-6d.png b/docs/media/staffclient-6d.png
similarity index 100%
rename from media/staffclient-6d.png
rename to docs/media/staffclient-6d.png
diff --git a/media/staffclient-7.png b/docs/media/staffclient-7.png
similarity index 100%
rename from media/staffclient-7.png
rename to docs/media/staffclient-7.png
diff --git a/media/staffclient-7a.png b/docs/media/staffclient-7a.png
similarity index 100%
rename from media/staffclient-7a.png
rename to docs/media/staffclient-7a.png
diff --git a/media/staffclient-8.png b/docs/media/staffclient-8.png
similarity index 100%
rename from media/staffclient-8.png
rename to docs/media/staffclient-8.png
diff --git a/media/staffclient-9.png b/docs/media/staffclient-9.png
similarity index 100%
rename from media/staffclient-9.png
rename to docs/media/staffclient-9.png
diff --git a/media/staffclientinstallation-proxy-putty-1.png b/docs/media/staffclientinstallation-proxy-putty-1.png
similarity index 100%
rename from media/staffclientinstallation-proxy-putty-1.png
rename to docs/media/staffclientinstallation-proxy-putty-1.png
diff --git a/media/staffclientinstallation-proxy-socks-1.png b/docs/media/staffclientinstallation-proxy-socks-1.png
similarity index 100%
rename from media/staffclientinstallation-proxy-socks-1.png
rename to docs/media/staffclientinstallation-proxy-socks-1.png
diff --git a/media/staffclientinstallation-proxy-socks-2.png b/docs/media/staffclientinstallation-proxy-socks-2.png
similarity index 100%
rename from media/staffclientinstallation-proxy-socks-2.png
rename to docs/media/staffclientinstallation-proxy-socks-2.png
diff --git a/media/staffclientinstallation-staffclient-1.png b/docs/media/staffclientinstallation-staffclient-1.png
similarity index 100%
rename from media/staffclientinstallation-staffclient-1.png
rename to docs/media/staffclientinstallation-staffclient-1.png
diff --git a/media/staffclientinstallation-staffclient-2.png b/docs/media/staffclientinstallation-staffclient-2.png
similarity index 100%
rename from media/staffclientinstallation-staffclient-2.png
rename to docs/media/staffclientinstallation-staffclient-2.png
diff --git a/media/staffclientinstallation-staffclient-3.png b/docs/media/staffclientinstallation-staffclient-3.png
similarity index 100%
rename from media/staffclientinstallation-staffclient-3.png
rename to docs/media/staffclientinstallation-staffclient-3.png
diff --git a/media/staffclientinstallation-staffclient-4.png b/docs/media/staffclientinstallation-staffclient-4.png
similarity index 100%
rename from media/staffclientinstallation-staffclient-4.png
rename to docs/media/staffclientinstallation-staffclient-4.png
diff --git a/media/staffclientinstallation-staffclient-workstationnames-1.png b/docs/media/staffclientinstallation-staffclient-workstationnames-1.png
similarity index 100%
rename from media/staffclientinstallation-staffclient-workstationnames-1.png
rename to docs/media/staffclientinstallation-staffclient-workstationnames-1.png
diff --git a/media/staffclientinstallation-staffclient-workstationnames-2.png b/docs/media/staffclientinstallation-staffclient-workstationnames-2.png
similarity index 100%
rename from media/staffclientinstallation-staffclient-workstationnames-2.png
rename to docs/media/staffclientinstallation-staffclient-workstationnames-2.png
diff --git a/media/staffclientinstallation-staffclient-workstationnames-3.png b/docs/media/staffclientinstallation-staffclient-workstationnames-3.png
similarity index 100%
rename from media/staffclientinstallation-staffclient-workstationnames-3.png
rename to docs/media/staffclientinstallation-staffclient-workstationnames-3.png
diff --git a/media/staffclientinstallation-tabbed-1.png b/docs/media/staffclientinstallation-tabbed-1.png
similarity index 100%
rename from media/staffclientinstallation-tabbed-1.png
rename to docs/media/staffclientinstallation-tabbed-1.png
diff --git a/media/survey-1.png b/docs/media/survey-1.png
similarity index 100%
rename from media/survey-1.png
rename to docs/media/survey-1.png
diff --git a/media/survey-10.png b/docs/media/survey-10.png
similarity index 100%
rename from media/survey-10.png
rename to docs/media/survey-10.png
diff --git a/media/survey-2.png b/docs/media/survey-2.png
similarity index 100%
rename from media/survey-2.png
rename to docs/media/survey-2.png
diff --git a/media/survey-3.png b/docs/media/survey-3.png
similarity index 100%
rename from media/survey-3.png
rename to docs/media/survey-3.png
diff --git a/media/survey-4.png b/docs/media/survey-4.png
similarity index 100%
rename from media/survey-4.png
rename to docs/media/survey-4.png
diff --git a/media/survey-5.png b/docs/media/survey-5.png
similarity index 100%
rename from media/survey-5.png
rename to docs/media/survey-5.png
diff --git a/media/survey-6.png b/docs/media/survey-6.png
similarity index 100%
rename from media/survey-6.png
rename to docs/media/survey-6.png
diff --git a/media/survey-7.png b/docs/media/survey-7.png
similarity index 100%
rename from media/survey-7.png
rename to docs/media/survey-7.png
diff --git a/media/survey-8.png b/docs/media/survey-8.png
similarity index 100%
rename from media/survey-8.png
rename to docs/media/survey-8.png
diff --git a/media/survey-9.png b/docs/media/survey-9.png
similarity index 100%
rename from media/survey-9.png
rename to docs/media/survey-9.png
diff --git a/media/tip.png b/docs/media/tip.png
similarity index 100%
rename from media/tip.png
rename to docs/media/tip.png
diff --git a/media/transit-1.png b/docs/media/transit-1.png
similarity index 100%
rename from media/transit-1.png
rename to docs/media/transit-1.png
diff --git a/media/transit-10.png b/docs/media/transit-10.png
similarity index 100%
rename from media/transit-10.png
rename to docs/media/transit-10.png
diff --git a/media/transit-2.png b/docs/media/transit-2.png
similarity index 100%
rename from media/transit-2.png
rename to docs/media/transit-2.png
diff --git a/media/transit-3.png b/docs/media/transit-3.png
similarity index 100%
rename from media/transit-3.png
rename to docs/media/transit-3.png
diff --git a/media/transit-4a.png b/docs/media/transit-4a.png
similarity index 100%
rename from media/transit-4a.png
rename to docs/media/transit-4a.png
diff --git a/media/transit-5.png b/docs/media/transit-5.png
similarity index 100%
rename from media/transit-5.png
rename to docs/media/transit-5.png
diff --git a/media/transit-6.png b/docs/media/transit-6.png
similarity index 100%
rename from media/transit-6.png
rename to docs/media/transit-6.png
diff --git a/media/transit-7.png b/docs/media/transit-7.png
similarity index 100%
rename from media/transit-7.png
rename to docs/media/transit-7.png
diff --git a/media/transit-8.png b/docs/media/transit-8.png
similarity index 100%
rename from media/transit-8.png
rename to docs/media/transit-8.png
diff --git a/media/transit-9.png b/docs/media/transit-9.png
similarity index 100%
rename from media/transit-9.png
rename to docs/media/transit-9.png
diff --git a/media/unified_volume_copy_creator1.jpg b/docs/media/unified_volume_copy_creator1.jpg
similarity index 100%
rename from media/unified_volume_copy_creator1.jpg
rename to docs/media/unified_volume_copy_creator1.jpg
diff --git a/media/unified_volume_copy_creator2.jpg b/docs/media/unified_volume_copy_creator2.jpg
similarity index 100%
rename from media/unified_volume_copy_creator2.jpg
rename to docs/media/unified_volume_copy_creator2.jpg
diff --git a/media/unified_volume_copy_creator3.jpg b/docs/media/unified_volume_copy_creator3.jpg
similarity index 100%
rename from media/unified_volume_copy_creator3.jpg
rename to docs/media/unified_volume_copy_creator3.jpg
diff --git a/media/unified_volume_copy_creator4.jpg b/docs/media/unified_volume_copy_creator4.jpg
similarity index 100%
rename from media/unified_volume_copy_creator4.jpg
rename to docs/media/unified_volume_copy_creator4.jpg
diff --git a/media/unified_volume_copy_creator5.jpg b/docs/media/unified_volume_copy_creator5.jpg
similarity index 100%
rename from media/unified_volume_copy_creator5.jpg
rename to docs/media/unified_volume_copy_creator5.jpg
diff --git a/media/unified_volume_copy_creator6.jpg b/docs/media/unified_volume_copy_creator6.jpg
similarity index 100%
rename from media/unified_volume_copy_creator6.jpg
rename to docs/media/unified_volume_copy_creator6.jpg
diff --git a/media/view-output-1.png b/docs/media/view-output-1.png
similarity index 100%
rename from media/view-output-1.png
rename to docs/media/view-output-1.png
diff --git a/media/view-output-2.png b/docs/media/view-output-2.png
similarity index 100%
rename from media/view-output-2.png
rename to docs/media/view-output-2.png
diff --git a/media/view-output-3.png b/docs/media/view-output-3.png
similarity index 100%
rename from media/view-output-3.png
rename to docs/media/view-output-3.png
diff --git a/media/view-output-4.png b/docs/media/view-output-4.png
similarity index 100%
rename from media/view-output-4.png
rename to docs/media/view-output-4.png
diff --git a/media/view-output-5.png b/docs/media/view-output-5.png
similarity index 100%
rename from media/view-output-5.png
rename to docs/media/view-output-5.png
diff --git a/media/warning.png b/docs/media/warning.png
similarity index 100%
rename from media/warning.png
rename to docs/media/warning.png
diff --git a/opac/my_lists.txt b/docs/opac/my_lists.txt
similarity index 100%
rename from opac/my_lists.txt
rename to docs/opac/my_lists.txt
diff --git a/reports/README b/docs/reports/README
similarity index 100%
rename from reports/README
rename to docs/reports/README
diff --git a/root.txt b/docs/root.txt
similarity index 95%
rename from root.txt
rename to docs/root.txt
index 3a39c65..5c03084 100644
--- a/root.txt
+++ b/docs/root.txt
@@ -60,7 +60,7 @@ in over a dozen countries worldwide.
// Push titles down one level.
:leveloffset: 1
-include::release_notes.txt[]
+include::RELEASE_NOTES_2_2.txt[]
// Return to normal title levels.
:leveloffset: 0
diff --git a/serials/A-intro.txt b/docs/serials/A-intro.txt
similarity index 100%
rename from serials/A-intro.txt
rename to docs/serials/A-intro.txt
diff --git a/serials/B-copy_template.txt b/docs/serials/B-copy_template.txt
similarity index 100%
rename from serials/B-copy_template.txt
rename to docs/serials/B-copy_template.txt
diff --git a/serials/C-subscription-SCV.txt b/docs/serials/C-subscription-SCV.txt
similarity index 100%
rename from serials/C-subscription-SCV.txt
rename to docs/serials/C-subscription-SCV.txt
diff --git a/serials/D-subscription-ASCV.txt b/docs/serials/D-subscription-ASCV.txt
similarity index 100%
rename from serials/D-subscription-ASCV.txt
rename to docs/serials/D-subscription-ASCV.txt
diff --git a/serials/E-edit_subscriptions.txt b/docs/serials/E-edit_subscriptions.txt
similarity index 100%
rename from serials/E-edit_subscriptions.txt
rename to docs/serials/E-edit_subscriptions.txt
diff --git a/serials/F-Receiving.txt b/docs/serials/F-Receiving.txt
similarity index 100%
rename from serials/F-Receiving.txt
rename to docs/serials/F-Receiving.txt
diff --git a/serials/G-Special_issue.txt b/docs/serials/G-Special_issue.txt
similarity index 100%
rename from serials/G-Special_issue.txt
rename to docs/serials/G-Special_issue.txt
diff --git a/serials/H-holdings_statements.txt b/docs/serials/H-holdings_statements.txt
similarity index 100%
rename from serials/H-holdings_statements.txt
rename to docs/serials/H-holdings_statements.txt
diff --git a/release_notes.txt b/release_notes.txt
deleted file mode 100644
index e382742..0000000
--- a/release_notes.txt
+++ /dev/null
@@ -1,611 +0,0 @@
-Release notes
-=============
-:toc:
-:numbered:
-
-Upgrade notes
--------------
-
-Z39.50 Server Definitions
-~~~~~~~~~~~~~~~~~~~~~~~
-Z39.50 server target definitions have been removed from the sample
-`opensrf.xml.example` file. To migrate existing settings from your
-`opensrf.xml` configuration file to the database, peform the
-following steps:
-
- 1. First, set up your custom Z39.50 sources in the database. For
- each entry in `z3950/services`, map the following XML paths to the
- corresponding `config.z3950_source` table column as follows:
-+
- ** `z3950/services/<entry>` = name
- ** `//<entry>/name` = label
- ** `//<entry>/host` = host
- ** `//<entry>/port` = port
- ** `//<entry>/db` = db
- ** `//<entry>/record_format` = record_format
- ** `//<entry>/transmission_format` = transmission_format
-+
- 2. Then, for each attribute defined in the `<attrs>` element for
- a given service, map the following XML paths to the corresponding
- `config.z3950_attr` table column as follows:
-+
- ** `z3950/services/<entry>` = source
- ** `//<entry>/attrs/<attr>` = name
- ** `//<entry>/attrs/<attr>/code` = code
- ** `//<entry>/attrs/<attr>/format` = format
-+
- 3. After adding the new Z39.50 sources and corresponding attributes,
- you will need to log out of the staff client and log back into the
- staff client to retrieve the new entry values. If a given Z39.50
- server does not work for a given attribute, pay attention to the
- `truncation` column for the attribute.
-
-
-New features
-------------
-
-Administration
-~~~~~~~~~~~~
-
-Custom Org Unit Trees
-^^^^^^^^^^^^^^^^^^^^^
-Evergreen enables you to create an organizational tree that describes the
-systems, branches, or other units that comprise your organization. By default,
-the org unit tree that appears to patrons in the OPAC is identical to the one
-that appears to users of the staff client. Using this feature, you can condense
-or re-order the organizational tree into a simpler structure for patrons using
-the OPAC while maintaining the complex organizational tree that is available to
-users of the staff client.
-
-As a further enhancement, you can hide a parental org unit yet still make its
-child org units visible in the OPAC. In previous versions of Evergreen, child
-org units inherited the visibility setting of their parents.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Fine Accrual on Closed Dates
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-By default, fines accrue only on dates that the library is open. This feature
-enables you to charge patrons fines on dates the library is closed. Fines
-accrue during scheduled closings as well as during normal weekly closed dates.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Target Copies for Holds at Closed Libraries
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-By default, when a patron places a hold on a title, the hold targeter will
-search for copies to fill the hold only at circulating libraries that are open.
-Copies at closed libraries are not targeted to fill holds. When turned on, this
-feature enables Evergreen to target copies that have closed circulating
-libraries to fill holds. Two new org unit settings control this feature.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-OPAC
-~~~~
-
-Template Toolkit OPAC (_TPAC_)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The basic catalog has been replaced by the Template Toolkit OPAC (_TPAC_).
-Compared to the traditional catalog (_JSPAC_), TPAC uses far fewer network
-calls for each page, resulting in faster loading pages. TPAC is built on the
-http://template-toolkit.org[Template Toolkit] language to enable simple but
-powerful customization, and supports integrated `gettext`-based translation
-for strings--including placeholders and quantities--for better
-internationalization support.
-
-The next feature release of Evergreen will make TPAC the primary catalog
-and deprecate the use of the JSPAC.
-
-Auto Suggest in Catalog Search
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The
-http://docs.evergreen-ils.org/2.2/_auto_suggest_in_catalog_search_2.html[auto
-suggest feature] suggests the completion of search terms as the user enters his
-query. By default, the user will see ten suggestions although this
-number is configurable at the database level. Scroll through suggestions with
-your mouse, or use the arrow keys to scroll through the suggestions. Select a
-suggestion to view records that are linked to this suggestion.
-
-This feature is not turned on by default. You must turn it on in the Admin
-module.
-
-Copy Location Groups
-^^^^^^^^^^^^^^^^^^^^
-This feature allows staff to create and name sets of copy locations to use as
-a search filter in the catalog. OPAC-visible groups will display within the
-library selector in the template toolkit OPAC. When a user selects a group
-and performs a search, the set of results will be limited to records that have
-copies in one of the copy locations within the group. Groups can live at any
-level of the library hierarchy and may include copy locations from any parent
-org unit or child org unit.
-
-For advanced users, this change includes a new Query Parser filter called
-location_groups().
-
-My Lists
-^^^^^^^^
-The My Lists feature replaces the bookbag feature that was available in
-versions proior to 2.2. This feature enables you to create temporary and
-permanent lists; create and edit notes for items in lists; place holds on items
-in lists; and share lists via RSS feeds and CSV files.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-SMS Text Messaging
-^^^^^^^^^^^^^^^^^^
-The SMS Text Messaging feature enables users to receive hold notices via text
-message. Users can opt-in to this hold notification as their default setting
-for all holds, or they can receive specific hold notifications via text
-message. Users can also send call numbers and copy locations via text message.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-New Patron Preferences
-^^^^^^^^^^^^^^^^^^^^^^^
-Users will now have the ability to designate the following preferences in the
-Template Toolkit catalog (_TPAC_):
-
-* A preferred search location. Unlike the default search library in JSPAC, this
- setting will also control which copies display first in search results and
- record detail screens.
-* A preferred pickup location.
-* The ability to keep a history of checked out items.
-* The ability to keep a history of holds.
-
-Credit Card Payment via Public Catalog
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Patrons can now use credit cards to pay fines and bills in *My Account* of the
-TPAC.
-
-Record Detail Print and E-mail Actions
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Implements Print and Email actions as links below the *Add to List* link
-in the TPAC record detail page.
-
-Identify Previously-Checked-Out Items in Search Results
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-When a user is logged into the TPAC and performs a search, this feature
-indicates in the results set when any of the result items were ever checked
-out by the logged-in user. Items will only be tagged when the related org
-setting is enabled and the user has opted in to circ history tracking.
-
-Patron Management
-~~~~~~~~~~~~~~~~~
-
-Patron Statistical Category Enhancements
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The following enhancements have been added to patron statistical categories:
-
- * categories can be marked as 'required' (must be filled out when a patron is
- registered)
- * categories can be marked to allow or disallow user-created entries
- * an entry for a given category and org unit can be marked as the default
- entry. It will be automatically selected in the new patron registration
- screen.
-
-User Settings Available from Patron Editor
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Staff can now access and update user settings, like notification prefererences
-and default pickup library, in the patron editor.
-
-Mark Patron E-mail or Phone as Invalid
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Staff can mark a patron's email address or phone number as invalid in the
-patron editor. The system will clear the email (or phone) field from
-`actor.usr`, and [both optionally, per OU setting]:
-
- . create a corresponding standing penalty against the user, for staff to
- notice next time they bring up said patron in the staff client;
- . create a patron note. Related penalties (but not notes) will be cleared
- whenever that patron's email address or phone number is updated again.
-
-Address Alert in Patron Registration
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Support for comparing user addresses to alert addresses. When an address is
-found, the address in question is styled (the header row turns red) and the
-configured alert message is shown along the top-right, where other warnings
-appear.
-
-Circulation
-~~~~~~~~~~~
-
-Telephony Improvements
-^^^^^^^^^^^^^^^^^^^^^^
-Enhancements to notifications by telephony, including:
-
-* A feature that allows an Evergreen system to roll over failed notifcations
- into new ones with a different notification method.
-* Holiday awareness. System administrators can, via `cron`, schedule the
- `set_pbx_holidays` script on an Evergreen system to periodically update
- the PBX's table of holidays, based on a given org unit's closed date ranges.
-* Smart retry. In certain situations, if you put too many callfiles into
- Asterisk's spool at once, Asterisk will try to make too many calls at
- once, and all such calls just fail. That is what the allocator is meant to
- prevent. Smart retry is about moving calls that have been tried once, and will
- be retried again later due to resulting in a busy signal or other problem, out
- of the spool to make room for other calls that could be made in the meantime.
-
-Circulation Limit Groups & Limit Sets
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The new *Circulation Limit Groups* interface found in the *Server
-administration* menu can be thought of as _tags_ the system places on
-circulations so that it can find them later. The *Limit Sets* interface found
-in the *Local administration* menu defines rules for limiting the number of
-active circulations a patron may have based on Circulation Modifiers and Limit
-Groups. These new features support the following options:
-
-* Setting circ limits for circulations that have no circ modifiers. This is
- useful for systems with circulation rules based on something other than
- circulation modifiers (for example, *MARC type*) or for grouping items
- that may have different circulation modifiers so that, for example, you
- can count every video, regardless of circulation modifiers.
-* The ability to set limits for a single library's items, regardless of
- the checkout library.
-
-New Checkin Modifiers
-^^^^^^^^^^^^^^^^^^^^^
-The following modifiers have been added to the check-in interface:
-
-* *Clear Shelf-Expired Holds*. When checking in something on the hold shelf,
- run a 'Clear Shelf Process' for the specific copy ID at that library to
- auto-clear any Shelf-Expired holds.
-* *Retarget Local Holds*. When checking in 'in process' items that are owned by
- the library, attempt to find a local hold to retarget. This is intended to
- help with proper targeting of newly-cataloged items.
-* *Retarget All Statuses*. Similar to 'Retarget Local Holds', this modifier will
- attempt to find a local hold to retarget, regardless of the status of the
- item being checked in. This modifier must be used in conjunction with the
- 'Retarget Local Holds' modifier.
-* *Capture Local Holds as Transits*. With this checkin modifier, any local holds
- will be given an 'in transit' status instead of 'holds shelf'. The intent is
- to stop the system from sending holds notifications before the item is ready
- to be placed on the holds shelf. Possible use cases include Automated
- Materials Handling(AMH) checkins, in which items may be sitting in a bin for a
- while before landing on the holds shelf, and checkins done on closed days.
-
-Copy Location Alerts
-^^^^^^^^^^^^^^^^^^^^
-This enhancement adds a new 'checkin_alert' column to copy locations. If true
-(defaults to false), then a routing alert is generated at reshelving time for
-the location. This is intended for special locations, such as 'Display', that
-may require special handling, or that temporarily contain items that are not
-normally in that location.
-
-Age Hold Protection Based on a Copy's Active Date
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-* Adds a 'Sets copy active' column to the 'Copy Statuses' interface to identify
- statuses that indicate a copy is active and ready for checkout. The first
- time a copy is set to one of these statuses, the system adds an 'active date'
- for the copy, which can be used for reporting.
-* Provides a new library setting for age hold protection to be based on the
- copy's active date instead of its create date.
-
-Option to Place Holds on Age Protected Items
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Allow choice of placing hold despite age protection. This alters the backend to
-watch when so much as one copy failed only due to age protection. In JSPAC, an
-alternate confirm message is shown. In TPAC, the failure message is changed
-and override is always allowed for the hold in question.
-
-Force and Cataloging Recall Holds
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Creates two new types of copy-level holds, *Force* and *Cataloging Recall*,
-that cut in front of all other holds and ignore hold rules. For cataloging
-recall holds, the copy's status changes to 'cataloging' when it reaches its
-destination.
-
-Archiving Statistical Categories and Circulation-Time Copy Locations
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Circulation-time copy locations are now archived with circulations (aged or active).
-
-Using the *Statistical Categories Editor*, staff can also designate statistical
-categories (patron and copy) to archive with circulations.
-
-Browse Holds Shelf Interface Displays Canceled Holds
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Holds that are canceled after they are placed on the holds shelf will continue
-to display in this interface and will also display in the 'shelf-expired holds'
-view.
-
-Acquisitions
-~~~~~~~~~~~~
-
-Vandelay Integration into Acquisitions
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The Acquisitions Load MARC Order Record interface enables you to add MARC
-records to selection lists and purchase orders and upload the records into the
-catalog. The Vandelay interface enables you to create specific match points
-between incoming MARC records and exisiting catalog records. Combining these
-two features enables you to track on order MARC records through the
-Acquisitions interface and to utilize the record matching mechanisms available
-in Vandelay when importing acquisitions records.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Receive Items from an Invoice
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-This feature enables users to receive items from an invoice. Staff can receive
-individual copies, or they can receive items in batch.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Lineitem and Copy Actions Accessible from More Interfaces
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Users can now access lineitem actions (for example, receive, unreceive, update
-barcodes, new invoice) from the acquisitions lineitem search results and
-selection list interfaces. Also available on these interfaces is a link to copy
-details where users can take receive actions (receive, unreceive, cancel) on
-individual copies.
-
-Improved Displays for Provider and Fund Administration Pages
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-This enhancement provides improved support for viewing the provider and fund
-administation pages. It also allows staff to use filters to find providers and
-funds.
-
-Cataloging
-~~~~~~~~~~
-
-Authority Control Sets
-^^^^^^^^^^^^^^^^^^^^^^
-The tags and subfields that display in authority records in Evergreen are
-proscribed by control sets. The Library of Congress control set is the default
-control set in all versions of Evergreen. However, in Evergreen release 2.2,
-you can create customized control sets for authority records, and you can
-define thesauri and authority fields for these control sets.
-
-Patrons and staff can browse authorities in the JSPAC. The following fields are
-browsable by default: author, series, subject, title, and topic. You can add
-custom browse axes in addition to these default fields.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Batch Importing MARC Records
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The MARC Batch Import interface features improved matching of records and
-managing of your import queue. In version 2.2, you can specify match points
-between incoming and existing records to better detect matching records and
-prevent record duplication. You can also create quality controls to ensure that
-incoming matching records are superior in quality to existing catalog records.
-
-You also have new options for managing your queue. You can apply filters to
-your queue, and you can generate a list of import errors. You can also print
-your queue, email your queue, or export your queue as a CSV file.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Hide Fields in Copy Editor
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-You can customize the *Copy Editor* for staff by hiding fields in the *Copy
-Editor* that are not relevant for workflows at particular org units. Descendant
-org units inherit the settings of their parents.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Prevent Bibliographic Records from Having Attached Copies
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-To enable libraries to designate specific sets of records as only for use as
-electronic resources, it is possible to configure a bibliographic source such
-that physical copies or MFHD records may not be attached to records from that
-source. The `config.bib_source` table now includes a new Boolean column,
-`can_have_copies`, that controls this behavior. If `can_have_copies` for a
-given bibliographic source is `TRUE`, then the staff client will prevent a
-cataloger from adding volumes or MFHD records to records belonging to that
-source.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Overlay Existing Catalog Record via Z39.50 Import
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-You can replace an existing catalog record with a record obtained through a
-Z39.50 search. No new permissions or administrative settings are needed to use
-this feature.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Restrict Z39.50 Sources by Permission Group
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-You can use a permission to restrict users' access to Z39.50 servers. You can
-apply a permission to the Z39.50 servers to restrict access to that server, and
-then assign that permission to users or groups so that they can access the
-restricted servers.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Switch Copy Location Name and Library Short Name in Copy Editor
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-By default, the copy editor shows the library shortname ('BR1' or 'CONS')
-followed by the copy location name ('Stacks', 'Reference'). A new workstation
-setting, under *Admin -> Workstation Administration -> Copy Editor: Copy
-Location Name First*, enables staff to change the display so that the copy
-location name is displayed first, followed by the library shortname. This may
-be particularly useful for libraries that have defined one set of copy
-locations at the consortial level and want to enable quick keyboard navigation
-to copy locations by typing just the first letters of the copy location.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-User Activity Types
-~~~~~~~~~~~~~~~~~~~
-The User Activity Types feature enables you to specify the user activity that
-you want to record in the database. You can use this feature for reporting
-purposes. This function will also display a last activity date in a user's
-account. Currently, this feature only tracks user authentication.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Authentication Proxy
-~~~~~~~~~~~~~~~~~~
-To support integration of Evergreen with organizational authentication systems,
-and to reduce the proliferation of user names and passwords, Evergreen offers
-a new service called `open-ils.auth_proxy`. If you enable the service,
-`open-ils.auth_proxy` supports different authentication mechanisms
-that implement the `authenticate` method. You can define a chain of these
-authentication mechanisms to be tried in order within the `<authenticators>`
-element of the `opensrf.xml` configuration file, with the option of falling
-back to the `native` mode that uses Evergreen's internal method of password
-authentication.
-
-This service only provides authentication; there is no support for automatic
-provisioning of accounts. To authenticate against any authentication system,
-the user account must first be defined within the Evergreen system, and
-authentication will be based on the user name as it exists in Evergreen.
-
-A sample authentication mechanism for LDAP is provided in
-`Open-ILS::Application::AuthProxy::LDAP_AUTH`, and corresponding sample
-attributes can be found in `opensrf.xml.example`.
-
-Auditor Tables
-~~~~~~~~~~~~~~
-This enhancement adds user and workstation IDs to the auditor tables. It also
-adds/changes auditor functions to allow for setting, getting, and clearing
-auditor information, as well as adding a couple of utility functions for
-updating auditors after changes to their origin columns.
-
-Reports
-~~~~~~~
-
-New Views for Reporting Sources
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-To support the creation of collection development reports, the following
-reporting sources have been added:
-
- * 'Last Circulation or Creation Date' is a source that offers the copy ID,
- the last circulation date or creation date, and the last circulation date
- * 'Hold/Copy Ratio per Bib and Pickup Library' is a source that calculates
- the number of holds per copy per bibliographic record, with granularity
- by pickup library.
-
-
-Staff Client Navigation
-~~~~~~~~~~~~~~~~~~~~~~~
-
-Customizable Toolbar
-^^^^^^^^^^^^^^^^^^^^
-By default, two toolbars are available in the staff client: circulation and
-cataloging. This feature enables you to customize toolbars in the staff client.
-You can add buttons that will enable quick access to a variety of features.
-You can create toolbars for specific org unit(s), workstation(s), or login(s).
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Double Clicking in the Staff Client
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-You can search for a patron's record, and double click on a result to access
-that record. You can double click on an item in the *Holdings Maintenance*
-screen to access copy information. The item is linked to the *Volume/Copy
-Creator*, if you turned it on in the staff client's org unit settings. If you
-did not turn on the *Volume/Copy Creator*, then the item links to the *Item
-Attributes*.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Recent Staff Searches
-^^^^^^^^^^^^^^^^^^^^^
-You can view your recent searches as you perform them in the staff client. By
-default, staff can view their recent searches, although the number is
-configurable. This feature is only available through the staff client; it is
-not available to patrons in the OPAC.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Return to Search Results from MARC Record
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-This feature enables you to return to your title search results directly from
-any view of the MARC record, including the *OPAC View*, *MARC Record*, *MARC
-Edit*, and *Holdings Maintenance* views. You can use this feature to page
-through records in the *MARC Record View* or *Edit* interfaces. You do not have
-to return to the *OPAC View* to access title results.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Sorting Columns
-^^^^^^^^^^^^^^^
-This feature enables you to sort by multiple display columns so that you can
-find easily the information that you need on a screen. You can sort display
-columns on any screen that is built on a grid, such as the *Check In* screen or
-the *On Shelf Pull List*.
-
-You can also sort the columns on the following *Administration* screens:
-
- * Circulation Policies
- * Hold Policies
- * Circulation Limit Sets
- * Barcode Completion
- * Acquisitions User Request List
- * Vandelay Import Errors
-
-You can sort items in an ascending or descending order, and you can prioritize
-the order in which columns will sort.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Tab Button
-^^^^^^^^^^
-This feature enables you to add a new tab to the Evergreen staff client by
-clicking the *+* sign adjacent to the tab that you currently have opened. As in
-previous versions, you can also add new tabs by clicking *File -> New Tab*, or
-use the hotkey, *Ctrl+T*.
-
-Documentation for this feature is available in the Book of Evergreen at
-http://docs.evergreen-ils.org/2.2/
-
-Close All Tabs Shortcut
-^^^^^^^^^^^^^^^^^^^^^^^
-You can use *CTRL+Click* on the close tab (*X*) button to close all tabs.
-
-Independent Column Configurations and Receipt Templates for Different Hold List Interfaces
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Previously, all hold list interfaces shared the same column picker settings and
-receipt templates. This enhancement creates independent settings for the
-following interfaces:
-
-* Actions for this Record -> View Holds
-* Patron Display -> Holds
-* Circulation -> Browse Hold Shelf
-* Circulation -> Pull List for Hold Requests
-
-Line Number Columns
-^^^^^^^^^^^^^^^^^^^
-List displays in the staff client now have a non-sortable line number column
-which displays the ordinal position of each row in the list. The first row in
-such a list will always have a value of 1 in the ordinal column, no matter how
-the list is sorted. There is no special handling for paged interfaces; the
-first row on any given page still gets an ordinal value of 1.
-
-Auto-Login
-^^^^^^^^^^
-Supports auto-login in the staff client by adding three new command line
-parameters:
-
-* `-ILSuser`: user name to log in with
-* `-ILSpassword`: password to use
-* `-ILShost`: hostname to use
-
-License
--------
-This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
-Unported License. To view a copy of this license, visit
-http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative
-Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.
commit 2ed40844755f81d399e0f5ae855e20906aa8fdc1
Merge: a5e1040 018034d
Author: Dan Scott <dscott at laurentian.ca>
Date: Fri Jul 13 23:19:09 2012 -0400
Merge remote-tracking branch 'docbook/master' into docs_merge
Conflicts:
README
Signed-off-by: Dan Scott <dscott at laurentian.ca>
commit 018034d1305d139228584006586174ac1117fde6
Author: rsoulliere <robert.soulliere at mohawkcollege.ca>
Date: Wed May 30 15:59:14 2012 -0400
removing adobe KDE supplied pdf image means we no longer need extra licensing note.
diff --git a/licensing.txt b/licensing.txt
index 64f7a56..a9f2ec3 100644
--- a/licensing.txt
+++ b/licensing.txt
@@ -10,180 +10,4 @@ This work is licensed under a
link:http://creativecommons.org/licenses/by-sa/3.0/[Creative
Commons Attribution-ShareAlike 3.0 Unported License].
-Additional Licensed Content
----------------------------
-The
-
-image::media/application-pdf.png["PDF"]
-
-icon comes from the KDE project at: http://kde.org/ and is licensed under the GNU
-Lesser General Public License 3.0
-
-....
-GNU LESSER GENERAL PUBLIC LICENSE
- Version 3, 29 June 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-
- This version of the GNU Lesser General Public License incorporates
-the terms and conditions of version 3 of the GNU General Public
-License, supplemented by the additional permissions listed below.
-
- 0. Additional Definitions.
-
- As used herein, "this License" refers to version 3 of the GNU Lesser
-General Public License, and the "GNU GPL" refers to version 3 of the GNU
-General Public License.
-
- "The Library" refers to a covered work governed by this License,
-other than an Application or a Combined Work as defined below.
-
- An "Application" is any work that makes use of an interface provided
-by the Library, but which is not otherwise based on the Library.
-Defining a subclass of a class defined by the Library is deemed a mode
-of using an interface provided by the Library.
-
- A "Combined Work" is a work produced by combining or linking an
-Application with the Library. The particular version of the Library
-with which the Combined Work was made is also called the "Linked
-Version".
-
- The "Minimal Corresponding Source" for a Combined Work means the
-Corresponding Source for the Combined Work, excluding any source code
-for portions of the Combined Work that, considered in isolation, are
-based on the Application, and not on the Linked Version.
-
- The "Corresponding Application Code" for a Combined Work means the
-object code and/or source code for the Application, including any data
-and utility programs needed for reproducing the Combined Work from the
-Application, but excluding the System Libraries of the Combined Work.
-
- 1. Exception to Section 3 of the GNU GPL.
-
- You may convey a covered work under sections 3 and 4 of this License
-without being bound by section 3 of the GNU GPL.
-
- 2. Conveying Modified Versions.
-
- If you modify a copy of the Library, and, in your modifications, a
-facility refers to a function or data to be supplied by an Application
-that uses the facility (other than as an argument passed when the
-facility is invoked), then you may convey a copy of the modified
-version:
-
- a) under this License, provided that you make a good faith effort to
- ensure that, in the event an Application does not supply the
- function or data, the facility still operates, and performs
- whatever part of its purpose remains meaningful, or
-
- b) under the GNU GPL, with none of the additional permissions of
- this License applicable to that copy.
-
- 3. Object Code Incorporating Material from Library Header Files.
-
- The object code form of an Application may incorporate material from
-a header file that is part of the Library. You may convey such object
-code under terms of your choice, provided that, if the incorporated
-material is not limited to numerical parameters, data structure
-layouts and accessors, or small macros, inline functions and templates
-(ten or fewer lines in length), you do both of the following:
-
- a) Give prominent notice with each copy of the object code that the
- Library is used in it and that the Library and its use are
- covered by this License.
-
- b) Accompany the object code with a copy of the GNU GPL and this license
- document.
-
- 4. Combined Works.
-
- You may convey a Combined Work under terms of your choice that,
-taken together, effectively do not restrict modification of the
-portions of the Library contained in the Combined Work and reverse
-engineering for debugging such modifications, if you also do each of
-the following:
-
- a) Give prominent notice with each copy of the Combined Work that
- the Library is used in it and that the Library and its use are
- covered by this License.
-
- b) Accompany the Combined Work with a copy of the GNU GPL and this license
- document.
-
- c) For a Combined Work that displays copyright notices during
- execution, include the copyright notice for the Library among
- these notices, as well as a reference directing the user to the
- copies of the GNU GPL and this license document.
-
- d) Do one of the following:
-
- 0) Convey the Minimal Corresponding Source under the terms of this
- License, and the Corresponding Application Code in a form
- suitable for, and under terms that permit, the user to
- recombine or relink the Application with a modified version of
- the Linked Version to produce a modified Combined Work, in the
- manner specified by section 6 of the GNU GPL for conveying
- Corresponding Source.
-
- 1) Use a suitable shared library mechanism for linking with the
- Library. A suitable mechanism is one that (a) uses at run time
- a copy of the Library already present on the user's computer
- system, and (b) will operate properly with a modified version
- of the Library that is interface-compatible with the Linked
- Version.
-
- e) Provide Installation Information, but only if you would otherwise
- be required to provide such information under section 6 of the
- GNU GPL, and only to the extent that such information is
- necessary to install and execute a modified version of the
- Combined Work produced by recombining or relinking the
- Application with a modified version of the Linked Version. (If
- you use option 4d0, the Installation Information must accompany
- the Minimal Corresponding Source and Corresponding Application
- Code. If you use option 4d1, you must provide the Installation
- Information in the manner specified by section 6 of the GNU GPL
- for conveying Corresponding Source.)
-
- 5. Combined Libraries.
-
- You may place library facilities that are a work based on the
-Library side by side in a single library together with other library
-facilities that are not Applications and are not covered by this
-License, and convey such a combined library under terms of your
-choice, if you do both of the following:
-
- a) Accompany the combined library with a copy of the same work based
- on the Library, uncombined with any other library facilities,
- conveyed under the terms of this License.
-
- b) Give prominent notice with the combined library that part of it
- is a work based on the Library, and explaining where to find the
- accompanying uncombined form of the same work.
-
- 6. Revised Versions of the GNU Lesser General Public License.
-
- The Free Software Foundation may publish revised and/or new versions
-of the GNU Lesser General Public License from time to time. Such new
-versions will be similar in spirit to the present version, but may
-differ in detail to address new problems or concerns.
-
- Each version is given a distinguishing version number. If the
-Library as you received it specifies that a certain numbered version
-of the GNU Lesser General Public License "or any later version"
-applies to it, you have the option of following the terms and
-conditions either of that published version or of any later version
-published by the Free Software Foundation. If the Library as you
-received it does not specify a version number of the GNU Lesser
-General Public License, you may choose any version of the GNU Lesser
-General Public License ever published by the Free Software Foundation.
-
- If the Library as you received it specifies that a proxy can decide
-whether future versions of the GNU Lesser General Public License shall
-apply, that proxy's public statement of acceptance of any version is
-permanent authorization for you to choose that version for the
-Library.
-....
commit f76dfb090b1275f44c6b976da76e0c5123eb5939
Author: rsoulliere <robert.soulliere at mohawkcollege.ca>
Date: Mon May 28 13:54:33 2012 -0400
Add Dan's PDF image.
diff --git a/media/pdf_icon.png b/media/pdf_icon.png
new file mode 100644
index 0000000..6820818
Binary files /dev/null and b/media/pdf_icon.png differ
-----------------------------------------------------------------------
Summary of changes:
.gitignore | 2 +
Open-ILS/src/extras/Makefile.install | 11 +-
README | 550 +-------------
docs/1.6/book1/sysadmin/indexedfieldweighting.xml | 233 ------
docs/1.6/styleguide/admon.xml | 104 ---
docs/1.6/styleguide/authoring.xml | 93 ---
docs/1.6/styleguide/books.xml | 256 ------
docs/1.6/styleguide/build.xml | 37 -
docs/1.6/styleguide/chapter.xml | 117 ---
docs/1.6/styleguide/conditional.xml | 203 -----
docs/1.6/styleguide/exclude.xml | 370 ---------
docs/1.6/styleguide/figures.xml | 169 ----
docs/1.6/styleguide/filenames.xml | 76 --
docs/1.6/styleguide/general.xml | 208 -----
docs/1.6/styleguide/glossary.xml | 18 -
docs/1.6/styleguide/indexterms.xml | 74 --
docs/1.6/styleguide/links.xml | 489 ------------
docs/1.6/styleguide/lists.xml | 400 ----------
docs/1.6/styleguide/overview.xml | 149 ----
docs/1.6/styleguide/programming.xml | 493 ------------
docs/1.6/styleguide/structure.xml | 133 ----
docs/1.6/styleguide/styleguide.xml | 26 -
docs/1.6/styleguide/tables.xml | 818 --------------------
docs/RELEASE_NOTES_2_2.txt | 9 +-
docs/acquisitions/introduction.txt | 25 +
docs/acquisitions/receive_items_from_invoice.txt | 73 ++
docs/acquisitions/selection_lists_po.txt | 136 ++++
.../vandelay_acquisitions_integration.txt | 69 ++
docs/admin/SMS_messaging.txt | 122 +++
docs/admin/acquisitions_admin.txt | 490 ++++++++++++
docs/admin/authorities.txt | 170 ++++
docs/admin/auto_suggest_search.txt | 32 +
docs/admin/booking-admin.txt | 199 +++++
docs/admin/cn_prefixes_and_suffixes.txt | 46 ++
docs/admin/customize_staff_client.txt | 59 ++
docs/admin/hold_driven_recalls.txt | 53 ++
docs/admin/lsa-library_settings_editor.txt | 38 +
docs/admin/lsa-statcat.txt | 79 ++
docs/admin/recent_staff_searches.txt | 49 ++
.../restrict_Z39.50_sources_by_perm_group.txt | 49 ++
docs/admin/staff_client-double_clicking.txt | 23 +
docs/admin/staff_client-recent_searches.txt | 42 +
.../staff_client-return_to_results_from_marc.txt | 6 +
docs/admin/staff_client-sorting_columns.txt | 59 ++
docs/admin/staff_client-tab_buttons.txt | 6 +
docs/admin/template_toolkit.txt | 294 +++++++
docs/admin/user_activity_type.txt | 32 +
docs/attributions.txt | 47 ++
docs/cataloging/batch_importing_MARC.txt | 214 +++++
docs/cataloging/conjoined_items.txt | 106 +++
docs/cataloging/monograph_parts.txt | 57 ++
docs/cataloging/overlay_record_3950_import.txt | 55 ++
.../oils/__init__.py => docs/circulation/README | 0
docs/circulation/booking.txt | 272 +++++++
docs/circulation/circulating_items.txt | 327 ++++++++
docs/circulation/circulation_patron_records.txt | 318 ++++++++
.../oils/__init__.py => docs/development/README | 0
.../updating_translations_launchpad.txt | 54 ++
docs/installation/edi_setup.txt | 212 +++++
docs/installation/server_installation.txt | 549 +++++++++++++
docs/installation/server_upgrade.txt | 245 ++++++
docs/installation/system_requirements.txt | 32 +
docs/licensing.txt | 14 +
docs/media/1.png | Bin 0 -> 329 bytes
docs/media/10.png | Bin 0 -> 361 bytes
docs/media/11.png | Bin 0 -> 565 bytes
docs/media/12.png | Bin 0 -> 617 bytes
docs/media/13.png | Bin 0 -> 623 bytes
docs/media/14.png | Bin 0 -> 411 bytes
docs/media/15.png | Bin 0 -> 640 bytes
docs/media/2.png | Bin 0 -> 353 bytes
docs/media/3.png | Bin 0 -> 350 bytes
docs/media/4.png | Bin 0 -> 345 bytes
docs/media/5.png | Bin 0 -> 348 bytes
docs/media/6.png | Bin 0 -> 355 bytes
docs/media/7.png | Bin 0 -> 344 bytes
docs/media/8.png | Bin 0 -> 357 bytes
docs/media/9.png | Bin 0 -> 357 bytes
docs/media/Authority_Control_Sets1.jpg | Bin 0 -> 27515 bytes
docs/media/Authority_Control_Sets1.jpg.1 | Bin 0 -> 27515 bytes
docs/media/Authority_Control_Sets2.jpg | Bin 0 -> 26955 bytes
docs/media/Authority_Control_Sets2.jpg.1 | Bin 0 -> 26955 bytes
docs/media/Authority_Control_Sets3.jpg | Bin 0 -> 36886 bytes
docs/media/Authority_Control_Sets3.jpg.1 | Bin 0 -> 36886 bytes
docs/media/Authority_Control_Sets4.jpg | Bin 0 -> 18819 bytes
docs/media/Authority_Control_Sets4.jpg.1 | Bin 0 -> 18819 bytes
docs/media/Authority_Control_Sets5.jpg | Bin 0 -> 31117 bytes
docs/media/Authority_Control_Sets5.jpg.1 | Bin 0 -> 31117 bytes
docs/media/Authority_Control_Sets6.jpg | Bin 0 -> 19165 bytes
docs/media/Authority_Control_Sets6.jpg.1 | Bin 0 -> 19165 bytes
docs/media/Authority_Control_Sets7.jpg | Bin 0 -> 17151 bytes
docs/media/Authority_Control_Sets7.jpg.1 | Bin 0 -> 17151 bytes
docs/media/Authority_Control_Sets8.jpg | Bin 0 -> 20607 bytes
docs/media/Authority_Control_Sets8.jpg.1 | Bin 0 -> 20607 bytes
docs/media/Authority_Control_Sets9.jpg | Bin 0 -> 16889 bytes
docs/media/Authority_Control_Sets9.jpg.1 | Bin 0 -> 16889 bytes
docs/media/Auto_Suggest_in_Catalog_Search1.jpg | Bin 0 -> 47280 bytes
docs/media/Auto_Suggest_in_Catalog_Search2.jpg | Bin 0 -> 93658 bytes
docs/media/Batch_Importing_MARC_Records1.jpg | Bin 0 -> 30087 bytes
docs/media/Batch_Importing_MARC_Records10.jpg | Bin 0 -> 51440 bytes
docs/media/Batch_Importing_MARC_Records11.jpg | Bin 0 -> 51440 bytes
docs/media/Batch_Importing_MARC_Records12.jpg | Bin 0 -> 109056 bytes
docs/media/Batch_Importing_MARC_Records13.jpg | Bin 0 -> 109056 bytes
docs/media/Batch_Importing_MARC_Records14.jpg | Bin 0 -> 71000 bytes
docs/media/Batch_Importing_MARC_Records15.jpg | Bin 0 -> 109309 bytes
docs/media/Batch_Importing_MARC_Records2.jpg | Bin 0 -> 52379 bytes
docs/media/Batch_Importing_MARC_Records3.jpg | Bin 0 -> 35709 bytes
docs/media/Batch_Importing_MARC_Records4.jpg | Bin 0 -> 38728 bytes
docs/media/Batch_Importing_MARC_Records5.jpg | Bin 0 -> 8669 bytes
docs/media/Batch_Importing_MARC_Records6.jpg | Bin 0 -> 43550 bytes
docs/media/Batch_Importing_MARC_Records7.jpg | Bin 0 -> 46386 bytes
docs/media/Batch_Importing_MARC_Records8.jpg | Bin 0 -> 8340 bytes
docs/media/Batch_Importing_MARC_Records9.jpg | Bin 0 -> 96178 bytes
.../Call_Number_Prefixes_and_Suffixes_2_21.jpg | Bin 0 -> 16467 bytes
.../Call_Number_Prefixes_and_Suffixes_2_22.jpg | Bin 0 -> 19815 bytes
.../Call_Number_Prefixes_and_Suffixes_2_22.jpg.1 | Bin 0 -> 19815 bytes
docs/media/Customizable_Toolbar1.jpg | Bin 0 -> 70158 bytes
docs/media/Customizable_Toolbar2.jpg | Bin 0 -> 117956 bytes
docs/media/Customizable_Toolbar3.jpg | Bin 0 -> 133064 bytes
docs/media/Customizable_Toolbar4.jpg | Bin 0 -> 131597 bytes
docs/media/Double_Click1.jpg | Bin 0 -> 91459 bytes
docs/media/Double_Click2.jpg | Bin 0 -> 70537 bytes
docs/media/Double_Click3.jpg | Bin 0 -> 70537 bytes
docs/media/Group_Serials_Issues_in_the_OPAC2.jpg | Bin 0 -> 60785 bytes
docs/media/Group_Serials_Issues_in_the_OPAC5.jpg | Bin 0 -> 155207 bytes
docs/media/Group_Serials_Issues_in_the_OPAC7.jpg | Bin 0 -> 154906 bytes
docs/media/My_Lists1.jpg | Bin 0 -> 45137 bytes
docs/media/My_Lists3.jpg | Bin 0 -> 38816 bytes
docs/media/My_Lists4.jpg | Bin 0 -> 29192 bytes
docs/media/My_Lists5.jpg | Bin 0 -> 40890 bytes
docs/media/My_Lists6.jpg | Bin 0 -> 34076 bytes
docs/media/My_Lists7.jpg | Bin 0 -> 15699 bytes
docs/media/New_Tab_Button1.jpg | Bin 0 -> 41200 bytes
.../Overlay_Existing_Record_via_Z39_50_Import1.jpg | Bin 0 -> 77337 bytes
.../Overlay_Existing_Record_via_Z39_50_Import2.jpg | Bin 0 -> 83348 bytes
.../Overlay_Existing_Record_via_Z39_50_Import3.jpg | Bin 0 -> 35215 bytes
.../Overlay_Existing_Record_via_Z39_50_Import4.jpg | Bin 0 -> 118787 bytes
.../Overlay_Existing_Record_via_Z39_50_Import5.jpg | Bin 0 -> 56064 bytes
.../Overlay_Existing_Record_via_Z39_50_Import6.jpg | Bin 0 -> 58548 bytes
docs/media/Receive_Items_From_an_Invoice1.jpg | Bin 0 -> 135124 bytes
docs/media/Receive_Items_From_an_Invoice2.jpg | Bin 0 -> 123420 bytes
docs/media/Receive_Items_From_an_Invoice3.jpg | Bin 0 -> 89033 bytes
docs/media/Receive_Items_From_an_Invoice4.jpg | Bin 0 -> 90190 bytes
docs/media/Receive_Items_From_an_Invoice5.jpg | Bin 0 -> 108075 bytes
docs/media/Receive_Items_From_an_Invoice6.jpg | Bin 0 -> 73018 bytes
docs/media/Receive_Items_From_an_Invoice7.jpg | Bin 0 -> 21413 bytes
...estrict_Z39_50_Sources_by_Permission_Group1.jpg | Bin 0 -> 38443 bytes
...estrict_Z39_50_Sources_by_Permission_Group2.jpg | Bin 0 -> 14756 bytes
...estrict_Z39_50_Sources_by_Permission_Group3.jpg | Bin 0 -> 36126 bytes
docs/media/SMS_Text_Messaging1.jpg | Bin 0 -> 133248 bytes
docs/media/SMS_Text_Messaging10.jpg | Bin 0 -> 88605 bytes
docs/media/SMS_Text_Messaging11.jpg | Bin 0 -> 30349 bytes
docs/media/SMS_Text_Messaging12.jpg | Bin 0 -> 39067 bytes
docs/media/SMS_Text_Messaging13.jpg | Bin 0 -> 54025 bytes
docs/media/SMS_Text_Messaging2.jpg | Bin 0 -> 116666 bytes
docs/media/SMS_Text_Messaging3.jpg | Bin 0 -> 119872 bytes
docs/media/SMS_Text_Messaging4.jpg | Bin 0 -> 97545 bytes
docs/media/SMS_Text_Messaging5.jpg | Bin 0 -> 175431 bytes
docs/media/SMS_Text_Messaging6.jpg | Bin 0 -> 77223 bytes
docs/media/SMS_Text_Messaging7.jpg | Bin 0 -> 39067 bytes
docs/media/SMS_Text_Messaging8.jpg | Bin 0 -> 78821 bytes
docs/media/SMS_Text_Messaging9.jpg | Bin 0 -> 26292 bytes
docs/media/Saved_Catalog_Searches_2_21.jpg | Bin 0 -> 59969 bytes
docs/media/Saved_Catalog_Searches_2_21.jpg.1 | Bin 0 -> 59969 bytes
docs/media/Saved_Catalog_Searches_2_22.jpg | Bin 0 -> 65179 bytes
docs/media/Saved_Catalog_Searches_2_22.jpg.1 | Bin 0 -> 65179 bytes
docs/media/Search_Results1.jpg | Bin 0 -> 102976 bytes
docs/media/Sorting_Columns2.jpg | Bin 0 -> 95104 bytes
docs/media/Sorting_Columns3.jpg | Bin 0 -> 109750 bytes
docs/media/Sorting_Columns3.jpg.1 | Bin 0 -> 109750 bytes
docs/media/Sorting_Columns4.jpg | Bin 0 -> 107143 bytes
docs/media/Sorting_Columns5.jpg | Bin 0 -> 99426 bytes
docs/media/Target_Pickup_Lib1.jpg | Bin 0 -> 121219 bytes
docs/media/Target_Pickup_Lib2.jpg | Bin 0 -> 121219 bytes
docs/media/User_Activity_Types1A.jpg | Bin 0 -> 157434 bytes
docs/media/User_Activity_Types2A.jpg | Bin 0 -> 54380 bytes
.../Vandelay_Integration_into_Acquisitions1.jpg | Bin 0 -> 87987 bytes
.../Vandelay_Integration_into_Acquisitions2.jpg | Bin 0 -> 24889 bytes
.../Vandelay_Integration_into_Acquisitions3.jpg | Bin 0 -> 31580 bytes
.../Vandelay_Integration_into_Acquisitions4.jpg | Bin 0 -> 99744 bytes
.../Vandelay_Integration_into_Acquisitions5.jpg | Bin 0 -> 81603 bytes
.../Vandelay_Integration_into_Acquisitions6.jpg | Bin 0 -> 92301 bytes
docs/media/acq_activate.png | Bin 0 -> 8272 bytes
docs/media/acq_apply_claim_policy.png | Bin 0 -> 9830 bytes
docs/media/acq_brief_record-2.png | Bin 0 -> 12198 bytes
docs/media/acq_brief_record.png | Bin 0 -> 12949 bytes
docs/media/acq_cancel_copy.png | Bin 0 -> 12397 bytes
docs/media/acq_cancel_line_items.png | Bin 0 -> 3413 bytes
docs/media/acq_claim_item-2.png | Bin 0 -> 14562 bytes
docs/media/acq_claim_item-3.png | Bin 0 -> 3245 bytes
docs/media/acq_claim_item-4.png | Bin 0 -> 13169 bytes
docs/media/acq_claim_item-5.png | Bin 0 -> 3171 bytes
docs/media/acq_claim_item.png | Bin 0 -> 9633 bytes
docs/media/acq_export_list.png | Bin 0 -> 15505 bytes
docs/media/acq_funds-2.png | Bin 0 -> 8210 bytes
docs/media/acq_funds.png | Bin 0 -> 19126 bytes
docs/media/acq_invoice_blanket.png | Bin 0 -> 21212 bytes
docs/media/acq_invoice_line_items.png | Bin 0 -> 9103 bytes
docs/media/acq_invoice_link.png | Bin 0 -> 11052 bytes
docs/media/acq_invoice_purchase_order.png | Bin 0 -> 9103 bytes
docs/media/acq_invoice_view-2.png | Bin 0 -> 10190 bytes
docs/media/acq_invoice_view.png | Bin 0 -> 8889 bytes
docs/media/acq_line_items_add_copies-2.png | Bin 0 -> 22922 bytes
docs/media/acq_line_items_add_copies-3.png | Bin 0 -> 3010 bytes
docs/media/acq_line_items_add_copies.png | Bin 0 -> 4285 bytes
docs/media/acq_line_items_add_notes.png | Bin 0 -> 4580 bytes
docs/media/acq_line_items_alerts-2.png | Bin 0 -> 3569 bytes
docs/media/acq_line_items_alerts.png | Bin 0 -> 6872 bytes
docs/media/acq_line_items_link-2.png | Bin 0 -> 4498 bytes
docs/media/acq_line_items_link.png | Bin 0 -> 6896 bytes
docs/media/acq_line_items_update_barcodes.png | Bin 0 -> 6031 bytes
docs/media/acq_line_items_view_history.png | Bin 0 -> 16235 bytes
docs/media/acq_line_items_worksheet.png | Bin 0 -> 12609 bytes
docs/media/acq_load_records.png | Bin 0 -> 29057 bytes
docs/media/acq_marc_search-2.png | Bin 0 -> 9132 bytes
docs/media/acq_marc_search.png | Bin 0 -> 13283 bytes
docs/media/acq_purchase_order_add_charges.png | Bin 0 -> 8272 bytes
docs/media/acq_purchase_order_add_note.png | Bin 0 -> 4640 bytes
docs/media/acq_purchase_order_create.png | Bin 0 -> 5375 bytes
docs/media/acq_purchase_order_history.png | Bin 0 -> 20094 bytes
docs/media/acq_purchase_order_name.png | Bin 0 -> 34129 bytes
docs/media/acq_purchase_order_print.png | Bin 0 -> 15577 bytes
docs/media/acq_purchase_order_split-2.png | Bin 0 -> 14160 bytes
docs/media/acq_purchase_order_split.png | Bin 0 -> 7376 bytes
docs/media/acq_purchase_order_view-2.png | Bin 0 -> 2373 bytes
docs/media/acq_purchase_order_view.png | Bin 0 -> 9941 bytes
docs/media/acq_search.png | Bin 0 -> 9528 bytes
docs/media/acq_selection_clone.png | Bin 0 -> 14313 bytes
docs/media/acq_selection_create.png | Bin 0 -> 8023 bytes
docs/media/acq_selection_mark_ready-2.png | Bin 0 -> 8747 bytes
docs/media/acq_selection_mark_ready.png | Bin 0 -> 2614 bytes
docs/media/acq_selection_merge.png | Bin 0 -> 11621 bytes
docs/media/acq_workflow.jpg | Bin 0 -> 63179 bytes
docs/media/add_holdings-1.png | Bin 0 -> 14268 bytes
docs/media/add_holdings-2.png | Bin 0 -> 55015 bytes
docs/media/add_holdings-3.png | Bin 0 -> 62139 bytes
docs/media/add_holdings-4.png | Bin 0 -> 94401 bytes
docs/media/add_holdings-5.png | Bin 0 -> 22909 bytes
docs/media/application-pdf.png | Bin 0 -> 4618 bytes
docs/media/ascv-distr.jpg | Bin 0 -> 49673 bytes
docs/media/ascv-issues.jpg | Bin 0 -> 54062 bytes
docs/media/ascv-sub.jpg | Bin 0 -> 105904 bytes
docs/media/backdate_checkin.png | Bin 0 -> 14276 bytes
docs/media/backdate_post_checkin.png | Bin 0 -> 25373 bytes
docs/media/backdate_post_date.png | Bin 0 -> 13217 bytes
docs/media/backdate_red.png | Bin 0 -> 10244 bytes
docs/media/bills-1.png | Bin 0 -> 3263 bytes
docs/media/bills-10.png | Bin 0 -> 34054 bytes
docs/media/bills-11.png | Bin 0 -> 17035 bytes
docs/media/bills-12.png | Bin 0 -> 8583 bytes
docs/media/bills-13.png | Bin 0 -> 21231 bytes
docs/media/bills-14.png | Bin 0 -> 34527 bytes
docs/media/bills-15.png | Bin 0 -> 16744 bytes
docs/media/bills-16.png | Bin 0 -> 17557 bytes
docs/media/bills-17.png | Bin 0 -> 58660 bytes
docs/media/bills-18.png | Bin 0 -> 66558 bytes
docs/media/bills-19.png | Bin 0 -> 25813 bytes
docs/media/bills-2.png | Bin 0 -> 45167 bytes
docs/media/bills-20.png | Bin 0 -> 26488 bytes
docs/media/bills-3.png | Bin 0 -> 8268 bytes
docs/media/bills-4.png | Bin 0 -> 10007 bytes
docs/media/bills-5.png | Bin 0 -> 26840 bytes
docs/media/bills-6.png | Bin 0 -> 24490 bytes
docs/media/bills-7.png | Bin 0 -> 17026 bytes
docs/media/bills-8.png | Bin 0 -> 10209 bytes
docs/media/bills-9.png | Bin 0 -> 16329 bytes
docs/media/booking-cancel-1.png | Bin 0 -> 103352 bytes
docs/media/booking-cancel-2.png | Bin 0 -> 43206 bytes
docs/media/booking-cancel-3.png | Bin 0 -> 94633 bytes
docs/media/booking-cancel-4.png | Bin 0 -> 94633 bytes
docs/media/booking-capture-1.png | Bin 0 -> 13051 bytes
docs/media/booking-capture-2.png | Bin 0 -> 28901 bytes
docs/media/booking-capture-3.png | Bin 0 -> 86099 bytes
docs/media/booking-create-1.png | Bin 0 -> 74512 bytes
docs/media/booking-create-2.png | Bin 0 -> 82930 bytes
docs/media/booking-create-3.png | Bin 0 -> 89863 bytes
docs/media/booking-create-4.png | Bin 0 -> 26907 bytes
docs/media/booking-create-5.png | Bin 0 -> 11687 bytes
docs/media/booking-create-6.png | Bin 0 -> 26054 bytes
docs/media/booking-create-7.png | Bin 0 -> 23795 bytes
docs/media/booking-create-8.png | Bin 0 -> 95671 bytes
docs/media/booking-create-9.png | Bin 0 -> 95671 bytes
docs/media/booking-create-bookable-1.png | Bin 0 -> 81226 bytes
docs/media/booking-create-bookable-2.png | Bin 0 -> 47321 bytes
docs/media/booking-create-bookable-3.png | Bin 0 -> 40695 bytes
docs/media/booking-create-bookable-4.png | Bin 0 -> 61875 bytes
docs/media/booking-create-bookable-5.png | Bin 0 -> 44721 bytes
docs/media/booking-create-bookable-6.png | Bin 0 -> 77788 bytes
docs/media/booking-create-module-1.png | Bin 0 -> 14279 bytes
docs/media/booking-create-module-2.png | Bin 0 -> 62962 bytes
docs/media/booking-create-module-3.png | Bin 0 -> 73069 bytes
docs/media/booking-create-module-4.png | Bin 0 -> 3679 bytes
docs/media/booking-create-resourcetype-1.png | Bin 0 -> 109759 bytes
docs/media/booking-create-resourcetype-2.png | Bin 0 -> 90808 bytes
docs/media/booking-create-resourcetype-3.png | Bin 0 -> 17114 bytes
docs/media/booking-create-resourcetype-4.png | Bin 0 -> 2552 bytes
docs/media/booking-create-resourcetype-5.png | Bin 0 -> 100267 bytes
docs/media/booking-pickup-1.png | Bin 0 -> 77021 bytes
docs/media/booking-pickup-2.png | Bin 0 -> 75242 bytes
docs/media/booking-pickup-3.png | Bin 0 -> 68699 bytes
docs/media/booking-pickup-module-1.png | Bin 0 -> 16583 bytes
docs/media/booking-pull-1.png | Bin 0 -> 11865 bytes
docs/media/booking-pull-2.png | Bin 0 -> 30008 bytes
docs/media/booking-pull-3.png | Bin 0 -> 81523 bytes
docs/media/booking-return-2.png | Bin 0 -> 73685 bytes
docs/media/booking-return-module-1.png | Bin 0 -> 12591 bytes
docs/media/booking-return-module-2.png | Bin 0 -> 36558 bytes
docs/media/booking-return-module-4.png | Bin 0 -> 74476 bytes
docs/media/cap-wiz-cal.jpg | Bin 0 -> 54207 bytes
docs/media/cap-wiz-chan.jpg | Bin 0 -> 55647 bytes
docs/media/cap-wiz-chron.jpg | Bin 0 -> 58578 bytes
docs/media/cap-wiz-freq.jpg | Bin 0 -> 54007 bytes
docs/media/cap-wiz-num.jpg | Bin 0 -> 66746 bytes
docs/media/catalogue-10.png | Bin 0 -> 1320 bytes
docs/media/catalogue-11.png | Bin 0 -> 3955 bytes
docs/media/catalogue-3.png | Bin 0 -> 45083 bytes
docs/media/catalogue-4.png | Bin 0 -> 62379 bytes
docs/media/catalogue-5.png | Bin 0 -> 21875 bytes
docs/media/catalogue-6.png | Bin 0 -> 34223 bytes
docs/media/catalogue-7.png | Bin 0 -> 41331 bytes
docs/media/catalogue-8.png | Bin 0 -> 87494 bytes
docs/media/catalogue-9.png | Bin 0 -> 28820 bytes
docs/media/caution.png | Bin 0 -> 2344 bytes
docs/media/ccbysa.png | Bin 0 -> 5083 bytes
docs/media/check_in_menu.png | Bin 0 -> 4761 bytes
docs/media/checkin_barcode.png | Bin 0 -> 13329 bytes
docs/media/checkin_options.png | Bin 0 -> 21665 bytes
docs/media/checkout_item_barcode.png | Bin 0 -> 3500 bytes
docs/media/checkout_menu.png | Bin 0 -> 4058 bytes
docs/media/circulation-1.png | Bin 0 -> 3829 bytes
docs/media/circulation-10.png | Bin 0 -> 4382 bytes
docs/media/circulation-11.png | Bin 0 -> 5429 bytes
docs/media/circulation-12.png | Bin 0 -> 15769 bytes
docs/media/circulation-13.png | Bin 0 -> 15728 bytes
docs/media/circulation-14.png | Bin 0 -> 12387 bytes
docs/media/circulation-15.png | Bin 0 -> 16558 bytes
docs/media/circulation-16.png | Bin 0 -> 24719 bytes
docs/media/circulation-17.png | Bin 0 -> 20829 bytes
docs/media/circulation-18.png | Bin 0 -> 20823 bytes
docs/media/circulation-19.png | Bin 0 -> 7608 bytes
docs/media/circulation-2.png | Bin 0 -> 5034 bytes
docs/media/circulation-20.png | Bin 0 -> 27945 bytes
docs/media/circulation-21.png | Bin 0 -> 28641 bytes
docs/media/circulation-22.png | Bin 0 -> 33302 bytes
docs/media/circulation-23.png | Bin 0 -> 22718 bytes
docs/media/circulation-24.png | Bin 0 -> 10809 bytes
docs/media/circulation-25.png | Bin 0 -> 17322 bytes
docs/media/circulation-26.png | Bin 0 -> 12002 bytes
docs/media/circulation-27.png | Bin 0 -> 14154 bytes
docs/media/circulation-28.png | Bin 0 -> 10829 bytes
docs/media/circulation-29.png | Bin 0 -> 28033 bytes
docs/media/circulation-3.png | Bin 0 -> 8391 bytes
docs/media/circulation-30.png | Bin 0 -> 28800 bytes
docs/media/circulation-31.png | Bin 0 -> 62690 bytes
docs/media/circulation-32.png | Bin 0 -> 29538 bytes
docs/media/circulation-33.png | Bin 0 -> 12609 bytes
docs/media/circulation-34.png | Bin 0 -> 82975 bytes
docs/media/circulation-35.png | Bin 0 -> 7350 bytes
docs/media/circulation-36.png | Bin 0 -> 81164 bytes
docs/media/circulation-4.png | Bin 0 -> 8600 bytes
docs/media/circulation-5.png | Bin 0 -> 3247 bytes
docs/media/circulation-6.png | Bin 0 -> 49637 bytes
docs/media/circulation-7.png | Bin 0 -> 18932 bytes
docs/media/circulation-8.png | Bin 0 -> 5999 bytes
docs/media/circulation-9.png | Bin 0 -> 17360 bytes
docs/media/circulation_patron_records-1.png | Bin 0 -> 24301 bytes
docs/media/circulation_patron_records-10.png | Bin 0 -> 22979 bytes
docs/media/circulation_patron_records-11.png | Bin 0 -> 49919 bytes
docs/media/circulation_patron_records-12.png | Bin 0 -> 24518 bytes
docs/media/circulation_patron_records-13.png | Bin 0 -> 13320 bytes
docs/media/circulation_patron_records-14.png | Bin 0 -> 5533 bytes
docs/media/circulation_patron_records-15.png | Bin 0 -> 3527 bytes
docs/media/circulation_patron_records-16.png | Bin 0 -> 6168 bytes
docs/media/circulation_patron_records-17.png | Bin 0 -> 2878 bytes
docs/media/circulation_patron_records-18.png | Bin 0 -> 7138 bytes
docs/media/circulation_patron_records-19.png | Bin 0 -> 13769 bytes
docs/media/circulation_patron_records-2.png | Bin 0 -> 117045 bytes
docs/media/circulation_patron_records-20.png | Bin 0 -> 4961 bytes
docs/media/circulation_patron_records-21.png | Bin 0 -> 2742 bytes
docs/media/circulation_patron_records-22.png | Bin 0 -> 18982 bytes
docs/media/circulation_patron_records-23.png | Bin 0 -> 9826 bytes
docs/media/circulation_patron_records-24.png | Bin 0 -> 20827 bytes
docs/media/circulation_patron_records-25.png | Bin 0 -> 40974 bytes
docs/media/circulation_patron_records-26.png | Bin 0 -> 15665 bytes
docs/media/circulation_patron_records-27.png | Bin 0 -> 50890 bytes
docs/media/circulation_patron_records-28.png | Bin 0 -> 97526 bytes
docs/media/circulation_patron_records-29.png | Bin 0 -> 11643 bytes
docs/media/circulation_patron_records-3.png | Bin 0 -> 39651 bytes
docs/media/circulation_patron_records-30.png | Bin 0 -> 43112 bytes
docs/media/circulation_patron_records-31.png | Bin 0 -> 88730 bytes
docs/media/circulation_patron_records-4.png | Bin 0 -> 95906 bytes
docs/media/circulation_patron_records-5.png | Bin 0 -> 2689 bytes
docs/media/circulation_patron_records-6.png | Bin 0 -> 4072 bytes
docs/media/circulation_patron_records-7.png | Bin 0 -> 3959 bytes
docs/media/circulation_patron_records-8.png | Bin 0 -> 15366 bytes
docs/media/circulation_patron_records-9.png | Bin 0 -> 69080 bytes
docs/media/claimed_date.png | Bin 0 -> 16196 bytes
docs/media/conj1.jpg | Bin 0 -> 69592 bytes
docs/media/conj10.jpg | Bin 0 -> 10517 bytes
docs/media/conj2.jpg | Bin 0 -> 51284 bytes
docs/media/conj3.jpg | Bin 0 -> 21309 bytes
docs/media/conj4.jpg | Bin 0 -> 18704 bytes
docs/media/conj5.jpg | Bin 0 -> 15313 bytes
docs/media/conj6.jpg | Bin 0 -> 25046 bytes
docs/media/conj7.jpg | Bin 0 -> 17270 bytes
docs/media/conj8.jpg | Bin 0 -> 12308 bytes
docs/media/conj9.jpg | Bin 0 -> 59770 bytes
docs/media/copy_alert_message.png | Bin 0 -> 5270 bytes
docs/media/copy_edit_alert.png | Bin 0 -> 15637 bytes
docs/media/create-template-1.png | Bin 0 -> 7515 bytes
docs/media/create-template-10.png | Bin 0 -> 11718 bytes
docs/media/create-template-11.png | Bin 0 -> 15294 bytes
docs/media/create-template-12.png | Bin 0 -> 29168 bytes
docs/media/create-template-13.png | Bin 0 -> 29605 bytes
docs/media/create-template-15.png | Bin 0 -> 18065 bytes
docs/media/create-template-16.png | Bin 0 -> 17877 bytes
docs/media/create-template-17.png | Bin 0 -> 18165 bytes
docs/media/create-template-19.png | Bin 0 -> 30073 bytes
docs/media/create-template-2.png | Bin 0 -> 10731 bytes
docs/media/create-template-20.png | Bin 0 -> 30603 bytes
docs/media/create-template-21.png | Bin 0 -> 16580 bytes
docs/media/create-template-22.png | Bin 0 -> 10669 bytes
docs/media/create-template-23.png | Bin 0 -> 14653 bytes
docs/media/create-template-24.png | Bin 0 -> 7766 bytes
docs/media/create-template-25.png | Bin 0 -> 44486 bytes
docs/media/create-template-26.png | Bin 0 -> 15945 bytes
docs/media/create-template-27.png | Bin 0 -> 26441 bytes
docs/media/create-template-28.png | Bin 0 -> 20287 bytes
docs/media/create-template-29.png | Bin 0 -> 16035 bytes
docs/media/create-template-3.png | Bin 0 -> 19150 bytes
docs/media/create-template-30.png | Bin 0 -> 11864 bytes
docs/media/create-template-31.png | Bin 0 -> 13098 bytes
docs/media/create-template-32.png | Bin 0 -> 5669 bytes
docs/media/create-template-33.png | Bin 0 -> 25136 bytes
docs/media/create-template-34.png | Bin 0 -> 17422 bytes
docs/media/create-template-35.png | Bin 0 -> 20879 bytes
docs/media/create-template-4.png | Bin 0 -> 13394 bytes
docs/media/create-template-5.png | Bin 0 -> 16326 bytes
docs/media/create-template-6.png | Bin 0 -> 22084 bytes
docs/media/create-template-7.png | Bin 0 -> 29544 bytes
docs/media/create-template-8.png | Bin 0 -> 17368 bytes
docs/media/create-template-9.png | Bin 0 -> 10845 bytes
docs/media/due_date_display.png | Bin 0 -> 7969 bytes
docs/media/edit_due_date_action.png | Bin 0 -> 21706 bytes
docs/media/epub_logo_color_ht39.gif | Bin 0 -> 509 bytes
docs/media/evergreen_logo.gif | Bin 0 -> 5306 bytes
docs/media/folder-1.png | Bin 0 -> 7268 bytes
docs/media/folder-10.png | Bin 0 -> 13525 bytes
docs/media/folder-11.png | Bin 0 -> 7276 bytes
docs/media/folder-12.png | Bin 0 -> 12437 bytes
docs/media/folder-13.png | Bin 0 -> 19901 bytes
docs/media/folder-14.png | Bin 0 -> 15345 bytes
docs/media/folder-7a.png | Bin 0 -> 5238 bytes
docs/media/generate-report-1.png | Bin 0 -> 4504 bytes
docs/media/generate-report-10.png | Bin 0 -> 22302 bytes
docs/media/generate-report-14.png | Bin 0 -> 16638 bytes
docs/media/generate-report-2.png | Bin 0 -> 21282 bytes
docs/media/generate-report-3.png | Bin 0 -> 12060 bytes
docs/media/generate-report-8.png | Bin 0 -> 18394 bytes
docs/media/generate-report-9.png | Bin 0 -> 8436 bytes
docs/media/hold-1.png | Bin 0 -> 39820 bytes
docs/media/hold-10.png | Bin 0 -> 24301 bytes
docs/media/hold-11.png | Bin 0 -> 20886 bytes
docs/media/hold-12.png | Bin 0 -> 88652 bytes
docs/media/hold-14.png | Bin 0 -> 38207 bytes
docs/media/hold-15.png | Bin 0 -> 36883 bytes
docs/media/hold-16.png | Bin 0 -> 21292 bytes
docs/media/hold-17.png | Bin 0 -> 22802 bytes
docs/media/hold-18.png | Bin 0 -> 21915 bytes
docs/media/hold-19.png | Bin 0 -> 35692 bytes
docs/media/hold-2.png | Bin 0 -> 80605 bytes
docs/media/hold-20.png | Bin 0 -> 81663 bytes
docs/media/hold-21.png | Bin 0 -> 14637 bytes
docs/media/hold-22.png | Bin 0 -> 38672 bytes
docs/media/hold-23.png | Bin 0 -> 17398 bytes
docs/media/hold-24.png | Bin 0 -> 29320 bytes
docs/media/hold-25.png | Bin 0 -> 17771 bytes
docs/media/hold-26.png | Bin 0 -> 18491 bytes
docs/media/hold-27.png | Bin 0 -> 47976 bytes
docs/media/hold-28.png | Bin 0 -> 17257 bytes
docs/media/hold-29.png | Bin 0 -> 102246 bytes
docs/media/hold-4.png | Bin 0 -> 30445 bytes
docs/media/hold-5.png | Bin 0 -> 29597 bytes
docs/media/hold-6.png | Bin 0 -> 12508 bytes
docs/media/hold-7.png | Bin 0 -> 46771 bytes
docs/media/hold-8.png | Bin 0 -> 11505 bytes
docs/media/hold-9.png | Bin 0 -> 11570 bytes
docs/media/holds-clearing-1.png | Bin 0 -> 16838 bytes
docs/media/holds-clearing-2.png | Bin 0 -> 76789 bytes
docs/media/holds-clearing-3.png | Bin 0 -> 8320 bytes
docs/media/holds-clearing-4.png | Bin 0 -> 21048 bytes
docs/media/holds-managing-1.png | Bin 0 -> 30579 bytes
docs/media/holds-managing-10.png | Bin 0 -> 25220 bytes
docs/media/holds-managing-11.png | Bin 0 -> 9031 bytes
docs/media/holds-managing-12.png | Bin 0 -> 24776 bytes
docs/media/holds-managing-13.png | Bin 0 -> 12643 bytes
docs/media/holds-managing-14.png | Bin 0 -> 26606 bytes
docs/media/holds-managing-15.png | Bin 0 -> 7576 bytes
docs/media/holds-managing-16.png | Bin 0 -> 24022 bytes
docs/media/holds-managing-17.png | Bin 0 -> 27748 bytes
docs/media/holds-managing-18.png | Bin 0 -> 8685 bytes
docs/media/holds-managing-19.png | Bin 0 -> 19402 bytes
docs/media/holds-managing-2.png | Bin 0 -> 10830 bytes
docs/media/holds-managing-3.png | Bin 0 -> 26015 bytes
docs/media/holds-managing-4.png | Bin 0 -> 20292 bytes
docs/media/holds-managing-5.png | Bin 0 -> 12632 bytes
docs/media/holds-managing-6.png | Bin 0 -> 18028 bytes
docs/media/holds-managing-7.png | Bin 0 -> 33855 bytes
docs/media/holds-managing-8.png | Bin 0 -> 6336 bytes
docs/media/holds-managing-9.png | Bin 0 -> 22775 bytes
docs/media/holds-notifications-1.png | Bin 0 -> 17651 bytes
docs/media/holds-notifications-2.png | Bin 0 -> 23274 bytes
docs/media/holds-notifications-3.png | Bin 0 -> 23445 bytes
docs/media/holds-notifications-4.png | Bin 0 -> 32580 bytes
docs/media/holds-placing-1.png | Bin 0 -> 44044 bytes
docs/media/holds-placing-10.png | Bin 0 -> 12477 bytes
docs/media/holds-placing-11.png | Bin 0 -> 42094 bytes
docs/media/holds-placing-2.png | Bin 0 -> 3910 bytes
docs/media/holds-placing-3.png | Bin 0 -> 26015 bytes
docs/media/holds-placing-4.png | Bin 0 -> 19087 bytes
docs/media/holds-placing-5.png | Bin 0 -> 6752 bytes
docs/media/holds-placing-6.png | Bin 0 -> 5704 bytes
docs/media/holds-placing-7.png | Bin 0 -> 5150 bytes
docs/media/holds-placing-8.png | Bin 0 -> 4897 bytes
docs/media/holds-placing-9.png | Bin 0 -> 8222 bytes
docs/media/holds-pull-1.png | Bin 0 -> 13969 bytes
docs/media/holds-pull-2.png | Bin 0 -> 50844 bytes
docs/media/holds-pull-3.png | Bin 0 -> 18411 bytes
docs/media/holds-pull-4.png | Bin 0 -> 9536 bytes
docs/media/holds-pull-5.png | Bin 0 -> 8648 bytes
docs/media/holds-pull-5a.png | Bin 0 -> 6376 bytes
docs/media/holds-pull-6.png | Bin 0 -> 9393 bytes
docs/media/holds-pull-7.png | Bin 0 -> 18584 bytes
docs/media/holds-pull-8.png | Bin 0 -> 10532 bytes
docs/media/holds-pull-9.png | Bin 0 -> 16408 bytes
docs/media/in_house_use.png | Bin 0 -> 6719 bytes
docs/media/item_status_altview.png | Bin 0 -> 57827 bytes
docs/media/item_status_barcode.png | Bin 0 -> 5971 bytes
docs/media/item_status_list_view.png | Bin 0 -> 17584 bytes
docs/media/item_status_menu.png | Bin 0 -> 9235 bytes
docs/media/items_out_click.png | Bin 0 -> 11941 bytes
docs/media/k_book_record.png | Bin 0 -> 18718 bytes
docs/media/last_few_circs_action.png | Bin 0 -> 17281 bytes
docs/media/last_few_circs_display.png | Bin 0 -> 55354 bytes
docs/media/lost_cr_section.png | Bin 0 -> 11398 bytes
docs/media/lsa-1.png | Bin 0 -> 10879 bytes
docs/media/lsa-10.jpg | Bin 0 -> 131072 bytes
docs/media/lsa-11.jpg | Bin 0 -> 73728 bytes
docs/media/lsa-12.jpg | Bin 0 -> 94208 bytes
docs/media/lsa-14.jpg | Bin 0 -> 55406 bytes
docs/media/lsa-16.jpg | Bin 0 -> 104821 bytes
docs/media/lsa-17.jpg | Bin 0 -> 177292 bytes
docs/media/lsa-18.jpg | Bin 0 -> 134241 bytes
docs/media/lsa-2.jpg | Bin 0 -> 91706 bytes
docs/media/lsa-22.png | Bin 0 -> 13292 bytes
docs/media/lsa-23.jpg | Bin 0 -> 57344 bytes
docs/media/lsa-25.jpg | Bin 0 -> 159744 bytes
docs/media/lsa-26.jpg | Bin 0 -> 253952 bytes
docs/media/lsa-27.jpg | Bin 0 -> 155648 bytes
docs/media/lsa-28.jpg | Bin 0 -> 90953 bytes
docs/media/lsa-32.jpg | Bin 0 -> 32768 bytes
docs/media/lsa-33.jpg | Bin 0 -> 115314 bytes
docs/media/lsa-4.jpg | Bin 0 -> 12288 bytes
docs/media/lsa-5.jpg | Bin 0 -> 114688 bytes
docs/media/lsa-7.jpg | Bin 0 -> 126976 bytes
docs/media/lsa-8.jpg | Bin 0 -> 73728 bytes
docs/media/lsa-closed-mountain-1.png | Bin 0 -> 8215 bytes
docs/media/lsa-closed-mountain-2.png | Bin 0 -> 7743 bytes
docs/media/lsa-group-0.png | Bin 0 -> 6109 bytes
docs/media/lsa-group-1.png | Bin 0 -> 21261 bytes
docs/media/lsa-group-1a.png | Bin 0 -> 9591 bytes
docs/media/lsa-group-2.png | Bin 0 -> 9503 bytes
docs/media/lsa-group-3.png | Bin 0 -> 4809 bytes
docs/media/lsa-group-4.png | Bin 0 -> 8967 bytes
docs/media/lsa-group-5.png | Bin 0 -> 11133 bytes
docs/media/lsa-group-6.png | Bin 0 -> 5385 bytes
docs/media/lsa-statcat-1.png | Bin 0 -> 19666 bytes
docs/media/lsa-statcat-2.png | Bin 0 -> 31932 bytes
docs/media/lsa-statcat-3.png | Bin 0 -> 41151 bytes
docs/media/lsa-statcat-4.png | Bin 0 -> 22354 bytes
docs/media/lsa-statcat-5.png | Bin 0 -> 47503 bytes
docs/media/lsa-statcat-6.png | Bin 0 -> 18218 bytes
docs/media/lsa-statcat-7.png | Bin 0 -> 21302 bytes
docs/media/lsa-statcat-8.png | Bin 0 -> 5358 bytes
.../web/opac/images => docs/media}/main_logo.jpg | Bin 8571 -> 8571 bytes
docs/media/mark_claims_returned.png | Bin 0 -> 24195 bytes
docs/media/mark_lost.png | Bin 0 -> 22838 bytes
docs/media/mark_missing_damaged.png | Bin 0 -> 19868 bytes
docs/media/monograph_parts1.jpg | Bin 0 -> 42391 bytes
docs/media/monograph_parts2.jpg | Bin 0 -> 62711 bytes
docs/media/monograph_parts3.jpg | Bin 0 -> 61278 bytes
docs/media/monograph_parts4.jpg | Bin 0 -> 29854 bytes
docs/media/monograph_parts5.jpg | Bin 0 -> 25997 bytes
docs/media/myaccount-bookbags.png | Bin 0 -> 12928 bytes
docs/media/myaccount-itemrenew.png | Bin 0 -> 10188 bytes
docs/media/myaccount-itemscheckedout.png | Bin 0 -> 10136 bytes
docs/media/myaccount-itemsonhold.png | Bin 0 -> 110264 bytes
docs/media/myaccount-login-arrow.png | Bin 0 -> 394 bytes
docs/media/myaccount-login-info.png | Bin 0 -> 461 bytes
docs/media/myaccount-login.png | Bin 0 -> 123125 bytes
docs/media/myaccount-loginpasswordupdate.png | Bin 0 -> 5396 bytes
docs/media/myaccount-summary.png | Bin 0 -> 16025 bytes
docs/media/note.png | Bin 0 -> 2347 bytes
docs/media/offline-1.png | Bin 0 -> 59920 bytes
docs/media/offline-10.png | Bin 0 -> 5195 bytes
docs/media/offline-11.png | Bin 0 -> 36906 bytes
docs/media/offline-12.png | Bin 0 -> 8048 bytes
docs/media/offline-13.png | Bin 0 -> 32139 bytes
docs/media/offline-14.png | Bin 0 -> 8048 bytes
docs/media/offline-15.png | Bin 0 -> 5949 bytes
docs/media/offline-16.png | Bin 0 -> 3411 bytes
docs/media/offline-17.png | Bin 0 -> 5902 bytes
docs/media/offline-18.png | Bin 0 -> 6801 bytes
docs/media/offline-19.png | Bin 0 -> 8285 bytes
docs/media/offline-2.png | Bin 0 -> 37765 bytes
docs/media/offline-20.png | Bin 0 -> 25657 bytes
docs/media/offline-21.png | Bin 0 -> 6534 bytes
docs/media/offline-22.png | Bin 0 -> 5700 bytes
docs/media/offline-23.png | Bin 0 -> 24435 bytes
docs/media/offline-24.png | Bin 0 -> 8586 bytes
docs/media/offline-25.png | Bin 0 -> 32816 bytes
docs/media/offline-26.png | Bin 0 -> 34571 bytes
docs/media/offline-27.png | Bin 0 -> 11250 bytes
docs/media/offline-28.png | Bin 0 -> 5962 bytes
docs/media/offline-29.png | Bin 0 -> 20385 bytes
docs/media/offline-3.png | Bin 0 -> 9451 bytes
docs/media/offline-30.png | Bin 0 -> 34584 bytes
docs/media/offline-31.png | Bin 0 -> 35818 bytes
docs/media/offline-32.png | Bin 0 -> 40429 bytes
docs/media/offline-33.png | Bin 0 -> 35172 bytes
docs/media/offline-34.png | Bin 0 -> 33055 bytes
docs/media/offline-35.png | Bin 0 -> 39776 bytes
docs/media/offline-36.png | Bin 0 -> 21112 bytes
docs/media/offline-4.png | Bin 0 -> 38004 bytes
docs/media/offline-5.png | Bin 0 -> 12201 bytes
docs/media/offline-6.png | Bin 0 -> 20501 bytes
docs/media/offline-7.png | Bin 0 -> 3090 bytes
docs/media/offline-8.png | Bin 0 -> 13920 bytes
docs/media/offline-9.png | Bin 0 -> 19735 bytes
docs/media/overdue_checkin.png | Bin 0 -> 5778 bytes
docs/media/passwordresetmessage.png | Bin 0 -> 10275 bytes
docs/media/patron-1.png | Bin 0 -> 15218 bytes
docs/media/patron-10.png | Bin 0 -> 10969 bytes
docs/media/patron-11.png | Bin 0 -> 9353 bytes
docs/media/patron-12.png | Bin 0 -> 5044 bytes
docs/media/patron-13.png | Bin 0 -> 6040 bytes
docs/media/patron-14.png | Bin 0 -> 9237 bytes
docs/media/patron-15.png | Bin 0 -> 9845 bytes
docs/media/patron-16.png | Bin 0 -> 10510 bytes
docs/media/patron-17.png | Bin 0 -> 14726 bytes
docs/media/patron-18.png | Bin 0 -> 35778 bytes
docs/media/patron-19.png | Bin 0 -> 29051 bytes
docs/media/patron-2.png | Bin 0 -> 18287 bytes
docs/media/patron-20.png | Bin 0 -> 13616 bytes
docs/media/patron-21.png | Bin 0 -> 8509 bytes
docs/media/patron-22.png | Bin 0 -> 6924 bytes
docs/media/patron-23.png | Bin 0 -> 45282 bytes
docs/media/patron-24.png | Bin 0 -> 15298 bytes
docs/media/patron-25.png | Bin 0 -> 15837 bytes
docs/media/patron-26.png | Bin 0 -> 13936 bytes
docs/media/patron-27.png | Bin 0 -> 63701 bytes
docs/media/patron-28.png | Bin 0 -> 8780 bytes
docs/media/patron-29.png | Bin 0 -> 18732 bytes
docs/media/patron-3.png | Bin 0 -> 43597 bytes
docs/media/patron-30.png | Bin 0 -> 6516 bytes
docs/media/patron-31.png | Bin 0 -> 70632 bytes
docs/media/patron-32.png | Bin 0 -> 20275 bytes
docs/media/patron-3a.png | Bin 0 -> 14196 bytes
docs/media/patron-4.png | Bin 0 -> 5556 bytes
docs/media/patron-5.png | Bin 0 -> 53290 bytes
docs/media/patron-6.png | Bin 0 -> 11036 bytes
docs/media/patron-7.png | Bin 0 -> 7078 bytes
docs/media/patron-8.png | Bin 0 -> 10298 bytes
docs/media/patron-9.png | Bin 0 -> 37392 bytes
docs/media/patron-record-status-1.png | Bin 0 -> 2854 bytes
docs/media/patron-record-status-dark-grey.png | Bin 0 -> 1185 bytes
docs/media/patron-record-status-green.png | Bin 0 -> 805 bytes
docs/media/patron-record-status-light-grey.png | Bin 0 -> 1021 bytes
docs/media/patron-record-status-orange.png | Bin 0 -> 1514 bytes
docs/media/patron-record-status-purple.png | Bin 0 -> 1092 bytes
docs/media/patron-record-status-red.png | Bin 0 -> 878 bytes
docs/media/patron-record-status-yellow.png | Bin 0 -> 1060 bytes
docs/media/patron_summary_checkouts.jpg | Bin 0 -> 18626 bytes
docs/media/pdf_icon.gif | Bin 0 -> 2551 bytes
docs/media/pre_cat_alert.png | Bin 0 -> 19222 bytes
docs/media/precat.png | Bin 0 -> 8730 bytes
docs/media/profile-5.png | Bin 0 -> 22559 bytes
docs/media/profile-6.png | Bin 0 -> 11652 bytes
docs/media/profile-7.png | Bin 0 -> 6019 bytes
docs/media/receipt-10.jpg | Bin 0 -> 73728 bytes
docs/media/receipt-11.jpg | Bin 0 -> 65536 bytes
docs/media/receipt-12.jpg | Bin 0 -> 53248 bytes
docs/media/receipt-13.jpg | Bin 0 -> 53248 bytes
docs/media/receipt-14.jpg | Bin 0 -> 81920 bytes
docs/media/receipt-15.jpg | Bin 0 -> 46856 bytes
docs/media/receipt-16.png | Bin 0 -> 16284 bytes
docs/media/receipt-17.jpg | Bin 0 -> 36864 bytes
docs/media/receipt-18.jpg | Bin 0 -> 131072 bytes
docs/media/receipt-19.jpg | Bin 0 -> 32768 bytes
docs/media/receipt-2.jpg | Bin 0 -> 112892 bytes
docs/media/receipt-20.jpg | Bin 0 -> 36864 bytes
docs/media/receipt-21.jpg | Bin 0 -> 118784 bytes
docs/media/receipt-22.jpg | Bin 0 -> 61440 bytes
docs/media/receipt-23.jpg | Bin 0 -> 32768 bytes
docs/media/receipt-24.jpg | Bin 0 -> 89243 bytes
docs/media/receipt-3.jpg | Bin 0 -> 180361 bytes
docs/media/receipt-4.jpg | Bin 0 -> 164476 bytes
docs/media/receipt-5.jpg | Bin 0 -> 163840 bytes
docs/media/receipt-6.jpg | Bin 0 -> 28672 bytes
docs/media/receipt-7.jpg | Bin 0 -> 69632 bytes
docs/media/receipt-8.jpg | Bin 0 -> 98304 bytes
docs/media/receipt-9.jpg | Bin 0 -> 69632 bytes
docs/media/record_in_house_action.png | Bin 0 -> 12900 bytes
docs/media/renew_action.png | Bin 0 -> 30528 bytes
docs/media/renew_item.png | Bin 0 -> 6841 bytes
docs/media/renew_item_calendar.png | Bin 0 -> 12664 bytes
docs/media/renew_specific_date.png | Bin 0 -> 15755 bytes
docs/media/retrieve_patron.png | Bin 0 -> 3999 bytes
docs/media/scv-crec.jpg | Bin 0 -> 110254 bytes
docs/media/scv-distr.jpg | Bin 0 -> 83584 bytes
docs/media/scv-iss.jpg | Bin 0 -> 230756 bytes
docs/media/scv-rec.jpg | Bin 0 -> 88441 bytes
docs/media/scv-srec.jpg | Bin 0 -> 30056 bytes
docs/media/scv-sub.jpg | Bin 0 -> 49342 bytes
docs/media/server-3.png | Bin 0 -> 7735 bytes
docs/media/server-4.png | Bin 0 -> 8937 bytes
docs/media/server-5.png | Bin 0 -> 7886 bytes
docs/media/server-6.png | Bin 0 -> 8815 bytes
docs/media/shared-template-6.png | Bin 0 -> 39462 bytes
docs/media/shared-template-7.png | Bin 0 -> 10199 bytes
docs/media/shared-template-9.png | Bin 0 -> 32141 bytes
docs/media/small_logo_white.jpg | Bin 0 -> 4921 bytes
docs/media/specify_due_date1.png | Bin 0 -> 14610 bytes
docs/media/specify_due_date2.png | Bin 0 -> 6310 bytes
docs/media/staffclient-1.png | Bin 0 -> 35498 bytes
docs/media/staffclient-2.png | Bin 0 -> 5503 bytes
docs/media/staffclient-3.png | Bin 0 -> 5982 bytes
docs/media/staffclient-4.png | Bin 0 -> 54260 bytes
docs/media/staffclient-5.png | Bin 0 -> 3869 bytes
docs/media/staffclient-6.png | Bin 0 -> 18281 bytes
docs/media/staffclient-6a.png | Bin 0 -> 11303 bytes
docs/media/staffclient-6b.png | Bin 0 -> 9990 bytes
docs/media/staffclient-6c.png | Bin 0 -> 4928 bytes
docs/media/staffclient-6d.png | Bin 0 -> 40149 bytes
docs/media/staffclient-7.png | Bin 0 -> 2058 bytes
docs/media/staffclient-7a.png | Bin 0 -> 7051 bytes
docs/media/staffclient-8.png | Bin 0 -> 5011 bytes
docs/media/staffclient-9.png | Bin 0 -> 18852 bytes
.../staffclientinstallation-proxy-putty-1.png | Bin 0 -> 109048 bytes
.../staffclientinstallation-proxy-socks-1.png | Bin 0 -> 199302 bytes
.../staffclientinstallation-proxy-socks-2.png | Bin 0 -> 227598 bytes
.../staffclientinstallation-staffclient-1.png | Bin 0 -> 18829 bytes
.../staffclientinstallation-staffclient-2.png | Bin 0 -> 26230 bytes
.../staffclientinstallation-staffclient-3.png | Bin 0 -> 1200 bytes
.../staffclientinstallation-staffclient-4.png | Bin 0 -> 1200 bytes
...installation-staffclient-workstationnames-1.png | Bin 0 -> 213684 bytes
...installation-staffclient-workstationnames-2.png | Bin 0 -> 236260 bytes
...installation-staffclient-workstationnames-3.png | Bin 0 -> 203430 bytes
docs/media/staffclientinstallation-tabbed-1.png | Bin 0 -> 59049 bytes
docs/media/survey-1.png | Bin 0 -> 33887 bytes
docs/media/survey-10.png | Bin 0 -> 18349 bytes
docs/media/survey-2.png | Bin 0 -> 8172 bytes
docs/media/survey-3.png | Bin 0 -> 6292 bytes
docs/media/survey-4.png | Bin 0 -> 19031 bytes
docs/media/survey-5.png | Bin 0 -> 7262 bytes
docs/media/survey-6.png | Bin 0 -> 2273 bytes
docs/media/survey-7.png | Bin 0 -> 10025 bytes
docs/media/survey-8.png | Bin 0 -> 12357 bytes
docs/media/survey-9.png | Bin 0 -> 9531 bytes
docs/media/tip.png | Bin 0 -> 953 bytes
docs/media/transit-1.png | Bin 0 -> 53265 bytes
docs/media/transit-10.png | Bin 0 -> 40977 bytes
docs/media/transit-2.png | Bin 0 -> 57748 bytes
docs/media/transit-3.png | Bin 0 -> 27246 bytes
docs/media/transit-4a.png | Bin 0 -> 10622 bytes
docs/media/transit-5.png | Bin 0 -> 27073 bytes
docs/media/transit-6.png | Bin 0 -> 18456 bytes
docs/media/transit-7.png | Bin 0 -> 10135 bytes
docs/media/transit-8.png | Bin 0 -> 22123 bytes
docs/media/transit-9.png | Bin 0 -> 28516 bytes
docs/media/unified_volume_copy_creator1.jpg | Bin 0 -> 47048 bytes
docs/media/unified_volume_copy_creator2.jpg | Bin 0 -> 66080 bytes
docs/media/unified_volume_copy_creator3.jpg | Bin 0 -> 105516 bytes
docs/media/unified_volume_copy_creator4.jpg | Bin 0 -> 78399 bytes
docs/media/unified_volume_copy_creator5.jpg | Bin 0 -> 97404 bytes
docs/media/unified_volume_copy_creator6.jpg | Bin 0 -> 99631 bytes
docs/media/view-output-1.png | Bin 0 -> 23969 bytes
docs/media/view-output-2.png | Bin 0 -> 17390 bytes
docs/media/view-output-3.png | Bin 0 -> 14618 bytes
docs/media/view-output-4.png | Bin 0 -> 10392 bytes
docs/media/view-output-5.png | Bin 0 -> 29235 bytes
docs/media/warning.png | Bin 0 -> 2344 bytes
docs/opac/my_lists.txt | 63 ++
.../python/oils/__init__.py => docs/reports/README | 0
docs/root.txt | 327 ++++++++
docs/serials/A-intro.txt | 30 +
docs/serials/B-copy_template.txt | 43 +
docs/serials/C-subscription-SCV.txt | 152 ++++
docs/serials/D-subscription-ASCV.txt | 188 +++++
docs/serials/E-edit_subscriptions.txt | 19 +
docs/serials/F-Receiving.txt | 64 ++
docs/serials/G-Special_issue.txt | 9 +
.../Group_Serials_Issues_in_the_OPAC_2.2.txt | 51 ++
docs/serials/H-holdings_statements.txt | 35 +
media/pdf_icon.png | Bin 0 -> 2888 bytes
805 files changed, 5648 insertions(+), 5024 deletions(-)
mode change 100644 => 120000 README
delete mode 100644 docs/1.6/book1/sysadmin/indexedfieldweighting.xml
delete mode 100644 docs/1.6/styleguide/admon.xml
delete mode 100644 docs/1.6/styleguide/authoring.xml
delete mode 100644 docs/1.6/styleguide/books.xml
delete mode 100644 docs/1.6/styleguide/build.xml
delete mode 100644 docs/1.6/styleguide/chapter.xml
delete mode 100644 docs/1.6/styleguide/conditional.xml
delete mode 100644 docs/1.6/styleguide/exclude.xml
delete mode 100644 docs/1.6/styleguide/figures.xml
delete mode 100644 docs/1.6/styleguide/filenames.xml
delete mode 100644 docs/1.6/styleguide/general.xml
delete mode 100644 docs/1.6/styleguide/glossary.xml
delete mode 100644 docs/1.6/styleguide/indexterms.xml
delete mode 100644 docs/1.6/styleguide/links.xml
delete mode 100644 docs/1.6/styleguide/lists.xml
delete mode 100644 docs/1.6/styleguide/overview.xml
delete mode 100644 docs/1.6/styleguide/programming.xml
delete mode 100644 docs/1.6/styleguide/structure.xml
delete mode 100644 docs/1.6/styleguide/styleguide.xml
delete mode 100644 docs/1.6/styleguide/tables.xml
create mode 100644 docs/acquisitions/introduction.txt
create mode 100644 docs/acquisitions/receive_items_from_invoice.txt
create mode 100644 docs/acquisitions/selection_lists_po.txt
create mode 100644 docs/acquisitions/vandelay_acquisitions_integration.txt
create mode 100644 docs/admin/SMS_messaging.txt
create mode 100644 docs/admin/acquisitions_admin.txt
create mode 100644 docs/admin/authorities.txt
create mode 100644 docs/admin/auto_suggest_search.txt
create mode 100644 docs/admin/booking-admin.txt
create mode 100644 docs/admin/cn_prefixes_and_suffixes.txt
create mode 100644 docs/admin/customize_staff_client.txt
create mode 100644 docs/admin/hold_driven_recalls.txt
create mode 100644 docs/admin/lsa-library_settings_editor.txt
create mode 100644 docs/admin/lsa-statcat.txt
create mode 100644 docs/admin/recent_staff_searches.txt
create mode 100644 docs/admin/restrict_Z39.50_sources_by_perm_group.txt
create mode 100644 docs/admin/staff_client-double_clicking.txt
create mode 100644 docs/admin/staff_client-recent_searches.txt
create mode 100644 docs/admin/staff_client-return_to_results_from_marc.txt
create mode 100644 docs/admin/staff_client-sorting_columns.txt
create mode 100644 docs/admin/staff_client-tab_buttons.txt
create mode 100644 docs/admin/template_toolkit.txt
create mode 100644 docs/admin/user_activity_type.txt
create mode 100644 docs/attributions.txt
create mode 100644 docs/cataloging/batch_importing_MARC.txt
create mode 100644 docs/cataloging/conjoined_items.txt
create mode 100644 docs/cataloging/monograph_parts.txt
create mode 100644 docs/cataloging/overlay_record_3950_import.txt
copy Open-ILS/src/python/oils/__init__.py => docs/circulation/README (100%)
create mode 100644 docs/circulation/booking.txt
create mode 100644 docs/circulation/circulating_items.txt
create mode 100644 docs/circulation/circulation_patron_records.txt
copy Open-ILS/src/python/oils/__init__.py => docs/development/README (100%)
create mode 100644 docs/development/updating_translations_launchpad.txt
create mode 100644 docs/installation/edi_setup.txt
create mode 100644 docs/installation/server_installation.txt
create mode 100644 docs/installation/server_upgrade.txt
create mode 100644 docs/installation/system_requirements.txt
create mode 100644 docs/licensing.txt
create mode 100644 docs/media/1.png
create mode 100644 docs/media/10.png
create mode 100644 docs/media/11.png
create mode 100644 docs/media/12.png
create mode 100644 docs/media/13.png
create mode 100644 docs/media/14.png
create mode 100644 docs/media/15.png
create mode 100644 docs/media/2.png
create mode 100644 docs/media/3.png
create mode 100644 docs/media/4.png
create mode 100644 docs/media/5.png
create mode 100644 docs/media/6.png
create mode 100644 docs/media/7.png
create mode 100644 docs/media/8.png
create mode 100644 docs/media/9.png
create mode 100644 docs/media/Authority_Control_Sets1.jpg
create mode 100644 docs/media/Authority_Control_Sets1.jpg.1
create mode 100644 docs/media/Authority_Control_Sets2.jpg
create mode 100644 docs/media/Authority_Control_Sets2.jpg.1
create mode 100644 docs/media/Authority_Control_Sets3.jpg
create mode 100644 docs/media/Authority_Control_Sets3.jpg.1
create mode 100644 docs/media/Authority_Control_Sets4.jpg
create mode 100644 docs/media/Authority_Control_Sets4.jpg.1
create mode 100644 docs/media/Authority_Control_Sets5.jpg
create mode 100644 docs/media/Authority_Control_Sets5.jpg.1
create mode 100644 docs/media/Authority_Control_Sets6.jpg
create mode 100644 docs/media/Authority_Control_Sets6.jpg.1
create mode 100644 docs/media/Authority_Control_Sets7.jpg
create mode 100644 docs/media/Authority_Control_Sets7.jpg.1
create mode 100644 docs/media/Authority_Control_Sets8.jpg
create mode 100644 docs/media/Authority_Control_Sets8.jpg.1
create mode 100644 docs/media/Authority_Control_Sets9.jpg
create mode 100644 docs/media/Authority_Control_Sets9.jpg.1
create mode 100644 docs/media/Auto_Suggest_in_Catalog_Search1.jpg
create mode 100644 docs/media/Auto_Suggest_in_Catalog_Search2.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records1.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records10.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records11.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records12.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records13.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records14.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records15.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records2.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records3.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records4.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records5.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records6.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records7.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records8.jpg
create mode 100644 docs/media/Batch_Importing_MARC_Records9.jpg
create mode 100644 docs/media/Call_Number_Prefixes_and_Suffixes_2_21.jpg
create mode 100644 docs/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg
create mode 100644 docs/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg.1
create mode 100644 docs/media/Customizable_Toolbar1.jpg
create mode 100644 docs/media/Customizable_Toolbar2.jpg
create mode 100644 docs/media/Customizable_Toolbar3.jpg
create mode 100644 docs/media/Customizable_Toolbar4.jpg
create mode 100644 docs/media/Double_Click1.jpg
create mode 100644 docs/media/Double_Click2.jpg
create mode 100644 docs/media/Double_Click3.jpg
create mode 100644 docs/media/Group_Serials_Issues_in_the_OPAC2.jpg
create mode 100644 docs/media/Group_Serials_Issues_in_the_OPAC5.jpg
create mode 100644 docs/media/Group_Serials_Issues_in_the_OPAC7.jpg
create mode 100644 docs/media/My_Lists1.jpg
create mode 100644 docs/media/My_Lists3.jpg
create mode 100644 docs/media/My_Lists4.jpg
create mode 100644 docs/media/My_Lists5.jpg
create mode 100644 docs/media/My_Lists6.jpg
create mode 100644 docs/media/My_Lists7.jpg
create mode 100644 docs/media/New_Tab_Button1.jpg
create mode 100644 docs/media/Overlay_Existing_Record_via_Z39_50_Import1.jpg
create mode 100644 docs/media/Overlay_Existing_Record_via_Z39_50_Import2.jpg
create mode 100644 docs/media/Overlay_Existing_Record_via_Z39_50_Import3.jpg
create mode 100644 docs/media/Overlay_Existing_Record_via_Z39_50_Import4.jpg
create mode 100644 docs/media/Overlay_Existing_Record_via_Z39_50_Import5.jpg
create mode 100644 docs/media/Overlay_Existing_Record_via_Z39_50_Import6.jpg
create mode 100644 docs/media/Receive_Items_From_an_Invoice1.jpg
create mode 100644 docs/media/Receive_Items_From_an_Invoice2.jpg
create mode 100644 docs/media/Receive_Items_From_an_Invoice3.jpg
create mode 100644 docs/media/Receive_Items_From_an_Invoice4.jpg
create mode 100644 docs/media/Receive_Items_From_an_Invoice5.jpg
create mode 100644 docs/media/Receive_Items_From_an_Invoice6.jpg
create mode 100644 docs/media/Receive_Items_From_an_Invoice7.jpg
create mode 100644 docs/media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg
create mode 100644 docs/media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg
create mode 100644 docs/media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg
create mode 100644 docs/media/SMS_Text_Messaging1.jpg
create mode 100644 docs/media/SMS_Text_Messaging10.jpg
create mode 100644 docs/media/SMS_Text_Messaging11.jpg
create mode 100644 docs/media/SMS_Text_Messaging12.jpg
create mode 100644 docs/media/SMS_Text_Messaging13.jpg
create mode 100644 docs/media/SMS_Text_Messaging2.jpg
create mode 100644 docs/media/SMS_Text_Messaging3.jpg
create mode 100644 docs/media/SMS_Text_Messaging4.jpg
create mode 100644 docs/media/SMS_Text_Messaging5.jpg
create mode 100644 docs/media/SMS_Text_Messaging6.jpg
create mode 100644 docs/media/SMS_Text_Messaging7.jpg
create mode 100644 docs/media/SMS_Text_Messaging8.jpg
create mode 100644 docs/media/SMS_Text_Messaging9.jpg
create mode 100644 docs/media/Saved_Catalog_Searches_2_21.jpg
create mode 100644 docs/media/Saved_Catalog_Searches_2_21.jpg.1
create mode 100644 docs/media/Saved_Catalog_Searches_2_22.jpg
create mode 100644 docs/media/Saved_Catalog_Searches_2_22.jpg.1
create mode 100644 docs/media/Search_Results1.jpg
create mode 100644 docs/media/Sorting_Columns2.jpg
create mode 100644 docs/media/Sorting_Columns3.jpg
create mode 100644 docs/media/Sorting_Columns3.jpg.1
create mode 100644 docs/media/Sorting_Columns4.jpg
create mode 100644 docs/media/Sorting_Columns5.jpg
create mode 100644 docs/media/Target_Pickup_Lib1.jpg
create mode 100644 docs/media/Target_Pickup_Lib2.jpg
create mode 100644 docs/media/User_Activity_Types1A.jpg
create mode 100644 docs/media/User_Activity_Types2A.jpg
create mode 100644 docs/media/Vandelay_Integration_into_Acquisitions1.jpg
create mode 100644 docs/media/Vandelay_Integration_into_Acquisitions2.jpg
create mode 100644 docs/media/Vandelay_Integration_into_Acquisitions3.jpg
create mode 100644 docs/media/Vandelay_Integration_into_Acquisitions4.jpg
create mode 100644 docs/media/Vandelay_Integration_into_Acquisitions5.jpg
create mode 100644 docs/media/Vandelay_Integration_into_Acquisitions6.jpg
create mode 100644 docs/media/acq_activate.png
create mode 100644 docs/media/acq_apply_claim_policy.png
create mode 100644 docs/media/acq_brief_record-2.png
create mode 100644 docs/media/acq_brief_record.png
create mode 100644 docs/media/acq_cancel_copy.png
create mode 100644 docs/media/acq_cancel_line_items.png
create mode 100644 docs/media/acq_claim_item-2.png
create mode 100644 docs/media/acq_claim_item-3.png
create mode 100644 docs/media/acq_claim_item-4.png
create mode 100644 docs/media/acq_claim_item-5.png
create mode 100644 docs/media/acq_claim_item.png
create mode 100644 docs/media/acq_export_list.png
create mode 100644 docs/media/acq_funds-2.png
create mode 100644 docs/media/acq_funds.png
create mode 100644 docs/media/acq_invoice_blanket.png
create mode 100644 docs/media/acq_invoice_line_items.png
create mode 100644 docs/media/acq_invoice_link.png
create mode 100644 docs/media/acq_invoice_purchase_order.png
create mode 100644 docs/media/acq_invoice_view-2.png
create mode 100644 docs/media/acq_invoice_view.png
create mode 100644 docs/media/acq_line_items_add_copies-2.png
create mode 100644 docs/media/acq_line_items_add_copies-3.png
create mode 100644 docs/media/acq_line_items_add_copies.png
create mode 100644 docs/media/acq_line_items_add_notes.png
create mode 100644 docs/media/acq_line_items_alerts-2.png
create mode 100644 docs/media/acq_line_items_alerts.png
create mode 100644 docs/media/acq_line_items_link-2.png
create mode 100644 docs/media/acq_line_items_link.png
create mode 100644 docs/media/acq_line_items_update_barcodes.png
create mode 100644 docs/media/acq_line_items_view_history.png
create mode 100644 docs/media/acq_line_items_worksheet.png
create mode 100644 docs/media/acq_load_records.png
create mode 100644 docs/media/acq_marc_search-2.png
create mode 100644 docs/media/acq_marc_search.png
create mode 100644 docs/media/acq_purchase_order_add_charges.png
create mode 100644 docs/media/acq_purchase_order_add_note.png
create mode 100644 docs/media/acq_purchase_order_create.png
create mode 100644 docs/media/acq_purchase_order_history.png
create mode 100644 docs/media/acq_purchase_order_name.png
create mode 100644 docs/media/acq_purchase_order_print.png
create mode 100644 docs/media/acq_purchase_order_split-2.png
create mode 100644 docs/media/acq_purchase_order_split.png
create mode 100644 docs/media/acq_purchase_order_view-2.png
create mode 100644 docs/media/acq_purchase_order_view.png
create mode 100644 docs/media/acq_search.png
create mode 100644 docs/media/acq_selection_clone.png
create mode 100644 docs/media/acq_selection_create.png
create mode 100644 docs/media/acq_selection_mark_ready-2.png
create mode 100644 docs/media/acq_selection_mark_ready.png
create mode 100644 docs/media/acq_selection_merge.png
create mode 100644 docs/media/acq_workflow.jpg
create mode 100644 docs/media/add_holdings-1.png
create mode 100644 docs/media/add_holdings-2.png
create mode 100644 docs/media/add_holdings-3.png
create mode 100644 docs/media/add_holdings-4.png
create mode 100644 docs/media/add_holdings-5.png
create mode 100644 docs/media/application-pdf.png
create mode 100644 docs/media/ascv-distr.jpg
create mode 100644 docs/media/ascv-issues.jpg
create mode 100644 docs/media/ascv-sub.jpg
create mode 100644 docs/media/backdate_checkin.png
create mode 100644 docs/media/backdate_post_checkin.png
create mode 100644 docs/media/backdate_post_date.png
create mode 100644 docs/media/backdate_red.png
create mode 100644 docs/media/bills-1.png
create mode 100644 docs/media/bills-10.png
create mode 100644 docs/media/bills-11.png
create mode 100644 docs/media/bills-12.png
create mode 100644 docs/media/bills-13.png
create mode 100644 docs/media/bills-14.png
create mode 100644 docs/media/bills-15.png
create mode 100644 docs/media/bills-16.png
create mode 100644 docs/media/bills-17.png
create mode 100644 docs/media/bills-18.png
create mode 100644 docs/media/bills-19.png
create mode 100644 docs/media/bills-2.png
create mode 100644 docs/media/bills-20.png
create mode 100644 docs/media/bills-3.png
create mode 100644 docs/media/bills-4.png
create mode 100644 docs/media/bills-5.png
create mode 100644 docs/media/bills-6.png
create mode 100644 docs/media/bills-7.png
create mode 100644 docs/media/bills-8.png
create mode 100644 docs/media/bills-9.png
create mode 100644 docs/media/booking-cancel-1.png
create mode 100644 docs/media/booking-cancel-2.png
create mode 100644 docs/media/booking-cancel-3.png
create mode 100644 docs/media/booking-cancel-4.png
create mode 100644 docs/media/booking-capture-1.png
create mode 100644 docs/media/booking-capture-2.png
create mode 100644 docs/media/booking-capture-3.png
create mode 100644 docs/media/booking-create-1.png
create mode 100644 docs/media/booking-create-2.png
create mode 100644 docs/media/booking-create-3.png
create mode 100644 docs/media/booking-create-4.png
create mode 100644 docs/media/booking-create-5.png
create mode 100644 docs/media/booking-create-6.png
create mode 100644 docs/media/booking-create-7.png
create mode 100644 docs/media/booking-create-8.png
create mode 100644 docs/media/booking-create-9.png
create mode 100644 docs/media/booking-create-bookable-1.png
create mode 100644 docs/media/booking-create-bookable-2.png
create mode 100644 docs/media/booking-create-bookable-3.png
create mode 100644 docs/media/booking-create-bookable-4.png
create mode 100644 docs/media/booking-create-bookable-5.png
create mode 100644 docs/media/booking-create-bookable-6.png
create mode 100644 docs/media/booking-create-module-1.png
create mode 100644 docs/media/booking-create-module-2.png
create mode 100644 docs/media/booking-create-module-3.png
create mode 100644 docs/media/booking-create-module-4.png
create mode 100644 docs/media/booking-create-resourcetype-1.png
create mode 100644 docs/media/booking-create-resourcetype-2.png
create mode 100644 docs/media/booking-create-resourcetype-3.png
create mode 100644 docs/media/booking-create-resourcetype-4.png
create mode 100644 docs/media/booking-create-resourcetype-5.png
create mode 100644 docs/media/booking-pickup-1.png
create mode 100644 docs/media/booking-pickup-2.png
create mode 100644 docs/media/booking-pickup-3.png
create mode 100644 docs/media/booking-pickup-module-1.png
create mode 100644 docs/media/booking-pull-1.png
create mode 100644 docs/media/booking-pull-2.png
create mode 100644 docs/media/booking-pull-3.png
create mode 100644 docs/media/booking-return-2.png
create mode 100644 docs/media/booking-return-module-1.png
create mode 100644 docs/media/booking-return-module-2.png
create mode 100644 docs/media/booking-return-module-4.png
create mode 100644 docs/media/cap-wiz-cal.jpg
create mode 100644 docs/media/cap-wiz-chan.jpg
create mode 100644 docs/media/cap-wiz-chron.jpg
create mode 100644 docs/media/cap-wiz-freq.jpg
create mode 100644 docs/media/cap-wiz-num.jpg
create mode 100644 docs/media/catalogue-10.png
create mode 100644 docs/media/catalogue-11.png
create mode 100644 docs/media/catalogue-3.png
create mode 100644 docs/media/catalogue-4.png
create mode 100644 docs/media/catalogue-5.png
create mode 100644 docs/media/catalogue-6.png
create mode 100644 docs/media/catalogue-7.png
create mode 100644 docs/media/catalogue-8.png
create mode 100644 docs/media/catalogue-9.png
create mode 100644 docs/media/caution.png
create mode 100644 docs/media/ccbysa.png
create mode 100644 docs/media/check_in_menu.png
create mode 100644 docs/media/checkin_barcode.png
create mode 100644 docs/media/checkin_options.png
create mode 100644 docs/media/checkout_item_barcode.png
create mode 100644 docs/media/checkout_menu.png
create mode 100644 docs/media/circulation-1.png
create mode 100644 docs/media/circulation-10.png
create mode 100644 docs/media/circulation-11.png
create mode 100644 docs/media/circulation-12.png
create mode 100644 docs/media/circulation-13.png
create mode 100644 docs/media/circulation-14.png
create mode 100644 docs/media/circulation-15.png
create mode 100644 docs/media/circulation-16.png
create mode 100644 docs/media/circulation-17.png
create mode 100644 docs/media/circulation-18.png
create mode 100644 docs/media/circulation-19.png
create mode 100644 docs/media/circulation-2.png
create mode 100644 docs/media/circulation-20.png
create mode 100644 docs/media/circulation-21.png
create mode 100644 docs/media/circulation-22.png
create mode 100644 docs/media/circulation-23.png
create mode 100644 docs/media/circulation-24.png
create mode 100644 docs/media/circulation-25.png
create mode 100644 docs/media/circulation-26.png
create mode 100644 docs/media/circulation-27.png
create mode 100644 docs/media/circulation-28.png
create mode 100644 docs/media/circulation-29.png
create mode 100644 docs/media/circulation-3.png
create mode 100644 docs/media/circulation-30.png
create mode 100644 docs/media/circulation-31.png
create mode 100644 docs/media/circulation-32.png
create mode 100644 docs/media/circulation-33.png
create mode 100644 docs/media/circulation-34.png
create mode 100644 docs/media/circulation-35.png
create mode 100644 docs/media/circulation-36.png
create mode 100644 docs/media/circulation-4.png
create mode 100644 docs/media/circulation-5.png
create mode 100644 docs/media/circulation-6.png
create mode 100644 docs/media/circulation-7.png
create mode 100644 docs/media/circulation-8.png
create mode 100644 docs/media/circulation-9.png
create mode 100644 docs/media/circulation_patron_records-1.png
create mode 100644 docs/media/circulation_patron_records-10.png
create mode 100644 docs/media/circulation_patron_records-11.png
create mode 100644 docs/media/circulation_patron_records-12.png
create mode 100644 docs/media/circulation_patron_records-13.png
create mode 100644 docs/media/circulation_patron_records-14.png
create mode 100644 docs/media/circulation_patron_records-15.png
create mode 100644 docs/media/circulation_patron_records-16.png
create mode 100644 docs/media/circulation_patron_records-17.png
create mode 100644 docs/media/circulation_patron_records-18.png
create mode 100644 docs/media/circulation_patron_records-19.png
create mode 100644 docs/media/circulation_patron_records-2.png
create mode 100644 docs/media/circulation_patron_records-20.png
create mode 100644 docs/media/circulation_patron_records-21.png
create mode 100644 docs/media/circulation_patron_records-22.png
create mode 100644 docs/media/circulation_patron_records-23.png
create mode 100644 docs/media/circulation_patron_records-24.png
create mode 100644 docs/media/circulation_patron_records-25.png
create mode 100644 docs/media/circulation_patron_records-26.png
create mode 100644 docs/media/circulation_patron_records-27.png
create mode 100644 docs/media/circulation_patron_records-28.png
create mode 100644 docs/media/circulation_patron_records-29.png
create mode 100644 docs/media/circulation_patron_records-3.png
create mode 100644 docs/media/circulation_patron_records-30.png
create mode 100644 docs/media/circulation_patron_records-31.png
create mode 100644 docs/media/circulation_patron_records-4.png
create mode 100644 docs/media/circulation_patron_records-5.png
create mode 100644 docs/media/circulation_patron_records-6.png
create mode 100644 docs/media/circulation_patron_records-7.png
create mode 100644 docs/media/circulation_patron_records-8.png
create mode 100644 docs/media/circulation_patron_records-9.png
create mode 100644 docs/media/claimed_date.png
create mode 100644 docs/media/conj1.jpg
create mode 100644 docs/media/conj10.jpg
create mode 100644 docs/media/conj2.jpg
create mode 100644 docs/media/conj3.jpg
create mode 100644 docs/media/conj4.jpg
create mode 100644 docs/media/conj5.jpg
create mode 100644 docs/media/conj6.jpg
create mode 100644 docs/media/conj7.jpg
create mode 100644 docs/media/conj8.jpg
create mode 100644 docs/media/conj9.jpg
create mode 100644 docs/media/copy_alert_message.png
create mode 100644 docs/media/copy_edit_alert.png
create mode 100644 docs/media/create-template-1.png
create mode 100644 docs/media/create-template-10.png
create mode 100644 docs/media/create-template-11.png
create mode 100644 docs/media/create-template-12.png
create mode 100644 docs/media/create-template-13.png
create mode 100644 docs/media/create-template-15.png
create mode 100644 docs/media/create-template-16.png
create mode 100644 docs/media/create-template-17.png
create mode 100644 docs/media/create-template-19.png
create mode 100644 docs/media/create-template-2.png
create mode 100644 docs/media/create-template-20.png
create mode 100644 docs/media/create-template-21.png
create mode 100644 docs/media/create-template-22.png
create mode 100644 docs/media/create-template-23.png
create mode 100644 docs/media/create-template-24.png
create mode 100644 docs/media/create-template-25.png
create mode 100644 docs/media/create-template-26.png
create mode 100644 docs/media/create-template-27.png
create mode 100644 docs/media/create-template-28.png
create mode 100644 docs/media/create-template-29.png
create mode 100644 docs/media/create-template-3.png
create mode 100644 docs/media/create-template-30.png
create mode 100644 docs/media/create-template-31.png
create mode 100644 docs/media/create-template-32.png
create mode 100644 docs/media/create-template-33.png
create mode 100644 docs/media/create-template-34.png
create mode 100644 docs/media/create-template-35.png
create mode 100644 docs/media/create-template-4.png
create mode 100644 docs/media/create-template-5.png
create mode 100644 docs/media/create-template-6.png
create mode 100644 docs/media/create-template-7.png
create mode 100644 docs/media/create-template-8.png
create mode 100644 docs/media/create-template-9.png
create mode 100644 docs/media/due_date_display.png
create mode 100644 docs/media/edit_due_date_action.png
create mode 100644 docs/media/epub_logo_color_ht39.gif
create mode 100644 docs/media/evergreen_logo.gif
create mode 100644 docs/media/folder-1.png
create mode 100644 docs/media/folder-10.png
create mode 100644 docs/media/folder-11.png
create mode 100644 docs/media/folder-12.png
create mode 100644 docs/media/folder-13.png
create mode 100644 docs/media/folder-14.png
create mode 100644 docs/media/folder-7a.png
create mode 100644 docs/media/generate-report-1.png
create mode 100644 docs/media/generate-report-10.png
create mode 100644 docs/media/generate-report-14.png
create mode 100644 docs/media/generate-report-2.png
create mode 100644 docs/media/generate-report-3.png
create mode 100644 docs/media/generate-report-8.png
create mode 100644 docs/media/generate-report-9.png
create mode 100644 docs/media/hold-1.png
create mode 100644 docs/media/hold-10.png
create mode 100644 docs/media/hold-11.png
create mode 100644 docs/media/hold-12.png
create mode 100644 docs/media/hold-14.png
create mode 100644 docs/media/hold-15.png
create mode 100644 docs/media/hold-16.png
create mode 100644 docs/media/hold-17.png
create mode 100644 docs/media/hold-18.png
create mode 100644 docs/media/hold-19.png
create mode 100644 docs/media/hold-2.png
create mode 100644 docs/media/hold-20.png
create mode 100644 docs/media/hold-21.png
create mode 100644 docs/media/hold-22.png
create mode 100644 docs/media/hold-23.png
create mode 100644 docs/media/hold-24.png
create mode 100644 docs/media/hold-25.png
create mode 100644 docs/media/hold-26.png
create mode 100644 docs/media/hold-27.png
create mode 100644 docs/media/hold-28.png
create mode 100644 docs/media/hold-29.png
create mode 100644 docs/media/hold-4.png
create mode 100644 docs/media/hold-5.png
create mode 100644 docs/media/hold-6.png
create mode 100644 docs/media/hold-7.png
create mode 100644 docs/media/hold-8.png
create mode 100644 docs/media/hold-9.png
create mode 100644 docs/media/holds-clearing-1.png
create mode 100644 docs/media/holds-clearing-2.png
create mode 100644 docs/media/holds-clearing-3.png
create mode 100644 docs/media/holds-clearing-4.png
create mode 100644 docs/media/holds-managing-1.png
create mode 100644 docs/media/holds-managing-10.png
create mode 100644 docs/media/holds-managing-11.png
create mode 100644 docs/media/holds-managing-12.png
create mode 100644 docs/media/holds-managing-13.png
create mode 100644 docs/media/holds-managing-14.png
create mode 100644 docs/media/holds-managing-15.png
create mode 100644 docs/media/holds-managing-16.png
create mode 100644 docs/media/holds-managing-17.png
create mode 100644 docs/media/holds-managing-18.png
create mode 100644 docs/media/holds-managing-19.png
create mode 100644 docs/media/holds-managing-2.png
create mode 100644 docs/media/holds-managing-3.png
create mode 100644 docs/media/holds-managing-4.png
create mode 100644 docs/media/holds-managing-5.png
create mode 100644 docs/media/holds-managing-6.png
create mode 100644 docs/media/holds-managing-7.png
create mode 100644 docs/media/holds-managing-8.png
create mode 100644 docs/media/holds-managing-9.png
create mode 100644 docs/media/holds-notifications-1.png
create mode 100644 docs/media/holds-notifications-2.png
create mode 100644 docs/media/holds-notifications-3.png
create mode 100644 docs/media/holds-notifications-4.png
create mode 100644 docs/media/holds-placing-1.png
create mode 100644 docs/media/holds-placing-10.png
create mode 100644 docs/media/holds-placing-11.png
create mode 100644 docs/media/holds-placing-2.png
create mode 100644 docs/media/holds-placing-3.png
create mode 100644 docs/media/holds-placing-4.png
create mode 100644 docs/media/holds-placing-5.png
create mode 100644 docs/media/holds-placing-6.png
create mode 100644 docs/media/holds-placing-7.png
create mode 100644 docs/media/holds-placing-8.png
create mode 100644 docs/media/holds-placing-9.png
create mode 100644 docs/media/holds-pull-1.png
create mode 100644 docs/media/holds-pull-2.png
create mode 100644 docs/media/holds-pull-3.png
create mode 100644 docs/media/holds-pull-4.png
create mode 100644 docs/media/holds-pull-5.png
create mode 100644 docs/media/holds-pull-5a.png
create mode 100644 docs/media/holds-pull-6.png
create mode 100644 docs/media/holds-pull-7.png
create mode 100644 docs/media/holds-pull-8.png
create mode 100644 docs/media/holds-pull-9.png
create mode 100644 docs/media/in_house_use.png
create mode 100644 docs/media/item_status_altview.png
create mode 100644 docs/media/item_status_barcode.png
create mode 100644 docs/media/item_status_list_view.png
create mode 100644 docs/media/item_status_menu.png
create mode 100644 docs/media/items_out_click.png
create mode 100644 docs/media/k_book_record.png
create mode 100644 docs/media/last_few_circs_action.png
create mode 100644 docs/media/last_few_circs_display.png
create mode 100644 docs/media/lost_cr_section.png
create mode 100644 docs/media/lsa-1.png
create mode 100644 docs/media/lsa-10.jpg
create mode 100644 docs/media/lsa-11.jpg
create mode 100644 docs/media/lsa-12.jpg
create mode 100644 docs/media/lsa-14.jpg
create mode 100644 docs/media/lsa-16.jpg
create mode 100644 docs/media/lsa-17.jpg
create mode 100644 docs/media/lsa-18.jpg
create mode 100644 docs/media/lsa-2.jpg
create mode 100644 docs/media/lsa-22.png
create mode 100644 docs/media/lsa-23.jpg
create mode 100644 docs/media/lsa-25.jpg
create mode 100644 docs/media/lsa-26.jpg
create mode 100644 docs/media/lsa-27.jpg
create mode 100644 docs/media/lsa-28.jpg
create mode 100644 docs/media/lsa-32.jpg
create mode 100644 docs/media/lsa-33.jpg
create mode 100644 docs/media/lsa-4.jpg
create mode 100644 docs/media/lsa-5.jpg
create mode 100644 docs/media/lsa-7.jpg
create mode 100644 docs/media/lsa-8.jpg
create mode 100644 docs/media/lsa-closed-mountain-1.png
create mode 100644 docs/media/lsa-closed-mountain-2.png
create mode 100644 docs/media/lsa-group-0.png
create mode 100644 docs/media/lsa-group-1.png
create mode 100644 docs/media/lsa-group-1a.png
create mode 100644 docs/media/lsa-group-2.png
create mode 100644 docs/media/lsa-group-3.png
create mode 100644 docs/media/lsa-group-4.png
create mode 100644 docs/media/lsa-group-5.png
create mode 100644 docs/media/lsa-group-6.png
create mode 100644 docs/media/lsa-statcat-1.png
create mode 100644 docs/media/lsa-statcat-2.png
create mode 100644 docs/media/lsa-statcat-3.png
create mode 100644 docs/media/lsa-statcat-4.png
create mode 100644 docs/media/lsa-statcat-5.png
create mode 100644 docs/media/lsa-statcat-6.png
create mode 100644 docs/media/lsa-statcat-7.png
create mode 100644 docs/media/lsa-statcat-8.png
copy {Open-ILS/web/opac/images => docs/media}/main_logo.jpg (100%)
create mode 100644 docs/media/mark_claims_returned.png
create mode 100644 docs/media/mark_lost.png
create mode 100644 docs/media/mark_missing_damaged.png
create mode 100644 docs/media/monograph_parts1.jpg
create mode 100644 docs/media/monograph_parts2.jpg
create mode 100644 docs/media/monograph_parts3.jpg
create mode 100644 docs/media/monograph_parts4.jpg
create mode 100644 docs/media/monograph_parts5.jpg
create mode 100644 docs/media/myaccount-bookbags.png
create mode 100644 docs/media/myaccount-itemrenew.png
create mode 100644 docs/media/myaccount-itemscheckedout.png
create mode 100644 docs/media/myaccount-itemsonhold.png
create mode 100644 docs/media/myaccount-login-arrow.png
create mode 100644 docs/media/myaccount-login-info.png
create mode 100644 docs/media/myaccount-login.png
create mode 100644 docs/media/myaccount-loginpasswordupdate.png
create mode 100644 docs/media/myaccount-summary.png
create mode 100644 docs/media/note.png
create mode 100644 docs/media/offline-1.png
create mode 100644 docs/media/offline-10.png
create mode 100644 docs/media/offline-11.png
create mode 100644 docs/media/offline-12.png
create mode 100644 docs/media/offline-13.png
create mode 100644 docs/media/offline-14.png
create mode 100644 docs/media/offline-15.png
create mode 100644 docs/media/offline-16.png
create mode 100644 docs/media/offline-17.png
create mode 100644 docs/media/offline-18.png
create mode 100644 docs/media/offline-19.png
create mode 100644 docs/media/offline-2.png
create mode 100644 docs/media/offline-20.png
create mode 100644 docs/media/offline-21.png
create mode 100644 docs/media/offline-22.png
create mode 100644 docs/media/offline-23.png
create mode 100644 docs/media/offline-24.png
create mode 100644 docs/media/offline-25.png
create mode 100644 docs/media/offline-26.png
create mode 100644 docs/media/offline-27.png
create mode 100644 docs/media/offline-28.png
create mode 100644 docs/media/offline-29.png
create mode 100644 docs/media/offline-3.png
create mode 100644 docs/media/offline-30.png
create mode 100644 docs/media/offline-31.png
create mode 100644 docs/media/offline-32.png
create mode 100644 docs/media/offline-33.png
create mode 100644 docs/media/offline-34.png
create mode 100644 docs/media/offline-35.png
create mode 100644 docs/media/offline-36.png
create mode 100644 docs/media/offline-4.png
create mode 100644 docs/media/offline-5.png
create mode 100644 docs/media/offline-6.png
create mode 100644 docs/media/offline-7.png
create mode 100644 docs/media/offline-8.png
create mode 100644 docs/media/offline-9.png
create mode 100644 docs/media/overdue_checkin.png
create mode 100644 docs/media/passwordresetmessage.png
create mode 100644 docs/media/patron-1.png
create mode 100644 docs/media/patron-10.png
create mode 100644 docs/media/patron-11.png
create mode 100644 docs/media/patron-12.png
create mode 100644 docs/media/patron-13.png
create mode 100644 docs/media/patron-14.png
create mode 100644 docs/media/patron-15.png
create mode 100644 docs/media/patron-16.png
create mode 100644 docs/media/patron-17.png
create mode 100644 docs/media/patron-18.png
create mode 100644 docs/media/patron-19.png
create mode 100644 docs/media/patron-2.png
create mode 100644 docs/media/patron-20.png
create mode 100644 docs/media/patron-21.png
create mode 100644 docs/media/patron-22.png
create mode 100644 docs/media/patron-23.png
create mode 100644 docs/media/patron-24.png
create mode 100644 docs/media/patron-25.png
create mode 100644 docs/media/patron-26.png
create mode 100644 docs/media/patron-27.png
create mode 100644 docs/media/patron-28.png
create mode 100644 docs/media/patron-29.png
create mode 100644 docs/media/patron-3.png
create mode 100644 docs/media/patron-30.png
create mode 100644 docs/media/patron-31.png
create mode 100644 docs/media/patron-32.png
create mode 100644 docs/media/patron-3a.png
create mode 100644 docs/media/patron-4.png
create mode 100644 docs/media/patron-5.png
create mode 100644 docs/media/patron-6.png
create mode 100644 docs/media/patron-7.png
create mode 100644 docs/media/patron-8.png
create mode 100644 docs/media/patron-9.png
create mode 100644 docs/media/patron-record-status-1.png
create mode 100644 docs/media/patron-record-status-dark-grey.png
create mode 100644 docs/media/patron-record-status-green.png
create mode 100644 docs/media/patron-record-status-light-grey.png
create mode 100644 docs/media/patron-record-status-orange.png
create mode 100644 docs/media/patron-record-status-purple.png
create mode 100644 docs/media/patron-record-status-red.png
create mode 100644 docs/media/patron-record-status-yellow.png
create mode 100644 docs/media/patron_summary_checkouts.jpg
create mode 100644 docs/media/pdf_icon.gif
create mode 100644 docs/media/pre_cat_alert.png
create mode 100644 docs/media/precat.png
create mode 100644 docs/media/profile-5.png
create mode 100644 docs/media/profile-6.png
create mode 100644 docs/media/profile-7.png
create mode 100644 docs/media/receipt-10.jpg
create mode 100644 docs/media/receipt-11.jpg
create mode 100644 docs/media/receipt-12.jpg
create mode 100644 docs/media/receipt-13.jpg
create mode 100644 docs/media/receipt-14.jpg
create mode 100644 docs/media/receipt-15.jpg
create mode 100644 docs/media/receipt-16.png
create mode 100644 docs/media/receipt-17.jpg
create mode 100644 docs/media/receipt-18.jpg
create mode 100644 docs/media/receipt-19.jpg
create mode 100644 docs/media/receipt-2.jpg
create mode 100644 docs/media/receipt-20.jpg
create mode 100644 docs/media/receipt-21.jpg
create mode 100644 docs/media/receipt-22.jpg
create mode 100644 docs/media/receipt-23.jpg
create mode 100644 docs/media/receipt-24.jpg
create mode 100644 docs/media/receipt-3.jpg
create mode 100644 docs/media/receipt-4.jpg
create mode 100644 docs/media/receipt-5.jpg
create mode 100644 docs/media/receipt-6.jpg
create mode 100644 docs/media/receipt-7.jpg
create mode 100644 docs/media/receipt-8.jpg
create mode 100644 docs/media/receipt-9.jpg
create mode 100644 docs/media/record_in_house_action.png
create mode 100644 docs/media/renew_action.png
create mode 100644 docs/media/renew_item.png
create mode 100644 docs/media/renew_item_calendar.png
create mode 100644 docs/media/renew_specific_date.png
create mode 100644 docs/media/retrieve_patron.png
create mode 100644 docs/media/scv-crec.jpg
create mode 100644 docs/media/scv-distr.jpg
create mode 100644 docs/media/scv-iss.jpg
create mode 100644 docs/media/scv-rec.jpg
create mode 100644 docs/media/scv-srec.jpg
create mode 100644 docs/media/scv-sub.jpg
create mode 100644 docs/media/server-3.png
create mode 100644 docs/media/server-4.png
create mode 100644 docs/media/server-5.png
create mode 100644 docs/media/server-6.png
create mode 100644 docs/media/shared-template-6.png
create mode 100644 docs/media/shared-template-7.png
create mode 100644 docs/media/shared-template-9.png
create mode 100644 docs/media/small_logo_white.jpg
create mode 100644 docs/media/specify_due_date1.png
create mode 100644 docs/media/specify_due_date2.png
create mode 100644 docs/media/staffclient-1.png
create mode 100644 docs/media/staffclient-2.png
create mode 100644 docs/media/staffclient-3.png
create mode 100644 docs/media/staffclient-4.png
create mode 100644 docs/media/staffclient-5.png
create mode 100644 docs/media/staffclient-6.png
create mode 100644 docs/media/staffclient-6a.png
create mode 100644 docs/media/staffclient-6b.png
create mode 100644 docs/media/staffclient-6c.png
create mode 100644 docs/media/staffclient-6d.png
create mode 100644 docs/media/staffclient-7.png
create mode 100644 docs/media/staffclient-7a.png
create mode 100644 docs/media/staffclient-8.png
create mode 100644 docs/media/staffclient-9.png
create mode 100644 docs/media/staffclientinstallation-proxy-putty-1.png
create mode 100644 docs/media/staffclientinstallation-proxy-socks-1.png
create mode 100644 docs/media/staffclientinstallation-proxy-socks-2.png
create mode 100644 docs/media/staffclientinstallation-staffclient-1.png
create mode 100644 docs/media/staffclientinstallation-staffclient-2.png
create mode 100644 docs/media/staffclientinstallation-staffclient-3.png
create mode 100644 docs/media/staffclientinstallation-staffclient-4.png
create mode 100644 docs/media/staffclientinstallation-staffclient-workstationnames-1.png
create mode 100644 docs/media/staffclientinstallation-staffclient-workstationnames-2.png
create mode 100644 docs/media/staffclientinstallation-staffclient-workstationnames-3.png
create mode 100644 docs/media/staffclientinstallation-tabbed-1.png
create mode 100644 docs/media/survey-1.png
create mode 100644 docs/media/survey-10.png
create mode 100644 docs/media/survey-2.png
create mode 100644 docs/media/survey-3.png
create mode 100644 docs/media/survey-4.png
create mode 100644 docs/media/survey-5.png
create mode 100644 docs/media/survey-6.png
create mode 100644 docs/media/survey-7.png
create mode 100644 docs/media/survey-8.png
create mode 100644 docs/media/survey-9.png
create mode 100644 docs/media/tip.png
create mode 100644 docs/media/transit-1.png
create mode 100644 docs/media/transit-10.png
create mode 100644 docs/media/transit-2.png
create mode 100644 docs/media/transit-3.png
create mode 100644 docs/media/transit-4a.png
create mode 100644 docs/media/transit-5.png
create mode 100644 docs/media/transit-6.png
create mode 100644 docs/media/transit-7.png
create mode 100644 docs/media/transit-8.png
create mode 100644 docs/media/transit-9.png
create mode 100644 docs/media/unified_volume_copy_creator1.jpg
create mode 100644 docs/media/unified_volume_copy_creator2.jpg
create mode 100644 docs/media/unified_volume_copy_creator3.jpg
create mode 100644 docs/media/unified_volume_copy_creator4.jpg
create mode 100644 docs/media/unified_volume_copy_creator5.jpg
create mode 100644 docs/media/unified_volume_copy_creator6.jpg
create mode 100644 docs/media/view-output-1.png
create mode 100644 docs/media/view-output-2.png
create mode 100644 docs/media/view-output-3.png
create mode 100644 docs/media/view-output-4.png
create mode 100644 docs/media/view-output-5.png
create mode 100644 docs/media/warning.png
create mode 100644 docs/opac/my_lists.txt
copy Open-ILS/src/python/oils/__init__.py => docs/reports/README (100%)
create mode 100644 docs/root.txt
create mode 100644 docs/serials/A-intro.txt
create mode 100644 docs/serials/B-copy_template.txt
create mode 100644 docs/serials/C-subscription-SCV.txt
create mode 100644 docs/serials/D-subscription-ASCV.txt
create mode 100644 docs/serials/E-edit_subscriptions.txt
create mode 100644 docs/serials/F-Receiving.txt
create mode 100644 docs/serials/G-Special_issue.txt
create mode 100644 docs/serials/Group_Serials_Issues_in_the_OPAC_2.2.txt
create mode 100644 docs/serials/H-holdings_statements.txt
create mode 100644 media/pdf_icon.png
hooks/post-receive
--
Evergreen ILS
More information about the open-ils-commits
mailing list