JP6337490B2 - Electronic book management program, electronic book management method, and electronic book management apparatus - Google Patents

Description

  The present invention relates to an electronic book management program, an electronic book management method, and an electronic book management apparatus.

  In recent years, in addition to books printed on paper, electronic books that can be browsed on a portable terminal or the like have also appeared. In the future, it is thought that libraries will handle electronic books. However, when handling electronic books in a library, it is necessary to prevent one electronic book from being lent to multiple people at the same time due to the nature of the library.

  Note that Patent Literature 1 discloses a technology that appropriately realizes the lending of a parking lot that is a loan target and effectively uses the loan target.

JP 2005-267601 A

  In the case of electronic books, unlike paper books, books can be exchanged and returned instantly, so it is considered easy to lend in short time units. For example, if a user who borrows an electronic book can lend an electronic book to another user for a period during which the user can lend it to another user, use promotion of the electronic book can be expected.

  However, Patent Literature 1 does not disclose a technique for estimating a period during which a user who borrows an electronic book may think that the electronic book may be lent to another user in the future.

  In one aspect, an object of the present invention is to provide an electronic book management program, an electronic book management method, and an electronic book management apparatus capable of promoting the use of electronic book data.

  In one aspect, the electronic book management program is an electronic book management program having an exclusive control function for rejecting simultaneous access from a plurality of access sources with respect to one electronic book data. Allowing access to the one electronic book data is started, and access to the one electronic book data by the first access source is possible based on an access history to the electronic book data from the first access source Estimating the future time when the gender is below a predetermined standard, and rejecting access to the one electronic book data from the first access source for the estimated time, and the one from the second access source It is a program for causing a computer to execute processing for performing control to permit access to electronic book data.

  In one aspect, the electronic book management method is such that a computer having an exclusive control function that rejects simultaneous access from a plurality of access sources for one electronic book data is sent to the one electronic book data from the first access source. The access possibility to the one electronic book data by the first access source is below a predetermined standard based on the access history to the electronic book data from the first access source. For the estimated time period, the access to the one electronic book data from the first access source is denied, and the access to the one electronic book data from the second access source is denied. It is an electronic book management method for performing processing that performs permissible control.

  In one aspect, the electronic book management apparatus is an electronic book management apparatus having an exclusive control function for rejecting simultaneous access from a plurality of access sources with respect to one electronic book data. The access to the one electronic book data by the first access source based on the access history to the electronic book data from the first access source when the permission of access to the one electronic book data is started An estimator that estimates a future time that is less than or equal to a predetermined criterion, and rejects access to the one electronic book data from the first access source for the time estimated by the estimator; And a control unit that performs control to allow access to the one electronic book data from two access sources.

  The use of electronic book data can be promoted.

It is a figure showing roughly the composition of the electronic book management system concerning one embodiment. FIG. 2A is a diagram illustrating a hardware configuration of the library server, and FIG. 2B is a diagram illustrating a hardware configuration of the user terminal. It is a functional block diagram of a library server and a user terminal. It is a figure which shows the data structure of user DB. It is a figure which shows the data structure of library DB. FIG. 6A is a diagram illustrating a data structure of the rental book DB, and FIG. 6B is a diagram illustrating a data structure of the reading time DB. It is a figure which shows the data structure of genre DB. It is a figure which shows the data structure of access right management DB. It is a flowchart (the 1) which shows the process at the time of rental by an electronic book management system. It is a flowchart (the 2) which shows the process at the time of rental by an electronic book management system. It is a flowchart (the 3) which shows the process at the time of rental by an electronic book management system. It is a flowchart which shows the specific process of the required reading time calculation process of FIG. It is a flowchart (the 4) which shows the process at the time of rental by an electronic book management system. FIG. 14A is a diagram illustrating an example of an authentication screen, and FIG. 14B is a diagram illustrating an example of an authentication error screen. FIG. 15A is a diagram illustrating an example of a lending request book input screen, and FIG. 15B is a diagram illustrating an example of a time lending screen. It is a figure which shows an example of a lending possible data list display screen. It is a figure which shows an example of an approval screen. FIG. 18A is a diagram illustrating an example of an approval / rejection result screen for transmitting approval, and FIG. 18B is a diagram illustrating an example of an approval / rejection result screen for transmitting rejection. It is a flowchart (the 1) which shows the process at the time of the browsing by an electronic book management system. It is a flowchart (the 2) which shows the process at the time of the browsing by an electronic book management system. It is a figure which shows an example of a browsing screen.

  Hereinafter, an embodiment of an electronic book management system will be described in detail with reference to FIGS. FIG. 1 schematically shows an electronic book management system 100 according to an embodiment.

  The electronic book management system 100 of this embodiment is provided with the library server 10 as an electronic book management apparatus, and the user terminal 20, as shown in FIG. The library server 10 and the user terminal 20 are connected to a network 80 such as the Internet or a LAN. This electronic book management system 100 is a system that enables electronic book data lending procedures and electronic book data browsing on a screen (provided from the library server 10) displayed on a browser in the user terminal 20.

  The library server 10 is a server that is installed in a data center or a library and manages electronic books. FIG. 2A shows the hardware configuration of the library server 10. As shown in FIG. 2A, the library server 10 includes a CPU (Central Processing Unit) 90, a ROM (Read Only Memory) 92, a RAM (Random Access Memory) 94, and a storage unit (here, an HDD (Hard Disk Drive)). ) 96, a network interface 97, a portable storage medium drive 99, and the like. Each component of the library server 10 is connected to a bus 98. In the library server 10, a program (including an electronic book management program) stored in the ROM 92 or the HDD 96, or a program (including an electronic book management program) read from the portable storage medium 91 by the portable storage medium drive 99. The functions shown in FIG. 3 are realized by the CPU 90 executing. Note that each function of FIG. 3 will be described later.

  The user terminal 20 is a terminal for a user who has borrowed an electronic book to browse the electronic book. The user terminal 20 is assumed to be a terminal such as a PC, a tablet terminal, or a smartphone. FIG. 2B shows the hardware configuration of the user terminal 20. As shown in FIG. 2B, the user terminal 20 includes a CPU 190, a ROM 192, a RAM 194, a storage unit (HDD) 196, a display unit 193, an input unit 195, a network interface 197, a portable storage medium drive 199, and the like. Each component of the user terminal 20 is connected to the bus 198. Also in the user terminal 20, the function shown in FIG. 3 is implement | achieved because CPU190 runs a program.

  FIG. 3 shows a functional block diagram of the library server 10 and the user terminal 20. As shown in FIG. 3, in the library server 10, the CPU 90 executes a program (including an electronic book management program), so that the functions as the lending processing unit 12 as the estimation unit and the control unit, and the information registration unit 14 are provided. It has been realized. In the user terminal 20, functions as the display processing unit 22 and the input processing unit 24 are realized by the CPU 190 executing the program. 3 also shows a user DB (database) 31, a book DB 32, a rental book DB 33, a reading time DB 34, a genre DB 35, and an access right management DB 36 stored in the HDD 96 of the library server 10.

  The lending processing unit 12 performs electronic book lending processing, that is, access right setting processing for electronic book data, transmission processing of an electronic book data browsing screen for users having access rights, and the like. Note that the lending processing unit 12 has a function of allowing only one user to access even if there is simultaneous access from a plurality of users (access sources) to one electronic book data, that is, an exclusive control function. .

  The information registration unit 14 acquires a browsing history of electronic book data by the user, acquires a reading time log of the user based on the browsing history, and calculates a reading speed for each user and a reading speed for each genre. Further, the information registration unit 14 registers the user's reading time log in the reading time DB 34 and registers the reading speed in the user DB 31 and the genre DB 35.

  The display processing unit 22 displays the screen transmitted from the lending processing unit 12 on the display unit 193 (in the browser). The input processing unit 24 transmits information input from a user using the user terminal 20 and instructions from the user (instructions input on the browser) to the lending processing unit 12 of the library server 10.

  The user DB 31 is a database that manages users who use the library server 10, that is, users who use the electronic book data of the library. FIG. 4 shows the data structure of the user DB 31. As shown in FIG. 4, the user DB 31 includes fields of “user ID”, “name”, “password”, “reading speed”, “total number of reading pages”, and “total reading time”. In the “user ID” field, identification information assigned to each user is stored. The name of the user is stored in the “name” field. The “password” field stores a password assigned to the user or set by the user. The “reading speed” field stores the average time (minutes) required to read one page calculated from the total number of pages read by the user and the total reading time. In the “total number of reading pages” field, the total number of pages of the electronic book data browsed by the user is stored. The “total reading time” field stores the total time that the user browsed the electronic book data.

  The book DB 32 is a database that stores information on electronic books managed by the library server 10. FIG. 5 shows the data structure of the book DB 32. As shown in FIG. 5, the book DB 32 stores “book ID”, “electronic book ID”, “title”, “author”, “genre”, “total number of pages”, “number of chapter pages”, “average number of characters”. Each field. In the “book ID” field, identification information of a book (book printed on paper) is stored. In the “electronic book ID” field, identification information of electronic book data is stored. The electronic book ID is obtained by adding a two-digit number to the end of the book ID. The last two digits are different for each electronic book data. The title of the book is stored in the “title” field. In the “author” field, the author name of the book is stored. In the “genre” field, a genre name of the book, for example, “novel” or “practical” is stored. The total page number of the book is stored in the “total page number” field. The “number of chapter pages” field stores the number of pages of each chapter included in the book. The average number of characters per page is stored in the “average number of characters” field.

  The lending book DB 33 is a database that manages lending book information. FIG. 6A shows the data structure of the loan book DB 33. As shown in FIG. 6A, the loan book DB 33 has fields of “user ID”, “name”, “borrowed book”, “electronic book ID”, and “browsing page”. In the “user ID” field, the ID of the user who borrows the electronic book data is stored. In the present embodiment, the rental book DB 33 stores the ID of a user who borrows electronic book data for a regular period such as two weeks. That is, it is assumed that the ID of a user who uses electronic book data time lending, which will be described later, is not stored in the lending book DB 33. The name of the user who borrows the electronic book data is stored in the “name” field. In the “borrowed book” field, the title of the book borrowed by the user is stored. In the “electronic book ID” field, the ID of electronic book data borrowed by the user is stored. The “browsing page” field stores the number of pages when the user interrupts browsing.

  The reading time DB 34 is a database that manages a reading time log of a user who borrows electronic book data. FIG. 6B shows the data structure of the reading time DB 34. As shown in FIG. 6B, the reading time DB 34 has fields of “user ID”, “name”, “electronic book ID”, and “reading time log”. The “user ID” and “name” fields store the ID and name of the user who borrowed the electronic book data. In the “electronic book ID” field, the ID of the electronic book borrowed by the user is stored. In the “reading time log” field, a log of the date and time when the user browsed the electronic book data is stored.

  The genre DB 35 is a database that manages the reading speed when all users who borrowed electronic book data read books of each genre. FIG. 7 shows the data structure of the genre DB 35. As shown in FIG. 7, the genre DB 35 includes fields of “genre”, “reading speed”, “total number of reading pages”, and “total reading time”. In the “genre” field, genre names such as “novel” and “practical” are stored. The “reading speed” field stores an average time (minutes) required to read one page of electronic books of each genre calculated from the total number of reading pages and the total reading time. The “total number of reading pages” field stores the total number of pages of electronic book data of each genre read by the user. The “total reading time” field stores the total time that the electronic book data of each genre is read by the user.

  The access right management DB 36 is a database that manages which users have access rights to electronic book data. FIG. 8 shows the data structure of the access right management DB 36. As shown in FIG. 8, the access right management DB 36 has fields of “electronic book ID”, “access right”, “user ID”, “name”, and “access right grant period”. The “electronic book ID” field stores the ID of the electronic book data, and the “access right” field stores “O” when there is an access right, and “-” when there is no access right. The In the “user ID” and “name” fields, the ID and name of a user to whom an access right is given or to be given in the future are stored. The “access right grant period” field stores an access right grant period for the user.

(Processing at the time of loan)
Next, processing at the time of lending electronic book data in the present embodiment will be described in detail along the flowcharts of FIGS. 9 to 13 with reference to other drawings as appropriate. Note that the lending of electronic book data means giving an access right to the electronic book data to a user who has made a request for lending electronic book data. In the present embodiment, if the electronic book data is not lent, the electronic book data is lent to the user for a regular period such as two weeks. On the other hand, when the electronic book data is being lent, a time lending process for the electronic book data that has already been lent to other users is executed.

  FIGS. 9 to 13 are flowcharts showing a series of processes at the time of lending electronic book data by the user terminal 20 (display processing unit 22 and input processing unit 24) and the library server 10 (lending processing unit 12). Has been. In the flowcharts of FIGS. 9 to 13, each process / determination is arranged in consideration of the timing of the process / determination between the user terminal 20 and the library server 10.

  In the process of FIG. 9, first, the input processing unit 24 of the user terminal 20 waits until receiving a request for lending electronic book data from the user in step S <b> 10. The lending request in this case is made when the user accesses the address of the library server 10 on the browser. If the determination in step S10 is affirmed, the process proceeds to step S12. If transfering it to step S12, the input process part 24 will transmit a rental request | requirement with respect to the library server 10 (lending process part 12).

  On the other hand, the lending processing unit 12 of the library server 10 stands by until a lending request is received from the user terminal 20 (input processing unit 24) in step S110. Therefore, in the lending processing unit 12, the input processing unit 24 proceeds to step S112 when the processing of step S12 is performed.

  In step S112, the lending processing unit 12 transmits data of the user ID and password input screen to the user terminal 20 (display processing unit 22). Assume that the input screen in this case is an authentication screen (a screen including user ID and password input fields and send and cancel buttons) as shown in FIG.

  On the other hand, after step S12, the display processing unit 22 of the user terminal 20 stands by until data of the user ID and password input screen is received from the lending processing unit 12 of the library server 10 in step S14. Therefore, as described above, when the input screen data is transmitted from the library server 10 in step S112, the display processing unit 22 proceeds to step S16.

  In step S <b> 16, the display processing unit 22 displays a user ID and password input screen (FIG. 14A) on the display unit 193 of the user terminal 20 (in the browser). Next, in step S18, the input processing unit 24 stands by until receiving an input of a user ID and a password. In this case, when the user inputs the user ID and password using the input unit 195 of the user terminal 20 and presses the transmission button, the process proceeds to step S20.

  If transfering it to step S20, the input process part 24 will transmit a user ID and a password with respect to the library server 10 (lending process part 12). In addition, after the process of step S20 is complete | finished, it transfers to step S22.

  On the other hand, the lending processing unit 12 of the library server 10 stands by after step S112 until the user ID and password are transmitted from the user terminal 20 (input processing unit 24) in step S114. Accordingly, the lending processing unit 12 proceeds to step S116 when the user ID or the like is transmitted from the input processing unit 24 in step S20.

  If transfering it to step S116, the lending process part 12 will authenticate a user using the transmitted user ID and password, and user DB31. Thereafter, the process proceeds to step S118.

  In step S118, the lending processing unit 12 determines whether the authentication is successful. If the determination here is negative, the data of the authentication error screen (FIG. 14B) is created and transmitted to the user terminal 20 (display processing unit 22). The process ends. On the other hand, if the determination in step S118 is affirmative, the process proceeds to step S130 in FIG. On the other hand, the user terminal 20 (display processing unit 22) determines whether or not the authentication error screen data has been received in step S22. If the determination here is affirmative, the authentication error screen of FIG. 14B is displayed on the display unit 193 (in the browser) of the user terminal 20 in step S24, and all the processes of FIGS. finish. On the other hand, if the determination in step S22 is negative, the process proceeds to step S30 in FIG.

  When the lending processing unit 12 of the library server 10 proceeds to step S <b> 130 of FIG. 10, the lending request book input screen data is transmitted to the display processing unit 22 of the user terminal 20. The loan request book input screen is a screen including an input field for a title of the loan request book as shown in FIG. 15A and a send button. In addition, the lending request book input screen may be provided with a search function for electronic books.

  On the other hand, on the user terminal 20 side, in step S30, the display processing unit 22 is on standby until it receives data on the desired book input screen from the library server 10. Therefore, at the timing when the process of step S130 is performed on the library server 10 side, the display processing unit 22 proceeds to step S32.

  If transfering it to step S32, the display process part 22 will display the rental wish book input screen shown to Fig.15 (a) on the display part 193 (in a browser). Next, in step S34, the input processing unit 24 stands by until receiving an input of a book desired to be lent. In other words, when the user inputs a desired loan title on the desired loan book input screen via the input unit 195 and presses the send button, the input processing unit 24 proceeds to step S36.

  When the process proceeds to step S36, the input processing unit 24 transmits information on the book to be lent to the lending processing unit 12 of the library server 10.

  On the other hand, on the library server 10 side, after step S130, in step S132, the lending processing unit 12 is on standby until it receives information on the book to be lent. Therefore, the lending processing unit 12 proceeds to step S134 when the process of step S36 is performed on the user terminal 20 side.

  In step S134, the lending processing unit 12 refers to the book DB 32 and the lending book DB 33, and determines whether all the electronic book data of the lending desired book is being lent. Specifically, the lending processing unit 12 determines whether or not the lending request book is lent based on whether or not all of the electronic book data of the lending request book included in the book DB 32 is registered in the lending book DB 33. To do.

  Next, in step S136, it is determined whether or not all of the electronic book data of the book to be lent is being lent. If the determination here is negative, that is, if it is not lent, the process proceeds to step S140. In step S140, the lending processing unit 12 grants the access right to the electronic book data of the book desired to be lent to the user for a normal period (for example, two weeks). In this case, the lending processing unit 12 registers the lending book information and the user information in the lending book DB 33. In addition, the lending processing unit 12 registers information on the book to be lent and user information in the access right management DB 36. In the access right management DB 36, in addition to the electronic book ID, user ID, and name, an access right “◯” and an access right grant period, for example, a period of two weeks from the loan date are registered. Although not shown in FIG. 10, when the access right is granted, the lending processing unit 12 transmits to the user terminal 20 (display processing unit 22) that the access right has been granted. Then, the user terminal 20 displays on the display unit 193 (in the browser) that the access right has been granted, and ends all the processes in FIGS.

  On the other hand, if the determination in step S136 is affirmative, that is, if the book to lend is lent, the process proceeds to step S138, and the lending processing unit 12 displays the data on the time lending screen on the user terminal 20 (display). To the processing unit 22). After step S138, the process proceeds to step S150 in FIG.

  On the other hand, on the user terminal 20 side, after step S36, the display processing unit 22 stands by until data on the time lending screen is received from the lending processing unit 12 of the library server 10 in step S38. Therefore, the display processing unit 22 proceeds to step S40 at the timing when the process of step S138 is performed on the library server 10 side.

  In step S40, the display processing unit 22 displays the time rental screen on the display unit 193 (in the browser). The time lending screen is a screen as shown in FIG. When the user wishes to lend time, he / she presses the “Yes” button after inputting the number of pages on the time lending screen, and presses the “No” button on the time screen when he / she does not desire lending.

  After step S40 is performed, when the process proceeds to step S50 in FIG. 11, the input processing unit 24 determines whether or not an input for requesting time lending has been received. If the determination in step S50 is negative, that is, if the user presses the “No” button on the time lending screen (FIG. 15B), all the processes in FIGS. 9 to 13 are terminated. On the other hand, if the determination in step S50 is affirmative, that is, if the user inputs the number of pages to be read on the time lending screen and presses the “Yes” button, the process proceeds to step S52.

  If transfering it to step S52, the input process part 24 will transmit to the lending process part 12 of the library server 10 with the information of the number of pages of the part which wants to read the information of time lending hope. The time lending request information can be said to be a request (first request) for accessing electronic book data. Further, it can be said that the information on the number of pages of the portion to be read is information indicating a location to be accessed in the electronic book data.

  On the other hand, on the library server 10 side, after step S138 in FIG. 10, in step S150 in FIG. 11, the lending processing unit 12 stands by until receiving the time lending request information. Therefore, the lending processing unit 12 proceeds to step S154 at the timing when step S52 is performed as described above.

  In step S154, the lending processing unit 12 executes a subroutine of required reading time calculation processing. In the necessary reading time calculation process, a process according to the flowchart of FIG. 12 is executed.

  In step S200 of FIG. 12, the lending processing unit 12 determines whether or not the reading speed of the user who desires time lending is stored in the user DB 31. If the determination is negative, that is, if the reading speed of the user who wants to lend time is not stored in the user DB 31, the process proceeds to step S202. Note that a user whose reading speed is not stored in the user DB 31 is a user who does not have a past reading history such as using the electronic book management system 100 for the first time.

  If transfering it to step S202, the lending process part 12 will extract the genre of the book of time lending hope. In this case, the lending processing unit 12 refers to the book DB 32 and extracts the genre of the time lending desired book. Here, it is assumed that the title of the book for time lending is “Hitomi no Ida” and the genre is “Novel”.

  Next, in step S204, the lending processor 12 extracts the reading speed of the genre extracted from the genre DB 35 (see FIG. 7). When the genre is “novel”, reading speed = 1 (min / p) is extracted from the genre DB 35 of FIG.

  Next, in step S208, the lending processing unit 12 calculates the necessary reading time by integrating the reading speed and the number of pages. For example, when the number of pages desired by the user is 100, 1 (min / p) × 100 (p) = 100 (min) is calculated as the required reading time. Thereafter, the process proceeds to step S156 in FIG.

  On the other hand, if the determination in step S200 is affirmative, that is, if the reading speed of the user who wishes to lend time is stored in the user DB 31, the process proceeds to step S206. If transfering it to step S206, the lending process part 12 will extract a user's reading speed from user DB31. For example, when the user who desires time lending is “Shiro Suzuki”, the reading speed = 1 (min / p) is extracted.

  In the next step S208, as described above, the lending processing unit 12 adds the reading speed and the number of pages extracted in step S206 to calculate the required reading time. Thereafter, the process proceeds to step S156 in FIG.

  When the process proceeds to step S156 in FIG. 11, the lending processing unit 12 extracts one user from the lending book DB 33 that lends the book for which time lending is desired. For example, when the title of the book that is requested for time lending is “Hitoshi no Iwata”, it is assumed that the user “Hanae Yamada” is extracted from the lending book DB 33 of FIG.

  Next, in step S157, the lending processing unit 12 estimates a future time (time range) in which the possibility of access to the electronic book data by the extracted user “Yamada Hanae” is lower than a predetermined reference. Specifically, the lending processing unit 12 refers to the reading time DB 34 and acquires the reading time log of the user “Yamada Hanae” extracted in step S156. And the lending process part 12 extracts the time range in which reading is not performed more than predetermined times (for example, twice) in the reading time log. People often read at a fixed time, such as on a commuter train or at lunch. Therefore, in the present embodiment, a time range in which reading is hardly performed in the past reading time log is extracted as a time range in which the possibility of accessing electronic book data is low.

  Next, in step S158, the lending processing unit 12 determines whether or not the extracted user can lend time. In this case, the lending processing unit 12 determines that the time lending is possible when the time range extracted in step S157 includes a time range longer than the necessary reading time calculated in step S208. For example, in the case of the user “Hanae Yamada”, from the reading time log in the reading time DB 34, the time range from 8:30 to 8:00 the next time the reading is not performed more than a predetermined number of times (for example, twice). Extracted as a range. Therefore, if this time range is equal to or longer than the required reading time, the user “Yamada Hanae” is determined to be able to lend time. If the determination in step S158 is affirmed, the lending processing unit 12 proceeds to step S160.

  If transfering it to step S160, the lending process part 12 will identify the user extracted by step S156 as a user who can lend time. In step S160, the lending processing unit 12 temporarily stores information on a time range in which time lending is possible together with the specified user information. Thereafter, the process proceeds to step S162.

  In addition, when judgment of step S158 is denied, ie, when time lending is impossible, it transfers to step S162, without passing through step S160.

  In step S162, the lending processing unit 12 determines whether or not all the users lending the books desired in the time period have been extracted. If the determination in step S162 is negative, the process returns to step S156, and the processing and determination in steps S156 to S162 are repeated. If the determination in step S162 is affirmative, the process proceeds to step S164.

  If transfering it to step S164, the lending process part 12 will transmit the data of the lending possible user list display screen to the display process part 22 of the user terminal 20. Thereafter, the process proceeds to step S170 in FIG.

  On the other hand, on the user terminal 20 side, after step S52, the display processing unit 22 stands by until data on the lending available data list display screen is received from the lending processing unit 12 of the library server 10 in step S54. Therefore, at the timing when the process of step S164 is executed as described above, the display processing unit 22 proceeds to step S56.

  If transfering it to step S56, the display process part 22 will display a lending possible data list display screen. The lending available user list display screen is, for example, a screen as shown in FIG. As shown in FIG. 16, the lending available data list display screen is provided with a “lending request” button along with columns of “book name”, “electronic book ID”, and “readable time”. In the “Readable time” column, the time range that can be rented temporarily stored in step S160 is displayed. It is assumed that the user refers to the “Readable time” column and presses the “rental request” button of the electronic book data including the time that the user wants to read. After the process of step S56 is performed, the process proceeds to step S70 of FIG.

  If transfering it to step S70, the input process part 24 will wait until it receives a time rental request. Here, the input processing unit 24 proceeds to step S72 when one “lending request” button is pressed on the lending available data list display screen of FIG.

  In step S72, the input processing unit 24 transmits information on the time lending request, that is, information on which electronic book data has been selected to the lending processing unit 12 of the library server 10. Note that the time lending request information can be said to be an access request (second request) for the time (readable time) transmitted from the library server 10 to the user terminal 20.

  On the other hand, on the library server 10 side, after step S164 in FIG. 11, in step S170 in FIG. 12, the lending processing unit 12 stands by until information on the time loan request is received. Therefore, the lending process part 12 transfers to step S172 at the timing when the process of step S72 was performed in the user terminal 20 side.

  If transfering it to step S172, the lending process part 12 will transmit the data of an approval screen with respect to the user terminal 20 (display process part 22) of the user (for example, user "Yamada Hanae") who requested time lending. In addition, the approval screen as shown in FIG. 17 is displayed on the user terminal 20 of the user who has requested the time lending that has received the approval screen data. The approval screen is provided with an “approval” button for approving the time loan request and a “reject” button for rejecting the request.

  Next, in step S174, the lending processing unit 12 waits until there is an input to the approval screen and the input result, that is, the approval result is transmitted. When receiving the approval result, the lending processing unit 12 proceeds to step S176 and determines whether or not the time lending is approved. When the determination in step S176 is affirmed, the process proceeds to step S178, and the lending processing unit 12 grants the user the access right for time lending. That is, the time lending information is registered in the access right management DB 36 (FIG. 8). For example, as shown in the second record in FIG. 8, the access right grant period is registered. In the access right management DB 36 of FIG. 8, the electronic book ID “ISDN01234-5678-9012-01” is assigned to the user “Shiro Suzuki” from 8:30 on July 14 to 8:00 on July 15th. Therefore, the access right of the user “Hanae Yamada” is deprived. On the other hand, the access right is granted to the user “Hanae Yamada” during the period from July 11th to July 24th except for July 14th 8:30 to July 15th 8:00. Thereafter, the process proceeds to step S180.

  On the other hand, if the determination in step S176 is negative, that is, if the “reject” button is pressed on the approval screen of FIG. 17, the process proceeds to step S180 without passing through step S178.

  In step S180, the lending processing unit 12 transmits the approval / rejection result screen data to the display processing unit 22 of the user terminal 20. For example, after step S178, the lending processing unit 12 transmits data of an approval / rejection result screen that conveys approval as shown in FIG. On the other hand, if step S178 is not passed, the lending processing unit 12 transmits data of an approval / rejection result screen for informing rejection as shown in FIG.

  By the way, on the user terminal 20 side of the user who desires time lending, after step S72, the display processing unit 22 stands by until receiving the data of the approval / rejection result screen in step S74. Therefore, the display processing unit 22 proceeds to step S76 at the timing when the above-described processing of step S180 is performed.

  In step S76, the display processing unit 22 displays an approval / rejection result screen (FIG. 18A or FIG. 18B).

  As described above, all the processes in FIGS. 9 to 13 are completed. In the present embodiment, the electronic book data that is not being lent can be lent to the user in a regular manner (for example, for two weeks) by performing the processes of FIGS. Further, even if the electronic book data is being lent, it is highly possible that the user of the borrower cannot read it, and it is possible to lend it for a period of time during which only the number of pages that the user wants to read can be read.

(Processing when browsing)
Next, the user terminal 20 (the display processing unit 22 and the input processing unit 24) and the library server 10 (the lending processing unit 12) at the time of browsing are referred to the other drawings as appropriate along the flowcharts of FIGS. Processing will be described.

  The process in FIG. 19 is the same as the process in FIG. 9 except for the process indicated by the bold line. Therefore, in the following, the processing of FIG. 19 will be described focusing on the points different from FIG.

  In FIG. 19, the input processing unit 24 of the user terminal 20 stands by until a browsing request is received from the user in step S <b> 10 ′. Then, when the browsing request is received, the process proceeds to step S <b> 12 ′, and the input processing unit 24 transmits the browsing request to the lending processing unit 12 of the library server 10.

  On the other hand, since the lending processing unit 12 of the library server 10 stands by until a browsing request is received from the user terminal 20 in step S110 ', the process proceeds to step S112 at the timing when step S12' is performed. Thereafter, the same processing as in FIG. 9 is executed from step S14 to S20 and from step S112 to S118. Then, the lending processing unit 12 of the library server 10 executes the process of step S119 when the determination of step S118 is affirmed as a result of the user authentication (S116).

  In step S119, the lending processing unit 12 determines whether the user has an access right. In this case, the lending processing unit 12 refers to the access right management DB 36 in FIG. 8 and determines whether or not “◯” is input in the access right column of the authenticated user. If the determination in step S119 is negative, the process proceeds to step S120. If the determination in step S119 is positive, the process proceeds to step S402 in FIG.

  When the process proceeds to step S402 in FIG. 20, the lending processing unit 12 transmits the data on the electronic book viewing screen on which the user has access rights. The electronic book browsing screen is, for example, a screen as shown in FIG. As shown in FIG. 21, a “previous page” button and a “next page” button are provided on the browsing screen. After step S402, the information registration unit 14 acquires the browsing start date and time and stores it in the “reading time log” of the reading time DB 34 in FIG. 6B in step S404. Thereafter, the process proceeds to step S406.

  On the other hand, on the user terminal 20 side, in step S302, the display processing unit 22 stands by until data on the electronic book viewing screen is received from the lending processing unit 12 of the library server 10. Accordingly, the display processing unit 22 proceeds to step S304 at the timing when the process of step S402 described above is performed.

  In step S304, the display processing unit 22 displays the browsing screen (FIG. 21) on the display unit 193 (in the browser). Next, in step S306, the input processing unit 24 determines whether the page is turned. Here, when the user presses the “next page” button on the browsing screen, the determination in step S306 is affirmed, and the input processing unit 24 proceeds to step S308. Note that the determination in step S306 may include sliding (flicking) the screen by hand in addition to pressing the “next page” button. In step S308, the input processing unit 24 changes the display page and transmits the change information to the lending processing unit 12 of the library server 10. Thereafter, the process proceeds to step S310. On the other hand, if the determination in step S306 is negative, the process proceeds to step S310.

  If transfering it to step S310, the input process part 24 will judge whether browsing is complete | finished. In this case, if the user has not closed the browsing screen and the browsing is not completed, the process returns to step S306. On the other hand, when the user closes the browsing screen, since browsing is ended, the determination in step S310 is affirmed, and the process proceeds to step S312.

  When the process proceeds to step S <b> 312, the input processing unit 24 transmits browsing end information to the lending processing unit 12 of the library server 10.

  By the way, after step S404, the lending processing unit 12 stands by until change information or browsing end information is received from the input processing unit 24 of the user terminal 20 in step S406 and step S410. And when change information is received (S406: Yes), the loan process part 12 transfers to step S408, and acquires a browsing log. Here, the browsing log means a history of the number of pages read by the user.

  On the other hand, when the browsing end information is received (S410: Yes), the lending processing unit 12 proceeds to step S412. In step S412, the information registration unit 14 acquires the browsing end date and time and stores it in the “reading time log” of the reading time DB 34 of FIG. When step S412 is performed, the lending processing unit 12 transmits the browsing log acquired in step S408 to the information registration unit 14 in FIG.

  Next, in step S414, the information registration unit 14 calculates the reading speed of the user and the reading speed for each genre, and updates the user DB 31 and the genre DB 35. Specifically, the information registration unit 14 adds the browsing log, that is, the number of pages read by the user to the total number of pages read by the user in the user DB 31. Moreover, the information registration part 14 adds browsing time (= browsing end time-browsing start time) to a user's total reading time in user DB31. And the information registration part 14 recalculates reading speed using the total number of reading pages and total reading time after addition, and updates the column of the reading speed of user DB31. Further, the information registration unit 14 also recalculates the reading speed for the genre DB 35 in the same manner as described above, and updates the reading speed column of the genre DB 35.

  In the present embodiment, access to the electronic book data from the user borrowing the electronic book (first access source) is rejected at the time estimated in step S157 by the processing of FIGS. It can be said that control is performed to allow access to the electronic book data from the time lending user (second access source).

  As described above, all the processes in FIGS. 19 and 20 are completed. In the present embodiment, the processing shown in FIGS. 19 and 20 is executed, so that a user having an access right to the electronic book data can view the electronic book data. Moreover, when electronic book data is browsed, a reading time log can be acquired, and the reading speed column of the user DB 31 and the reading speed column of the genre DB 35 can be updated.

  As described above in detail, according to the present embodiment, the lending processing unit 12 grants an access right to certain electronic book data to one user (for example, “Yamada Hanae”), and then the user ( Based on the access history (reading time log) for the electronic book data from Hanae Yamada), the future time when the accessibility to the electronic book data by the user (Hanae Yamada) is below a predetermined standard is estimated (S157). In addition, the lending processing unit 12 performs control for rejecting access to the electronic book data by the user (Yamada Hanae) and allowing access to another user (for example, “Shiro Suzuki”) for the estimated time. Accordingly, it is possible to lend electronic book data to other users at a time when there is a low possibility of accessing the electronic book estimated by the lending processing unit 12 based on the reading habit of the user (Yamada Hanae). Therefore, according to the present embodiment, it is possible to give a reading opportunity to other users without disturbing the reading of the user (Yamada Hanae) to whom the access right has been granted, so that the user can promote the use of electronic book data. Can be planned.

  Further, in the present embodiment, when the lending processing unit 12 receives a time lending request from the user (Shiro Suzuki), the lending processing unit 12 sets the estimated time (“readable time” on the lending available data list display screen in FIG. 16) to the user ( To the user terminal 20 of Shiro Suzuki) (S164). Then, when the lending processing unit 12 receives the time lending request information at the estimated time from the user terminal 20 (S170: affirmative), the user terminal 20 (display processing unit 22) of the user (Yamada Hanae) who has been requested for lending. ), The approval screen data is transmitted (S172). When the lending processing unit 12 receives the approval result from the user terminal 20 of the user (Yamada Hanae), the lending processing unit 12 determines whether or not the time lending is approved (S174). When the time lending at the estimated time is approved (S176: affirmative), the user (Shiro Suzuki) is allowed access for that time. Thereby, it becomes possible to permit the user's access at a time desired by the user who requested the time loan.

  In this embodiment, the time lending request from the user (Shiro Suzuki) includes information on the number of pages to be read, and the lending processing unit 12 reads the user's reading stored in the user DB 31. The necessary reading time for the user is calculated from the reading speed for each genre stored in the speed or genre DB 35 and the information on the number of pages of the portion to be read. Then, the lending processing unit 12 “reads the time when the access possibility to the electronic book data by the user having access right (Hanae Yamada) has a length equal to or longer than the required reading time among the future times below a predetermined standard. The rentable data list display screen displayed as “time” is transmitted to the user terminal 20. This makes it possible to lend electronic book data for a time sufficient for the user to read the portion he / she wants to read.

  In addition, although the said embodiment demonstrated the case where the reading speed was calculated for every user and every genre, and stored in user DB31 and genre DB35, it is not restricted to this. For example, in the user DB 31, the reading speed of each genre of each user may be stored. The required reading time can be calculated with higher accuracy by using the reading speed of each genre of each user in calculating the required reading time.

  In the above embodiment, the determination in step S200 in FIG. 12 may be omitted, and steps S202 and S204 may be always executed. In this case, the reading speed may not be stored in the user DB 31. Similarly, in the process of FIG. 12, the determination in step S200 may be omitted, and step S206 may always be executed. In this case, the genre DB 35 becomes unnecessary.

  In the above embodiment, the average number of characters stored in the book DB 32 may be used in calculating the required reading time. For example, the time required to read one character for each user and each genre may be calculated, and the required reading time may be calculated using the calculated time and the average number of characters.

  In the time lending screen in FIG. 15B, the case where the user who desires time lending inputs the number of pages has been described. However, the present invention is not limited to this. (Eg, chapter number) may be input by the user.

  In the above-described embodiment, the description is omitted, but when the lending processing unit 12 determines whether or not the time lending is possible in step S158 in FIG. 11, is the user extracted in step S156 already lending time? It is necessary to consider whether and when it is time lending.

  The above processing functions can be realized by a computer. In that case, a program describing the processing contents of the functions that the processing apparatus should have is provided. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing contents can be recorded on a computer-readable recording medium (except for a carrier wave).

  When the program is distributed, for example, it is sold in the form of a portable recording medium such as a DVD (Digital Versatile Disc) or a CD-ROM (Compact Disc Read Only Memory) on which the program is recorded. It is also possible to store the program in a storage device of a server computer and transfer the program from the server computer to another computer via a network.

  The computer that executes the program stores, for example, the program recorded on the portable recording medium or the program transferred from the server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. Further, each time the program is transferred from the server computer, the computer can sequentially execute processing according to the received program.

  The above-described embodiment is an example of a preferred embodiment of the present invention. However, the present invention is not limited to this, and various modifications can be made without departing from the scope of the present invention.

In addition, the following additional remarks are disclosed regarding description of the above embodiment.
(Supplementary Note 1) An electronic book management program having an exclusive control function for rejecting simultaneous access from a plurality of access sources for one electronic book data,
Starting to allow access to the one electronic book data to the first access source;
Based on the access history for the electronic book data from the first access source, estimate the future time when the possibility of access to the one electronic book data by the first access source is below a predetermined standard,
For the estimated time period, control is performed to deny access to the one electronic book data from the first access source and to allow access to the one electronic book data from the second access source.
An electronic book management program which causes a computer to execute processing.
(Additional remark 2) The process which estimates the said time is specified by the said 1st request | requirement, if the 1st request | requirement which is a request | requirement of access to the said one electronic book data is received from the said 2nd access source. Estimating the time for the one electronic book data, and transmitting information about the estimated time to the second access source;
When the process for performing the control receives a second request, which is a request for access to the transmitted time period, from the second access source, the one time period from the first access source is transmitted for the transmitted time period. Denying access to electronic book data and allowing access to the one electronic book data from the second access source;
The electronic book management program according to appendix 1, wherein
(Supplementary Note 3) The first request includes information indicating a location to be accessed in the one electronic book data,
The process for estimating the time refers to the data storing the information indicating the reading speed for each user, and based on the information indicating the reading speed corresponding to the user of the second access source, And calculating the time required for reading by the second access source,
Estimating a future time when the possibility of access to the one electronic book data by the first access source is not more than a predetermined reference and has a length not less than the calculated time,
The electronic book management program according to Supplementary Note 2, wherein
(Supplementary Note 4) The first request includes information indicating a location to be accessed in the one electronic book data,
The process of estimating the time refers to data in which information indicating reading speed is stored for each genre of electronic book data, and based on information indicating reading speed corresponding to the genre of the one electronic book data, While calculating the time required for reading by the second access source for the location,
Estimating a future time when the possibility of access to the one electronic book data by the first access source is not more than a predetermined reference and has a length not less than the calculated time,
The electronic book management program according to Supplementary Note 2, wherein
(Supplementary Note 5) A computer having an exclusive control function for rejecting simultaneous access from a plurality of access sources for one electronic book data,
Starting to allow access to the one electronic book data to the first access source;
Based on the access history for the electronic book data from the first access source, estimate the future time when the possibility of access to the one electronic book data by the first access source is below a predetermined standard,
For the estimated time period, control is performed to deny access to the one electronic book data from the first access source and to allow access to the one electronic book data from the second access source.
An electronic book management method characterized by executing processing.
(Additional remark 6) The process which estimates the said time is specified by the said 1st request | requirement, if the 1st request | requirement which is a request | requirement of access to the said one electronic book data is received from the said 2nd access source. Estimating the time for the one electronic book data, and transmitting information about the estimated time to the second access source;
When the process for performing the control receives a second request, which is a request for access to the transmitted time period, from the second access source, the one time period from the first access source is transmitted for the transmitted time period. Denying access to electronic book data and allowing access to the one electronic book data from the second access source;
The electronic book management method according to Supplementary Note 5, wherein
(Supplementary Note 7) The first request includes information indicating a location to be accessed in the one electronic book data,
The process for estimating the time refers to the data storing the information indicating the reading speed for each user, and based on the information indicating the reading speed corresponding to the user of the second access source, And calculating the time required for reading by the second access source,
Estimating a future time when the possibility of access to the one electronic book data by the first access source is not more than a predetermined reference and has a length not less than the calculated time,
The electronic book management method according to appendix 6, wherein:
(Supplementary Note 8) The first request includes information indicating a location to be accessed in the one electronic book data,
The process of estimating the time refers to data in which information indicating reading speed is stored for each genre of electronic book data, and based on information indicating reading speed corresponding to the genre of the one electronic book data, While calculating the time required for reading by the second access source for the location,
Estimating a future time when the possibility of access to the one electronic book data by the first access source is not more than a predetermined reference and has a length not less than the calculated time,
The electronic book management method according to appendix 6, wherein:
(Supplementary Note 9) An electronic book management apparatus having an exclusive control function for rejecting simultaneous access from a plurality of access sources for one electronic book data,
When the first access source starts to allow access to the one electronic book data, the first access source performs the access based on the access history for the electronic book data from the first access source. An estimation unit for estimating a future time when the possibility of access to the one electronic book data is below a predetermined standard;
Control for rejecting access to the one electronic book data from the first access source and permitting access to the one electronic book data from the second access source for the time estimated by the estimation unit. A control unit to perform,
An electronic book management apparatus comprising:
(Supplementary Note 10) When the estimation unit receives a first request that is a request for access to the one electronic book data from the second access source, the one estimation unit specified by the first request Estimating the time for electronic book data, sending information about the estimated time to the second access source,
When the control unit receives from the second access source a second request that is an access request for the transmitted time period, the control unit transmits the one electronic book from the first access source for the transmitted time period. Deny access to data and allow access to the one electronic book data from the second access source;
The electronic book management apparatus according to Supplementary Note 9, wherein
(Supplementary Note 11) The first request includes information indicating a location to be accessed in the one electronic book data,
The estimation unit refers to data in which information indicating reading speed is stored for each user, and based on the information indicating reading speed corresponding to the user of the second access source, Calculate the time required for reading by 2 access sources,
Estimating a future time when the possibility of access to the one electronic book data by the first access source is not more than a predetermined reference and has a length not less than the calculated time,
The electronic book management apparatus according to Supplementary Note 10, wherein:
(Supplementary Note 12) The first request includes information indicating a location to be accessed in the one electronic book data,
The estimation unit refers to data in which information indicating reading speed is stored for each genre of electronic book data, and based on the information indicating reading speed corresponding to the genre of the one electronic book data, In contrast to calculating the time required for reading by the second access source,
Estimating a future time when the possibility of access to the one electronic book data by the first access source is not more than a predetermined reference and has a length not less than the calculated time,
The electronic book management apparatus according to Supplementary Note 10, wherein:

10 Library server (electronic book management device)
12 Lending processing part (estimation part, control part)

Claims (6)

An electronic book management program having an exclusive control function for rejecting simultaneous access from a plurality of access sources for one electronic book data,
Starting to allow access to the one electronic book data to the first access source;
Based on the access history for the electronic book data from the first access source, estimate the future time when the possibility of access to the one electronic book data by the first access source is below a predetermined standard,
For the estimated time period, control is performed to deny access to the one electronic book data from the first access source and to allow access to the one electronic book data from the second access source.
An electronic book management program which causes a computer to execute processing. When the process for estimating the timing receives a first request, which is a request for access to the one electronic book data, from the second access source, the one electronic specified by the first request. Estimating the time for the book data, and transmitting information about the estimated time to the second access source;
When the process for performing the control receives a second request, which is a request for access to the transmitted time period, from the second access source, the one time period from the first access source is transmitted for the transmitted time period. Denying access to electronic book data and allowing access to the one electronic book data from the second access source;
The electronic book management program according to claim 1, wherein: The first request includes information indicating a location to be accessed in the one electronic book data,
The process for estimating the time refers to the data storing the information indicating the reading speed for each user, and based on the information indicating the reading speed corresponding to the user of the second access source, And calculating the time required for reading by the second access source,
Estimating a future time when the possibility of access to the one electronic book data by the first access source is not more than a predetermined reference and has a length not less than the calculated time,
The electronic book management program according to claim 2, wherein: The first request includes information indicating a location to be accessed in the one electronic book data,
The process of estimating the time refers to data in which information indicating reading speed is stored for each genre of electronic book data, and based on information indicating reading speed corresponding to the genre of the one electronic book data, While calculating the time required for reading by the second access source for the location,
Estimating a future time when the possibility of access to the one electronic book data by the first access source is not more than a predetermined reference and has a length not less than the calculated time,
The electronic book management program according to claim 2, wherein: A computer having an exclusive control function for rejecting simultaneous access from a plurality of access sources for one electronic book data,
Starting to allow access to the one electronic book data to the first access source;
Based on the access history for the electronic book data from the first access source, estimate the future time when the possibility of access to the one electronic book data by the first access source is below a predetermined standard,
For the estimated time period, control is performed to deny access to the one electronic book data from the first access source and to allow access to the one electronic book data from the second access source.
An electronic book management method characterized by executing processing. An electronic book management apparatus having an exclusive control function for rejecting simultaneous access from a plurality of access sources for one electronic book data,
When the first access source starts to allow access to the one electronic book data, the first access source performs the access based on the access history for the electronic book data from the first access source. An estimation unit for estimating a future time when the possibility of access to the one electronic book data is below a predetermined standard;
Control for rejecting access to the one electronic book data from the first access source and permitting access to the one electronic book data from the second access source for the time estimated by the estimation unit. A control unit to perform,
An electronic book management apparatus comprising:

Images