Thanks, Jojo. I will reach out with more details by email!

Meant ‘I recommend getting…’

Hi Mark (and Stephen),

Jill mentioned you were discussing OJS and I thought I’d check in. To build a little bit on what Stephen said, my understanding from other JITP members is that the platform at the time was very difficult to manage given the size of JITP’s editorial collective and the turnover of issue editors. The managing editor at the…[Read more]

I recommend that getting a small group of users together to simulate the submission workflow process with an admin, author (submitter), editors, reviewers etc. otherwise it’ll be difficult to actually see if it works.

Installing a test instance is a good idea! We are not prepared to self-host a production version at Kingsborough, so we would be looking at the hosted option instead. But we are totally prepared to install a test so that we can kick the tires. It would also be a super interesting way to get more perspective on what is happening under the hood.…[Read more]

Hi Mark!

To learn the feasibility of using the new release of OJS, I installed it on my workstation using XAMPP when GC IT stopped supporting it ~2018. It was a fairly simple process, but the then new release was definitely not ready for prime time.

Best,
Stephen

Stephen Klein
Digital Services Librarian
CUNY Graduate Center

Thank you both! This is helpful! We are OJS-curious at the Kingsborough library, so we are doing our research 🙂

My memory is also fuzzy, but perhaps between my and Stephen’s fuzzy memories, the fuller picture can come into view. If I recall correctly, the initial request was from one of the journals to IT, without the library in the mix (i.e., it wasn’t a library-run journal publishing service), and it was handled by one specific IT employee who was also a…[Read more]

My pleasure Mark. There were about ~8 journals being hosted and I learned that JITP  was the most active user of OJS in my dual roles working on the JITP collective and attempting to perform archive and preserve as a GC librarian, so there was no compelling reason attempting to retain the platform, especially since IT was no longer about to…[Read more]

Interesting! Thank you Stephen! So the impression I’m getting is that GC was self-hosting and that this became unworkable for a variety of (mostly technical) reasons. That makes sense.

All the best,

Mark

My memory is a bit fuzzy, but if were to accurately recall there was an array of issues. A new release was not even on the horizon and the old version had severe limitations. I was part of JITP back then an in addition to using OJS, we had to use a few spreadsheets to support the submission to publishing process. Also, GC IT lost a sys admin who…[Read more]