[Clipart] Deleting infringing clipart
chovynz at gmail.com
Tue Jul 13 14:06:45 PDT 2010
I'm aware that you think we don't need a delete function for Librarians
- due to "dangerous" permission levels for a Librarian to abuse those
abilities. While that might be valid reasoning that if someone loses
their Librarian password or their account gets hacked or whatever (there
are a few more reasons that Bassel and I have talked about, I'm just
moving quickly to my points...), I think we do need the delete function
for the betterment of OCAL.
I've been just watching quietly how Librarians work, and how users
upload things, and I really can't see any reason why copyright or
trademark infringing clipart needs to remain in the Library.
Here are the issues that come up at the moment with no Delete function,
and will be fixed, once clipart is actually deleted.
1. As a Librarian, it can be confusing to see a "hidden" clipart, if
given the direct link, when you are not logged in. Confusion isn't
good for librarians or admins, OR users since it complicates the
process of downloading. Jon knows about this confusion, since he
had it when I sent him a "hidden" clipart link. I've had it first
hand after Tom sent the mailing list a few hidden links. I'm sure
others have had the confusion from my emails too.
2. As an anonymous user, you would not know if the clipart was hidden
or not, unless someone explained it to you. There is currently no
visual indicator to say if a clipart is hidden.
3. "Hidden" clipart might not come up in the search or gallery, but
knowing human nature, if we have a direct link available, (and
anyone is able to read the mailing list archives) then anyone
(including anonymous users) can still download that infringing
Actual removal of the clipart (or a higher level of Hiding) will stop
further infringement via OCAL, and it will remove confusion for all
users. Those are two good things in my books. At the very least, only
the uploader and Librarians should be able to access any "hidden"
clipart, even via direct link.
As for thoughts on how to address these, If you really don't want to
give Librarians the delete function, then perhaps I can suggest that one
person be given that ability? that person will need to be contactable,
and do their job of deletion within a reasonable timeframe and with good
researching skills to see if that clipart really does need deleting. Or
an automatic Database Job that once every two months, clipart with a
certain system tag, gets deleted from the Library? Perhaps "Deletion" or
something, applied and removable by Librarians only. These are just
ideas on how to address the problems identified above. (If you are on
the mailing list and reading this, and have ideas on this, please let us
On the other hand, I also think that Librarians need to be trusted to do
their job (custodianship of the Library) and needs the tools to able to
do their jobs. Clipart deletion, or permenant record removal from the
Library, is one of those jobs. It's a high trust job, but a necessary
one. Is there a way to facilitate the needs of the Librarian, with the
security of logins/powerful tools? I don't really like the idea of one
particular job resting with one person. I prefer transferably-skilled
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the clipart