JP2009110330A - Method, device, and program for mediating translation - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To inexpensively provide a translation mediating method capable of allowing a translation request person to request translation. <P>SOLUTION: The payment application of a shared amount to be paid as a part of translation charge is received from the translation request person. The trust application of a translation charge and a translation period is received from a translator (S353). When the applied translation charge is lower than the stored translation charge (S357:YES), the translation charge and the translator are newly updated (S359). When the applied translation period is shorter than the stored translation period (S361:YES), the stored translation period and translator are newly updated (S363). When the translation charge stored at this point of time becomes equal to or lower than the total shared amount (S365:YES), the translation request is ordered to the translator who performs the trust application of the translation charge (S367). <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a translation mediation method, a translation mediation device, and a translation mediation program, and more specifically, a translation mediation method, a translation mediation device, and a translation mediation that enable a translation requester to make a translation request at a lower cost. Regarding the program.

With the spread of the Internet, the need for communication between different cultures and different languages is increasing. As a translation system that can be used on the Internet, a machine translation system that performs translation by language processing by a computer is widely used. However, it is difficult to accurately understand the meaning of the machine translation results obtained with currently developed translation algorithms, and it is difficult to say that it is practically usable. Under such circumstances, a system that mediates between a translation requester and a translator via the Internet has been proposed (for example, see Patent Document 1). In this system, a translation requester requests a specific translator to translate content such as a home page, and the translator translates the content accordingly, and the translation requester charges the translation request. Do.
JP 2001-290814 A

  However, there is a problem that the translation by the translator is difficult to use easily because a great burden is generated particularly in terms of funds.

  The present invention has been made to solve the above-described problems, and provides a translation mediating method, a translation mediating apparatus, and a translation mediating program that enable a translation requester to make a translation request at a lower cost. With the goal.

  In order to solve the above-mentioned problem, the translation mediation method of the invention according to claim 1 is a translation mediation method processed by a translation mediation device connectable to a network, and information for specifying content requested for translation The translation request information including at least the content information and the application for sharing payment, which is a fee paid as part of the translation fee required to request the translation of the content, is output from the user terminal connected to the network. The request information receiving step for receiving the translation request information and the application for payment of the share, and the content information included in the translation request information when the translation request information is received in the request information receiving step. A translation fee determination unit for determining the amount of the translation fee based on the translation fee and storing the determined translation fee in the translation fee storage means. And a notification requesting the translator to translate the content when the sum of the amount of contributions applied for payment received in the request information receiving step exceeds the amount of the translation fee. A translated content receiving step for receiving the translated content when the translated content that is the translated content of the content ordered in the ordering step is output from a user terminal connected to the network; A translated content storage step of storing the translated content received in the translated content reception step in the translated content storage means.

  Further, the translation mediation method of the invention according to claim 2 is a request information storage that stores the content information received in the request information receiving step in a request information storage means that can be disclosed in addition to the configuration of the invention of claim 1. Step, and when the bid application for the commissioned fee for the content translation work specified by the content information performed by the translator is output from the user terminal connected to the network, the commission for accepting the bid application for the commissioned fee A fee acceptance step; a trust fee storage step of storing the trust fee in the trust fee storage means when a bid application for the trust fee is accepted in the trust fee reception step; a trust fee stored in the trust fee storage means; A charge comparison step of comparing the translation charge stored in the translation charge storage means, and the charge comparison step A translation fee for determining the amount of the commissioned fee as the amount of the translation fee and updating the translation fee of the translation fee storage means when it is determined that the amount of the commissioned fee is less than the amount of the translation fee An update step, and a translator update step in which an applicant who applied for a bid for the commission fee that has become the translation fee updated in the translation fee update step is a translator to be ordered. The translator that has been updated in the publisher update step is notified of a request for translation of the content.

  Further, the translation mediation method of the invention according to claim 3 is included in the translation request information when translation request information is received in the request information reception step in addition to the configuration of the invention of claim 1 or 2. A translation period determining step for determining a translation period based on the content information, and storing the determined translation period in the translation period storage means; and bidding for a contract period for the translation work of the content specified by the content information performed by the translator When the application is output from a user terminal connected to the network, the acceptance period accepting step for accepting a bid application for the acceptance period, and the acceptance period when accepting the bid application for the acceptance period in the acceptance period accepting step. A contract period storage step for storing the information in the contract period storage means, a contract period stored in the trust period storage means, and the translation In the period comparison step of comparing the translation period stored in the inter-memory storage unit and the period comparison step, when it is determined that the trust period is shorter than the translation period, the trust period is determined as the translation period. A translation period update step for updating the translation period of the translation period storage means, and a translation for which the applicant who applied for a bid for the contract period that became the translation period updated in the translation period update step is a translator to be ordered A translator update step, wherein the ordering step notifies the translator updated in the translator update step to request content translation.

  In addition to the configuration of the invention according to claim 2 or 3, the translation mediation method of the invention according to claim 4 is provided for a translator before update when the translator is updated in the translator update step. A translator change notification step for performing a translator change notification indicating that the translator has been changed.

  Further, the translation mediation method of the invention according to claim 5 is the information related to the translator, in addition to the configuration of the invention according to any one of claims 1 to 4, wherein the translator's translatable language information is Referring to at least the stored translator information storage means, further comprising a translator determining step for determining a translator capable of translating the content specified by the content information received in the request information receiving step, wherein the ordering step comprises: The translator is notified of a request for translation of the content.

  In addition to the configuration of the invention according to any one of claims 1 to 5, the translation mediation method of the invention according to claim 6 is provided by a person other than the translation requester in the translation content storage means in the translation content storage step. A usage fee reception step for accepting a payment application for a usage fee when a payment application for the usage fee, which is a fee to be paid when the user wishes to obtain translated content stored in the network, is output from a user terminal connected to the network; The translation fee is paid to each translation requester in accordance with the ratio of the amount of the contribution paid by each translation requester in the total amount of the contribution paid by the translation requester who requested the creation of the translation content. And a client return step.

  In addition to the configuration of the invention according to any one of claims 1 to 6, the translation mediation method of the invention according to claim 7 is a method in which a person other than the translation requester performs the translation content storage means in the translation content storage step. A usage fee receiving step of accepting a usage fee payment application when a payment application for the usage fee, which is a fee to be paid when the user wishes to obtain translation content stored in the network, is output from a user terminal connected to the network; And a translator return step of paying a part or all of the usage fee to the translator who created the translated content.

  The translation mediating apparatus according to the invention of claim 8 is a translation mediating apparatus connectable to a network, and includes translation request information including at least content information that is information for specifying content requested for translation; Request information accepting means for accepting a share payment application, which is a charge paid as part of the translation fee required for requesting content translation, via the network, When accepted, the translation fee determining means for determining the amount of the translation fee based on the content information included in the translation request information and storing the determined translation fee in the translation fee storage means; If the total amount of contributions requested for payment exceeds the amount of the translation fee, In ordering means for requesting translation of the content, translation content accepting means for accepting, via a network, translated content that is a content obtained by translating the content ordered in the ordering means, and in the translated content accepting means Translation content storage control means for storing the received translation content in the translation content storage means.

  According to a ninth aspect of the invention, a translation mediation program causes a computer to execute each processing step of the translation mediation method according to any one of the first to seventh aspects.

  The translation mediation method of the invention according to claim 1 accepts content information for requesting translation of content and an application for payment of a share paid as part of a translation fee. Next, the amount of translation fee is determined based on the received content information. Then, when the total amount of payment application contributions received exceeds the amount of the translation fee, the translator is requested to translate the content. Therefore, when a translation requester requests translation of content, a plurality of translation requesters can share and pay the required translation fee, thereby reducing the translation fee burden of each translation requester. It becomes possible.

  In addition to the effect of the invention of claim 1, the translation mediation method of the invention according to claim 2 accepts a bid application for a contract fee for content translation work from a translator. Then, the commission fee and the translation fee are compared, and if the commission fee is less than the translation fee, the commission fee is determined as the translation fee. Then, the applicant who applied for a bid for the commissioned fee, which is the translation fee, is the translator to be ordered, and a translation request notification is made. Therefore, an applicant who wishes to accept a translation request can accept a translation request by presenting the cheapest commission fee. In addition, since the translation fee is reduced, the translation fee burden of the translation requester is reduced.

  The translation mediation method of the invention according to claim 3 determines the translation period based on the received content information in addition to the effect of the invention of claim 1 or 2. In addition, it accepts bid applications from translators during the period of content translation work. Then, the commission period is compared with the translation period, and when the commission period is shorter than the translation period, the commission period is determined as the translation period. Then, the applicant who applied for a bid for the contract period that is the translation period is set as a translator to be ordered, and a translation request notification is made. Therefore, an applicant who wishes to accept a translation request can accept a translation item by presenting the shortest translation period. In addition, the translation period is shortened, and translation can be performed with a short delivery time.

  In addition, in the translation mediation method of the invention according to claim 4, in addition to the effect of the invention of claim 2 or 3, when the translator is updated, the translator is changed with respect to the translator before the update. Translator change notification is sent. Therefore, since it becomes possible to grasp that the translator has been changed from oneself to another, it is a motivation to apply for a better translation condition and accept a translation project.

  In addition to the effect of the invention according to any one of claims 1 to 4, the translation mediation method of the invention according to claim 5 can translate content by referring to information of a translator's translatable language. Determine translators. Then, a translation request notification is sent to the determined translator. Therefore, if there is a translation request, the translator can be tentatively determined even if the condition is not presented by the translator, so it is possible to prevent a situation where translation is not performed. Become.

  In addition to the effect of the invention according to any one of claims 1 to 5, the translation mediation method of the invention according to claim 6 is a fee that is paid when a person other than the translation requester wants to obtain the translation content The usage fee payment application is accepted, and the usage fee is paid to each translation requester according to the ratio of the amount of the contribution paid by each translation requester to the total amount of the contribution paid by the translation requester. . Therefore, it is possible to reduce the fee burden required for translation by the translation requester. In addition, it becomes possible to distribute more usage fees to the translation requester who has paid a large amount of contributions, which motivates the translation requester to pay more of the contributions.

  In addition to the effect of the invention according to any one of claims 1 to 6, the translation mediation method of the invention according to claim 7 is a fee that is paid by a person other than the translation requester for obtaining translation contents The application for payment of the usage fee is accepted, and part or all of the usage fee is paid to the translator who created the translated content. Therefore, it becomes a motivation for the translator to set the price of the initial translation fee lower in anticipation of the usage fee after translation.

  In addition, the translation mediating apparatus of the invention according to claim 8 accepts content information for requesting content translation and an application for payment of a share paid as part of a translation fee. Next, the amount of translation fee is determined based on the received content information. Then, when the total amount of the payment application contribution received is equal to or greater than the amount of the translation fee, the translator is notified of the request for content translation. Furthermore, the translated content obtained by translating the content is stored. Therefore, when a translation requester requests translation of content, a plurality of translation requesters can share and pay the necessary fee, which can reduce the translation fee burden of each translation requester. Become.

  The translation mediation program of the invention according to claim 9 causes the computer to execute each processing step of the translation mediation method according to any one of claims 1 to 7, thereby causing the computer to execute the processing steps according to any one of claims 1 to 7. The effect similar to the effect of this invention can be produced.

  Embodiments of a translation mediation system using the translation mediation method of the present invention will be described below with reference to the drawings. The present invention provides a translation intermediary that enables a person who desires to translate a specific content (hereinafter referred to as a “translation requester”) to make a translation request to the translator under good translation conditions (charge, period, etc.). This is related to the system (hereinafter, the content requested for translation is referred to as “requested content”). The principal part is: (1) A plurality of translation requesters who wish to translate the same content share and pay the necessary translation fee (hereinafter, the divided fee paid is referred to as “sharing money”). (2) A translator who has presented the best translation conditions (charges, duration, etc.) among a plurality of translators through a so-called reverse auction can accept a translation project. (3) After the content is translated, the fee (hereinafter referred to as “use fee”) that is paid when a person other than the translation requester who paid the share payment acquires the translation result is translated. By providing the request to the client and the translator, it is further provided that the fee burden on the client is reduced as a result.

  First, the outline of the translation mediation system of this embodiment will be described with reference to FIG. FIG. 1 is a schematic diagram showing a configuration of an apparatus used in a translation mediation system. As shown in FIG. 1, in the present embodiment, a management server 1, a client client 2, a translator client 3, and a Web server 5 are connected to the Internet 7. The requester client 2 is used by a translation requester who requests translation, and the translator client 3 is used by a translator who performs translation. The management server 1 performs translation request management, shared payment processing, translation result management, translation result usage request, usage fee payment processing, and the like. The management server 1 includes a translation result registration database (hereinafter referred to as “translation result DB”) 1551 for storing translation results, and a request database (hereinafter referred to as “request DB”) for storing information related to translation requests and the use status of translation results. .) 1531. Further, it is connected to the credit company management computer 6 through the network 8. The network 8 may be a dedicated network constructed using a telephone line or an optical fiber, or may be the Internet 7. The Web server 5 stores a Web page 51 to be disclosed on the Internet 7.

  Next, the management server 1 will be described with reference to FIGS. 2 is a block diagram illustrating a hardware configuration of the management server 1, FIG. 3 is a schematic diagram illustrating an example of a configuration of the translator information storage area 151, and FIG. 4 illustrates a translation requester information storage area 152. 5 is a schematic diagram illustrating an example of the configuration of the request DB 1531. FIG. 6 is a schematic diagram illustrating an example of the configuration of the request status storage area 154.

  First, the hardware configuration of the management server 1 will be described with reference to FIG. As shown in FIG. 2, the management server 1 is provided with a CPU 10 that controls the management server 1. The CPU 10 includes a RAM 11 that temporarily stores various data, a ROM 12 that stores BIOS, and the like. Are connected to an I / O interface 14 that mediates the delivery of. A hard disk device 15 is connected to the I / O interface 14, and the hard disk device 15 includes a translator information storage area 151, a translation requester information storage area 152, a request DB storage area 153, and a request status storage area 154. An original text storage area 155, a translation result storage area 156, a content management program storage area 157, and other information storage areas 158 are provided.

  The translator information storage area 151 stores information about the translator, the translation requester information storage area 152 stores information about the translator, and the request DB storage area 153 stores the request DB 1531 (see FIG. 1). ) Is stored, the request status storage area 154 stores information about the requester of the translation and the contribution, the original text storage area 155 stores the original text of the requested content, and the translation result storage area 156 stores the translation result. A DB 1551 (see FIG. 1) is stored, a program executed by the CPU 10 is stored in the content management program storage area 157, and the client client 2 and the translator client 3 are stored in the other information storage area 158, for example. The management server 1 uses screen forms to be displayed on the browser screen and data stored temporarily Other information are stored.

  In addition, a mouse controller 18, a video controller 16, a key controller 17, and a communication device 19 are connected to the I / O interface 14. A mouse 181 is connected to the mouse controller 18, a display 161 is connected to the video controller 16, a keyboard 171 is connected to the key controller 17, and the communication device 19 can be connected to the Internet 7 and the network 8. Yes.

  Next, an example of the configuration of the translator information storage area 151 will be described with reference to FIG. As shown in FIG. 3, the translator information storage area 151 has a number field. In correspondence with the number stored in the number field (hereinafter referred to as “translator number”), at least a name field, an address field, a transfer account field, a contact field, and a translatable language field are provided. A group of information described in one line in FIG. 3 is called an “entry” (the same applies to FIGS. 4 to 6). The name field stores the name of the translator, the address field stores the address of the translator, the transfer account field stores information about the bank account into which the translation fee to be paid to the translator is transferred, and the contact field. Stores the contact information for contacting the translator, and the translatable language field stores information on the languages that can be translated. By referring to these pieces of information, it is determined whether or not the requested content can be translated into the translation destination language, and the translation request is notified to the translator. In addition, the translation fee can be paid to the translator.

  For example, in the example shown in FIG. 3, the translator “Hanako Ito” of the translator number “T1” has an address of “Tokyo Metropolitan XX District Δ △ cho 1”, and the transfer account is “B Bank B Branch Normal “123456”, the contact is “hanako@abc.com”, indicating that translation from Japanese to English and translation from English to Japanese can be performed. In addition, the translator “Jiro Sato” with the translator number “T2” has an address of “Osaka Prefecture △△ City ×× Machi 2-chome”, and the bank account is “C Bank C Branch Normal 123456”. Is "jiro@cde.com" and indicates that it is possible to translate from Japanese to French and from French to Japanese. Also, the translator “Saburo Kojima” with the translator number “T3” has an address “Shizuoka △△ City XX Town 3-chome”, the bank account “D Bank D Branch Normal 123456”, and contact information. Is "saburo@cde.com" and shows that it is possible to translate from Japanese to English and from English to Japanese.

  Next, an example of the configuration of the translation requester information storage area 152 will be described with reference to FIG. As shown in FIG. 4, the translation requester information storage area 152 has a number field. Then, corresponding to the number stored in the number field (hereinafter referred to as “translation requester number”), the name field, address field, transfer account field, credit card number field, credit card expiration field, contact field Is provided at least. The name of the translation requester is stored in the name field, the address of the translation requester is stored in the address field, and the bank account information to which the fee to be paid to the translation requester is transferred is stored in the transfer account field. The card number field stores credit card number information that charges a fee required for requesting translation, the credit card expiration field stores the credit card expiration date, and the contact field stores the translation. The contact information for the client is stored. By referring to this information, billing according to the share applied for by the translation requester is realized.

  For example, in the example shown in FIG. 4, the translation requester “Taro Yamada” with the translation requester number “R1” has an address “Aichi prefecture △△ city XX ward ×× machi 3 chome” and the transfer account is “ Bank A Branch A Normal 123456 ”, Credit Card Number is“ 1234-5678-90 ”, Credit Card Expiration Date is“ January 1, 2008 ”, and contact information is“ taro@abc.com ” It is. In addition, the translation requester “Sachiko Suzuki” of the translation requester number “R2” has an address of “Kanagawa XX City XX Town 5-chome”, and the transfer account is “Bank A Head Office Normal 345678”, with credit The card number is “0987-6543-21”, the credit card expiration date is “December 31, 2006”, and the contact information is “sachiko@xyz.com”.

  Next, an example of the configuration of the request DB 1531 stored in the request DB storage area 153 will be described with reference to FIG. The request DB 1531 stores information related to the translation request requested by the translation requester. As shown in FIG. 5, the request DB 1512 has a translation request number column. Corresponding to the translation request number stored in the translation request number field, the translation requester number field, the translator number field, the order status field, the request URI field, the original URI field, the translation source language field, the translation destination language Column, translation result URI column, translation period column, order deadline date column, translation fee column, minimum contribution column, translation completion contact column, usage fee column, and usage count column. The translation requester number field is a translation requester number that identifies the translation requester who registered the translation request of the content of the same entry, and corresponds to the number field in the translation requester information storage area 152 (see FIG. 4). The client number is stored. The translator number column is a translator number for identifying a translator responsible for translating the contents of the same entry, and stores the translator number corresponding to the number column in the translator information storage area 151 (see FIG. 3). The In the order status, the progress status of the request for translation of the contents of the same entry is stored. If the request for translation of the requested content has not been ordered to the translator, “unordered” is stored, and the order has already been placed. If it has been made, “ordered” is stored. The request URI field stores a URI indicating the location of the requested content (hereinafter referred to as “request URI”), and the original text URI field refers to the original text of the requested content obtained by referring to the requested URI (hereinafter “original text content”). The URI indicating the location where the “.” Is stored is stored. In the translation source language column, the description language of the requested content is stored, and in the translation destination language column, information on the language in which the requested content is translated is stored. Also, in the translation result URI field, when a translation result (hereinafter referred to as “translation content”) when the requested content is translated is registered, a URI indicating a location where the translation content is stored is stored. The The translation period column stores a period from when the request for translation of the requested content is ordered until it is completed. The order deadline date desired by the translation requester is stored in the order deadline column. A translation fee is stored in the translation fee column. In the minimum contribution column, a minimum amount when the translation requester pays as a contribution is stored. In the translation completion contact field, a contact to be notified when the requested content has been translated is stored. In the usage fee column, a person other than the translation requester who applied for the contribution and requested the translation of the requested content and who wants to obtain the translated content (hereinafter referred to as “translation user”) obtains it. The usage fee, which is the fee to be paid for, is stored. The number of times of use of the translated content by the translation user is stored in the usage number column.

  For example, in the example shown in FIG. 5, the translation request with the translation request number “1” is requested by the translation requester with the translation requester number “R1” for the Web page with the request URI “http://www.bbbb.com”. The translation is performed by a translator having a translator number “T1”. The original text at the time of translation is stored in “http://www.bbbb.co.jp/A1.html”, and the translation work has already been completed. The translated content is stored in “http://www.bbbb.co.jp/B1.html”. The original language is English and the translated language is Japanese. Moreover, the translation period is “28 days”, the order deadline is “November 10, 2007”, the translation fee is “50,000 yen”, and the minimum contribution is “300 yen” The usage fee is “500 yen” and the usage count is “50 times”. The translation request with the translation request number “2” is a request from the translation requester with the translation requester number “R1” for the Web page of the request URI “http://www.cccc.co.fr”. Translation is performed by a translator having a translator number “T2”. The original text at the time of translation is stored in “http://www.bbbb.co.jp/A2.html” and is currently being translated. The original language is French and the translated language is Japanese. Also, the translation period is “20 days”, the order deadline is “December 5, 2007”, the translation fee is “80,000 yen”, and the minimum contribution is “300 yen”. After the translation is completed, notification of completion will be sent to “goro@abc.com”. The usage fee is “800 yen” and the usage count is “0”. The translation request with the translation request number “3” is a request from the translation requester with the translation requester number “R4” for the Web page of the request URI “http://www.dddd.co.jp”. The translation of the translator number “T1” is scheduled for translation, but has not yet been ordered. The original text to be translated is stored in “http://www.bbbb.co.jp/A3.html”, the original language is Japanese, and the translated language is English. Also, the translation period is “14 days”, the order deadline is “January 5, 2008”, the translation fee is “40,000 yen”, and the minimum contribution is “300 yen” The usage fee is “400 yen” and the usage count is “0”. The translation request with the translation request number “4” is a request from the translation requester with the translation requester number “R4” for the Web page of the request URI “http://www.eeee.co.jp”. The translation of the translator number “T2” is scheduled for translation, but has not yet been ordered. The original text to be translated is stored in “http://www.bbbb.co.jp/A4.html”, the language of the original text is Japanese, and the translated language is French. The translation period is “28 days”, the order deadline is “February 10, 2008”, the translation fee is “60,000 yen”, and the minimum contribution is “300 yen”. The usage fee is “600 yen”, and the usage count is “0”. The translation request with the translation request number “5” is a request from the translation requester with the translation requester number “R2” for the Web page of the request URI “http://www.ffff.co.jp”. The translation of the translator number “T3” is scheduled for translation, but has not yet been ordered. The original text to be translated is stored in “http / www.bbbb.co.jp / A5.html”, the language of the original text is English, and the translated language is Japanese. The translation period is “28 days”, the order deadline is “November 30, 2007”, the translation fee is “50,000 yen”, and the minimum contribution is “300 yen”. The usage fee is “600 yen”, and the usage count is “0”.

  Next, an example of the configuration of the request status storage area 154 will be described with reference to FIG. In the request status storage area 154, information on the translation requester who requests translation of the requested content and the share of money borne by the translation requester are stored. As shown in FIG. 6, the request status storage area 154 has a translation request number column. The translation request number column is a number for specifying a translation request, and corresponds to the translation request number stored in the translation request number column (see FIG. 5) of the request DB 1531. Corresponding to the translation request number, a translation requester number column and a contribution column are provided. In the translation requester number column, the translation requester who registered the translation request corresponding to the translation request number of the same entry, and the translation requester who applied for the share and participated in the translation request (hereinafter referred to as “request participant”). The translation requester number is stored. This number corresponds to the translation request number stored in the number column (see FIG. 4) of the translation requester information storage area 152. Also, in the sharing money column, the sharing money applied from the translation requester of the translation requester number of the same entry is stored. By referring to these pieces of information, it is possible to grasp the share applied for the translation request. Further, by summing up the contributions of the entries having the same translation request number, it is possible to calculate the total amount of the contributions applied for the translation request.

  For example, in the example shown in FIG. 6, with respect to the translation request with the translation request number “1”, the translation requester with the translation requester number “R1”, “R2”, “R3”, “R4”. Who requested the translation, and the amount of money each of them applied for is “R1” is “500 Yen”, “R2” is “300 Yen”, “R3” is “1,000 Yen” , "R4" is "800 yen" ... "R100" is "1,000 yen". Also, for the translation request with the translation request number “3”, the translation requester of “R4” requests translation, and the applied share is “3,000 yen”. Therefore, for example, the total of the contributions of the translation request number “1” can be calculated as “500 yen + 300 yen + 1,000 yen + 800 yen +... +1,000 yen”.

  Next, referring to FIG. 7 to FIG. 11, a screen displayed when the translation requester and the request participant input the conditions for the translation request via the requester client 2 (see FIG. 1), and the translation use A screen displayed when the client applies for the use of translation content registered via the client client 2 (see FIG. 1) will be described. 7 is an example of a request URI input screen for inputting a request URI, FIG. 8 is an example of a request condition input screen for inputting a request condition by a translation requester, and FIG. 9 is input by a request participant. 10 is an example of a participation condition input screen, FIG. 10 is an example of a contact input screen for inputting a contact address of a translation requester, and FIG. 11 is an example of a use application screen for a translation user to use translated content. is there.

  First, an example of a request URI input screen will be described with reference to FIG. The request URI screen is displayed from the client client 2 (see FIG. 1), and is a screen for inputting the request URI and the translation language, and is displayed first in the series of display screens in the translation mediation method of the present invention. It is a screen.

  As shown in FIG. 7, the request URI input screen includes a translation target URI field and a language selection field. The translation target URI column is provided for inputting a request URI, and the language selection column is provided for inputting a language into which the requested content stored in the input request URI is translated. Yes. The request URI and language information input on this screen are temporarily stored in the RAM 11 (see FIG. 2). For example, in the example shown in FIG. 7, the request content for translating the request content stored in the request URI “http://bbbb.com” into “Japanese” is input.

  Next, an example of the request condition input screen will be described with reference to FIG. The request condition input screen is a screen for inputting and registering a new translation condition when the translation requester requests translation of the requested content. The request URI and translation language are entered on the request URI input screen (see FIG. 7). Is input from the client client 2 (see FIG. 1).

  As shown in FIG. 8, the request condition input screen includes a translation target URI field, a translation period field, a translation fee field, a minimum contribution, a contribution, a usage fee field, an order due date field, a payment due date field, “OK”. "Button and" Cancel "button are provided. Among these, the translation target URI column is a column in which the request URI is displayed, and the request URI input on the request URI input screen (see FIG. 7) is read from the RAM 11 (see FIG. 2) and displayed.

  The translation period column is a column in which the translation period from the order of the request for translation of the requested content to the completion is displayed. When the request URI is input from the request URI input screen (see FIG. 7), the translation period is calculated by a predetermined calculation method based on the request content and language information indicated by the input request URI, and the RAM 11 (see FIG. 2). ) Temporarily stored. In the translation period column, the calculated translation period is read and displayed.

  The translation fee column is a column in which the translation fee is displayed. When the request URI is input from the request URI input screen (see FIG. 7), the translation fee is calculated by a predetermined calculation method based on the request content and language information indicated by the input request URI, and the RAM 11 (see FIG. 2). ) Temporarily stored. In the translation fee column, the calculated translation fee is read and displayed.

  The sharing column is a column for inputting a sharing amount that the translation requester applies for at the same time as the request for translation of the requested content. The minimum contribution column is a column for inputting the minimum amount of the contribution that the requesting participant applies to participate in the translation request. The input contribution and the minimum contribution are temporarily stored in the RAM 11 (see FIG. 2). The usage fee column is a column for inputting a usage fee necessary for the translation user to acquire translated content that has already been translated. The input usage fee is temporarily stored in the RAM 11 (see FIG. 2).

  Only one of the pieces of information is input to the order due date column and the payment due date column by selecting one of the selection check boxes. Among these, the order due date field is a field for inputting the order due date desired by the translation requester, and the payment due date field is a field for entering the payment due date for the translation content desired by the translation requester. It is. The order deadline date and the payment deadline date are “payment deadline date” = “order deadline date” + “translation period”. When the order due date column is selected and input, the payment due date is automatically calculated and temporarily stored in the RAM 11 (see FIG. 2) together with the input order due date information. When the payment due date is selected and entered, the order due date is automatically calculated and temporarily stored in the RAM 11 (see FIG. 2) together with the inputted payment due date.

  The “OK” button confirms the information (translation target URI, translation period, translation fee, minimum contribution, contribution, usage fee, order deadline date, payment deadline date) displayed after the input is completed. Pressed to do. When the “OK” button is pressed, the request URI, translation period, translation fee, order deadline date, minimum due amount, usage fee, and order deadline date stored in the RAM 11 (see FIG. 2) are displayed in the request DB 1531 (see FIG. 5)) request URI column, translation period column, order deadline date column, translation fee column, minimum contribution column, usage fee column, order deadline column, and a new translation request in the translation request number column of the same entry. The number is stored. In addition, the sharing money includes the translation requester number of the translation requester and the newly stored translation request number, the translation request number field in the request status storage area 154 (see FIG. 10), the translation requester number field, and the sharing. It is memorized in the gold column.

  The “Cancel” button is pressed to invalidate the information input in the input field. When the “Cancel” button is pressed, the information temporarily stored in the RAM 11 (see FIG. 2) is deleted, the request condition input screen is closed, and the request URI input screen (see FIG. 7) is restored.

  For example, in the example shown in FIG. 8, the request URI is requested to be translated as “http://bbbb.com”, the translation period is “28 days”, and the translation fee is “48”. , 000 yen ”,“ 300 yen ”is entered as the minimum contribution,“ 500 yen ”is entered as the contribution,“ 300 yen ”is entered as the usage fee, and the order deadline "November 10, 2007" is entered as.

  Next, an example of the participation condition input screen will be described with reference to FIG. The participation condition input screen is a screen for inputting conditions in order to participate as a request participant in a translation request already made by another translation requester. When a request URI or the like is input on the request URI input screen (see FIG. 7), the requester is returned when the same request URI is already stored in the request URI column of the request DB 1531 (see FIG. 5). Displayed from the client 2 (see FIG. 1).

  As shown in FIG. 9, the participation condition input screen includes a translation target URI field, a translation period field, a translation fee field, a minimum charge field, an application share field, a total share field, a usage charge field, an order deadline date. Column, a due date field, an “OK” button, and a “Cancel” button. Among them, the URI field for translation, the translation period field, the order deadline date field, the translation fee field, the minimum contribution field, and the usage fee field include the request URI field, translation period field, order deadline field, translation fee of the request DB 1531. The column, minimum contribution, and usage fee column (see FIG. 5) are read out and displayed. In the payment due date column, the order due date and the payment due date calculated from the translation period are displayed. Also, in the total amount of contributions column, the total amount of contributions applied to the currently displayed request URI is calculated and displayed from the amount of contributions in the contributions column of the request status storage area 154 (see FIG. 6). The

  The translation target URI column is a column in which the request URI is displayed, the translation period column is a column in which a period from when the request for translation of the requested content is ordered to the completion is displayed, and the translation fee column is a translation fee Is displayed, and the minimum contribution column is a column for inputting the minimum amount of the contribution that the translation participant applies for participating in the translation request. The application allotment column is a column for inputting the allotment applied by the requesting participant. The input share is temporarily stored in the RAM 11 (see FIG. 5). The total amount of contributions column is a column for displaying the total amount of contributions applied for the translation request, and the total amount of contributions calculated from the request status storage area 154 (see FIG. 6) is displayed. The The usage fee column is a column for displaying the usage fee paid by the translation user. The order deadline column is a deadline date for confirming the translation request to the translator and placing an order, and the payment deadline input column is a deadline date for the translator to deliver the translation result when an order is placed.

  In addition, the “OK” button is pressed when confirming the input share. When the “OK” button is pressed, the contributions stored in the RAM 11 (see FIG. 2) are translated in the request status storage area 154 together with the translation requester number of the requesting participant and information on the translation request number. It is stored in the request number column, the translation requester number column, and the contribution column (see FIG. 6).

  The “Cancel” button is pressed when invalidating the share input in the input field. When the “Cancel” button is pressed, the share temporarily stored in the RAM 11 (see FIG. 2) is deleted, the request condition input screen is closed, and the request URI input screen (see FIG. 7) is restored.

  For example, in the example shown in FIG. 9, the request content whose request URI is “http://bbbb.com” is participated in the request, the translation period is “28 days”, and the translation fee is “48,000 yen”, the minimum share is “300 yen”, “1,000 yen” is entered as the share to be applied, and the total share is “40,000 yen”. The charge is “300 yen”, the order deadline is “November 10, 2007”, and the payment deadline is “December 8, 2007”.

  Next, an example of a contact input screen will be described with reference to FIG. The contact address input screen is displayed by the client client 2 (see FIG. 1) in order to input a contact address when notifying a person who wishes to be notified that the translation by the translator has been completed.

  As shown in FIG. 10, the contact input screen is provided with a URI field to be translated, a contact field, and an “OK” button. The translation target URI column is a column for displaying the request URI of the requested content being requested for translation. The contact field is a field for inputting the mail address of the contact. The “OK” button is pressed when confirming the mail address of the input contact. When the “OK” button is pressed, the input contact information is stored in the translation completion contact information column of the request DB 1531 (see FIG. 5).

  For example, in the example shown in FIG. 10, the request URI is a screen for setting a notification of completion of translation of the requested content indicated by “http://bbbb.com”, and “taro @ abc. com "is entered.

  Next, an example of the usage application screen will be described with reference to FIG. The use application screen is a screen for the translation user to apply for using the registered translation content. When the request URI is input on the request URI input screen (see FIG. 7), the request DB 1531 ( When the URI is stored in the translation result URI column of the entry including the same request URI in FIG. 5), it is determined that the translation content is registered, and is displayed on the requester client 2 (see FIG. 2). The

  As shown in FIG. 11, the use application screen is provided with a URI to be translated column, a use fee column, an “OK” button, and a “cancel” button. In the URI to be translated column and the usage fee column, values stored in the request URI column and the usage fee column (see FIG. 5) of the request DB 1531 are read and displayed.

  For example, in the example shown in FIG. 11, a request for use of translated content obtained by translating requested content whose request URI is “http://bbbb.com” is applied, and the usage fee is “300 yen”. .

  As described above, when a request URI is entered from the request input screen (see FIG. 7), if a translation request for the same request URI is not registered, a new translation request is registered and an application for share is made. A request condition input screen (see FIG. 8) is displayed. If a translation request for the same request URI has already been registered, a translation condition input screen (see FIG. 9) for applying for a share for participation in the translation request is displayed. If translation content has already been registered, a translation content use application screen (see FIG. 11) is displayed. Via these screens, a translation requester can newly register a translation request and apply for a share, a request participant can apply for a share, and can use a translation content.

  Next, with reference to FIGS. 12 and 13, a screen displayed on the translator client 3 (see FIG. 1) when the translator inputs translation conditions for entrusting a translation request will be described. In the translation mediation method of the present embodiment, when a translation request is made by the translation requester via the request URI input screen (see FIG. 7) and the request condition input screen (see FIG. 8), the translator in charge of the translation is provisionally assigned. The translation conditions (translation fee, translation period) are notified to the translator. From then on, other translators will present better translation conditions than the translation conditions notified to the translator until the total amount of contributions from the translation requester exceeds the translation fee and the order for the translation request is processed. In that case, the translator can accept a translation request instead. As a result, the translation fee is cheaper, the translation period is shorter, the burden on the translation requester is reduced, and even if the translation request is not presented by the translation requester, the requested content is not translated. Is preventing. FIG. 12 shows an example of a translation condition input screen in which the translator who has the right to accept the translation request and presents the best translation conditions browses the translation conditions presented by himself / herself. It is an example of the translation condition input screen which browses the information regarding the translation item which does not present the translation conditions and does not have the right to entrust a translation request. In the present embodiment, a screen for displaying information on a translation project that has the right to accept a translation request is distinguished from a screen for displaying information on a translation project that does not have the right to accept a translation request. This makes it easy to present translation conditions.

  First, with reference to FIG. 12, an example of a translation condition input screen for browsing information related to a translation item having the right to accept a translation request will be described. As shown in FIG. 12, the translation condition input screen includes a translation request number field, a translation fee field, a translation period field, a total contribution field, an original URI field, a translation source language field, a translation destination language field, and a minimum allocated amount field. , A translator name column, a translator number column, a translation request number column, a translation fee column, a translation period column, an “OK” button, and a “cancel” button.

  The translation request number field, translation fee field, translation period field, original URI field, translation source language field, translation destination language field, and minimum contribution column are browsed among the information in the request DB 1531 (see FIG. 5). The translation request number, translation fee, translation period, original URI, translation source language, translation destination language, and minimum contribution of the entry including the translator number of the translator are read and displayed. In the total amount of contributions column, the contributions of entries including the translation request number of the target translation request in the request status storage area 154 (see FIG. 6) are totaled and displayed. In the translator name display field and the translator number field, the name and translator number of the currently viewed translator are read from the translator information storage area 151 (see FIG. 3) and displayed. The translation request number column is a column for inputting a translation request number for changing the translation condition.

  The translation fee column is a column for inputting how much lower the translation fee is to be presented than the current translation fee (translation fee column). A fee obtained by subtracting the input fee from the translation fee displayed in the translation fee column is a fee that the translator presents as a new translation fee. This translation fee is temporarily stored in the RAM 11 (see FIG. 2).

  The translation period column is a column for inputting how short a translation period is to be presented from the current translation period (translation period column). A period obtained by subtracting the input period from the translation period displayed in the translation period column is a period presented by the translator as a new translation period. This translation period is temporarily stored in the RAM 11 (see FIG. 2).

  The “OK” button is pressed to confirm the information input in the input field. By depressing the “OK” button, the translation fee and translation period determined are overwritten and stored on the translation fee and translation period in the request DB 1531 (see FIG. 5).

  The “Cancel” button is pressed when invalidating the information input in the input field. By pressing the “Cancel” button, the translation fee and translation period temporarily stored in the RAM 11 (see FIG. 2) are deleted.

  For example, in the example shown in FIG. 12, the translator “Saburo Kojima” browses from the display screen of the translator client 3 (see FIG. 1), and “Saburo Kojima” (translator number: “T3”) Information is displayed. The translation request number is “5”, the translation fee is “50,000 yen”, the translation period is “28 days”, the total amount of contribution is “48,000 yen”, and the original URI is “http : //bbbb.co.jp/A5.html ”, the translation source language is“ English ”, the translation destination language is“ Japanese ”, and the minimum share amount is“ 300 yen ”. Under these conditions, the translation fee is further changed to “48,000 yen”, which is “2,000 yen”, and the translation period is further changed to “26 days”, which is “2 days” shorter. When the “OK” button is pressed in this state, the set translation fee and translation period are overwritten in the translation fee column and translation period column of the request DB 1531 (see FIG. 5), and updated as the best translation conditions. The

  Next, with reference to FIG. 13, an example of a translation condition input screen for browsing information related to a translation project that does not have the right to accept a translation request will be described. As shown in FIG. 13, the translation condition input screen includes a translation request number field, a translation fee field, a translation period field, a total contribution field, a source URI field, a translation source language field, a translation destination language field, and a minimum sharing amount field. , A translator name field, a translator number field, a translation request number field, a translation fee field, a translation period field, an “OK” button, and a “cancel” button. These are the same as the translation condition input screen shown in FIG.

  Of the information in the request DB 1531 (see FIG. 5), the translation request number field, translation fee field, translation period field, original URI field, translation source language field, translation destination language field, and minimum contribution field are viewed. The translation request number, translation fee, translation period, source URI, translation source language, translation destination language, and minimum contribution of the entry not including the translator number of the translator are read and displayed. In the total amount of contributions column, the contributions of entries including the same translation request number in the request status storage area 154 (see FIG. 6) are totaled and displayed. The information being browsed relates to a translation project that does not present the best translation conditions, and all the displayed information is the translation conditions presented by other translators.

  In the translator name display field and the translator number field, the name and translator number of the currently viewed translator are read from the translator information storage area 151 (see FIG. 3) and displayed. The translation request number column is a column for inputting a translation request number for changing the translation condition.

  The translation fee column is a column for inputting how much lower the translation fee is to be presented than the current translation fee (translation fee column). A fee obtained by subtracting the input fee from the translation fee displayed in the translation fee column is a fee that the translator presents as a new translation fee. This translation fee is temporarily stored in the RAM 11 (see FIG. 2).

  The translation period column is a column for inputting how short a translation period is to be presented from the current translation period (translation period column). A period obtained by subtracting the input period from the translation period displayed in the translation period column is a period presented by the translator as a new translation period. This translation period is temporarily stored in the RAM 11 (see FIG. 2).

  The “OK” button is pressed to confirm the information input in the input field. By depressing the “OK” button, the confirmed input information (translation fee, translation period) is overwritten and stored in the translation fee and translation period of the request DB 1531 (see FIG. 5).

  The “Cancel” button is pressed when invalidating the information input in the input field. By pressing the “Cancel” button, the translation fee and translation period temporarily stored in the RAM 11 (see FIG. 2) are deleted.

  For example, in the example shown in FIG. 13, “Ito Hanako” (translator number “T1”) is a screen viewed from the display screen of the translator client 3 (see FIG. 1). For the translation request with the translation request number “3”, the translation fee is “50,000 yen”, the translation period is “14 days”, the total amount of contribution is “35,000 yen”, and the original URI Is "http://bbbb.co.jp/A3.html", the source language is "Japanese", the target language is "English", and the minimum share is "300 yen" . For the translation request with the translation request number “4”, the translation fee is “60,000 yen”, the translation period is “28 days”, and the total amount of contribution is “2,000 yen” The original URI is "http://bbbb.co.jp/A4.html", the source language is "Japanese", the target language is "French", and the minimum share is "300 yen" It is. Among these conditions, for the translation request with the translation request number “4”, the translation fee is to be changed to “50,000 yen”, which is “10,000 yen”, and the translation period is further set to “10 days”. "I'm trying to change it to a short" 18 days ". The presented conditions are stored in the request DB 1531 (see FIG. 5) together with the translator number of the entered translator. Thus, the translator “Hanako Ito” (translator number “T1”) has the right to accept a translation request for the translation request number “4”. Accordingly, when “Hanako Ito” inputs translation conditions via the translator client 3 (see FIG. 3), the translation condition input screen shown in FIG. 12 is displayed.

  As described above, the translator can present the translation conditions via the translation condition input screen, and the right to accept the translation request can be obtained by presenting the best translation conditions. Then, when the total amount of contributions applied by the translation requester exceeds the translation fee, the acceptance of the application for translation conditions from the translator is terminated and stored in the request DB 1531 (see FIG. 5). An order for a translation request is made to a translator with a translator number.

  Next, with reference to FIGS. 14 to 18, processing when the translation requester requests translation of the requested content will be described. 14 is a main flowchart of translation request processing, FIG. 15 is a flowchart of translation request registration processing, FIG. 16 is a flowchart of ordering processing, and FIG. 17 is a flowchart of request participation processing. 18 is a flowchart of the translation use process.

  First, the main flowchart of the translation request process will be described with reference to FIG. In the translation request process, a translation requester, a request participant, and a translation user receive information input via the requester client 2 (see FIG. 1), a translation request registration process, a translation request participation process, Executes ordering processing for translators and usage processing by translation users.

  As shown in FIG. 14, in the translation request process, first, a request URI input screen (see FIG. 7) is displayed on the client client 2 (see FIG. 1), and the request URI and the translation destination language are received from the translation requester. (S101). Next, it is determined whether or not a translation request has already been made for the same requested content. If a translation request has not yet been made, a translation request registration process for newly registering a translation request (see S117, FIG. 15). , Described later). If a translation request has already been made, a request participation process for participating in the requested translation request as a request participant (S121, see FIG. 17) or a translation user as a translation content The translation use process (S119, see FIG. 18) is executed.

  Whether or not a translation request has been made is determined by checking whether or not the same URI as the request URI input on the request URI input screen (see FIG. 7) is stored in the request URI column of the request DB 1531 (see FIG. 5). (S103). If the same URI is not stored (S103: NO), it is determined that a translation request has not yet been made, and a translation request registration process for newly registering a translation request for the input request URI (see S117, FIG. 15). , Described later). In the translation request registration process, when a translation request is registered and the amount of contributions requested by the translation requester for the registered translation request exceeds the translation fee, an order for the translation request is made to the translator. The

  On the other hand, when the same URI as the input request URI is already stored in the request URI column of the request DB 1531 (see FIG. 5) (S103: YES), the translation request has already been made by another translation requester. Next, it is determined whether or not the requested content indicated by the requested URI has already been translated and the translated content is registered (S105). This determination is made by determining whether a URI indicating the location of the translated content is stored in the translation result URI column of the request DB 1531 (see FIG. 5). If the URI is stored in the translation result URI field of the request DB 1531 (see FIG. 5) (S105: YES), the translation of the requested content has already been completed and the translated content has been registered. A process of using the translated content (S107 to S119) is performed.

  In the process of using the translated content (S107 to S119), it is first determined whether or not the requested content has been changed (S107). The translator translates the original text content acquired from the URI in the request URI column (see FIG. 5) of the request DB 1531. If the requested content indicated by the request URI is changed after the acquisition of the original text content, This is because the translated content may not be used as it is without being reflected in the original content. This is because if the requested content is changed, the already translated content cannot be used as it is, and retranslation is required. Whether or not the requested content has been changed is determined by acquiring the original text content indicated by the URI stored in the original URI field of the request DB 1531 (see FIG. 5), and presently indicating the URI stored in the requested URI field. This is done by comparing with the requested content. If there is no difference between the two contents, there is no change in the requested content from the time of translation (S107: NO), that is, no new translation is required, so the translation requester becomes a translation user and obtains the translated content. Translation use processing is performed (S119, see FIG. 18, described later). As a result, the translation requester can acquire the translated content on condition that the usage fee is paid.

  On the other hand, if there is a change in the requested content since the time of translation (S107: YES), whether to use the translated content based on the requested content before the change or re-translate to the translation requester Processing for prompting selection is performed (S109 to S115). First, the original text content indicated by the URI stored in the original text URI column of the request DB 1531 (see FIG. 5) is compared with the requested content indicated by the URI stored in the request URI column. Then, the ratio of the difference portion in the entire content is calculated and displayed on the client client 2 (see FIG. 1) (S109). Next, information on the date and time when the translated content was created is displayed on the client client 2 (see FIG. 1) (S111). Based on these pieces of information, the translation requester is prompted to select whether to use already translated content or to request retranslation of the changed requested content (S113). When the translation requester selects retranslation of the requested content (S115: YES), the process proceeds to a translation request registration process (S117, see FIG. 15, which will be described later) for newly registering a translation request, and the requested content after the change Execute translation request registration for. On the other hand, when the translation requester determines that the translated content is to be used (S115: NO), the translation requester becomes a translation user and performs a translation usage process for obtaining the translated content (S119, see FIG. 18, described later). . By executing the above processing, the translation requester completes the translation of the requested content, and if the requested content has been changed even if the translated content is registered, It is possible to select whether to use the translated content obtained by translating the requested content or to re-translate the changed requested content.

  On the other hand, when the URI is not stored in the translation result URI column of the request DB 1531 (see FIG. 5) (S105: NO), the translation of the requested content is still completed although the translation request is registered by another translation requester. It will be in a state that is not. Therefore, next, a request for translation of the requested content has already been made to the translator, and the translation work has been started, or no request for translation of the requested content has been placed. It is determined whether the application is being accepted (S123). This determination is made based on information stored in the order status column of the request DB 1531 (see FIG. 5). If “ordered” is stored in the order status column and the requested content has already been ordered for translation (S123: YES), it is not possible to jointly request translations as request participants. After the translation work is completed, it is necessary to perform a translation use process (S119, see FIG. 18, described later) for becoming a translation user and using the translated content. Therefore, a contact information input screen (see FIG. 10) is displayed from the requester client 2 (see FIG. 1) in order to notify the translation requester to use the translated content after the translation is completed (S125). . The contact information input via the contact information input screen is stored in the translation completion contact field of the request DB 1531 (see FIG. 5).

  On the other hand, when “unordered” is stored in the order status column of the request DB 1531 (see FIG. 5) and the requested content is not ordered (S123: NO), the translation requester becomes the request participant and translates. In order to participate in the request, a request participation process (S121, FIG. 17, described later) is executed. In the request participation process, the request participant can request a translation of the requested content jointly with the translation requester and other request participants by applying for the share.

  Next, the translation request registration process will be described with reference to FIG. As shown in FIG. 15, in the translation request registration process, first, a translator who orders the translation of the requested content indicated by the request URI entered by the translation requester on the request URI input screen (see FIG. 7) is determined ( S151). The translator searches for and determines a translator who can translate the description language of the requested requested content into the target language among the translators stored in the translator information storage area 151 (see FIG. 3). Specifically, the language and translation destination language of the requested content specified by the requested URI entered via the requested URI input screen (see FIG. 7) are referred to, and these languages are stored in the translator information storage area. The translator stored in the translatable language field 151 (see FIG. 3) is selected (S151). If there are multiple translators selected, select one. Then, the selected translator information is temporarily stored in the RAM 11 (see FIG. 2). Next, a request condition input screen (see FIG. 8) is displayed on the client client 2 (see FIG. 1), and initial conditions for the translation request are presented to the translation requester (S153). The request condition is received from the translation requester (S155). The conditions for accepting are a contribution, a minimum contribution, a usage fee, an order deadline or a payment deadline. The accepted value is temporarily stored in the RAM 11 (see FIG. 1) (S155).

  Then, it is determined whether or not the “OK” button is selected under this condition (S157). If the “OK” button is selected (S157: YES), then personal information (name, address, bank account, contact information, credit card number, credit card expiration date) via the personal information input screen (not shown) ) Is executed (S159). The personal information input by the translation requester is stored in the translation requester information storage area 152 (see FIG. 4), and a requester number is newly assigned. Next, the content indicated by the request URI is stored in the original text storage area 155 (see FIG. 2) as the original text content (S161), and the input request conditions (share, minimum share, usage fee, order date), The request conditions (translation requester, translator, source language, target language, request URI, translation period, translation fee) stored in the RAM 11 (see FIG. 2) are stored in the request DB 1531 (see FIG. 5). Assign a translation request number. Further, the translation requester number of the translation requester, the assigned translation request number, and the input share are stored in the request status storage area 154 (see FIG. 6) (S165).

  Next, the amount stored in the translation fee column of the request DB 1531 (see FIG. 5) is compared with the sum total of the applied contributions (hereinafter referred to as “total amount of contributions”) (S167). The total amount of contributions is the sum of the contributions of entries whose translation request number stored in the translation request number column of the request status storage area 154 (see FIG. 6) is the same number as the translation request number assigned in S165. To calculate. Then, when the contribution becomes equal to or higher than the translation fee, that is, when the translation requester applies for the contribution higher than the translation fee (S167: YES), an ordering process for the translator is executed (S169, see FIG. 16). ). On the other hand, if the share is less than the translation fee (S167: NO), the ordering process is not performed, the translation request registration process is terminated, and the process returns to the translation request process (see FIG. 14). Then, in the subsequent application process (S212, see FIG. 14) to the request for translation from the requesting participant, and the commission application process (see FIG. 19) by presenting the translation conditions from the translator, the total amount of contribution is more than the translation fee. In this case, the ordering process (see FIG. 16) is performed.

  Next, the ordering process will be described with reference to FIG. In the ordering process, when the total amount of contributions applied by the translation requester and the requesting participant exceeds the translation fee, an order for the translation request is made to the translator. Therefore, when the total amount of contribution is changed in the translation request registration process (see FIG. 15) and the request participation process (see FIG. 17), and the translation fee is changed in the translation commission application process (see FIG. 19). When this happens, the ordering process is executed.

  As shown in FIG. 16, in the ordering process, firstly, a share applied for by each translation requester is charged. Specifically, an application fee payment request is transmitted to the credit company management computer 6 (see FIG. 1) (application fee payment step), and it is confirmed that the payment procedure has been completed (application fee payment confirmation step). For the personal information for the payment request, refer to the credit card number and the credit card expiration date in the personal information input in S159 (see FIG. 15). In the application fee payment confirmation step, application fee payment is confirmed from all the translation requesters of the entry including the target translation request number stored in the request status storage area 154 (see FIG. 6) (S203: YES), a translation request is notified to the translator stored in the entry including the translation request number of the target translation request in the request DB 1531 (see FIG. 5) (S205), and the request DB 1531 (see FIG. 5). Is stored in the status column (S207), the process is terminated, the process returns to FIG. 15, and the process returns to the translation request registration process (see FIG. 14). As a result, translation of the requested content by the translator who has received the notification is started. On the other hand, when the application fee payment from the translation requester cannot be confirmed (S203: NO), the payment request is canceled and refunded (S209), and the payment procedure fails in the request status storage area 154 (see FIG. 6). The entry including the requested translation requester is deleted and excluded from the list (S211), the excluded translation requester is notified of the exclusion (S213), the process ends, and the translation request registration process (see FIG. 15) Return to). As a result, a request for a translation request from the requesting participant (see FIG. 17) and a translation condition presentation from the translator (see FIG. 19) are continuously received. In this way, the translation request is registered by the translation requester.

  Next, the request participation process will be described with reference to FIG. In the request participation process, if the request content identical to the request content requested by the translation requester has already been registered as a translation request by another translation requester, the translation requester becomes the request participant and applies for the share The request content is requested to be translated together with the translation requester and other request participants. In the request participation process, in S101 (see FIG. 14), the same URI as the request URI inputted via the request URI input screen (see FIG. 7) displayed on the requester client 2 (see FIG. 1) is displayed. , Already stored in the request URI column of the request DB 1531 (see FIG. 5), and the translator request has not been ordered yet, and “unordered” is stored in the order status column. If executed.

  As shown in FIG. 17, in the request participation process, first, a participant condition input screen (see FIG. 9) is displayed on the client client 2 (see FIG. 1), and the translation period, translation fee, minimum contribution, and contribution The total amount, the usage fee, the order due date, and the payment due date are displayed (S301). Next, the requested participant accepts the contribution applied by inputting into the contribution column (S303).

  In this state, when the “OK” button is selected and the input condition is confirmed (S305: YES), personal information (name, address, bank account, contact information, An input screen (not shown) for a credit card number and a credit card expiration date is displayed, and input of personal information is accepted (S307). The inputted personal information is stored in the translation requester information storage area 152 (see FIG. 4), and a new requester number is assigned. Then, the input contribution is stored in the translation requester number column and the contribution column in the request status storage area 154 (see FIG. 6) together with the translation requester number (S309).

  Next, the translation fee of the registered request DB 1531 (see FIG. 5) is compared with the total amount of contribution (S311). The total amount of contributions is the sum of the contributions of entries whose translation request number stored in the translation request number column of the request status storage area 154 (see FIG. 6) is the same number as the translation request number assigned in S309. To calculate. Then, when the total amount of contribution becomes equal to or higher than the translation fee (S311: YES), an ordering process for the translator (see FIG. 16) is executed (S313). In the ordering process, after requesting the share (S201, see FIG. 16), the translator is notified of the translation request (S205, see FIG. 16). In this way, a translation request is made to the translator.

  By executing the above processing, the request participant requesting the translation of the requested content can apply for the contribution, and can request the translation of the requested content jointly with the translation requester and other request participants. Become. Since the translation requester and the participation requester can request the translation of the requested content by paying a part of the translation fee as a contribution, it is possible to significantly reduce the fee burden.

  Next, the translation use process will be described with reference to FIG. The translation use process is a process executed when a translation user who wishes to acquire translation content pays a usage fee and uses the translation content when the translation content is already registered. In S101 (see FIG. 14), the same URI as the request URI input via the request URI input screen (see FIG. 7) displayed on the requester client 2 (see FIG. 1) is already the request URI of the request D1531. This processing is executed when it is determined that the translation content is registered when the URI is stored in the column (see FIG. 5) and the URI is stored in the translation result URI column (see FIG. 5). .

  As shown in FIG. 18, in the translation use process, first, the user condition input screen (see FIG. 11) is displayed on the client client 2 (see FIG. 1), and the URI to be translated and the use fee are presented (S251). . Then, in this state, the user is urged to determine whether or not to pay the usage fee and use the translated content (S253). In this state, when the “OK” button is selected and the translation user pays the displayed usage fee (S255: YES), the translation user is charged for the usage fee (S257). Specifically, a payment request for the application fee is transmitted to the credit company management computer 6 (see FIG. 1) (use fee payment step), and it is confirmed that the payment procedure has been completed (use fee payment confirmation step). The personal information for the payment request refers to the credit card number and the credit card time limit in the stored personal information. Next, “1” is added to the use count stored in the use count column of the request DB 1531 (see FIG. 2) (S259). Then, the translated content is displayed on the client client 2 (see FIG. 1) and provided to the translation user (S261), the process is terminated, and the process returns to the translation request process (see FIG. 14). By executing the above processing, the translation user can acquire and use the translated content on condition that the usage fee is paid. The paid usage fee is returned to the translation requester, the requesting participant, and the translator in a translator reward process (see FIG. 22) and a cashback process (FIG. 23) described later.

  Next, with reference to FIG. 19 and FIG. 20, the translation request entrustment application process by the translator will be described. In the present embodiment, when a translation requester registers a translation request, a translator in charge of translation and translation conditions (translation fee, translation period) are provisionally determined (S151, see FIG. 15). However, when other translators submit a contract application that presents better conditions for the translation requester than the prescribed translation conditions (translation fee, translation period), that is, a lower translation fee or a shorter translation period, It is possible to obtain a right to entrust translation of requested content on behalf of a translator who is provisionally determined. After that, the total amount of contributions from the translation requester will be more than the translation fee, and until the translation request is ordered, the translation will be sent to the translator who applied for the contract with the cheapest translation fee and the shortest translation period. The right to trust is granted. Then, an order for the translation request is officially made to the translator who has the right to receive the commission when the total amount of the contribution applied for by the translation requester becomes higher than the translation fee. FIG. 19 is a flowchart of the translation commission application process, and FIG. 20 is a flowchart of the translation result registration process.

  First, with reference to FIG. 19, the translation commission application process will be described. The translation commission application process is a process when a commission application is performed by a translator via the translator client 3 (see FIG. 1). The display screen to be displayed on the translator client 3 (see FIG. 1), the screen (see FIG. 12) displaying the information of the translation project that has the right to entrust the translation request, and the right to entrust the translation request. The translation condition input operation of the translator is facilitated by switching between the screen (see FIG. 13) displaying the information on the untranslated project.

  As shown in FIG. 19, in the translation commission application process, first, a translator who intends to commission a contract is specified via the translator client 3 (see FIG. 1), and a display screen is determined and displayed. The method for specifying the translator may be specified by, for example, a login ID when logging in to the translator client 3 (see FIG. 1), or another screen for separately specifying a name or the like for the translator. May be displayed and specified by the inputted input information.

  Next, a screen (see FIG. 12) that displays information related to a translation item that has the right to accept a translation request, and a screen that displays information related to a translation item that does not have the right to accept a translation request (see FIG. 12). 13), the translator is urged to select which one to display. Here, when the display of a screen (see FIG. 12) for displaying information relating to a translation project having the right to accept a translation request is selected, the translator information of the identified translator is entered in the translator information storage area 151. Is extracted from the number field (see FIG. 3), and it is confirmed whether or not the same number as the extracted translator number is stored in the translator number field of the request DB 1531 (see FIG. 5). And when it is memorize | stored in the translator number column (refer FIG. 5), according to the translation condition input screen shown in FIG. 12, the translation fee of the entry containing the translator number, translation period, original URI, translation source language, The translation destination language, the minimum contribution, and the corresponding total contribution are calculated from the request status storage area 154 (see FIG. 2) and displayed on the translator client 3 (see FIG. 1) (S351). On the other hand, when the display of a screen (see FIG. 13) for displaying information relating to a translation project that does not have the right to accept a translation request is selected, the translator number of the identified translator is stored in the translator information storage area 151. An entry extracted from the number field (see FIG. 3) and the same number as the extracted translator number is not stored in the translator number field of the request DB 1531 (see FIG. 5) according to the translation condition input screen shown in FIG. The translation fee, translation period, original URI, translation source language, translation destination language, minimum contribution, and the corresponding total contribution amount are calculated from the request status storage area 154 (see FIG. 2), and the translator client 3 ( (See FIG. 1) (S351).

  Next, a translation fee (hereinafter referred to as “new translation fee”) and a translation period (hereinafter referred to as “new translation period”) input by the translator via the translator client 3 (see FIG. 1). "New translation fee" and "new translation period" together are referred to as "new translation conditions") (S353). These are compared with the translation fee stored in the translation fee column (see FIG. 5) of the request DB 1531 and the translation period (see FIG. 5) stored in the translation period column. If the new translation fee is more expensive than the stored translation fee or if the new translation period is longer than the stored translation period (S355: YES), the input translation condition is greater than the stored translation condition. Since it is not a good condition, the process returns to S351 as invalid, and the translation condition is continuously received from the translator (S351).

  When the new translation fee is cheaper than the stored translation fee, or when the new translation period is shorter than the stored translation period (S355: NO), the input translation condition is an existing translation condition. It is judged that the condition is better. If the new translation fee is lower than the stored translation fee (S357: YES), the new translation fee is overwritten and stored in the translation fee column (see FIG. 5) of the request DB 1531, and the translator number column ( The translator number of the translator who entered the translation condition is overwritten and stored in (see FIG. 5) (S359). As a result, the translator who entered the translation conditions has the right to accept the translation request, and the translation request can be accepted when the total amount of contributions applied by the translation requester exceeds the translation fee presented. Ready to go. Then, the translator who has been overwritten and has lost the right to accept the translation request is notified that the translator having the right has been changed (S360). Next, when the new translation period is shorter than the stored translation period (S361: YES), the new translation period is overwritten and stored in the translation period column (see FIG. 5) of the request DB 1531 (S363). As a result, the translator who has entered the translation conditions has the right to accept the translation request, and can accept the translation request if the contribution applied by the translator exceeds the translation fee presented. become. Then, the translator who has been overwritten and has lost the right to accept the translation request is notified that the translator having the right has been changed (S364).

  Next, the translation fee stored in the translation fee column (see FIG. 5) of the request DB 1531 is compared with the total amount of contribution calculated from the request status storage area 154 (see FIG. 2). Then, when the total amount of contribution becomes equal to or more than the translation fee (S365: YES), the process proceeds to the ordering process (S367, see FIG. 16). In the ordering process, after requesting the contribution from the translation requester who applied for the payment of the contribution (see S201, FIG. 16), the translation of the requested content is made to the translator who has entered the translation conditions as described above. A request is notified (S205, see FIG. 16).

  As explained above, by changing the display content as appropriate, the translation conditions of the translation project that has the right to accept translation requests are presented to encourage the presentation of better conditions, while the right to accept translation requests By presenting the translation conditions of the translation projects that have not been obtained, it is encouraged to present even better conditions so that the right to accept a translation request can be obtained. In addition, translators obtain the right to accept translation requests by presenting better translation conditions than other translators, and when the total amount of contribution exceeds the translation fee, You can accept translation requests. On the other hand, the translation requester will present a better translation condition for the translation requester in order to obtain the right to entrust the translation request, so that the translation request is made at a lower translation fee and in a shorter translation period. It becomes possible.

  Next, the translation result registration process will be described with reference to FIG. In the translation result registration process, when the translation request is notified to the translator and the translation work is performed, as a result of the translation content being translated, the translation content is stored in the translation result storage area 156 of the management server 1. Registration processing is performed (see FIG. 2). The translated content is input by a translator through a translation result registration screen (not shown) displayed on the translator client 3.

  As shown in FIG. 20, in the translation result registration process, first, a translation request number for which the translator has commissioned and performed the translation work is input (S401), and then the requested content specified by the translation request number. The translated content translated from is selected (S403). The selected translation result content is stored in the translation result storage area 156 (see FIG. 2) of the management server 1, and a new URI indicating the stored location is assigned (S405), and input in the request DB 1531 (see FIG. 5). It is stored in the translation result URI field of the entry including the same number as the translated request number. Then, referring to the request status storage area 154 (see FIG. 6), the translation requester corresponding to the translation requester number of the entry including the same number as the input translation request number is informed that the translation has been completed. Then, notification of URI indicating the location where the translation result newly given in S405 is stored is performed (S407). Furthermore, a notification that the translation has been completed is sent to the contact stored in the translation completion contact field of the entry including the same number as the input request number in the request DB 1531 (see FIG. 5) (S409). Then, referring to the information in the transfer account column of the translator information storage area 151 (see FIG. 3), the translation fee is transferred to the translator (S411). Through the above translation result registration process, the translation requester can know that the translation has been completed and the translated content can be acquired, and the translated content can be acquired. In addition, the translation user can know that the translation has been completed and the translated content can be used.

  Next, with reference to FIG. 21 to FIG. 23, a description will be given of a monthly process that is a process for returning the usage fee paid by the translation user to the translation requester and the translator. The translated content translated by the translator is stored in the translation result storage area 156 (see FIG. 2) of the management server 1 by the translation result registration process (see FIG. 20) by the translator. The registered translation content can be acquired by a translation user on the premise of payment of a usage fee. In the present invention, a part or all of the paid usage fee is returned to the translator and the translation requester, thereby reducing the burden of the translation fee paid by the translation requester and the translator. Urges further reduction of the translation fee presented by. FIG. 21 is a main flowchart of monthly processing, FIG. 22 is a flowchart of translator reward processing that is processing for paying a translator, and FIG. 23 is processing for paying a translator. It is a flowchart of a certain cash-back process.

  First, monthly processing will be described with reference to FIG. Monthly processing is batch processing that starts at a monthly cycle. As shown in FIG. 21, in the monthly process, a translator reward process (S431) and a cashback process (S433) are executed. Then, in order to prevent the remuneration amount from being paid multiple times during the monthly processing of the next month, the usage count stored in the usage fee column (see FIG. 5) of the request DB 1531 is cleared (S435).

  Next, the translator reward process will be described with reference to FIG. As shown in FIG. 22, in the translator reward process, a reward is calculated that is a usage fee to be returned to each translator stored in the translator information storage area 151 (see FIG. 3). Here, the usage fee is a fee paid for the translation user to acquire the translated content in the translation usage process (see FIG. 18). First, translator information stored in the translator information storage area 151 (see FIG. 3) is acquired in order from the top (S501). When the process for all translators is completed (S503: NO), the process is terminated and the process returns to the monthly process (see FIG. 20).

  If unprocessed translators remain (S503: YES), first, the temporary variable “reward” is initialized with “0” (S505). Next, in the request DB 1531 (see FIG. 5), information in the translation result URI column of the entry including the same translator number as the obtained translator number is obtained (S507). If the translation result URI is stored (S509: YES), it is determined that the translation content created by the translator is registered and may have been used by the translation user. Next, the usage count stored in the usage count column of the same entry is acquired (S511), and the usage fee stored in the usage fee column is acquired (S513). Then, the amount of remuneration is calculated according to the calculation formula ““ reward ”+ (“ use fee ”ד use count ”ד translator return rate ””). In the formula, “translator return rate” is a parameter that is determined in advance and stored in the RAM 11 (see FIG. 2). Then, the value of the obtained reward amount is stored in the temporary variable “reward” (S515). Then, the process returns to S509 and the request DB 1531 (see FIG. 5) is referred to, and the above process is repeated for all entries whose URI is stored in the translation result URI column among the entries for the target translator (S509 to S509). S515).

  When the calculation processing of the reward amount is completed for all entries (S509: NO), unless the temporary variable “reward” is “0”, that is, when there is a reward to be paid to the translator (S517: YES), the calculated amount of the temporary variable “reward” is transferred to the translator's account (S519). Then, returning to S501, the same processing is repeated for the request information for the remaining translators. As a result, more reward money can be returned to translators who have translated translated content that is frequently used.

  Next, the cache back process will be described with reference to FIG. As shown in FIG. 23, in the cash-back process, a remuneration that is a usage fee to be returned to each translation requester stored in the translation requester information storage area 152 (see FIG. 4) is calculated. Here, the usage fee is a fee paid for the translation user to acquire the translated content in the translation usage process (see FIG. 18). First, information on the translation requester stored in the translation requester information storage area 152 (see FIG. 4) is acquired in order from the top (S451). When the processes for all the translation requesters are completed (S453: NO), the process ends and the process returns to the monthly process (see FIG. 20).

  If an unprocessed translation requester remains (S453: YES), first, the temporary variable “reward” is initialized with “0” (S455). Next, in the request DB 1531 (see FIG. 5), information in the translation result URI column of the entry including the same translation requester number as the acquired translation requester number is acquired (S457). If the translation result URI is stored (S459: YES), it is determined that the translation content created by the translation requester is registered and may have been used by the translation user. Next, the usage count stored in the usage count column of the same entry is acquired (S461), and the usage fee stored in the usage fee column is acquired (S463). Then, the amount of the remuneration is calculated according to the calculation formula ““ reward ”+ (“ use fee ”ד use count ”ד translation requester return rate ”) × (“ share ”/“ total amount of share ”)”. . In the formula, “translation requester return rate” is a parameter that is determined in advance and stored in the RAM 11 (see FIG. 2). Then, the value of the obtained reward amount is stored in the temporary variable “reward” (S465). Returning to S459, the request DB 1531 (see FIG. 5) is referred to, and the above processing is repeated for all entries whose URI is stored in the translation result URI column among the entries for the target translation requester (S459). ~ S465).

  When the calculation processing of the reward amount is completed for all entries (S459: NO), if the temporary variable “reward” is not “0”, that is, if there is a reward to be paid to the translation requester (S467). : YES), the calculated amount of the temporary variable “reward” is transferred to the account of the translation requester (S469). Then, the process returns to S451, and the same processing is repeated for the request information for the remaining translators. As a result, more reward money can be returned to the translation requester who requested the translated content that is used frequently and the translation requester who has paid a large share.

  As described above, the translation requester pays a share for the request for translation of the requested content, and jointly requests the translation, thereby reducing the charge burden on each translation requester. In addition, the so-called reverse auction allows the translator to present the translation conditions and allows the translator who has presented the best translation conditions to accept the translation. The burden of sharing is further reduced. Also, after the translation by the translator is completed, the usage fee paid by the translation user who wants to obtain the translation content is returned to the translation requester and translator, resulting in a lower cost required for the translation request. It becomes. Here, by associating the amount returned to the translation requester with the paid share, it becomes a motivation to apply for a large share at the time of the initial share payment application. Further, by reducing the usage fee to the translator, the translation fee that the translator applies for commissioning is set low, and as a result, the burden of the translation requester on the translation request is reduced.

  The client client 2 and the translator client 3 shown in FIG. 1 correspond to a “user terminal”. In addition, information input on the translation request screen shown in FIG. 7 and received by the management server 1 corresponds to “content information”. Also, information received by the management server 1 that is input on the request condition input screen shown in FIG. 8 and the participation condition input screen shown in FIG. 9 corresponds to “translation request information”.

  Further, the translation fee stored in the translation fee column in the request DB 1531 shown in FIG. 5 corresponds to “translation fee”. Further, the request DB 1531 shown in FIG. 5 corresponds to “request information storage unit”, “translation fee storage unit”, “consignment fee storage unit”, “translation period storage unit”, and “consignment period storage unit”. Also, the translation result storage area 156 shown in FIG. 2 corresponds to “translated content storage means”. Also, the translator information storage area 151 shown in FIG. 3 corresponds to “translator information storage means”.

  In addition, the step of accepting the content requested for translation and the contribution in S101 in the translation request process shown in FIG. 14, S155 in the translation request registration process shown in FIG. 15, and S303 in the request participation process shown in FIG. Corresponds to the “request information reception step”. Further, the step of determining the translation fee and the translation period in S153 in the translation request registration process shown in FIG. 15 corresponds to the “translation fee determining step” and the “translation period determining step”. Also, the step of notifying the translator of the translation request in S205 in the ordering process shown in FIG. 16 corresponds to the “ordering step”. Further, the step of accepting the translation fee in S353 in the translation commission application process shown in FIG. Further, the step of comparing the translation fee with the commission fee in S357 in the translation commission application process shown in FIG. 19 corresponds to the “fee comparison step”. Further, the step of updating the translation fee in S359 in the translation commission application process shown in FIG. 19 corresponds to the “translation fee update step” and the “translator update step”. Further, the step of comparing the translation period with the commission period in S361 in the translation commission application process shown in FIG. 19 corresponds to the “period comparison step”. Further, the step of updating the translation period in S363 in the translation commission application process shown in FIG. 19 corresponds to the “translation period update step”. Further, the step of notifying the translator in S360 and S364 in the translation commission application process shown in FIG. 19 corresponds to the “translator change notification step”. Further, the step of determining a translator in S151 in the translation request registration process shown in FIG. 15 corresponds to a “translator determination step”. Also, the step of accepting the usage fee in S251 in the translation usage process shown in FIG. 18 corresponds to the “use fee acceptance step”. 23 corresponds to the “translation requester return step”, and the translator reward process shown in FIG. 23 corresponds to the “translator return step”. Further, in S401 and S403 in the translation result registration process shown in FIG. 20, the step of receiving the translation result corresponds to the “translation content reception step” and the “translation content storage step”.

  Further, in S101 in the translation request process shown in FIG. 14, S155 in the translation request registration process shown in FIG. 15, and S303 in the request participation process shown in FIG. Corresponds to the “request information receiving means”, and the CPU 10 that performs the process of determining the translation fee and the translation period in S153 in the translation request registration process shown in FIG. 15 corresponds to the “translation fee determining means”. Further, the CPU 10 that sends a translation request notification to the translator in S205 in the ordering process shown in FIG. 16 corresponds to an “ordering unit”. Further, the CPU 10 that performs the process of receiving the translation result in S401 and S403 in the translation result registration process shown in FIG.

  The translation mediation management method of the present invention is not limited to the embodiment described above, and can be modified without departing from the gist of the present invention.

  In the above embodiment, the translation requester applied for payment of the share as part of the translation fee, and requested translation, but is not limited to this, for example, the translation requester applied for the number of units, A translation request may be made by paying as an allotted amount an amount obtained by multiplying the determined unit price per unit. In this case, the translator presents the number of recruitment as a translation condition and applies for a commission request.

It is a schematic diagram which shows the structure of the apparatus used with a translation mediation system. 2 is a block diagram illustrating a hardware configuration of a management server 1. FIG. It is a schematic diagram which shows an example of a structure of the translator information storage area 151. FIG. It is a schematic diagram which shows an example of a structure of the translation requester information storage area. 5 is a schematic diagram illustrating an example of a configuration of a request DB storage area 153. FIG. 5 is a schematic diagram illustrating an example of a configuration of a request status storage area 154. FIG. It is an example of a request URI input screen for inputting a request URI. It is an example of a request condition input screen. It is an example of a participation condition input screen. It is an example of a contact input screen. It is an example of a use application screen. This is an example of a translation condition input screen in which a translator who presents the best translation conditions and has the right to accept a translation request browses the translation conditions presented by himself / herself. It is an example of the translation condition input screen which browses the information regarding the translation project which does not have the right to entrust a translation request. It is a main flowchart of a translation request process. It is a flowchart of a translation request registration process. It is a flowchart of an ordering process. It is a flowchart of a request participation process. It is a flowchart of a translation utilization process. It is a flowchart of a translation commission application process. It is a flowchart of a translation result registration process. It is a main flowchart of a monthly process. It is a flowchart of a translator reward process. It is a flowchart of a cash-back process.

Explanation of symbols

1 management server 2 client client 3 translator client 6 credit company management computer 7 internet 15 hard disk device 151 translator information storage area 152 translation requester information storage area 153 storage area 154 request status storage area 155 original text storage area 156 translation result storage Area 157 Content management program storage area

Claims (9)

A translation mediation method processed by a translation mediation device connectable to a network,
Request for payment of translation request information including at least content information, which is information for specifying the content requested for translation, and a share paid as part of the translation fee required for requesting translation of the content Is output from a user terminal connected to the network, a request information receiving step for receiving the translation request information and a payment application for the share,
Translation fee determination that determines the amount of the translation fee based on the content information included in the translation request information when the translation request information is received in the request information reception step, and stores the determined translation fee in the translation fee storage means Steps,
An ordering step of notifying the translator to request the translation of the content when the total amount of the share applied for payment received in the request information receiving step exceeds the amount of the translation fee. When,
A translated content receiving step for receiving the translated content when the translated content that is the translated content of the content ordered in the ordering step is output from a user terminal connected to the network;
A translation mediation method comprising: a translation content storage step of storing the translation content received in the translation content reception step in a translation content storage means. A request information storage step for storing the content information received in the request information reception step in a request information storage means that can be disclosed;
A commission fee receiving step for accepting a bid application for the commission fee when the bid application for the commission work for the content specified by the content information performed by the translator is output from a user terminal connected to the network. When,
When accepting a bid application for a commission fee in the commission fee acceptance step, a commission fee storage step of storing the commission fee in a commission fee storage means;
A charge comparison step of comparing the trust fee stored in the trust fee storage means with the translation fee stored in the translation fee storage means;
In the fee comparison step, when it is determined that the amount of the commissioned fee is less than the amount of the translation fee, the amount of the commissioned fee is determined as the amount of the translation fee, and the translation fee stored in the translation fee storage means is A translation fee update step to be updated,
A translator update step in which the applicant who applied for a bid for the commission fee that has been the translation fee updated in the translation fee update step is a translator to be ordered.
The ordering step includes:
The translation mediation method according to claim 1, wherein the translator updated in the translator update step is notified to request translation of content. A translation period determining step of determining a translation period based on content information included in the translation request information when storing translation request information in the request information receiving step, and storing the determined translation period in a translation period storage unit;
A commission period acceptance step for accepting a bid application for the commission period when a bid application for the commission period of the content translation work specified by the content information performed by the translator is output from a user terminal connected to the network When,
The acceptance period storage step of storing the acceptance period in the acceptance period storage means when accepting a bid application for the acceptance period in the acceptance period acceptance step;
A period comparison step for comparing the commission period stored in the commission period storage means with the translation period stored in the translation period storage means;
In the period comparison step, when it is determined that the trust period is shorter than the translation period, the trust period is determined as the translation period, and a translation period update step of updating the translation period of the translation period storage unit;
A translator update step in which the applicant who applied for a bid for the contract period that became the translation period updated in the translation period update step is a translator to be ordered.
The ordering step includes:
3. The translation mediation method according to claim 1, wherein a notification for requesting translation of content is sent to the translator updated in the translator update step.   When the translator is updated in the translator update step, the translator update notification step further includes a translator change notification step for notifying the translator before the update that the translator has been changed. The translation mediation method according to claim 2 or 3. Translation of content specified by the content information received in the request information receiving step with reference to the translator information storage means that is information relating to the translator and stores at least information on the translator's translatable language. A translator determination step for determining possible translators;
The ordering step includes:
5. The translation mediation method according to claim 1, wherein a notification for requesting translation of the content is sent to the translator. When a person other than the translation requester wishes to obtain the translation content stored in the translation content storage means in the translation content storage step, a payment application for a usage fee is paid from the user terminal connected to the network. A usage fee reception step for accepting an application for payment of the usage fee, if output,
A translation request that pays each translation requester a usage fee according to the ratio of the amount of the contribution paid by each translation client to the total amount of the contribution paid by the translation client who requested the translation content creation. The translation mediation method according to claim 1, further comprising a person returning step. When a person other than the translation requester wishes to obtain the translation content stored in the translation content storage means in the translation content storage step, a payment application for a usage fee is paid from the user terminal connected to the network. A usage fee reception step for accepting an application for payment of the usage fee, if output,
The translation mediation method according to any one of claims 1 to 6, further comprising a translator return step of paying a part or all of a usage fee to a translator who created the translation content. A translation intermediary device connectable to a network,
Request for payment of translation request information including at least content information, which is information for specifying the content requested for translation, and a share paid as part of the translation fee required for requesting translation of the content And request information receiving means for receiving via the network,
When the request information receiving means accepts the translation request information, the translation fee determination is performed to determine the amount of the translation fee based on the content information included in the translation request information and to store the determined translation fee in the translation fee storage means Means,
Ordering means for notifying translators of requesting translation of the content when the total amount of shares applied for payment received by the request information receiving means exceeds the amount of the translation fee When,
A translated content receiving means for receiving, via a network, translated content that is a content obtained by translating the content ordered by the ordering means;
A translation mediation apparatus comprising translation content storage control means for storing translation content received by the translation content reception means in translation content storage means.   The translation mediation program which makes a computer implement each process step of the translation mediation method in any one of Claims 1 thru | or 7.

Images