Re: [Koha-devel] Convincing City IT Dept.
I really think what Ed is asking is how can he get his management to pay for Migration and support for this "Free" Opensource software I have no doubt they are willing to use Koha, but IT people see it as a database is a database just "upload your data"... The key here is - ok when I have a patron who checks out a book and it says it is the wrong book who do I call... Or - if you are using any SIP items - How do I get the system up an running and talking... How many hours did it take you with the existing system to get it up and running and tell them an IT person will have to work on setting this up. Do they have a programmer up to speed already with Perl to fix things that break? You might also mention that there is this circulation data that has to move as well and there isn't a standard for moving that so how do you propose getting that data out and into Koha? LibLime will do that for you... Not to mention the status' on all your items. Unless you are going cold turkey and loosing all your history on your old system. You want to setup the system the most efficiently right, but you don't have the time so Migration costs are legit... to pay LibLime. Those are my 2 cents. David Schuster Michael Hafen-3 wrote: > > I would start by pointing them at the MARC standard: > http://www.loc.gov/marc/ , and tell them to start there. If that > doesn't dissuade them then look up the z39.50 protocol, and tell them > that that is the next step. Then point them at IndexData's Zebra > engine, and that's the next step. > > Then tell them "or we can use Koha which has already done all this work > for you". > > Good luck. > > On Tue, 2008-08-05 at 09:31 -0500, Ed Veal wrote: >> I have an interesting situation here. We had LibLime come and give us >> a presentation last week and I thought it would be best to invite the >> city IT staff to take a look so that they could be onboard with any >> decision that we make. However, what has happened is that they seem >> to think that they have the expertise to do this on their own. I >> shudder at the thought. They have already set up a server and are >> wanting my advice and guidance in migrating data. My advice is to >> contract it out, we don't have the resources or the expertise to >> accomplish this. >> >> So my question is how do I convince the IT department of this? I can't >> seem to get it through to them that this is not just any old SQL >> database. >> >> >> >> Edward Veal ([EMAIL PROTECTED]) >> System Administrator >> Lubbock Public Library >> http://www.lubbocklibrary.com >> Mahon Library >> 1306 9th St. >> Lubbock, TX 79401 >> voice: 806-775-2849 >> fax: 806-775-2827 >> *** >> ___ >> Koha-devel mailing list >> Koha-devel@lists.koha.org >> http://lists.koha.org/mailman/listinfo/koha-devel > > ___ > Koha-devel mailing list > Koha-devel@lists.koha.org > http://lists.koha.org/mailman/listinfo/koha-devel > > -- View this message in context: http://www.nabble.com/Convincing-City-IT-Dept.-tp18834177p18870532.html Sent from the Koha - Dev mailing list archive at Nabble.com. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] RFC 3.2 : guided reports improved
I love this idea! I've also wondered about the possibility of the system admin creating some "canned" type reports that everyone would see and could "modify with location etc..." then "save them" in their saved reports to run again in the future. For some people even the guided reports they are lost on. I was looking for a way to "push" some templated type reports out to people. Paul POULAIN-2 wrote: > > (http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_guided_reports) > > Guided reports are great. However, they are fully hardcoded SQL atm. > There's no possibilities to have parameters that are fixed at run time. > That would be usefull, for example, when you want to build a report that > runs between a date range, or on a given branch or itemtype. > > for example, a tool to let a given branch see what they added in the > catalogue could be : > SELECT biblio,author FROM biblio LEFT JOIN items USING(biblionumber) > WHERE items.homebranch=XXX > > This RFC suggest to add some improvements to be able to specify XXX at > runtime. > > - A simple solution could be to have a specific syntax to say "enter > value here". For example : ??? > - A better sotution could be to have the syntax + a label to display to > the patron. For example : ???Enter branch code??? that would display > "Enter branch code : ___" in the > - The best solution would be to have a list where applicable (branch, > itemtype...). > > The 2 first are easy to code, the 3rd could be tricky. > > but undoubtfully usefull ! > > -- > Paul POULAIN > http://www.biblibre.com > Expert en Logiciels Libres pour l'info-doc > NOUVEAU TELEPHONE : 04 91 81 35 08 > ___ > Koha-devel mailing list > Koha-devel@lists.koha.org > http://lists.koha.org/mailman/listinfo/koha-devel > > -- View this message in context: http://www.nabble.com/RFC-3.2-%3A-guided-reports-improved-tp18832709p18872423.html Sent from the Koha - Dev mailing list archive at Nabble.com. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
[Koha-devel] Where is the information about what username created/modified a "biblio" record saved?
Hi list, I'm using the last "snapshot" development version of Koha 3 from git, but I think my question is also applicable to older Koha 3 "versions" (and probably also to Koha 2.X versions). I'm using UNIMARC (but NOT using Zebra) in my Linux installation (running openSUSE 11.0). Basically, the question is the one that I put in the subject of this message, that is: "Where is the information about what username created/modified a biblio record saved?" When I say this, I'm thinking of a Library that uses Koha, and where several Librarians have a Koha username and password for logging in the "Intranet" area for adding / modifying bibliographic records in the Library's Catalog. So, what I'm asking is this: 1 - Does the Koha (MySQL) database include any table(s)/field(s) for the username that created/modified a bibliographic record? I couldn't find it in the most "obvious suspect", the "biblio" table. I *did* find a "datecreated" and a "timestamp" fields in this "biblio" table, though. 2 - Do the UNIMARC / MARC 21 standards include any tag / subfield where this information should / may be saved in a bibliographic record? I have consulted the "Log Viewer" that is available in the "Tools" page of the "Intranet" area of Koha, but could NOT find any entry for creation / modification of bibliographic records: http://192.168.0.2:8080/cgi-bin/koha/tools/viewlog.pl Am I looking for this in the wrong places? If this functionality has NOT been implemented yet, are there any reasons for NOT doing it (e.g: any legal restrictions related to privacy concerns)? Thanks in advance! Best wishes, Ricardo Dias Marques lists AT ricmarques DOT net ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Where is the information about what username created/modified a "biblio" record saved?
* Ricardo Dias Marques ([EMAIL PROTECTED]) wrote: > Hi list, > > > I have consulted the "Log Viewer" that is available in the "Tools" > page of the "Intranet" area of Koha, but could NOT find any entry for > creation / modification of bibliographic records: > > http://192.168.0.2:8080/cgi-bin/koha/tools/viewlog.pl > > > Am I looking for this in the wrong places? No, but you may not have switched the logging on at http://librarian.koha.workbuffer.org/cgi-bin/koha/admin/systempreferences.pl?tab=Logs I have the logs turned on, and I can see things like this in the logviewer 2008-07-15 12:00:03 1 CATALOGUING ADD biblio 9 biblio (where 1 is a link to the librarian who did it, and 9 is a link to the biblio) There are also entries for modifys, but its too big to paste nicely :) Chris ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] RFC 3.2 : guided reports improved
On Thu, Aug 7, 2008 at 10:58 AM, David Schuster <[EMAIL PROTECTED]> wrote: > > I love this idea! I've also wondered about the possibility of the system > admin creating some "canned" type reports that everyone would see and could > "modify with location etc..." then "save them" in their saved reports to run > again in the future. > > For some people even the guided reports they are lost on. I was looking for > a way to "push" some templated type reports out to people. It'd be cool if we could push reports upstream to the community as part of the http://contribs.koha.org site, with a new feature to allow you to find and add reports to your Koha system that others had created and pushed up ... Josh > > > Paul POULAIN-2 wrote: >> >> (http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_guided_reports) >> >> Guided reports are great. However, they are fully hardcoded SQL atm. >> There's no possibilities to have parameters that are fixed at run time. >> That would be usefull, for example, when you want to build a report that >> runs between a date range, or on a given branch or itemtype. >> >> for example, a tool to let a given branch see what they added in the >> catalogue could be : >> SELECT biblio,author FROM biblio LEFT JOIN items USING(biblionumber) >> WHERE items.homebranch=XXX >> >> This RFC suggest to add some improvements to be able to specify XXX at >> runtime. >> >> - A simple solution could be to have a specific syntax to say "enter >> value here". For example : ??? >> - A better sotution could be to have the syntax + a label to display to >> the patron. For example : ???Enter branch code??? that would display >> "Enter branch code : ___" in the >> - The best solution would be to have a list where applicable (branch, >> itemtype...). >> >> The 2 first are easy to code, the 3rd could be tricky. >> >> but undoubtfully usefull ! >> >> -- >> Paul POULAIN >> http://www.biblibre.com >> Expert en Logiciels Libres pour l'info-doc >> NOUVEAU TELEPHONE : 04 91 81 35 08 >> ___ >> Koha-devel mailing list >> Koha-devel@lists.koha.org >> http://lists.koha.org/mailman/listinfo/koha-devel >> >> > > -- > View this message in context: > http://www.nabble.com/RFC-3.2-%3A-guided-reports-improved-tp18832709p18872423.html > Sent from the Koha - Dev mailing list archive at Nabble.com. > > ___ > Koha-devel mailing list > Koha-devel@lists.koha.org > http://lists.koha.org/mailman/listinfo/koha-devel > -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE CEO migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS [EMAIL PROTECTED] |Full Demos at http://liblime.com/koha |1(888)KohaILS ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
