You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(5) |
Sep
(39) |
Oct
(18) |
Nov
(16) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(15) |
Feb
(90) |
Mar
(41) |
Apr
(129) |
May
(69) |
Jun
(112) |
Jul
(153) |
Aug
(82) |
Sep
(95) |
Oct
(111) |
Nov
(39) |
Dec
(50) |
| 2009 |
Jan
(11) |
Feb
(63) |
Mar
(51) |
Apr
(45) |
May
(68) |
Jun
(84) |
Jul
(114) |
Aug
(149) |
Sep
(259) |
Oct
(179) |
Nov
(132) |
Dec
(87) |
| 2010 |
Jan
(59) |
Feb
(88) |
Mar
(145) |
Apr
(130) |
May
(24) |
Jun
(36) |
Jul
(143) |
Aug
(94) |
Sep
(125) |
Oct
(142) |
Nov
(100) |
Dec
(103) |
| 2011 |
Jan
(76) |
Feb
(105) |
Mar
(145) |
Apr
(112) |
May
(74) |
Jun
(157) |
Jul
(95) |
Aug
(191) |
Sep
(75) |
Oct
(91) |
Nov
(100) |
Dec
(102) |
| 2012 |
Jan
(100) |
Feb
(126) |
Mar
(97) |
Apr
(74) |
May
(161) |
Jun
(135) |
Jul
(161) |
Aug
(132) |
Sep
(266) |
Oct
(212) |
Nov
(114) |
Dec
(87) |
| 2013 |
Jan
(101) |
Feb
(254) |
Mar
(236) |
Apr
(244) |
May
(144) |
Jun
(156) |
Jul
(203) |
Aug
(242) |
Sep
(118) |
Oct
(206) |
Nov
(140) |
Dec
(108) |
| 2014 |
Jan
(141) |
Feb
(88) |
Mar
(167) |
Apr
(61) |
May
(109) |
Jun
(105) |
Jul
(218) |
Aug
(125) |
Sep
(152) |
Oct
(217) |
Nov
(129) |
Dec
(63) |
| 2015 |
Jan
(121) |
Feb
(78) |
Mar
(156) |
Apr
(92) |
May
(91) |
Jun
(118) |
Jul
(114) |
Aug
(236) |
Sep
(75) |
Oct
(112) |
Nov
(106) |
Dec
(74) |
| 2016 |
Jan
(121) |
Feb
(165) |
Mar
(127) |
Apr
(145) |
May
(142) |
Jun
(113) |
Jul
(66) |
Aug
(61) |
Sep
(46) |
Oct
(120) |
Nov
(59) |
Dec
(49) |
| 2017 |
Jan
(67) |
Feb
(55) |
Mar
(79) |
Apr
(28) |
May
(49) |
Jun
(50) |
Jul
(119) |
Aug
(72) |
Sep
(40) |
Oct
(45) |
Nov
(66) |
Dec
(60) |
| 2018 |
Jan
(63) |
Feb
(52) |
Mar
(48) |
Apr
(52) |
May
(60) |
Jun
(41) |
Jul
(78) |
Aug
(63) |
Sep
(46) |
Oct
(48) |
Nov
(17) |
Dec
(21) |
| 2019 |
Jan
(74) |
Feb
(78) |
Mar
(46) |
Apr
(42) |
May
(49) |
Jun
(15) |
Jul
(50) |
Aug
(16) |
Sep
(49) |
Oct
(63) |
Nov
(14) |
Dec
(11) |
| 2020 |
Jan
(36) |
Feb
(31) |
Mar
(36) |
Apr
(9) |
May
(92) |
Jun
(42) |
Jul
(29) |
Aug
(29) |
Sep
(66) |
Oct
(13) |
Nov
(29) |
Dec
(14) |
| 2021 |
Jan
(8) |
Feb
(34) |
Mar
(30) |
Apr
(14) |
May
(17) |
Jun
(28) |
Jul
(23) |
Aug
(25) |
Sep
(28) |
Oct
(32) |
Nov
(50) |
Dec
(19) |
| 2022 |
Jan
(25) |
Feb
(54) |
Mar
(44) |
Apr
(19) |
May
(11) |
Jun
(9) |
Jul
(17) |
Aug
(27) |
Sep
(33) |
Oct
(24) |
Nov
(37) |
Dec
(17) |
| 2023 |
Jan
(15) |
Feb
(21) |
Mar
(40) |
Apr
(16) |
May
(20) |
Jun
(117) |
Jul
(59) |
Aug
(18) |
Sep
(28) |
Oct
(13) |
Nov
(54) |
Dec
(20) |
| 2024 |
Jan
(24) |
Feb
(39) |
Mar
(26) |
Apr
(26) |
May
(33) |
Jun
(39) |
Jul
(16) |
Aug
(31) |
Sep
(5) |
Oct
(9) |
Nov
(31) |
Dec
(2) |
| 2025 |
Jan
(19) |
Feb
(30) |
Mar
(28) |
Apr
(38) |
May
(28) |
Jun
(22) |
Jul
(17) |
Aug
(9) |
Sep
(23) |
Oct
(11) |
Nov
(13) |
Dec
(10) |
| 2026 |
Jan
(25) |
Feb
(27) |
Mar
(21) |
Apr
(5) |
May
(6) |
Jun
(6) |
Jul
(9) |
Aug
(4) |
Sep
(2) |
Oct
(6) |
Nov
(2) |
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
1
|
|
2
|
3
|
4
(2) |
5
|
6
(1) |
7
(2) |
8
(1) |
|
9
|
10
(1) |
11
|
12
|
13
|
14
|
15
|
|
16
|
17
|
18
|
19
|
20
(1) |
21
(3) |
22
(3) |
|
23
|
24
(6) |
25
(4) |
26
(1) |
27
(3) |
28
|
29
|
|
30
|
|
|
|
|
|
|
|
From: Demian K. <dem...@vi...> - 2017-04-27 17:10:01
|
Hello, everyone - The biggest new feature for VuFind 4.0, the channeled browse mode, has just been merged to master. You can find some overview documentation in the wiki here: https://vufind.org/wiki/configuration:channels I encourage everyone to try this out if you have not already; feedback is still welcome, and there is certainly time to make further improvements before release if necessary. - Demian |
|
From: Demian K. <dem...@vi...> - 2017-04-27 16:50:02
|
Hello, The most common solution to this problem is to subscribe to a web-scale discovery service like EDS, Primo Central or Summon. This provides an API that aggregates content from subscription databases, and VuFind includes support for the major providers. Obviously the disadvantage to this approach is that there is a subscription cost for the aggregation service – and this cost is often quite high. If that option is not available, there are a couple of possibilities: 1.) If you can obtain metadata for the database, you can index it into your local Solr index. This works well when it is possible, but most vendors are unwilling to share their data with individual institutions. 2.) If the database has an API, you can implement a connector in VuFind to allow direct access. This is unfortunately a significant amount of work, and aggregating content from multiple databases quickly becomes difficult and slow due to the amount of network traffic required. If you would be satisfied with searching one database at a time, or featuring one or two specific collections, this might still be viable. As you can see, there is no ideal solution – there are technical or cost trade-offs involved, and it is made more difficult by the lack of open data for most databases. However, I hope this information is helpful to you. Please let me know if you still have any questions. - Demian From: Abner Mizael Vasquez Estrada [mailto:amv...@za...] Sent: Thursday, April 27, 2017 11:05 AM To: vuf...@li... Subject: [VuFind-Tech] Vufind whit Database of pay Hello vufind- tech team, my name is Abner Vasquez, library systems analyst, recentlyinstall 3.1.2 Vufind works very well with the contents of the institution, OJS, Koha and Dspace. I want to go but it is integrating databases of pay, e-Libro, JSTORE, SPRINGERLINK, PROQUEST, AGORA, we are already paying the subscription. That metadata exactly would need them to be able to index them with Solr. It is possible to integrate these databases, that recommendations and sugenrenciascan give me. Thank you. |
|
From: Abner M. V. E. <amv...@za...> - 2017-04-27 15:26:52
|
Hello vufind- tech team, my name is Abner Vasquez, library systems analyst, recentlyinstall 3.1.2 Vufind works very well with the contents of the institution, OJS, Koha and Dspace?. I want to go but it is integrating databases of pay, e-Libro, JSTORE, SPRINGERLINK, PROQUEST, AGORA, we are already paying the subscription. That metadata exactly would need them to be able to index them with Solr. It is possible to integrate these databases, that recommendations and sugenrenciascan give me. Thank you. |
|
From: Demian K. <dem...@vi...> - 2017-04-26 15:00:26
|
Hello, everyone! Just a heads-up that I am planning to upgrade Solr in master on Monday by merging this pull request: https://github.com/vufind-org/vufind/pull/869 For now, I'm going to plan on using version 6.4.2 in VuFind 4.0; there is a 6.5.0 out now, but it sounds like there are some known issues there that are going to have to be fixed in 6.5.1. I would prefer to stick with a known stable version for the moment and continue moving forward in a future release. Please be prepared for this change of Solr version, and please test the PR between now and Monday if you have concerns about this causing problems for you. thanks, Demian |
|
From: Demian K. <dem...@vi...> - 2017-04-25 13:27:59
|
Here are the minutes from today's developers call: https://vufind.org/wiki/developers_call:minutes20170425 Of particular note is the announcement of July 10, 2017 as the release date for VuFind 4.0. The next call will be Tuesday, May 9, 2017 at 9am Eastern Daylight Time (13:00 GMT). - Demian |
|
From: george v. <gve...@gm...> - 2017-04-25 12:29:05
|
ok solved I didn’t enable “[OAI] section header” !! Thanks, George > On 25 Apr 2017, at 15:26, Demian Katz <dem...@vi...> wrote: > > George, > > That message generally means that you are missing the expected settings from the [OAI] section of config.ini: > > https://github.com/vufind-org/vufind/blob/master/config/vufind/config.ini#L1033 > > I'd check two things: > > 1.) Are you editing the correct version of the file? Make sure you modify $VUFIND_LOCAL_DIR/config/vufind/config.ini and not $VUFIND_HOME/config/vufind/config.ini -- in the majority of VuFind setups, the local copy is the one that gets used; the one in the home directory is just a template that gets copied during installation. > > 2.) Did you uncomment all of the relevant lines, including the [OAI] section header? > > If you're still having trouble after confirming those things, please feel free to share the relevant parts of your configuration file for analysis (and let us know exactly which version you are using). > > Thanks, good luck, and let me know if I can do more to help! > > - Demian > > -----Original Message----- > From: gveranis [mailto:gve...@gm...] > Sent: Tuesday, April 25, 2017 7:36 AM > To: vuf...@li... > Subject: [VuFind-Tech] OAI Server enable problem > > Hi All, > > I follow the instructions for enabling OAI Server in Vufind but still now I get "OAI Server Not Configured". > The steps that I follow was based on that page : > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fvufind.org%2Fwiki%2Findexing%3Atracking_record_changes&data=02%7C01%7Cdemian.katz%40villanova.edu%7Ccd009a1814894c83753908d48bd0eb7d%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636287176847857852&sdata=zjWDFh2xsXsFStrB3Ee9M58fMdrb2T6LhhIXODSpcAw%3D&reserved=0 > It something else that I can do for enabling? > > Thanks, > George > > > > -- > View this message in context: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvufind.2307425.n4.nabble.com%2FOAI-Server-enable-problem-tp4671305.html&data=02%7C01%7Cdemian.katz%40villanova.edu%7Ccd009a1814894c83753908d48bd0eb7d%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636287176847857852&sdata=ciQzJIvcoWuTRbHNHQoLKYc%2B%2BjaEEEHJXMpBjFxgYI4%3D&reserved=0 > Sent from the vufind-tech mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdot&data=02%7C01%7Cdemian.katz%40villanova.edu%7Ccd009a1814894c83753908d48bd0eb7d%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636287176847857852&sdata=AUIUYrS5xgK6IyyPANGAQ4yOZkyln3DhjF%2Bj3LKpg60%3D&reserved=0 > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fvufind-tech&data=02%7C01%7Cdemian.katz%40villanova.edu%7Ccd009a1814894c83753908d48bd0eb7d%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636287176847857852&sdata=SSfNet2yTO0YNbMw6%2FkxJyYq7ukW4l%2FcbbOd5y6hZ8w%3D&reserved=0 |
|
From: Demian K. <dem...@vi...> - 2017-04-25 12:27:07
|
George, That message generally means that you are missing the expected settings from the [OAI] section of config.ini: https://github.com/vufind-org/vufind/blob/master/config/vufind/config.ini#L1033 I'd check two things: 1.) Are you editing the correct version of the file? Make sure you modify $VUFIND_LOCAL_DIR/config/vufind/config.ini and not $VUFIND_HOME/config/vufind/config.ini -- in the majority of VuFind setups, the local copy is the one that gets used; the one in the home directory is just a template that gets copied during installation. 2.) Did you uncomment all of the relevant lines, including the [OAI] section header? If you're still having trouble after confirming those things, please feel free to share the relevant parts of your configuration file for analysis (and let us know exactly which version you are using). Thanks, good luck, and let me know if I can do more to help! - Demian -----Original Message----- From: gveranis [mailto:gve...@gm...] Sent: Tuesday, April 25, 2017 7:36 AM To: vuf...@li... Subject: [VuFind-Tech] OAI Server enable problem Hi All, I follow the instructions for enabling OAI Server in Vufind but still now I get "OAI Server Not Configured". The steps that I follow was based on that page : https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fvufind.org%2Fwiki%2Findexing%3Atracking_record_changes&data=02%7C01%7Cdemian.katz%40villanova.edu%7Ccd009a1814894c83753908d48bd0eb7d%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636287176847857852&sdata=zjWDFh2xsXsFStrB3Ee9M58fMdrb2T6LhhIXODSpcAw%3D&reserved=0 It something else that I can do for enabling? Thanks, George -- View this message in context: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvufind.2307425.n4.nabble.com%2FOAI-Server-enable-problem-tp4671305.html&data=02%7C01%7Cdemian.katz%40villanova.edu%7Ccd009a1814894c83753908d48bd0eb7d%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636287176847857852&sdata=ciQzJIvcoWuTRbHNHQoLKYc%2B%2BjaEEEHJXMpBjFxgYI4%3D&reserved=0 Sent from the vufind-tech mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdot&data=02%7C01%7Cdemian.katz%40villanova.edu%7Ccd009a1814894c83753908d48bd0eb7d%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636287176847857852&sdata=AUIUYrS5xgK6IyyPANGAQ4yOZkyln3DhjF%2Bj3LKpg60%3D&reserved=0 _______________________________________________ Vufind-tech mailing list Vuf...@li... https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fvufind-tech&data=02%7C01%7Cdemian.katz%40villanova.edu%7Ccd009a1814894c83753908d48bd0eb7d%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636287176847857852&sdata=SSfNet2yTO0YNbMw6%2FkxJyYq7ukW4l%2FcbbOd5y6hZ8w%3D&reserved=0 |
|
From: gveranis <gve...@gm...> - 2017-04-25 11:46:44
|
Hi All, I follow the instructions for enabling OAI Server in Vufind but still now I get "OAI Server Not Configured". The steps that I follow was based on that page : https://vufind.org/wiki/indexing:tracking_record_changes It something else that I can do for enabling? Thanks, George -- View this message in context: http://vufind.2307425.n4.nabble.com/OAI-Server-enable-problem-tp4671305.html Sent from the vufind-tech mailing list archive at Nabble.com. |
|
From: Brad B. <bbu...@uc...> - 2017-04-24 16:08:14
|
Thanks Demian! I'll talk it over with the team. We appreciate your advice. -Brad On 4/24/17 11:04 AM, Demian Katz wrote: > > Brad, > > You probably merged in a fairly small window of time between the stats > code being removed and the resulting bug in the upgrade script being > found and corrected. This commit should fix everything: > > https://github.com/vufind-org/vufind/commit/23b33ed80f83ba5c70d6560f0b5a141e015e8214 > > You might just want to merge up to that point, if it’s not too > burdensome (or you could merge to an even newer point in time to get > more bug fixes… but that’s probably more work!) > > - Demian > > *From:*Brad Busenius [mailto:bbu...@uc...] > *Sent:* Monday, April 24, 2017 12:01 PM > *To:* Demian Katz; vuf...@li... > *Subject:* Re: [VuFind-Tech] user stats and upgrading from VuFind 2.3 > > Hi Demian, > > Yes, I think you are correct. We seem to have merged at > 862184b54e4fd427de1c1142d4340a8da2f6c623. What do you recommend? > > Brad > > On 4/21/17 7:58 PM, Demian Katz wrote: > > Just to be clear, which code are you running? The stats code will > be removed in 4.0 but is still present in 3.1.1. Is it possible > you are working from a post-3.1.1 master checkout where the > version number hasn't been incremented yet? I will be happy to > look into this further on Monday but first want to be sure we are > both looking at the same thing. > > Thanks, > Demian > > Get Outlook for Android > <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36&data=02%7C01%7Cdemian.katz%40villanova.edu%7C4b100fca700e4c2b5e8d08d48b2b3e1a%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636286465254648469&sdata=giTQGZDpYhW%2FzdYaVUuVSk4piVnZLpgS4LHLEgsRNsE%3D&reserved=0> > > ------------------------------------------------------------------------ > > *From:*Brad Busenius <bbu...@uc...> > <mailto:bbu...@uc...> > *Sent:* Friday, April 21, 2017 5:48:17 PM > *To:* vuf...@li... > <mailto:vuf...@li...> > *Subject:* [VuFind-Tech] user stats and upgrading from VuFind 2.3 > > After upgrading our codebase from VuFind 2.3.1 to VuFind 3.1.1 we > are preparing to upgrade our production machines. Our problem is > that the upgrade script /vufind/Upgrade/Home does not work. We > sidestepped this in development by running the install script and > working on development machines. Now that we have to upgrade > production, this will not work. We need to make the upgrade > process function. > > The error that we're getting is: "get was unable to fetch or > create an instance for userstatsfields". We've looked at all the > related code but can't figure out why this is happening. We see > that the Statistics Module was removed in 3b78461. In our > database, the user_stats and user_stats_fields tables are empty. > We tried manually dropping them from a copy of the database, just > to see what would happen. It didn't change the result. > > Does anyone know what we might need to do? > > Your help is greatly appreciated. > > -Brad > |
|
From: Demian K. <dem...@vi...> - 2017-04-24 16:05:06
|
Brad, You probably merged in a fairly small window of time between the stats code being removed and the resulting bug in the upgrade script being found and corrected. This commit should fix everything: https://github.com/vufind-org/vufind/commit/23b33ed80f83ba5c70d6560f0b5a141e015e8214 You might just want to merge up to that point, if it's not too burdensome (or you could merge to an even newer point in time to get more bug fixes... but that's probably more work!) - Demian From: Brad Busenius [mailto:bbu...@uc...] Sent: Monday, April 24, 2017 12:01 PM To: Demian Katz; vuf...@li... Subject: Re: [VuFind-Tech] user stats and upgrading from VuFind 2.3 Hi Demian, Yes, I think you are correct. We seem to have merged at 862184b54e4fd427de1c1142d4340a8da2f6c623. What do you recommend? Brad On 4/21/17 7:58 PM, Demian Katz wrote: Just to be clear, which code are you running? The stats code will be removed in 4.0 but is still present in 3.1.1. Is it possible you are working from a post-3.1.1 master checkout where the version number hasn't been incremented yet? I will be happy to look into this further on Monday but first want to be sure we are both looking at the same thing. Thanks, Demian Get Outlook for Android<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36&data=02%7C01%7Cdemian.katz%40villanova.edu%7C4b100fca700e4c2b5e8d08d48b2b3e1a%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636286465254648469&sdata=giTQGZDpYhW%2FzdYaVUuVSk4piVnZLpgS4LHLEgsRNsE%3D&reserved=0> ________________________________ From: Brad Busenius <bbu...@uc...><mailto:bbu...@uc...> Sent: Friday, April 21, 2017 5:48:17 PM To: vuf...@li...<mailto:vuf...@li...> Subject: [VuFind-Tech] user stats and upgrading from VuFind 2.3 After upgrading our codebase from VuFind 2.3.1 to VuFind 3.1.1 we are preparing to upgrade our production machines. Our problem is that the upgrade script /vufind/Upgrade/Home does not work. We sidestepped this in development by running the install script and working on development machines. Now that we have to upgrade production, this will not work. We need to make the upgrade process function. The error that we're getting is: "get was unable to fetch or create an instance for userstatsfields". We've looked at all the related code but can't figure out why this is happening. We see that the Statistics Module was removed in 3b78461. In our database, the user_stats and user_stats_fields tables are empty. We tried manually dropping them from a copy of the database, just to see what would happen. It didn't change the result. Does anyone know what we might need to do? Your help is greatly appreciated. -Brad |
|
From: Brad B. <bbu...@uc...> - 2017-04-24 16:01:21
|
Hi Demian, Yes, I think you are correct. We seem to have merged at 862184b54e4fd427de1c1142d4340a8da2f6c623. What do you recommend? Brad On 4/21/17 7:58 PM, Demian Katz wrote: > > Just to be clear, which code are you running? The stats code will be > removed in 4.0 but is still present in 3.1.1. Is it possible you are > working from a post-3.1.1 master checkout where the version number > hasn't been incremented yet? I will be happy to look into this further > on Monday but first want to be sure we are both looking at the same thing. > > Thanks, > Demian > > Get Outlook for Android <https://aka.ms/ghei36> > > > ------------------------------------------------------------------------ > *From:* Brad Busenius <bbu...@uc...> > *Sent:* Friday, April 21, 2017 5:48:17 PM > *To:* vuf...@li... > *Subject:* [VuFind-Tech] user stats and upgrading from VuFind 2.3 > > After upgrading our codebase from VuFind 2.3.1 to VuFind 3.1.1 we are > preparing to upgrade our production machines. Our problem is that the > upgrade script /vufind/Upgrade/Home does not work. We sidestepped this > in development by running the install script and working on > development machines. Now that we have to upgrade production, this > will not work. We need to make the upgrade process function. > > The error that we're getting is: "get was unable to fetch or create an > instance for userstatsfields". We've looked at all the related code > but can't figure out why this is happening. We see that the Statistics > Module was removed in 3b78461. In our database, the user_stats and > user_stats_fields tables are empty. We tried manually dropping them > from a copy of the database, just to see what would happen. It didn't > change the result. > > Does anyone know what we might need to do? > > Your help is greatly appreciated. > > -Brad > > |
|
From: P. S. M. <psm...@gm...> - 2017-04-24 14:24:46
|
Thanks Demain for a detail explanation. Will try and report ASAP. Regards On Mon, Apr 24, 2017 at 6:48 PM, Demian Katz <dem...@vi...> wrote: > Yes, your understanding of what the import rule will do is correct. > > > > The batch-import-marc.sh script accepts a -p switch to specify which > properties file to use during indexing. This makes it possible to set up > multiple configurations for multiple ILS instances. > > > > One possible point of confusion, though: the -p switch does NOT refer to > marc_local.properties or other mapping files. Instead, it refers to the > file that by default is called import.properties. This file contains all of > the SolrMarc settings, one of which is the list of mappings files to use > (which includes marc_local.properties). So you want to do this: > > > > 1. Copy import.properties to import-k41.properties, and copy > marc_local.properties to marc_local-k41.properties. > > 2. Edit import-k41.properties to refer to marc_local-k41.properties. > > 3. Run the batch import with -p import-k41.properties as an > additional parameter. > > > > I hope this helps! > > - Demian > > > > *From:* P. S. Mukhopadhyay [mailto:psm...@gm...] > *Sent:* Saturday, April 22, 2017 6:09 AM > *To:* Demian Katz > *Cc:* vufind-tech > *Subject:* Re: [VuFind-Tech] Merging MARC records from different ILS > instances > > > > Another confusion: > > Say I'm following > > id = 001, (pattern_map.id_prefix), first > > pattern_map.id_prefix.pattern_0 = (.+)=>K41_$1 > > will it store id in vufind as K41.1234 for a record in Koha with bib id 1234? > > We have to create two marc_local.properties (say marc_local-k41.properties and > marc_local-k42.properties) for two instances/installations. Then how can we instruct to use respective marc_local durong batc-import? > > Regards > > > > > > On Sat, Apr 22, 2017 at 2:52 PM, P. S. Mukhopadhyay < > psm...@gm...> wrote: > > Thanks Demian. The ID issue is possibly the reason as pointed out by you. > In fact a closer look shows that each harvested record has different ID > (generated by VuFind) but inside the record the ID is Koha biblio ID stored > in non-MARC tag 999 $c. This we mentioned in marc_local.properties file as > id=999c, first. As a result, all first 101 records (from Koha set 1) got > replaced by the first 101 records from Koha set 2. > > I'll study the study materials as advised by you and bounce back with the > outcome of the experiment. Meanwhile one doubt... How can the VuFind track > real time status of documents available in different Koha installations (as > we can select only one driver in config.ini)? > > Regards > > > > On Sat, Apr 22, 2017 at 2:09 AM, Demian Katz <dem...@vi...> > wrote: > > I would guess that the problem you are running into here is ID collisions. > If you set up two instances of Koha, they're both going to start with > record ID 1 and increment from there. If you index those into the same > VuFind instance, some of the IDs are going to be the same, and then they're > going to overwrite each other. > > > > The solution is to use a different marc_local.properties file for each > instance so that you can assign a different prefix to each ID based on > which Koha instance it came from; then you can ensure that all IDs are > unique. This will cause problems for the Koha ILS driver, though, because > it expects the raw ID value, not a prefixed version -- but that's where the > MultiBackend driver can come in to proxy appropriate requests to > appropriate drivers. > > > > This wiki page talks about the MultiBackend driver and provides a link to > the SolrMarc configuration to achieve ID prefixing: > > > > https://vufind.org/wiki/configuration:ils:multibackend_driver > <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fvufind.org%2Fwiki%2Fconfiguration%3Ails%3Amultibackend_driver&data=02%7C01%7Cdemian.katz%40villanova.edu%7C85652c494b14451fb87e08d48967b4a3%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636284525881087988&sdata=agSeMl4VeHNwv5xVr5f4GmrYWtL8I1AemoYqtdkZSbg%3D&reserved=0> > > > > Please let me know if you still have any questions or problems! > > > > - Demian > > > ------------------------------ > > *From:* P. S. Mukhopadhyay <psm...@gm...> > *Sent:* Friday, April 21, 2017 3:37 PM > *To:* vufind-tech > *Subject:* [VuFind-Tech] Merging MARC records from different ILS instances > > > > Dear all > > Today I encountered an unexpected result in VuFind 3.1.3 (working on > Ubuntu LTS 16.04 with PHP 7.0). > > 1. harvested records (marcxml) from two different installation of Koha > (one includes 101 and next includes 112 records respectively; > > > > the process went on successfully. > > 2. indexed harvested records; > > this has also performed by the system without any error. > > The surprise came in next level. Instead merging records (101+112), Solr > is actually replacing first records set (101 number records) with second > records set (112 records). As a result after importing in solr we are > getting 112 records in place of 101+112 records. Initially we though there > some problems in our process but found same results after performing the > entire process in three different times. > > Our expectation was that - after harvesting and importing records from > different Koha instances (or installations) we will get a union catalogue > kind of things in VuFind discovery system. But it is not happening. What > are we missing? > > Note: we have included different sections for different Koha instance > with unique id by IP address e.g [Koha-42 and Koha-41]. > > Regards > > > -- > > ----------------------------------------------------------------------- > Dr. Parthasarathi Mukhopadhyay > Associate Professor, Department of Library and Information Science, > University of Kalyani, > Kalyani - 741 235 (WB), India > ----------------------------------------------------------------------- > > > > > -- > > ----------------------------------------------------------------------- > Dr. Parthasarathi Mukhopadhyay > Associate Professor, Department of Library and Information Science, > University of Kalyani, > Kalyani - 741 235 (WB), India > ----------------------------------------------------------------------- > > > > > -- > > ----------------------------------------------------------------------- > Dr. Parthasarathi Mukhopadhyay > Associate Professor, Department of Library and Information Science, > University of Kalyani, > Kalyani - 741 235 (WB), India > ----------------------------------------------------------------------- > -- ----------------------------------------------------------------------- Dr. Parthasarathi Mukhopadhyay Associate Professor, Department of Library and Information Science, University of Kalyani, Kalyani - 741 235 (WB), India ----------------------------------------------------------------------- |
|
From: Demian K. <dem...@vi...> - 2017-04-24 13:18:44
|
Yes, your understanding of what the import rule will do is correct. The batch-import-marc.sh script accepts a -p switch to specify which properties file to use during indexing. This makes it possible to set up multiple configurations for multiple ILS instances. One possible point of confusion, though: the -p switch does NOT refer to marc_local.properties or other mapping files. Instead, it refers to the file that by default is called import.properties. This file contains all of the SolrMarc settings, one of which is the list of mappings files to use (which includes marc_local.properties). So you want to do this: 1. Copy import.properties to import-k41.properties, and copy marc_local.properties to marc_local-k41.properties. 2. Edit import-k41.properties to refer to marc_local-k41.properties. 3. Run the batch import with -p import-k41.properties as an additional parameter. I hope this helps! - Demian From: P. S. Mukhopadhyay [mailto:psm...@gm...] Sent: Saturday, April 22, 2017 6:09 AM To: Demian Katz Cc: vufind-tech Subject: Re: [VuFind-Tech] Merging MARC records from different ILS instances Another confusion: Say I'm following id = 001, (pattern_map.id_prefix), first pattern_map.id_prefix.pattern_0 = (.+)=>K41_$1 will it store id in vufind as K41.1234 for a record in Koha with bib id 1234? We have to create two marc_local.properties (say marc_local-k41.properties and marc_local-k42.properties) for two instances/installations. Then how can we instruct to use respective marc_local durong batc-import? Regards On Sat, Apr 22, 2017 at 2:52 PM, P. S. Mukhopadhyay <psm...@gm...<mailto:psm...@gm...>> wrote: Thanks Demian. The ID issue is possibly the reason as pointed out by you. In fact a closer look shows that each harvested record has different ID (generated by VuFind) but inside the record the ID is Koha biblio ID stored in non-MARC tag 999 $c. This we mentioned in marc_local.properties file as id=999c, first. As a result, all first 101 records (from Koha set 1) got replaced by the first 101 records from Koha set 2. I'll study the study materials as advised by you and bounce back with the outcome of the experiment. Meanwhile one doubt... How can the VuFind track real time status of documents available in different Koha installations (as we can select only one driver in config.ini)? Regards On Sat, Apr 22, 2017 at 2:09 AM, Demian Katz <dem...@vi...<mailto:dem...@vi...>> wrote: I would guess that the problem you are running into here is ID collisions. If you set up two instances of Koha, they're both going to start with record ID 1 and increment from there. If you index those into the same VuFind instance, some of the IDs are going to be the same, and then they're going to overwrite each other. The solution is to use a different marc_local.properties file for each instance so that you can assign a different prefix to each ID based on which Koha instance it came from; then you can ensure that all IDs are unique. This will cause problems for the Koha ILS driver, though, because it expects the raw ID value, not a prefixed version -- but that's where the MultiBackend driver can come in to proxy appropriate requests to appropriate drivers. This wiki page talks about the MultiBackend driver and provides a link to the SolrMarc configuration to achieve ID prefixing: https://vufind.org/wiki/configuration:ils:multibackend_driver<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fvufind.org%2Fwiki%2Fconfiguration%3Ails%3Amultibackend_driver&data=02%7C01%7Cdemian.katz%40villanova.edu%7C85652c494b14451fb87e08d48967b4a3%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636284525881087988&sdata=agSeMl4VeHNwv5xVr5f4GmrYWtL8I1AemoYqtdkZSbg%3D&reserved=0> Please let me know if you still have any questions or problems! - Demian ________________________________ From: P. S. Mukhopadhyay <psm...@gm...<mailto:psm...@gm...>> Sent: Friday, April 21, 2017 3:37 PM To: vufind-tech Subject: [VuFind-Tech] Merging MARC records from different ILS instances Dear all Today I encountered an unexpected result in VuFind 3.1.3 (working on Ubuntu LTS 16.04 with PHP 7.0). 1. harvested records (marcxml) from two different installation of Koha (one includes 101 and next includes 112 records respectively; the process went on successfully. 2. indexed harvested records; this has also performed by the system without any error. The surprise came in next level. Instead merging records (101+112), Solr is actually replacing first records set (101 number records) with second records set (112 records). As a result after importing in solr we are getting 112 records in place of 101+112 records. Initially we though there some problems in our process but found same results after performing the entire process in three different times. Our expectation was that - after harvesting and importing records from different Koha instances (or installations) we will get a union catalogue kind of things in VuFind discovery system. But it is not happening. What are we missing? Note: we have included different sections for different Koha instance with unique id by IP address e.g [Koha-42 and Koha-41]. Regards -- ----------------------------------------------------------------------- Dr. Parthasarathi Mukhopadhyay Associate Professor, Department of Library and Information Science, University of Kalyani, Kalyani - 741 235 (WB), India ----------------------------------------------------------------------- -- ----------------------------------------------------------------------- Dr. Parthasarathi Mukhopadhyay Associate Professor, Department of Library and Information Science, University of Kalyani, Kalyani - 741 235 (WB), India ----------------------------------------------------------------------- -- ----------------------------------------------------------------------- Dr. Parthasarathi Mukhopadhyay Associate Professor, Department of Library and Information Science, University of Kalyani, Kalyani - 741 235 (WB), India ----------------------------------------------------------------------- |
|
From: Demian K. <dem...@vi...> - 2017-04-24 13:15:09
|
Regarding your question about real time status in different Koha installations, that is what the MultiBackend ILS driver described in the wiki link does – it acts as a proxy in front of other ILS driver objects, allowing VuFind to communicate with multiple systems. It uses your custom ID prefixes to route requests to the most appropriate drivers. - Demian From: P. S. Mukhopadhyay [mailto:psm...@gm...] Sent: Saturday, April 22, 2017 5:23 AM To: Demian Katz Cc: vufind-tech Subject: Re: [VuFind-Tech] Merging MARC records from different ILS instances Thanks Demian. The ID issue is possibly the reason as pointed out by you. In fact a closer look shows that each harvested record has different ID (generated by VuFind) but inside the record the ID is Koha biblio ID stored in non-MARC tag 999 $c. This we mentioned in marc_local.properties file as id=999c, first. As a result, all first 101 records (from Koha set 1) got replaced by the first 101 records from Koha set 2. I'll study the study materials as advised by you and bounce back with the outcome of the experiment. Meanwhile one doubt... How can the VuFind track real time status of documents available in different Koha installations (as we can select only one driver in config.ini)? Regards On Sat, Apr 22, 2017 at 2:09 AM, Demian Katz <dem...@vi...<mailto:dem...@vi...>> wrote: I would guess that the problem you are running into here is ID collisions. If you set up two instances of Koha, they're both going to start with record ID 1 and increment from there. If you index those into the same VuFind instance, some of the IDs are going to be the same, and then they're going to overwrite each other. The solution is to use a different marc_local.properties file for each instance so that you can assign a different prefix to each ID based on which Koha instance it came from; then you can ensure that all IDs are unique. This will cause problems for the Koha ILS driver, though, because it expects the raw ID value, not a prefixed version -- but that's where the MultiBackend driver can come in to proxy appropriate requests to appropriate drivers. This wiki page talks about the MultiBackend driver and provides a link to the SolrMarc configuration to achieve ID prefixing: https://vufind.org/wiki/configuration:ils:multibackend_driver<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fvufind.org%2Fwiki%2Fconfiguration%3Ails%3Amultibackend_driver&data=02%7C01%7Cdemian.katz%40villanova.edu%7C6dba4ec85f7d4803cdc708d4896120cd%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636284497634566473&sdata=pXGIolkp%2FU7ylV2PX5y07aw0q9c6qcXYTaGpKPVcE1w%3D&reserved=0> Please let me know if you still have any questions or problems! - Demian ________________________________ From: P. S. Mukhopadhyay <psm...@gm...<mailto:psm...@gm...>> Sent: Friday, April 21, 2017 3:37 PM To: vufind-tech Subject: [VuFind-Tech] Merging MARC records from different ILS instances Dear all Today I encountered an unexpected result in VuFind 3.1.3 (working on Ubuntu LTS 16.04 with PHP 7.0). 1. harvested records (marcxml) from two different installation of Koha (one includes 101 and next includes 112 records respectively; the process went on successfully. 2. indexed harvested records; this has also performed by the system without any error. The surprise came in next level. Instead merging records (101+112), Solr is actually replacing first records set (101 number records) with second records set (112 records). As a result after importing in solr we are getting 112 records in place of 101+112 records. Initially we though there some problems in our process but found same results after performing the entire process in three different times. Our expectation was that - after harvesting and importing records from different Koha instances (or installations) we will get a union catalogue kind of things in VuFind discovery system. But it is not happening. What are we missing? Note: we have included different sections for different Koha instance with unique id by IP address e.g [Koha-42 and Koha-41]. Regards -- ----------------------------------------------------------------------- Dr. Parthasarathi Mukhopadhyay Associate Professor, Department of Library and Information Science, University of Kalyani, Kalyani - 741 235 (WB), India ----------------------------------------------------------------------- -- ----------------------------------------------------------------------- Dr. Parthasarathi Mukhopadhyay Associate Professor, Department of Library and Information Science, University of Kalyani, Kalyani - 741 235 (WB), India ----------------------------------------------------------------------- |
|
From: P. S. M. <psm...@gm...> - 2017-04-22 10:09:10
|
Another confusion: Say I'm following id = 001, (pattern_map.id_prefix), first pattern_map.id_prefix.pattern_0 = (.+)=>K41_$1 will it store id in vufind as K41.1234 for a record in Koha with bib id 1234? We have to create two marc_local.properties (say marc_local-k41.properties and marc_local-k42.properties) for two instances/installations. Then how can we instruct to use respective marc_local durong batc-import? Regards On Sat, Apr 22, 2017 at 2:52 PM, P. S. Mukhopadhyay < psm...@gm...> wrote: > Thanks Demian. The ID issue is possibly the reason as pointed out by you. > In fact a closer look shows that each harvested record has different ID > (generated by VuFind) but inside the record the ID is Koha biblio ID stored > in non-MARC tag 999 $c. This we mentioned in marc_local.properties file as > id=999c, first. As a result, all first 101 records (from Koha set 1) got > replaced by the first 101 records from Koha set 2. > > I'll study the study materials as advised by you and bounce back with the > outcome of the experiment. Meanwhile one doubt... How can the VuFind track > real time status of documents available in different Koha installations (as > we can select only one driver in config.ini)? > > Regards > > On Sat, Apr 22, 2017 at 2:09 AM, Demian Katz <dem...@vi...> > wrote: > >> I would guess that the problem you are running into here is ID >> collisions. If you set up two instances of Koha, they're both going to >> start with record ID 1 and increment from there. If you index those into >> the same VuFind instance, some of the IDs are going to be the same, and >> then they're going to overwrite each other. >> >> >> The solution is to use a different marc_local.properties file for each >> instance so that you can assign a different prefix to each ID based on >> which Koha instance it came from; then you can ensure that all IDs are >> unique. This will cause problems for the Koha ILS driver, though, because >> it expects the raw ID value, not a prefixed version -- but that's where the >> MultiBackend driver can come in to proxy appropriate requests to >> appropriate drivers. >> >> >> This wiki page talks about the MultiBackend driver and provides a link to >> the SolrMarc configuration to achieve ID prefixing: >> >> >> https://vufind.org/wiki/configuration:ils:multibackend_driver >> >> >> Please let me know if you still have any questions or problems! >> >> >> - Demian >> >> ------------------------------ >> *From:* P. S. Mukhopadhyay <psm...@gm...> >> *Sent:* Friday, April 21, 2017 3:37 PM >> *To:* vufind-tech >> *Subject:* [VuFind-Tech] Merging MARC records from different ILS >> instances >> >> Dear all >> >> Today I encountered an unexpected result in VuFind 3.1.3 (working on >> Ubuntu LTS 16.04 with PHP 7.0). >> >> 1. harvested records (marcxml) from two different installation of Koha >> (one includes 101 and next includes 112 records respectively; >> >> the process went on successfully. >> >> 2. indexed harvested records; >> >> this has also performed by the system without any error. >> >> The surprise came in next level. Instead merging records (101+112), Solr >> is actually replacing first records set (101 number records) with second >> records set (112 records). As a result after importing in solr we are >> getting 112 records in place of 101+112 records. Initially we though there >> some problems in our process but found same results after performing the >> entire process in three different times. >> >> Our expectation was that - after harvesting and importing records from >> different Koha instances (or installations) we will get a union catalogue >> kind of things in VuFind discovery system. But it is not happening. What >> are we missing? >> >> Note: we have included different sections for different Koha instance >> with unique id by IP address e.g [Koha-42 and Koha-41]. >> >> Regards >> >> -- >> ----------------------------------------------------------------------- >> Dr. Parthasarathi Mukhopadhyay >> Associate Professor, Department of Library and Information Science, >> University of Kalyani, >> Kalyani - 741 235 (WB), India >> ----------------------------------------------------------------------- >> > > > > -- > ----------------------------------------------------------------------- > Dr. Parthasarathi Mukhopadhyay > Associate Professor, Department of Library and Information Science, > University of Kalyani, > Kalyani - 741 235 (WB), India > ----------------------------------------------------------------------- > -- ----------------------------------------------------------------------- Dr. Parthasarathi Mukhopadhyay Associate Professor, Department of Library and Information Science, University of Kalyani, Kalyani - 741 235 (WB), India ----------------------------------------------------------------------- |
|
From: P. S. M. <psm...@gm...> - 2017-04-22 09:22:46
|
Thanks Demian. The ID issue is possibly the reason as pointed out by you. In fact a closer look shows that each harvested record has different ID (generated by VuFind) but inside the record the ID is Koha biblio ID stored in non-MARC tag 999 $c. This we mentioned in marc_local.properties file as id=999c, first. As a result, all first 101 records (from Koha set 1) got replaced by the first 101 records from Koha set 2. I'll study the study materials as advised by you and bounce back with the outcome of the experiment. Meanwhile one doubt... How can the VuFind track real time status of documents available in different Koha installations (as we can select only one driver in config.ini)? Regards On Sat, Apr 22, 2017 at 2:09 AM, Demian Katz <dem...@vi...> wrote: > I would guess that the problem you are running into here is ID collisions. > If you set up two instances of Koha, they're both going to start with > record ID 1 and increment from there. If you index those into the same > VuFind instance, some of the IDs are going to be the same, and then they're > going to overwrite each other. > > > The solution is to use a different marc_local.properties file for each > instance so that you can assign a different prefix to each ID based on > which Koha instance it came from; then you can ensure that all IDs are > unique. This will cause problems for the Koha ILS driver, though, because > it expects the raw ID value, not a prefixed version -- but that's where the > MultiBackend driver can come in to proxy appropriate requests to > appropriate drivers. > > > This wiki page talks about the MultiBackend driver and provides a link to > the SolrMarc configuration to achieve ID prefixing: > > > https://vufind.org/wiki/configuration:ils:multibackend_driver > > > Please let me know if you still have any questions or problems! > > > - Demian > > ------------------------------ > *From:* P. S. Mukhopadhyay <psm...@gm...> > *Sent:* Friday, April 21, 2017 3:37 PM > *To:* vufind-tech > *Subject:* [VuFind-Tech] Merging MARC records from different ILS instances > > Dear all > > Today I encountered an unexpected result in VuFind 3.1.3 (working on > Ubuntu LTS 16.04 with PHP 7.0). > > 1. harvested records (marcxml) from two different installation of Koha > (one includes 101 and next includes 112 records respectively; > > the process went on successfully. > > 2. indexed harvested records; > > this has also performed by the system without any error. > > The surprise came in next level. Instead merging records (101+112), Solr > is actually replacing first records set (101 number records) with second > records set (112 records). As a result after importing in solr we are > getting 112 records in place of 101+112 records. Initially we though there > some problems in our process but found same results after performing the > entire process in three different times. > > Our expectation was that - after harvesting and importing records from > different Koha instances (or installations) we will get a union catalogue > kind of things in VuFind discovery system. But it is not happening. What > are we missing? > > Note: we have included different sections for different Koha instance > with unique id by IP address e.g [Koha-42 and Koha-41]. > > Regards > > -- > ----------------------------------------------------------------------- > Dr. Parthasarathi Mukhopadhyay > Associate Professor, Department of Library and Information Science, > University of Kalyani, > Kalyani - 741 235 (WB), India > ----------------------------------------------------------------------- > -- ----------------------------------------------------------------------- Dr. Parthasarathi Mukhopadhyay Associate Professor, Department of Library and Information Science, University of Kalyani, Kalyani - 741 235 (WB), India ----------------------------------------------------------------------- |
|
From: Demian K. <dem...@vi...> - 2017-04-22 00:59:02
|
Just to be clear, which code are you running? The stats code will be removed in 4.0 but is still present in 3.1.1. Is it possible you are working from a post-3.1.1 master checkout where the version number hasn't been incremented yet? I will be happy to look into this further on Monday but first want to be sure we are both looking at the same thing. Thanks, Demian Get Outlook for Android<https://aka.ms/ghei36> ________________________________ From: Brad Busenius <bbu...@uc...> Sent: Friday, April 21, 2017 5:48:17 PM To: vuf...@li... Subject: [VuFind-Tech] user stats and upgrading from VuFind 2.3 After upgrading our codebase from VuFind 2.3.1 to VuFind 3.1.1 we are preparing to upgrade our production machines. Our problem is that the upgrade script /vufind/Upgrade/Home does not work. We sidestepped this in development by running the install script and working on development machines. Now that we have to upgrade production, this will not work. We need to make the upgrade process function. The error that we're getting is: "get was unable to fetch or create an instance for userstatsfields". We've looked at all the related code but can't figure out why this is happening. We see that the Statistics Module was removed in 3b78461. In our database, the user_stats and user_stats_fields tables are empty. We tried manually dropping them from a copy of the database, just to see what would happen. It didn't change the result. Does anyone know what we might need to do? Your help is greatly appreciated. -Brad |
|
From: Brad B. <bbu...@uc...> - 2017-04-21 21:48:23
|
After upgrading our codebase from VuFind 2.3.1 to VuFind 3.1.1 we are preparing to upgrade our production machines. Our problem is that the upgrade script /vufind/Upgrade/Home does not work. We sidestepped this in development by running the install script and working on development machines. Now that we have to upgrade production, this will not work. We need to make the upgrade process function. The error that we're getting is: "get was unable to fetch or create an instance for userstatsfields". We've looked at all the related code but can't figure out why this is happening. We see that the Statistics Module was removed in 3b78461. In our database, the user_stats and user_stats_fields tables are empty. We tried manually dropping them from a copy of the database, just to see what would happen. It didn't change the result. Does anyone know what we might need to do? Your help is greatly appreciated. -Brad |
|
From: Demian K. <dem...@vi...> - 2017-04-21 20:39:31
|
I would guess that the problem you are running into here is ID collisions. If you set up two instances of Koha, they're both going to start with record ID 1 and increment from there. If you index those into the same VuFind instance, some of the IDs are going to be the same, and then they're going to overwrite each other. The solution is to use a different marc_local.properties file for each instance so that you can assign a different prefix to each ID based on which Koha instance it came from; then you can ensure that all IDs are unique. This will cause problems for the Koha ILS driver, though, because it expects the raw ID value, not a prefixed version -- but that's where the MultiBackend driver can come in to proxy appropriate requests to appropriate drivers. This wiki page talks about the MultiBackend driver and provides a link to the SolrMarc configuration to achieve ID prefixing: https://vufind.org/wiki/configuration:ils:multibackend_driver Please let me know if you still have any questions or problems! - Demian ________________________________ From: P. S. Mukhopadhyay <psm...@gm...> Sent: Friday, April 21, 2017 3:37 PM To: vufind-tech Subject: [VuFind-Tech] Merging MARC records from different ILS instances Dear all Today I encountered an unexpected result in VuFind 3.1.3 (working on Ubuntu LTS 16.04 with PHP 7.0). 1. harvested records (marcxml) from two different installation of Koha (one includes 101 and next includes 112 records respectively; the process went on successfully. 2. indexed harvested records; this has also performed by the system without any error. The surprise came in next level. Instead merging records (101+112), Solr is actually replacing first records set (101 number records) with second records set (112 records). As a result after importing in solr we are getting 112 records in place of 101+112 records. Initially we though there some problems in our process but found same results after performing the entire process in three different times. Our expectation was that - after harvesting and importing records from different Koha instances (or installations) we will get a union catalogue kind of things in VuFind discovery system. But it is not happening. What are we missing? Note: we have included different sections for different Koha instance with unique id by IP address e.g [Koha-42 and Koha-41]. Regards -- ----------------------------------------------------------------------- Dr. Parthasarathi Mukhopadhyay Associate Professor, Department of Library and Information Science, University of Kalyani, Kalyani - 741 235 (WB), India ----------------------------------------------------------------------- |
|
From: P. S. M. <psm...@gm...> - 2017-04-21 19:37:41
|
Dear all Today I encountered an unexpected result in VuFind 3.1.3 (working on Ubuntu LTS 16.04 with PHP 7.0). 1. harvested records (marcxml) from two different installation of Koha (one includes 101 and next includes 112 records respectively; the process went on successfully. 2. indexed harvested records; this has also performed by the system without any error. The surprise came in next level. Instead merging records (101+112), Solr is actually replacing first records set (101 number records) with second records set (112 records). As a result after importing in solr we are getting 112 records in place of 101+112 records. Initially we though there some problems in our process but found same results after performing the entire process in three different times. Our expectation was that - after harvesting and importing records from different Koha instances (or installations) we will get a union catalogue kind of things in VuFind discovery system. But it is not happening. What are we missing? Note: we have included different sections for different Koha instance with unique id by IP address e.g [Koha-42 and Koha-41]. Regards -- ----------------------------------------------------------------------- Dr. Parthasarathi Mukhopadhyay Associate Professor, Department of Library and Information Science, University of Kalyani, Kalyani - 741 235 (WB), India ----------------------------------------------------------------------- |
|
From: Demian K. <dem...@vi...> - 2017-04-20 12:57:00
|
The next developers call will be Tuesday, April 25, 2017 at 9am Eastern Standard Time (13:00 GMT).
AGENDA
1. Development Updates
2. Development Planning
a. VuFind on Heroku
b. Image Metadata API Revisited
c. Breaking Up Templates
d. Channels
e. Modularization
f. Next ZF Version
g. Improved Use of Permissions
h. Solr 6
i. Deprecation Progress
j. Wiki Documentation Improvements?
k. Preparing for 4.0
l. Front End Updates
3. VuFind Usage Survey
4. Institutional Home
5. Other Topics?
More information on the free online call can be found at https://vufind.org/wiki/developers_call -- all are welcome!
- Demian
|
|
From: Demian K. <dem...@vi...> - 2017-04-10 16:13:03
|
Hello, everyone - Just wanted to let you know that I am once again attending a conference this week, so my email response times may be slower than usual beginning tomorrow. I'll be back in the office a week from today and will try to check messages as frequently as possible in the meantime. - Demian |
|
From: jaya <mj...@gm...> - 2017-04-08 17:33:34
|
Thanks it's working... and I am doing more customizations now. Regards, Jay ----- Information Specialist International Water Management Institute Sri Lanka -- View this message in context: http://vufind.2307425.n4.nabble.com/An-error-displaying-import-marc-data-tp4671186p4671267.html Sent from the vufind-tech mailing list archive at Nabble.com. |
|
From: jaya <mj...@gm...> - 2017-04-07 06:01:09
|
Dear Demian, I have successfully import marc data into vufind interface. And I want to know how to edit item display page (image attached) in results. For an example.. I have to add or remove some bibliographic details in my item display page. <http://vufind.2307425.n4.nabble.com/file/n4671265/Screenshot_from_2017-04-07_11-18-19.png> Thanks Jay.. ----- Information Specialist International Water Management Institute Sri Lanka -- View this message in context: http://vufind.2307425.n4.nabble.com/An-error-displaying-import-marc-data-tp4671186p4671265.html Sent from the vufind-tech mailing list archive at Nabble.com. |