 |
 |
The first pre-release of Traject 3.0 has been released. This is expected to be a very easy upgrade from Traject 2.0, but feedback to that is very welcome. This is labelled alpha because both additional features and incompatible changes are still possible before a final 3.0 release. But if I get no such relevant feedback — or no feedback at all! — this could become the final release. The traject 3.0 release is focused mainly on: 1) Abstracting architecture to support non-MARC uses better, at this point with XML support built in. 2) Providing more convenient API and documentation for programmatic use (not via `traject` command line). The traject repo master branch is now 3.0.0 work. You may want to look at: CHANGES: https://github.com/traject/traject/blob/master/CHANGES.md New guide doc on XML use: https://github.com/traject/traject/blob/master/doc/xml.md New guide doc on programmatic use: https://github.com/traject/traject/blob/master/doc/programmatic_use.md Updated README: https://github.com/traject/traject/blob/master/README.md Feedback of any sort is VERY WELCOME. Even just “I tried it out it’s good”. It’s been challenging for me to get traject feedback. Please feel free to use: Traject GH Issues, https://github.com/traject/traject/issues. The #traject channel on Code4Lib slack, https://code4lib.org/irc/ . Or if neither of these work for you, email to me directly. (The Code4Lib listserv also works for me if it doesn’t annoy anyone else).