From: Assaf W. <as...@po...> - 2014-01-18 22:27:26
|
??"? Hi, After a pretty long period of 'getting started' I was playing with the software a bit, took a look on the DB and please have a few more questions: 1. I saw that in the session table - a single session was calculated until I was closing the browser, so I went to the config.ini saw it under the 'session' section and changed it to be '60' just to see what will happen. Then - I indeed see that running a new search query after each 60 seconds causes the ID of this session to be promoted but it's still all under the same session which is actually the same behavior as before except for the ID that is being changed. (The new ID overrides the old one and the old ID cannot be found), so: a. Is that the expected behavior? b. Is there a way to define that after period of 'x' seconds - create a new entry in the 'sessions' table? c. I also noticed that each search ('lookfor') overrides the previous, meaning - there is no way to see ALL values that were searched during this session. Is there a configuration parameter/workaround for allowing it? 2. I added a user entry to the user table but still cannot 'login' - is it something with the authentication method in the config.ini? (Currently set to LDAP). Which log tracks the authentication attempts? 3. I need some directing in the code, I am please looking for the code sections that handle: a. Writing down to the DB. b. GUI of main vufind homepage. Thanks a lot in advance. Assaf We |
From: Demian K. <dem...@vi...> - 2014-01-20 15:30:45
|
1a/b. I might be able to answer these better if I understood more about what you're hoping to do with sessions. The main purpose of the VuFind session is to track the user's login status and to remember search history. Is there a reason you wish to make these expire at a particular rate? 1c. The search history shows all searches performed during the current session... there should be a link to it in the footer, or you can go to the Search/History URL within VuFind. 2. If you are not using LDAP and want VuFind to manage its own internal accounts, change the authentication setting to use DB instead of LDAP. There is not an authentication-specific log in VuFind, though you could create one fairly easily if you needed to, or you might be able to figure out counts through Apache log analysis (though the Apache log won't tell you which user is trying to log in, of course). 3a. In VuFind 1.x, all of the database writing is done through PEAR's DB abstraction library. The classes representing the database tables are found in web/services/MyResearch/lib, and they are called from the controllers in the various other web/services directories. 3b. The default homepage layout can be found in web/interface/themes/[your theme]/Search/home.tpl -- and if you need to set extra variables for use in this template, you can modify the corresponding controller in the web/services directory. Please let me know if you still have questions! - Demian ________________________________ From: Assaf Weinrib [as...@po...] Sent: Saturday, January 18, 2014 5:27 PM To: vuf...@li... Subject: [VuFind-General] A few questions please בס"ד Hi, After a pretty long period of 'getting started' I was playing with the software a bit, took a look on the DB and please have a few more questions: 1. I saw that in the session table – a single session was calculated until I was closing the browser, so I went to the config.ini saw it under the 'session' section and changed it to be '60' just to see what will happen. Then – I indeed see that running a new search query after each 60 seconds causes the ID of this session to be promoted but it's still all under the same session which is actually the same behavior as before except for the ID that is being changed. (The new ID overrides the old one and the old ID cannot be found), so: a. Is that the expected behavior? b. Is there a way to define that after period of 'x' seconds – create a new entry in the 'sessions' table? c. I also noticed that each search ('lookfor') overrides the previous, meaning – there is no way to see ALL values that were searched during this session. Is there a configuration parameter/workaround for allowing it? 2. I added a user entry to the user table but still cannot 'login' - is it something with the authentication method in the config.ini? (Currently set to LDAP). Which log tracks the authentication attempts? 3. I need some directing in the code, I am please looking for the code sections that handle: a. Writing down to the DB. b. GUI of main vufind homepage. Thanks a lot in advance. Assaf We |
From: Assaf W. <as...@po...> - 2014-01-21 10:57:35
|
בס"ד 1a/b. I might be able to answer these better if I understood more about what you're hoping to do with sessions. The main purpose of the VuFind session is to track the user's login status and to remember search history. Is there a reason you wish to make these expire at a particular rate? My plan is as follows: I want to analyze the searches that have been performed on my system, e.g. How many times the term <TERM> was searched? How many search queries have been triggered today? And many more So for the above I guess I can use the 'search' table, without involving the session table. Is there a way to extract the search queries out of the BLOB?? (I was trying using the 2char cast but didn't seem to help). Later on I would also like to analyze multiple queries that a single user was running during a single session – that's the aspect from which I was asking why the 'lookfor' value is being overridden for the session. How would you suggest me to extract this data from within the DB?? - But is just to understand the System design and business logic, if i'll have a solution for the above part i would be able also to perform queries for where the session ID is the same. 1c. The search history shows all searches performed during the current session... there should be a link to it in the footer, or you can go to the Search/History URL within VuFind. Ok still looking for a straight forward DB way to gain this data. 2. If you are not using LDAP and want VuFind to manage its own internal accounts, change the authentication setting to use DB instead of LDAP. There is not an authentication-specific log in VuFind, though you could create one fairly easily if you needed to, or you might be able to figure out counts through Apache log analysis (though the Apache log won't tell you which user is trying to log in, of course). Thanks, works. 3a. In VuFind 1.x, all of the database writing is done through PEAR's DB abstraction library. The classes representing the database tables are found in web/services/MyResearch/lib, and they are called from the controllers in the various other web/services directories. Thanks (nevertheless sounds complicated… J) 3b. The default homepage layout can be found in web/interface/themes/[your theme]/Search/home.tpl -- and if you need to set extra variables for use in this template, you can modify the corresponding controller in the web/services directory. Thanks Please let me know if you still have questions! Thanks a lot, indeed seems like I'm going to harass this mail list… - Demian Thanks a lot Demian! ________________________________ מ: Demian Katz <dem...@vi...> נשלח: יום שני 20 ינואר 2014 15:30 אל: Assaf Weinrib; vuf...@li... נושא: RE: A few questions please 1a/b. I might be able to answer these better if I understood more about what you're hoping to do with sessions. The main purpose of the VuFind session is to track the user's login status and to remember search history. Is there a reason you wish to make these expire at a particular rate? 1c. The search history shows all searches performed during the current session... there should be a link to it in the footer, or you can go to the Search/History URL within VuFind. 2. If you are not using LDAP and want VuFind to manage its own internal accounts, change the authentication setting to use DB instead of LDAP. There is not an authentication-specific log in VuFind, though you could create one fairly easily if you needed to, or you might be able to figure out counts through Apache log analysis (though the Apache log won't tell you which user is trying to log in, of course). 3a. In VuFind 1.x, all of the database writing is done through PEAR's DB abstraction library. The classes representing the database tables are found in web/services/MyResearch/lib, and they are called from the controllers in the various other web/services directories. 3b. The default homepage layout can be found in web/interface/themes/[your theme]/Search/home.tpl -- and if you need to set extra variables for use in this template, you can modify the corresponding controller in the web/services directory. Please let me know if you still have questions! - Demian ________________________________ From: Assaf Weinrib [as...@po...] Sent: Saturday, January 18, 2014 5:27 PM To: vuf...@li... Subject: [VuFind-General] A few questions please בס"ד Hi, After a pretty long period of 'getting started' I was playing with the software a bit, took a look on the DB and please have a few more questions: 1. I saw that in the session table – a single session was calculated until I was closing the browser, so I went to the config.ini saw it under the 'session' section and changed it to be '60' just to see what will happen. Then – I indeed see that running a new search query after each 60 seconds causes the ID of this session to be promoted but it's still all under the same session which is actually the same behavior as before except for the ID that is being changed. (The new ID overrides the old one and the old ID cannot be found), so: a. Is that the expected behavior? b. Is there a way to define that after period of 'x' seconds – create a new entry in the 'sessions' table? c. I also noticed that each search ('lookfor') overrides the previous, meaning – there is no way to see ALL values that were searched during this session. Is there a configuration parameter/workaround for allowing it? 2. I added a user entry to the user table but still cannot 'login' - is it something with the authentication method in the config.ini? (Currently set to LDAP). Which log tracks the authentication attempts? 3. I need some directing in the code, I am please looking for the code sections that handle: a. Writing down to the DB. b. GUI of main vufind homepage. Thanks a lot in advance. Assaf We |
From: Demian K. <dem...@vi...> - 2014-01-21 14:35:55
|
The blob field in the database is a serialized PHP object. You could write a script to unserialize the objects and extract the queries from there. The search table containing the blobs also should have a session field that links together searches from a single user session. If users save their searches, the session field gets cleared and the user’s ID is attached instead… but this happens very infrequently and probably doesn’t need to be accounted for to get a rough idea of user behavior. If you don’t want to deal with the complexity of the PEAR DB library, you can always write a stand-alone script that connects to MySQL independently and just pulls data directly from the search table. For statistical analysis purposes, I see no harm in doing that. Let me know if you still have questions! - Demian From: Assaf Weinrib [mailto:as...@po...] Sent: Tuesday, January 21, 2014 5:57 AM To: Demian Katz; vuf...@li... Subject: RE: A few questions please בס"ד 1a/b. I might be able to answer these better if I understood more about what you're hoping to do with sessions. The main purpose of the VuFind session is to track the user's login status and to remember search history. Is there a reason you wish to make these expire at a particular rate? My plan is as follows: I want to analyze the searches that have been performed on my system, e.g. How many times the term <TERM> was searched? How many search queries have been triggered today? And many more So for the above I guess I can use the 'search' table, without involving the session table. Is there a way to extract the search queries out of the BLOB?? (I was trying using the 2char cast but didn't seem to help). Later on I would also like to analyze multiple queries that a single user was running during a single session – that's the aspect from which I was asking why the 'lookfor' value is being overridden for the session. How would you suggest me to extract this data from within the DB?? - But is just to understand the System design and business logic, if i'll have a solution for the above part i would be able also to perform queries for where the session ID is the same. 1c. The search history shows all searches performed during the current session... there should be a link to it in the footer, or you can go to the Search/History URL within VuFind. Ok still looking for a straight forward DB way to gain this data. 2. If you are not using LDAP and want VuFind to manage its own internal accounts, change the authentication setting to use DB instead of LDAP. There is not an authentication-specific log in VuFind, though you could create one fairly easily if you needed to, or you might be able to figure out counts through Apache log analysis (though the Apache log won't tell you which user is trying to log in, of course). Thanks, works. 3a. In VuFind 1.x, all of the database writing is done through PEAR's DB abstraction library. The classes representing the database tables are found in web/services/MyResearch/lib, and they are called from the controllers in the various other web/services directories. Thanks (nevertheless sounds complicated… :)) 3b. The default homepage layout can be found in web/interface/themes/[your theme]/Search/home.tpl -- and if you need to set extra variables for use in this template, you can modify the corresponding controller in the web/services directory. Thanks Please let me know if you still have questions! Thanks a lot, indeed seems like I'm going to harass this mail list… - Demian Thanks a lot Demian! ________________________________ מ: Demian Katz <dem...@vi...> נשלח: יום שני 20 ינואר 2014 15:30 אל: Assaf Weinrib; vuf...@li... נושא: RE: A few questions please 1a/b. I might be able to answer these better if I understood more about what you're hoping to do with sessions. The main purpose of the VuFind session is to track the user's login status and to remember search history. Is there a reason you wish to make these expire at a particular rate? 1c. The search history shows all searches performed during the current session... there should be a link to it in the footer, or you can go to the Search/History URL within VuFind. 2. If you are not using LDAP and want VuFind to manage its own internal accounts, change the authentication setting to use DB instead of LDAP. There is not an authentication-specific log in VuFind, though you could create one fairly easily if you needed to, or you might be able to figure out counts through Apache log analysis (though the Apache log won't tell you which user is trying to log in, of course). 3a. In VuFind 1.x, all of the database writing is done through PEAR's DB abstraction library. The classes representing the database tables are found in web/services/MyResearch/lib, and they are called from the controllers in the various other web/services directories. 3b. The default homepage layout can be found in web/interface/themes/[your theme]/Search/home.tpl -- and if you need to set extra variables for use in this template, you can modify the corresponding controller in the web/services directory. Please let me know if you still have questions! - Demian ________________________________ From: Assaf Weinrib [as...@po...] Sent: Saturday, January 18, 2014 5:27 PM To: vuf...@li... Subject: [VuFind-General] A few questions please בס"ד Hi, After a pretty long period of 'getting started' I was playing with the software a bit, took a look on the DB and please have a few more questions: 1. I saw that in the session table – a single session was calculated until I was closing the browser, so I went to the config.ini saw it under the 'session' section and changed it to be '60' just to see what will happen. Then – I indeed see that running a new search query after each 60 seconds causes the ID of this session to be promoted but it's still all under the same session which is actually the same behavior as before except for the ID that is being changed. (The new ID overrides the old one and the old ID cannot be found), so: a. Is that the expected behavior? b. Is there a way to define that after period of 'x' seconds – create a new entry in the 'sessions' table? c. I also noticed that each search ('lookfor') overrides the previous, meaning – there is no way to see ALL values that were searched during this session. Is there a configuration parameter/workaround for allowing it? 2. I added a user entry to the user table but still cannot 'login' - is it something with the authentication method in the config.ini? (Currently set to LDAP). Which log tracks the authentication attempts? 3. I need some directing in the code, I am please looking for the code sections that handle: a. Writing down to the DB. b. GUI of main vufind homepage. Thanks a lot in advance. Assaf We |
From: Václav R. <xro...@gm...> - 2014-01-21 11:27:56
|
Hi You can also turn on Statistics in your config.ini and use Db as a target for gathering statistics, ie.: [Statistics] mode[] = Db I did a custom query for our module that returns the most searched queries for the given time range (taking into account user sessions, so the queries searched multiple times in the same session are counted only once) and filtering out searches, that returned empty result set: https://github.com/moravianlibrary/VuFind-2.x/blob/master/module/VuFind/src/VuFind/Db/Table/UserStatsFields.php#L125 I can create a pull request on Github if someone is interested. Vasek 2014/1/21 Assaf Weinrib <as...@po...>: > בס"ד > > > 1a/b. I might be able to answer these better if I understood more about what > you're hoping to do with sessions. The main purpose of the VuFind session is > to track the user's login status and to remember search history. Is there a > reason you wish to make these expire at a particular rate? > > My plan is as follows: > > I want to analyze the searches that have been performed on my system, e.g. > > How many times the term <TERM> was searched? > > How many search queries have been triggered today? > > And many more > > > > So for the above I guess I can use the 'search' table, without involving the > session table. > > Is there a way to extract the search queries out of the BLOB?? (I was trying > using the 2char cast but didn't seem to help). > > > > Later on I would also like to analyze multiple queries that a single user > was running during a single session – that's the aspect from which I was > asking why the 'lookfor' value is being overridden for the session. > > How would you suggest me to extract this data from within the DB?? - But is > just to understand the System design and business logic, if i'll have a > solution for the above part i would be able also to perform queries for > where the session ID is the same. > > > > 1c. The search history shows all searches performed during the current > session... there should be a link to it in the footer, or you can go to the > Search/History URL within VuFind. > > Ok still looking for a straight forward DB way to gain this data. > > > > 2. If you are not using LDAP and want VuFind to manage its own internal > accounts, change the authentication setting to use DB instead of LDAP. There > is not an authentication-specific log in VuFind, though you could create one > fairly easily if you needed to, or you might be able to figure out counts > through Apache log analysis (though the Apache log won't tell you which user > is trying to log in, of course). > > Thanks, works. > > > > 3a. In VuFind 1.x, all of the database writing is done through PEAR's DB > abstraction library. The classes representing the database tables are found > in web/services/MyResearch/lib, and they are called from the controllers in > the various other web/services directories. > > Thanks (nevertheless sounds complicated… J) > > > > 3b. The default homepage layout can be found in web/interface/themes/[your > theme]/Search/home.tpl -- and if you need to set extra variables for use in > this template, you can modify the corresponding controller in the > web/services directory. > Thanks > > > > Please let me know if you still have questions! > > Thanks a lot, indeed seems like I'm going to harass this mail list… > > - Demian > > > > Thanks a lot Demian! > > > > > > ________________________________ > מ: Demian Katz <dem...@vi...> > נשלח: יום שני 20 ינואר 2014 15:30 > אל: Assaf Weinrib; vuf...@li... > נושא: RE: A few questions please > > 1a/b. I might be able to answer these better if I understood more about what > you're hoping to do with sessions. The main purpose of the VuFind session is > to track the user's login status and to remember search history. Is there a > reason you wish to make these expire at a particular rate? > > 1c. The search history shows all searches performed during the current > session... there should be a link to it in the footer, or you can go to the > Search/History URL within VuFind. > > 2. If you are not using LDAP and want VuFind to manage its own internal > accounts, change the authentication setting to use DB instead of LDAP. There > is not an authentication-specific log in VuFind, though you could create one > fairly easily if you needed to, or you might be able to figure out counts > through Apache log analysis (though the Apache log won't tell you which user > is trying to log in, of course). > > 3a. In VuFind 1.x, all of the database writing is done through PEAR's DB > abstraction library. The classes representing the database tables are found > in web/services/MyResearch/lib, and they are called from the controllers in > the various other web/services directories. > > 3b. The default homepage layout can be found in web/interface/themes/[your > theme]/Search/home.tpl -- and if you need to set extra variables for use in > this template, you can modify the corresponding controller in the > web/services directory. > > Please let me know if you still have questions! > > - Demian > > ________________________________ > From: Assaf Weinrib [as...@po...] > Sent: Saturday, January 18, 2014 5:27 PM > To: vuf...@li... > Subject: [VuFind-General] A few questions please > > בס"ד > > Hi, > > After a pretty long period of 'getting started' I was playing with the > software a bit, took a look on the DB and please have a few more questions: > > 1. I saw that in the session table – a single session was calculated > until I was closing the browser, so I went to the config.ini saw it under > the 'session' section and changed it to be '60' just to see what will > happen. > > > > Then – I indeed see that running a new search query after each 60 seconds > causes the ID of this session to be promoted but it's still all under the > same session which is actually the same behavior as before except for the ID > that is being changed. > > (The new ID overrides the old one and the old ID cannot be found), so: > > > > a. Is that the expected behavior? > > b. Is there a way to define that after period of 'x' seconds – create a > new entry in the 'sessions' table? > > c. I also noticed that each search ('lookfor') overrides the previous, > meaning – there is no way to see ALL values that were searched during this > session. > > Is there a configuration parameter/workaround for allowing it? > > > > 2. I added a user entry to the user table but still cannot 'login' - > is it something with the authentication method in the config.ini? (Currently > set to LDAP). > > Which log tracks the authentication attempts? > > > > 3. I need some directing in the code, I am please looking for the code > sections that handle: > > a. Writing down to the DB. > > b. GUI of main vufind homepage. > > > > Thanks a lot in advance. > > Assaf We > > > > > > > > > > > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > VuFind-General mailing list > VuF...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-general > |
From: Demian K. <dem...@vi...> - 2014-01-21 14:36:16
|
Unfortunately, the advanced statistics gathering was not added until VuFind 2.x. VuFind 1.x does have a stats option, but data is only collected to Solr; there is no database option in that version. - Demian > -----Original Message----- > From: Václav Rosecký [mailto:xro...@gm...] > Sent: Tuesday, January 21, 2014 6:28 AM > To: Assaf Weinrib > Cc: Demian Katz; vuf...@li... > Subject: Re: [VuFind-General] A few questions please > > Hi > > You can also turn on Statistics in your config.ini and use Db as a > target for gathering statistics, ie.: > > [Statistics] > mode[] = Db > > I did a custom query for our module that returns the most searched > queries for the given time range (taking into account user sessions, > so the queries searched multiple times in the same session are counted > only once) and filtering out searches, that returned empty result set: > > https://github.com/moravianlibrary/VuFind- > 2.x/blob/master/module/VuFind/src/VuFind/Db/Table/UserStatsFields.php#L125 > > I can create a pull request on Github if someone is interested. > > Vasek > > 2014/1/21 Assaf Weinrib <as...@po...>: > > בס"ד > > > > > > 1a/b. I might be able to answer these better if I understood more about what > > you're hoping to do with sessions. The main purpose of the VuFind session is > > to track the user's login status and to remember search history. Is there a > > reason you wish to make these expire at a particular rate? > > > > My plan is as follows: > > > > I want to analyze the searches that have been performed on my system, e.g. > > > > How many times the term <TERM> was searched? > > > > How many search queries have been triggered today? > > > > And many more > > > > > > > > So for the above I guess I can use the 'search' table, without involving the > > session table. > > > > Is there a way to extract the search queries out of the BLOB?? (I was trying > > using the 2char cast but didn't seem to help). > > > > > > > > Later on I would also like to analyze multiple queries that a single user > > was running during a single session – that's the aspect from which I was > > asking why the 'lookfor' value is being overridden for the session. > > > > How would you suggest me to extract this data from within the DB?? - But is > > just to understand the System design and business logic, if i'll have a > > solution for the above part i would be able also to perform queries for > > where the session ID is the same. > > > > > > > > 1c. The search history shows all searches performed during the current > > session... there should be a link to it in the footer, or you can go to the > > Search/History URL within VuFind. > > > > Ok still looking for a straight forward DB way to gain this data. > > > > > > > > 2. If you are not using LDAP and want VuFind to manage its own internal > > accounts, change the authentication setting to use DB instead of LDAP. There > > is not an authentication-specific log in VuFind, though you could create one > > fairly easily if you needed to, or you might be able to figure out counts > > through Apache log analysis (though the Apache log won't tell you which user > > is trying to log in, of course). > > > > Thanks, works. > > > > > > > > 3a. In VuFind 1.x, all of the database writing is done through PEAR's DB > > abstraction library. The classes representing the database tables are found > > in web/services/MyResearch/lib, and they are called from the controllers in > > the various other web/services directories. > > > > Thanks (nevertheless sounds complicated… J) > > > > > > > > 3b. The default homepage layout can be found in web/interface/themes/[your > > theme]/Search/home.tpl -- and if you need to set extra variables for use in > > this template, you can modify the corresponding controller in the > > web/services directory. > > Thanks > > > > > > > > Please let me know if you still have questions! > > > > Thanks a lot, indeed seems like I'm going to harass this mail list… > > > > - Demian > > > > > > > > Thanks a lot Demian! > > > > > > > > > > > > ________________________________ > > מ: Demian Katz <dem...@vi...> > > נשלח: יום שני 20 ינואר 2014 15:30 > > אל: Assaf Weinrib; vuf...@li... > > נושא: RE: A few questions please > > > > 1a/b. I might be able to answer these better if I understood more about what > > you're hoping to do with sessions. The main purpose of the VuFind session is > > to track the user's login status and to remember search history. Is there a > > reason you wish to make these expire at a particular rate? > > > > 1c. The search history shows all searches performed during the current > > session... there should be a link to it in the footer, or you can go to the > > Search/History URL within VuFind. > > > > 2. If you are not using LDAP and want VuFind to manage its own internal > > accounts, change the authentication setting to use DB instead of LDAP. There > > is not an authentication-specific log in VuFind, though you could create one > > fairly easily if you needed to, or you might be able to figure out counts > > through Apache log analysis (though the Apache log won't tell you which user > > is trying to log in, of course). > > > > 3a. In VuFind 1.x, all of the database writing is done through PEAR's DB > > abstraction library. The classes representing the database tables are found > > in web/services/MyResearch/lib, and they are called from the controllers in > > the various other web/services directories. > > > > 3b. The default homepage layout can be found in web/interface/themes/[your > > theme]/Search/home.tpl -- and if you need to set extra variables for use in > > this template, you can modify the corresponding controller in the > > web/services directory. > > > > Please let me know if you still have questions! > > > > - Demian > > > > ________________________________ > > From: Assaf Weinrib [as...@po...] > > Sent: Saturday, January 18, 2014 5:27 PM > > To: vuf...@li... > > Subject: [VuFind-General] A few questions please > > > > בס"ד > > > > Hi, > > > > After a pretty long period of 'getting started' I was playing with the > > software a bit, took a look on the DB and please have a few more questions: > > > > 1. I saw that in the session table – a single session was calculated > > until I was closing the browser, so I went to the config.ini saw it under > > the 'session' section and changed it to be '60' just to see what will > > happen. > > > > > > > > Then – I indeed see that running a new search query after each 60 seconds > > causes the ID of this session to be promoted but it's still all under the > > same session which is actually the same behavior as before except for the ID > > that is being changed. > > > > (The new ID overrides the old one and the old ID cannot be found), so: > > > > > > > > a. Is that the expected behavior? > > > > b. Is there a way to define that after period of 'x' seconds – create a > > new entry in the 'sessions' table? > > > > c. I also noticed that each search ('lookfor') overrides the previous, > > meaning – there is no way to see ALL values that were searched during this > > session. > > > > Is there a configuration parameter/workaround for allowing it? > > > > > > > > 2. I added a user entry to the user table but still cannot 'login' - > > is it something with the authentication method in the config.ini? (Currently > > set to LDAP). > > > > Which log tracks the authentication attempts? > > > > > > > > 3. I need some directing in the code, I am please looking for the code > > sections that handle: > > > > a. Writing down to the DB. > > > > b. GUI of main vufind homepage. > > > > > > > > Thanks a lot in advance. > > > > Assaf We > > > > > > > > > > > > > > > > > > > > > > > > > > ---------------------------------------------------------------------------- > -- > > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > > Learn Why More Businesses Are Choosing CenturyLink Cloud For > > Critical Workloads, Development Environments & Everything In Between. > > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > > _______________________________________________ > > VuFind-General mailing list > > VuF...@li... > > https://lists.sourceforge.net/lists/listinfo/vufind-general > > |
From: Assaf W. <as...@po...> - 2014-01-22 11:11:47
|
Thanks a lot to you both! I'm checking the suggested options. Thanks for the meanwhile ________________________________________ מ: Demian Katz <dem...@vi...> נשלח: יום שלישי 21 ינואר 2014 14:36 אל: Václav Rosecký; Assaf Weinrib עותק: vuf...@li... נושא: RE: [VuFind-General] A few questions please Unfortunately, the advanced statistics gathering was not added until VuFind 2.x. VuFind 1.x does have a stats option, but data is only collected to Solr; there is no database option in that version. - Demian > -----Original Message----- > From: Václav Rosecký [mailto:xro...@gm...] > Sent: Tuesday, January 21, 2014 6:28 AM > To: Assaf Weinrib > Cc: Demian Katz; vuf...@li... > Subject: Re: [VuFind-General] A few questions please > > Hi > > You can also turn on Statistics in your config.ini and use Db as a > target for gathering statistics, ie.: > > [Statistics] > mode[] = Db > > I did a custom query for our module that returns the most searched > queries for the given time range (taking into account user sessions, > so the queries searched multiple times in the same session are counted > only once) and filtering out searches, that returned empty result set: > > https://github.com/moravianlibrary/VuFind- > 2.x/blob/master/module/VuFind/src/VuFind/Db/Table/UserStatsFields.php#L125 > > I can create a pull request on Github if someone is interested. > > Vasek > > 2014/1/21 Assaf Weinrib <as...@po...>: > > בס"ד > > > > > > 1a/b. I might be able to answer these better if I understood more about what > > you're hoping to do with sessions. The main purpose of the VuFind session is > > to track the user's login status and to remember search history. Is there a > > reason you wish to make these expire at a particular rate? > > > > My plan is as follows: > > > > I want to analyze the searches that have been performed on my system, e.g. > > > > How many times the term <TERM> was searched? > > > > How many search queries have been triggered today? > > > > And many more > > > > > > > > So for the above I guess I can use the 'search' table, without involving the > > session table. > > > > Is there a way to extract the search queries out of the BLOB?? (I was trying > > using the 2char cast but didn't seem to help). > > > > > > > > Later on I would also like to analyze multiple queries that a single user > > was running during a single session – that's the aspect from which I was > > asking why the 'lookfor' value is being overridden for the session. > > > > How would you suggest me to extract this data from within the DB?? - But is > > just to understand the System design and business logic, if i'll have a > > solution for the above part i would be able also to perform queries for > > where the session ID is the same. > > > > > > > > 1c. The search history shows all searches performed during the current > > session... there should be a link to it in the footer, or you can go to the > > Search/History URL within VuFind. > > > > Ok still looking for a straight forward DB way to gain this data. > > > > > > > > 2. If you are not using LDAP and want VuFind to manage its own internal > > accounts, change the authentication setting to use DB instead of LDAP. There > > is not an authentication-specific log in VuFind, though you could create one > > fairly easily if you needed to, or you might be able to figure out counts > > through Apache log analysis (though the Apache log won't tell you which user > > is trying to log in, of course). > > > > Thanks, works. > > > > > > > > 3a. In VuFind 1.x, all of the database writing is done through PEAR's DB > > abstraction library. The classes representing the database tables are found > > in web/services/MyResearch/lib, and they are called from the controllers in > > the various other web/services directories. > > > > Thanks (nevertheless sounds complicated… J) > > > > > > > > 3b. The default homepage layout can be found in web/interface/themes/[your > > theme]/Search/home.tpl -- and if you need to set extra variables for use in > > this template, you can modify the corresponding controller in the > > web/services directory. > > Thanks > > > > > > > > Please let me know if you still have questions! > > > > Thanks a lot, indeed seems like I'm going to harass this mail list… > > > > - Demian > > > > > > > > Thanks a lot Demian! > > > > > > > > > > > > ________________________________ > > מ: Demian Katz <dem...@vi...> > > נשלח: יום שני 20 ינואר 2014 15:30 > > אל: Assaf Weinrib; vuf...@li... > > נושא: RE: A few questions please > > > > 1a/b. I might be able to answer these better if I understood more about what > > you're hoping to do with sessions. The main purpose of the VuFind session is > > to track the user's login status and to remember search history. Is there a > > reason you wish to make these expire at a particular rate? > > > > 1c. The search history shows all searches performed during the current > > session... there should be a link to it in the footer, or you can go to the > > Search/History URL within VuFind. > > > > 2. If you are not using LDAP and want VuFind to manage its own internal > > accounts, change the authentication setting to use DB instead of LDAP. There > > is not an authentication-specific log in VuFind, though you could create one > > fairly easily if you needed to, or you might be able to figure out counts > > through Apache log analysis (though the Apache log won't tell you which user > > is trying to log in, of course). > > > > 3a. In VuFind 1.x, all of the database writing is done through PEAR's DB > > abstraction library. The classes representing the database tables are found > > in web/services/MyResearch/lib, and they are called from the controllers in > > the various other web/services directories. > > > > 3b. The default homepage layout can be found in web/interface/themes/[your > > theme]/Search/home.tpl -- and if you need to set extra variables for use in > > this template, you can modify the corresponding controller in the > > web/services directory. > > > > Please let me know if you still have questions! > > > > - Demian > > > > ________________________________ > > From: Assaf Weinrib [as...@po...] > > Sent: Saturday, January 18, 2014 5:27 PM > > To: vuf...@li... > > Subject: [VuFind-General] A few questions please > > > > בס"ד > > > > Hi, > > > > After a pretty long period of 'getting started' I was playing with the > > software a bit, took a look on the DB and please have a few more questions: > > > > 1. I saw that in the session table – a single session was calculated > > until I was closing the browser, so I went to the config.ini saw it under > > the 'session' section and changed it to be '60' just to see what will > > happen. > > > > > > > > Then – I indeed see that running a new search query after each 60 seconds > > causes the ID of this session to be promoted but it's still all under the > > same session which is actually the same behavior as before except for the ID > > that is being changed. > > > > (The new ID overrides the old one and the old ID cannot be found), so: > > > > > > > > a. Is that the expected behavior? > > > > b. Is there a way to define that after period of 'x' seconds – create a > > new entry in the 'sessions' table? > > > > c. I also noticed that each search ('lookfor') overrides the previous, > > meaning – there is no way to see ALL values that were searched during this > > session. > > > > Is there a configuration parameter/workaround for allowing it? > > > > > > > > 2. I added a user entry to the user table but still cannot 'login' - > > is it something with the authentication method in the config.ini? (Currently > > set to LDAP). > > > > Which log tracks the authentication attempts? > > > > > > > > 3. I need some directing in the code, I am please looking for the code > > sections that handle: > > > > a. Writing down to the DB. > > > > b. GUI of main vufind homepage. > > > > > > > > Thanks a lot in advance. > > > > Assaf We > > > > > > > > > > > > > > > > > > > > > > > > > > ---------------------------------------------------------------------------- > -- > > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > > Learn Why More Businesses Are Choosing CenturyLink Cloud For > > Critical Workloads, Development Environments & Everything In Between. > > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > > _______________________________________________ > > VuFind-General mailing list > > VuF...@li... > > https://lists.sourceforge.net/lists/listinfo/vufind-general > > |