Eric,<div><br></div><div><br></div><div>That seems like a good way to deal with not wiping out someone's active data, while still keeping the database clean. I'll look into it.</div><div><br></div><div>Thanks!</div>
<div><br></div><div><br></div><div>-Ian<br><br><div class="gmail_quote">On Wed, Mar 24, 2010 at 1:19 PM, Eric Bégin <span dir="ltr"><<a href="mailto:Eric.Begin@inlibro.com">Eric.Begin@inlibro.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#333333">
Thank you Ian for letting us know.<br>
<br>
My suggestion would be to reset the database every hour only if there
was no active sessions in the last <timeout syspref value>
seconds.<br>
<br>
How that sounds?<br>
<br>
Eric<br>
<br>
Josh Westbrook wrote:
<blockquote type="cite"><div><div></div><div class="h5">I think if you listed at what time the database resets,
that would be fine. Something like, the database resets at the top of
every hour, or on every even hour, etc. Awhile back I took a look at
the Bywater demos and there was something questionable in the news
section then too. I can't remember what it was exactly - but it
obviously shouldn't have been there.<br>
<br clear="all">
Josh Westbrook<br>
Prescott Library Mngr/District Technology Mngr<br>
Walla Walla County Rural Library District<br>
<a href="mailto:joshw@wwrurallibrary.com" target="_blank">joshw@wwrurallibrary.com</a><br>
<a href="http://www.wwrurallibrary.com" target="_blank">http://www.wwrurallibrary.com</a><br>
<br>
<br>
<div class="gmail_quote">2010/3/24 Ian Walls <span dir="ltr"><<a href="mailto:ian.walls@bywatersolutions.com" target="_blank">ian.walls@bywatersolutions.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">Everyone,
<div><br>
</div>
<div><br>
</div>
<div>As many of you know, the Koha demos currently linked to <a href="http://koha-community.org" target="_blank">koha-community.org</a>
are hosted by ByWater Solutions. This morning we noticed some
offensive vandalism on the main staff page. It has been removed, but
it's gotten us thinking about how we can secure the demos better
against such things in the future. </div>
<div><br>
</div>
<div>Current thinking is that we should set the database up to
refresh from a clean copy every hour. This would limit exposure to
offensive damage to a brief window, but would also mean that anyone
taking a tour and adding test records may lose them midway through
their explorations. A brief note to this effect should be put both
outside and inside the demo, but it would still prove annoying.</div>
<div><br>
</div>
<div>Rather than acting unilaterally upon a community resource, we
thought it would be best to get the community's opinions on how best to
handle this. Is an hour too narrow a window? Should we only refresh
certain tables (like systempreferences) and leave others (like biblios
or borrowers)? Are there other methods we should consider?</div>
<div><br>
</div>
<div>My goal is to get this taken care of by the end of the day.
If good ideas come in after that, though, I am of course willing to
change course.</div>
<div><br>
</div>
<div>Cheers,</div>
<div><br>
</div>
<font color="#888888">
<div><br>
</div>
<div>-Ian Walls</div>
<div>Lead Developer</div>
<div>ByWater Solutions</div>
</font><br>
_______________________________________________<br>
Koha mailing list<br>
<a href="mailto:Koha@lists.katipo.co.nz" target="_blank">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
<br>
</blockquote>
</div>
<br>
</div></div><pre><hr size="4" width="90%"><div class="im">
_______________________________________________
Koha mailing list
<a href="mailto:Koha@lists.katipo.co.nz" target="_blank">Koha@lists.katipo.co.nz</a>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a>
</div></pre>
</blockquote>
</div>
</blockquote></div><br></div>