All good thoughts<br><br><div class="gmail_quote">On Wed, Mar 9, 2011 at 7:30 AM, Nathan Eady <span dir="ltr"><<a href="mailto:eady@galion.lib.oh.us">eady@galion.lib.oh.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">> On Sun, Mar 6, 2011 at 9:17 AM, <a href="mailto:jon@rejon.org">jon@rejon.org</a> <<a href="mailto:jon@rejon.org">jon@rejon.org</a>> wrote:<br>
><br>
>> btw, we should not be naive either...there are ppl who will try to<br>
>> submit bad stuff in order to create problems too....delete delete<br>
>> delete!<br>
<br>
</div><div class="im">chovynz <<a href="mailto:chovynz@gmail.com">chovynz@gmail.com</a>> writes:<br>
<br>
> There's no delete function yet. And Bassel is not convinced we<br>
> should delete records either.<br>
<br>
</div>Barring receipt of an actual DMCA take-down notice (or a serious<br>
disk-space shortage), I would not be in favor of irrevocable deletion<br>
as such. The mere existence of that kind of delete functionality in<br>
the web UI would pretty much guarantee accidental deletion of wanted<br>
materials, and there is also the potential for deliberate abuse. It's<br>
just not a good idea. If we have a special case where real deletion<br>
becomes really actually necessary, someone with a shell acount can do<br>
it by hand, but that may *never* be needed, and it certainly won't be<br>
needed on a day-to-day basis.<br></blockquote><div><br>We got a DMCA takedown a few days ago that I dealt with privately, off list. It was a legit notice. I've asked the user to delete the clipart from their clipart management page, since librarians don't have a way to delete it. I can name a number of cliparts that shouldn't be on the library collection at all.<br>
<br>I understand there is a potential for abuse. I'm just saying, in the course of my librarian duties, I've come across many clipart that violate copyright (and there is no way that MS will ever allow their logos into the public domain), that are not suitable for OCAL. Our hide function only stops it from being searched for and displayed in results, but anyone with a bit of intelligence can find the direct links.<br>
<br>To my mind that means we are still providing copyrighted material, which is not something I want OCAL to do.<br><br>If we did have a delete function, I think we also need to setup a deletion review process. Maybe something like, 4 librarians need to veto the deletion of clipart marked for delete or something? It would have to be hardcoded so that no one librarian can just delete something, but maybe something like 4 checkboxes (that each librarian only has access to one checkbox, but can see the others results?). Then of course, the system needs to record the actions and responses too, to be able to action something.<br>
<br>Or maybe, one person can have delete "powers" but only deletes clipart that have passed the deletion process (whatever that may be). Much like a judge in a democratic society. The judge doesn't actually determine guilt or innocence, they only action what the jury has determined.<br>
<br>Most clipart wouldn't even be touched by this, but I really do think we need a better system than what we currently have, which is a superficial "hiding". <br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
I am, however, very definitely in favor of marking them pd_issue and<br>
copyright or trademark or whatever and hiding them so they don't turn<br>
up in search results, if we have any reason to believe they are not<br>
legitimately in the public domain. I do this whenever I notice them.<br>
(I think I did this to several versions of the Debian logo a week or<br>
two ago.)<br>
<br>
That way, if we later discover we were mistaken about any image, or if<br>
we nixed the wrong one, or if the three-thousand-and-ninety-third<br>
person who uploads Tux turns out to actually be Larry Ewing and he's<br>
really intending to release it into the PD, or whatever... the tags<br>
and so forth can be easily undone, no harm no foul. The ability to<br>
undo is good.<br></blockquote><div> </div><div>Hehe, that made me chuckle. You really do know what it's like to be a librarian, lol. <br><br>These are good first steps, but what about the three-thousand-and-ninety-second images of Tux that are needlessly taking up space, and cluttering up the librarians back end? Until Larry does release Tux into the PD, those other Tux'es aren't supposed to be on the library at all. Do you want to sort through 3092+ hidden cliparts that just repeat the same things over and over? <br>
<br>Is there some way we can make the librarians job easier, when this site is even bigger? I'm one for lean processing. I don't like magpie syndrome.<br><br>Many of these education and copyright issues would be more easily fixed with a working email functionality. I need some of Bassels time. Or someone needs to make it.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Also, assuming the software tracks who does what, any deliberate abuse<br>
that should arise can be dealt with. (Everything they do can be<br>
straightforwardly reversed, and since only people who have been made<br>
librarians can do this stuff, a user whose account is suspended for<br>
such abuses cannot just easily create a fresh account and keep redoing<br>
it. They would have to convince someone to make their new account a<br>
librarian, _each_ time an account is suspended.)<br></blockquote><div>Yeah that's a problem. Bassel started on a tracker (for the admin panel) but I don't believe that it does nearly enough, or has near enough information to be able to undo things.<br>
<br>At the moment OCAL itself has no tracker. And have niether the time nor inclination to make one, so until someone makes one, we have nothing to see what people are doing. Not to mention we need email capability, since 6 months ago.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
And yeah, if there's a particular user and we have to keep repeatedly<br>
explaining what PD means to him and he never gets it and keeps<br>
uploading non-PD material, there are ways to deal with that too. If<br>
it becomes a sufficiently serious problem, newly created accounts<br>
could be marked automatically with some flag, and newly uploaded<br>
clipart by such authors could be automatically flagged as pending<br>
review until a librarian takes a look at it and takes off the flag;<br>
when a librarian notices that a given user has consistently uploaded<br>
original or genuinely-PD content, their "needs-review" flag could be<br>
taken off. If the user later _develops_ a discernment problem, the<br>
flag could be put back. Hopefully we won't need to go quite as far as<br>
all that, but even if we do, it should still be possible to handle it<br>
all without an irreversable-nuke button, IMO.<br></blockquote><div><br>Side-topic: I'd love to have all new clipart automatically marked as "unchecked" like before. But again, I don't know how to do so. If bassel or someone could walk me through I could do something.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<font color="#888888"><br>
--<br>
Nathan Eady<br>
Galion Public Library<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
clipart mailing list<br>
<a href="mailto:clipart@lists.freedesktop.org">clipart@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/clipart" target="_blank">http://lists.freedesktop.org/mailman/listinfo/clipart</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Cheers<br>Chovynz<br>