Transition to in-database Z39.50 sources - rip out of opensrf.xml.example

[Dan Scott]

For a long time now (2.0, at least), Z39.50 sources configured in config.z3950_* have offered more options and flexibility than the ones defined in opensrf.xml.example. For example, changes to database configs will be picked at each workstations the next time somone logs into their staff client - no restart of services needed.

Ergo, pull the sample definitions out of opensrf.xml.example, point to the Release Notes for a description of how the old entries map to the database tables, and call it a day. Unless someone wants to also rip out the opensrf.xml-parsing code and replace it with warnings, or write a script that will automatically migrate opensrf.xml entries into the database. But this seems to be a good first step.

See working/user/dbs/byebyez3950

[Ben Shum (bshum)]

Ripped out the z39.50 parts in our opensrf.xml on our test server running master. And nothing bad seems to have happened so far.

Tested converting the release_notes file into HTML using ASCIIDOC. Reads reasonably well.

Signed-off: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/bshum/byebyez3950

[Dan Scott (denials)]

Many thanks Ben! I pushed your branch to master.