Week 12: Kaltura, ArchivesSpace, and Google Studio.

Three items of systems related success this week:

1. Kaltura issues: so we are using up all the disk space on the server. I decided to try and just delete files to get enough room so if I have to remove content it is updated in the database properly.
   
   As I would expect it, I remove and make space one day with no luck, then the next day I move one of the videos over to WU's hosted server, and prep a page for it on my development server. I remember that there are some interviews also on our pages that I might have to bring over, and sure enough, the interview loads fine as well as well as the admin pages now. So well keep this as is until next week when we meet with Casey regarding disk space.
2. ArchivesSpace issues: so everyone once in a while I think the archivesspace software loses its connection to the MySQL database. I think with a lot of the content, it just relies on the SOLR indexes, but on the main repositories query when clicking on "Collections" and if you tried to do a search in a specific collection both functions failed with an error unable to connect to the database. A reboot of the software fixed the problem and restored the collections listing and search.
3. Google Studio: so last week I got to attend a great conference, it was the NWACC 2018 Instruction Technology Roundtable, NWACC is the Northwest Academic Computing Consortium. One of the best sessions was a breakout session on technology tools, and one of the top picks besides Adobe Spark that I picked up was Google Studio. I have started working on a number of different reports now, with different data sources, and it looks like might even be able to sync some of the data up with our Google Analytics, but well save that for another blog post. Here is a link to libguides usage at Willamette, with a data source being a Google Doc spreadsheet.

Week 10 - Fall 2018 (cron jobs, analytics, and archivesspace OAI)

Three items of systems related success this week:

1. Cron jobs are now running to backup the archivesspace database, using cron and the .my.cnf file this is now working reasonably well with a backup every morning at 6:30 a.m. we are going to keep just the last two created
   
2. The second thing I worked on was getting the new Finding Aids from ArchivesSpace piped into our Primo instance. So I had to delete the all of the old WUARCHIVES scope, and then harvest the new finding aids from the OAI (port 8082) of our server which for some unknown reason to me was not open. Then once WITS opened permanently for me, since I could open temporarily by editing the IP tables, I had to set up a proxy for it since ExLibris from off-campus had to do the harvesting. Which also had me create a new normalization rule similar to the CONTENTdm one with some minor modifications.
   
3. Finished off this week with some alma analytics trying to clean up some old messy records on our system and also demo something for the upcoming systems call for analytics.