Re: [CODE4LIB] python 2 versus python 3

2018-03-07 Thread Bryan Brown
Hi Eric, Unless you are specifically working on a legacy project written in Python 2 that is to large to update, I would strongly recommend working with 3 as its the future. Staying with 2 means you won't have access to cool new features in 3. I ran into issues when I started working in Pyth

Re: [CODE4LIB] Lightweight IR infrastructure

2017-10-25 Thread Bryan Brown
Josh, Theres nothing wrong with what you are describing if its all your institution needs, but I would be careful about promoting that as an IR. An IR is much more than a bunch of documents. The metadata modelling, preservation features and indexing that you want to leave out are what makes it