Some users reporting that saved settings are occasionally lost.

[mgobat]

From ALMA-L:

We are testing SpineOMatic and setting it up ready for when we return to normal. Unfortunately having a slight problem as it seems it is not loading the previous settings. Seems like it forgets them if the program is not used for a few days/week. Pressing load doesn't seem to make a difference, even though the settings file is saved. Obviously we would like to solve this issue before using it in earnest!

Any help appreciated

============================================

This is an one aspect of SpineOMatic that takes special attention. SpineOMatic is otherwise a great program. And keep in mind , it was developed by BC as they went live back when Alma was getting started.

When you exit SpineOMatic if you “save settings”, it unfortunately saves the current XML that’s in the XML tab, which is the XML for the last scanner item. This overwrites the settings. Our solution is to ask student workers not to save when they exit , and also to save an original version of SpineOMatic with our correct settings on Box, and overwrite the local version if this happens.

Other libraries May have a better approach if
they know SpineOMatic better than we do

============================================

We have noticed this happening from time to time. There doesn't seem to be any pattern of cause and effect. I simply say to all users to keep a separate backup copy of the settings.som file in another directory, and when you notice SpineOmatic starting up without the correct parameters, just copy the backup version over the ‘vanilla’ version which will be in the SpineOmatic directory.
Obviously when you make any changes that you want to retain, such as margin adjustments etc. you need to make a new version of the backup copy.

It’s also a good policy to ‘save settings’ immediately after you make any adjustments, and NEVER save when you shut the program down, as those changes would be accidental and unwanted.

===========================================

We haven't experienced this problem, or at least didn't before March 13. This might be one of those fun and exciting Windows permission issues where users don't have full read/write access. You may want to check the file properties security settings.

[mgobat]

Replicated....once. Cannot make it happen consistently.

[mgobat]

Well, I thought I replicated this problem once....but since I can't get it to happen again, maybe I'm wrong. I've traced through the code for quite a bit, and don't see how this is happening. Does anyone have any reliable steps to replicate the problem? Thanks.

[cmc-tech]

I can't offer the steps to replicate the issue, but I was told by the librarian that uses Spine-O-Matic that she just started the application the other day and the settings were gone! I doubt she did anything other than her normal method, but the settings had to be recreated, and now we have another issue related to a 400 error message that I posted on that thread, too. If somebody can shed some light on this problem, it would be greatly appreciated!

P.S. This software is usually only used once or twice in a week, usually on a Wednesday. Hope that helps!