Jennifer,
I had a vendor set up our notices, but I wanted to point you to a
little bit of extra documentation that is available. It is part of an
older EG documentation project called Evergreen in Action. There is
a section that covers action notices...
Hello everyone
I'm Vanya, from India. I'm a candidate for OPW Round9 internship with
evergreen.
While discussing the idea of Awesome Box integration with Evergreen, Kathy
and I discussed the possibility of making the Evergreen support for Awesome
Box more interpretive using Artificial
I can see some challenges to tracking genre and I'd be hesitant to put too
much value on it. There are ways to catalog it but in my experience
actually relying on it being in records (much less being consistent) is
very unreliable in organizations that do a lot of copy cataloging / don't
have
Hello Rogan
Thank you for your input. Now that you pointed it out, it seems to be a
valid point.
Maybe, as a solution to that, we can have a hierarchical algorithm for
categorizing. In other words, we can allow the administrator to decide
whether the categorization comes all the way down to
Agreed - it's a great idea in theory, but I'm not sure how well it would work
in actual practice. Even in a single library, genre subject headings are
usually pretty inconsistent in the MARC records because of copy cataloging, and
that usually gets even more inconsistent in a consortium of
I don't see an issue with doing analysis of circulation patterns on the
backend so long as nothing identifying is exposed.
For example, if all I saw as a patron was a tab in my opac that said you
thought The Yiddish Policeman's Union was Awesome! Some others do did also
thought this was Awesome
Hello Rogan
This is exactly what I had in mind. All the recommendation processing will
take place in background, and all the user will see is a recommendation and
not the information of any other patron. This way his experience with
Awesome Box will get enhanced.
And yes, we can maybe, start off
Hello Rogan
This is exactly what I had in mind. All the recommendation processing will
take place in background, and all the user will see is a recommendation and
not the information of any other patron. This way his experience with
Awesome Box will get enhanced.
And yes, we can maybe, start off
This relies on the circulation and rating data still being tied to the patron
in the system, though - yes, it'd be on the database side and not on public
view, but it's still creating a picture of a patron's reading history that has
privacy implications. Of course, this feature should be set
I suppose I don't understand the concern on your part as at that level if
someone could access the raw db they could just query someone's circulation
history, fine payments, etc... since those are recorded as transactions
unless you're doing something to anonymize or wipe those as soon as they're
Overall, I really like the ideas talked about but I agree with Terran that
something would have to be done with circ data related to patrons. We use
the purge function to anonymize our patron data but I could see other ways
of dealing with this. We also have retention policies related to
Hi all,
Great discussion so far!
We had a bit of a discussion about privacy concerns in IRC after Terran
sent her original message. One approach we were discussing was storing
the awesome tags in an anonymous fashion, except in cases where patrons
have opted into saving their circ history.
I'm concerned with project creep as well as I noted in one of early
missives. If this is stored independent of patron data (which actually I
think it should) then I think we should also track circs since the feature
was turned on so it could say 3 out of 4 people found it awesome.
Stepping back
13 matches
Mail list logo
