Oh, you mean a "property-of" sticker. I was talking about the stickers that Sai proposed, i.e. stickers that communicate intent of the donor. If the books were catalogued and inventoried, then this 'intent' information could just as easily be provided within the system.<br>
<br>A property-of sticker is fairly orthogonal, and probably a good idea anyway.<br><br>- Brian<br><br><div class="gmail_quote">On Tue, Feb 9, 2010 at 2:58 PM, Rachel McConnell <span dir="ltr"><<a href="mailto:rachel@xtreme.com">rachel@xtreme.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">A sticker or stamp serves a different purpose than a checkout system.<br>
There is no reason I can think of not to have a stamp like:<br>
<br>
Ex Libris Noisebridge<br>
If found, please return to<br>
2169 Mission, 3rd floor<br>
San Francisco, CA, USA<br>
<br>
also with the logo & URL of course. A checkout/reminder system is<br>
separate and I personally have no opinion on that.<br>
<br>
Will anyone actually object if I order a stamp as I have described above?<br>
<br>
Rachel<br>
<div class="im"><br>
<br>
Brian Molnar wrote:<br>
> Definitely in favor of the electronic approach. Stickers/stamps are<br>
> nice, but the computerized approach certainly has more hack value to it.<br>
> Plus, if the entire book inventory is kept in a DB then we could even<br>
> make that data available on the website/wiki, in case people would like<br>
> search for a particular book.<br>
><br>
> - Brian<br>
><br>
> On Tue, Feb 9, 2010 at 2:32 PM, Martin Bogomolni <<a href="mailto:martinbogo@gmail.com">martinbogo@gmail.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:martinbogo@gmail.com">martinbogo@gmail.com</a>>> wrote:<br>
><br>
> I know it might sound a bit silly but ...<br>
><br>
> All books have a UPC barcode on them. Barcode scanners like the<br>
> cueCat are still pretty plentiful and not ridiculously difficult to<br>
> code for. Perhaps a little checkout computer? Scan all the books<br>
> into it, and when someone wants to check a book out -- they scan it<br>
> and leave an email address (nicely anonymous) and they can get a<br>
> reminder when the book needs to be returned (say 14 days?)<br>
><br>
> Nothing rocket science-y. Python + sqllite/berkeleyDB + cueCat + a<br>
> couple weekends of work. I certainly can give coding up something a<br>
> go, since I need something similar for the Austin Hacker Space.<br>
><br>
> -Martin<br>
><br>
> On Tue, Feb 9, 2010 at 4:27 PM, Sai Emrys <<a href="mailto:noisebridge@saizai.com">noisebridge@saizai.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:noisebridge@saizai.com">noisebridge@saizai.com</a>>> wrote:<br>
> > On Tue, Feb 9, 2010 at 1:49 PM, Albert Sweigart<br>
</div><div><div></div><div class="h5">> <<a href="mailto:asweigart@gmail.com">asweigart@gmail.com</a> <mailto:<a href="mailto:asweigart@gmail.com">asweigart@gmail.com</a>>> wrote:<br>
> >><br>
> >> I think a stamp might be a bit easier to manage than stickers,<br>
> just as<br>
> >> an idea. I worry about stickers falling off and leaving sticky goop<br>
> >> behind.<br>
> ><br>
> > The benefit I saw from having it be a sticker is the visibility.<br>
> Stamps I<br>
> > think are less visually obvious, and for this it's important for<br>
> it to be<br>
> > instantly recognizable. But maybe I just don't know stamps well<br>
> enough?<br>
> ><br>
> > They also have the benefit (if they have good adhesive) of being<br>
> likely to<br>
> > adhere to more things than ink does.<br>
> ><br>
> > I looked at prices; 1.5" stickers are ~17-25˘ per (depending on<br>
> volume); 1"<br>
> > are ~10˘ (ditto). Dunno how much stamps would be.<br>
> ><br>
> > My aesthetic ideal would be that it looks something like the CC<br>
> symbols[0],<br>
> > but with text. I.e., 2-3 small stickers that clearly show what to<br>
> do with<br>
> > the thing.<br>
> ><br>
> > Stickers are messier though, it's true. And stamps probably would<br>
> be cheaper<br>
> > over time.<br>
> ><br>
> > - Sai<br>
> ><br>
> > [0] <a href="http://creativecommons.org/about/licenses/" target="_blank">http://creativecommons.org/about/licenses/</a><br>
> > _______________________________________________<br>
> > Noisebridge-discuss mailing list<br>
> > <a href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a><br>
</div></div>> <mailto:<a href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a>><br>
<div class="im">> > <a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
> ><br>
> ><br>
> _______________________________________________<br>
> Noisebridge-discuss mailing list<br>
> <a href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a><br>
</div>> <mailto:<a href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a>><br>
<div><div></div><div class="h5">> <a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
><br>
><br>
><br>
> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> Noisebridge-discuss mailing list<br>
> <a href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a><br>
> <a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
</div></div></blockquote></div><br>