Web program, printing program, server, and system

Abstract

To provide a technique capable of easily printing label data in a server in a system promoting use of label data.SOLUTION: A web application 36 incorporated in a label management server 3 receives, from a terminal 1, selection of label data including a text object associated with attribute, and when receiving an instruction to print the selected label data, calls a printing application 46B of the terminal 1. The terminal 1 downloads label data to be printed by using a printing application 46. The terminal 1 rewrites a text of the text object associated with attribute, which is included in the downloaded label data, into attribute information of a log-in user corresponding to the attribute. The printing application 46B causes a label printer 2 to perform printing based on the label data after the re-writing.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The technical field disclosed in this specification relates to a web program, a printing program, a server, and a system used in a system that utilizes label data. [Background technology]

[0002] A conventional system for utilizing content data is known in which a server that stores content data is provided on the Internet, content data is posted from a user's device, i.e., uploaded to the server, and the content data is then downloaded to another user's device.

[0003] An example of a document disclosing the above-mentioned system is Patent Document 1. In the points management system disclosed in Patent Document 1, when photo data is uploaded from User A's PC to a WWW server and purchased by User B's PC and downloaded from the WWW server, points are added to User B, the purchaser, according to the purchase amount, and further points are added to User A, the contributor, according to the data size of the photo data when the photo data is uploaded or downloaded. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-99746 Summary of the Invention [Problem to be solved by the invention]

[0005] In recent years, there have been systems that utilize label data used to print labels on label printers as content data. In such systems, a user may upload label data they created to a server, and other users may download and print that label data. However, label data created by a user may contain private information, such as a user's name. When downloading and printing such label data from the server, the user must rewrite the private information with their own information before printing the label data, which can be a time-consuming process for the user. [Means for solving the problem]

[0006] A web application made to solve the above-mentioned problems is a web program executable by a server, the server being able to access a label database and a user database, the label database being able to register a plurality of label data, the label data being data that can be printed by a label printer, the label data being able to include text objects with attributes associated therewith, the user database being able to register a plurality of user information, the user information being information associated with a user account required for login, the user information being able to include attribute information corresponding to the attributes, when label data is uploaded from a first information processing device, the server's computer being caused to execute a registration process to register the uploaded label data in the label database, and the server's computer being further caused to receive from a second information processing device label data registered in the label database that includes the text objects with the attributes associated therewith. and causing the computer of the server to execute an acceptance process for selecting at least one of the label data and accepting a print instruction for the selected label data, and further causing the computer of the server to execute a print request process for causing a label printer connected to the second information processing device to print based on the selected label data in response to accepting the print instruction for the selected label data from the second information processing device, wherein the print request process calls a print program installed on the second information processing device using a call instruction, and the call instruction for calling the print program includes label information necessary for downloading the selected label data, and the print program called by the call instruction downloads the selected label data to the second information processing device using the label information included in the call instruction, and obtains attribute information corresponding to the attribute associated with the text object included in the downloaded label data from the user information of the logged-in user registered in the user database.The system is configured to cause the label printer to perform printing based on the label data in which the text shown in the text object associated with the attribute included in the downloaded label data has been rewritten with the acquired attribute information.

[0007] A web program having the above configuration accepts, from a second information processing device, a selection of label data including text objects associated with attributes. When the web program further accepts an instruction to print the selected label data, it calls the print program of the second information processing device using a call instruction including label information for the label data to be printed. The second information processing device downloads the label data to be printed using the print program, rewrites the text of the text objects associated with attributes included in the downloaded label data with the attribute information of the logged-in user corresponding to the attributes, and causes the label printer to print based on the rewritten label data. In this way, the logged-in user of the second information processing device can automatically call the print program of the second information processing device by simply selecting the label data to be printed and issuing a print instruction. The text objects for the label data are then rewritten with the logged-in user's information and printed. This saves the logged-in user the trouble of operating the print program or editing the text objects, allowing them to easily print label data containing private information.

[0008] A server, system, and control method for realizing the functions of the above-mentioned web program, a storage medium readable by a computer of a server that stores the web program, a printing program, a storage medium readable by a computer of an information processing device that stores the printing program, and an information processing device that can execute the printing program are also new and useful. [Effects of the Invention]

[0009] The technology disclosed in this specification realizes a technology that allows label data stored on a server to be easily printed in a system that utilizes label data. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is an explanatory diagram schematically illustrating a label data sharing system according to a first embodiment. [Figure 2] FIG. 1 is a diagram illustrating an example of a URL scheme. [Figure 3] FIG. 2 is a diagram illustrating an example of a label database. [Figure 4] FIG. 2 is a diagram illustrating an example of a user database. [Figure 5] FIG. 10 is a sequence diagram illustrating an example of a posting process. [Figure 6] FIG. 10 is a sequence diagram illustrating an example of a label display process. [Figure 7] FIG. 10 is a diagram illustrating an example of a screen transition. [Figure 8] FIG. 10 is a diagram illustrating an example of a screen transition. [Figure 9] FIG. 10 is a sequence diagram illustrating an example of a call process. [Figure 10] FIG. 10 is a sequence diagram illustrating an example of replacement printing processing. [Figure 11] FIG. 10 is a sequence diagram illustrating an example of replacement printing processing executed in the label data sharing system of the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] An embodiment of a web program, a print program, a server, and a system for sharing label data will be described in detail with reference to the accompanying drawings. This embodiment discloses a system in which an information processing device incorporating a print program and a server incorporating a web program can be connected via a network.

[0012] (First embodiment) A label data sharing system 100 (hereinafter referred to as "system 100") of the first embodiment shown in Fig. 1 is a system provided by, for example, a label printer vendor. The system 100 comprises a label management server 3 and a terminal 1, and the label management server 3 and terminal 1 are connected via the Internet 9. The terminal 1 can be connected to a label printer 2. The system 100 is an example of a "system." The label management server 3 is an example of a "server." The Internet 9 is an example of a "network."

[0013] 1 shows only one terminal 1 that can be connected to the label management server 3, but in reality, many terminals 1 are connected to the label management server 3. The label printer 2 may be connected to multiple terminals. Furthermore, the terminal 1 may be used by multiple users.

[0014] The label printer 2 is a device that has at least a printing function and a communication function. The label printer 2 is connected to the terminal 1 via wireless LAN communication such as Wi-Fi (registered trademark) or short-range wireless communication such as Bluetooth (registered trademark). The label printer 2 may also be connected to the terminal 1 via a wired connection using the USB communication standard.

[0015] For example, the tape that can be attached to each label printer 2 is predetermined for each model. When the label printer 2 receives a print job that includes label data, it prints based on the label data while feeding the tape and ejects the printed tape outside the machine. A label of a specified size is formed using the ejected tape.

[0016] The terminal 1 is an information processing device used by the owner or user (hereinafter referred to as "user") of the label printer 2. The terminal 1 is, for example, a smartphone, a tablet terminal, or a personal computer (PC). The terminal 1 has a controller 10 including a CPU 11 and a memory 12. The CPU 11 is an example of a "computer of an information processing device." The terminal 1 has a user interface (hereinafter referred to as "user IF") 13 and a communication interface (hereinafter referred to as "communication IF") 14, which are connected to the controller 10.

[0017] The label management server 3 is a server provided by the vendor of the label printer 2. The label management server 3 of this embodiment comprises a controller 30 including a CPU 31 and a memory 32. The CPU 31 is an example of a "server computer." The label management server 3 comprises a user interface (hereinafter referred to as "user IF") 33, a communication interface (hereinafter referred to as "communication IF") 34, and an interface 35, which are connected to the controller 30.

[0018] Note that the controllers 10 and 30 in Figure 1 are general terms for the hardware and software used to control the terminal 1 or the label management server 3, and do not necessarily represent a single piece of hardware that actually exists in the terminal 1 or the label management server 3.

[0019] The CPU 11 of the terminal 1 and the CPU 31 of the label management server 3 execute various processes according to programs read from the memory 12 of the terminal 1 and the memory 32 of the label management server 3, respectively, and based on user operations. The memories 12 and 32 store various programs and various data. The memories 12 and 32 are also used as work areas when various processes are executed. The buffers provided in the CPUs 11 and 31 are also an example of memory. Note that examples of the memories 12 and 32 are not limited to ROM, RAM, HDD, etc. built into the terminal 1 or the label management server 3, but may also be storage media readable and writable by the CPUs 11 and 31, such as recording media, for example, CD-ROM, DVD-ROM, etc.

[0020] The user IF 13, 33 includes hardware that displays a screen for notifying the user of information and hardware that accepts user operations. For example, the user IF 13 includes a display 13a that displays information. The user IF 13, 33 may be a combination of a display that can display information and a mouse, keyboard, or the like that has an input acceptance function, or may be a touch panel that has both a display function and an input acceptance function.

[0021] The communication IFs 14 and 34 include hardware for communicating with external devices. The terminal 1 and the label management server 3 can connect to the Internet 9 via the communication IFs 14 and 34 and communicate with each other. The terminal 1 can connect to the label printer 2 via the communication IF 14. The communication IFs 14 and 34 can use communication standards such as Ethernet (registered trademark), Wi-Fi (registered trademark), and USB. The terminal 1 and the label management server 3 may be equipped with multiple communication IFs 14 and 34 that support multiple communication standards.

[0022] The memory 12 of the terminal 1 stores various programs and data, including an operating system (hereinafter referred to as "OS") 21, a browser 45, and a print application program (hereinafter referred to as "print app") 46. The browser 45 and the print app 46 are also referred to as "client apps." The print app 46 is an example of a "print program."

[0023] OS21 is a multitasking OS that can process multiple tasks in parallel by managing and switching between them. Examples of OS21 include Windows (registered trademark), macOS (registered trademark), Linux (registered trademark), iOS (registered trademark), and Android (registered trademark).

[0024] The OS21 of this embodiment has a mechanism for launching a program by a URL scheme and executing a function specified by the URL scheme. The OS21 has registered therein programs to be launched by the URL scheme. That is, the OS21 stores, for example, the scheme name of the URL scheme and the program to be launched by the scheme name in association with each other.

[0025] As shown in FIG. 2, a URL scheme includes a function specification section 110, a first data specification section 120, a second data specification section 130, a third data specification section 140, and a fourth data specification section 150. The function specification section 110 specifies the program to be launched by the URL scheme and the function to be executed by the launched program. For example, in this embodiment, the function specification section 110 describes the scheme name of the printing application 46 and a print command for downloading and printing label data. If the label data includes text with attributes, the print command may include a function to rewrite the attributes. The OS 21 stores the scheme name of the printing application 46 in association with the printing application 46.

[0026] Data to be used when executing a function specified by a URL scheme is specified in first to fourth data specification units 120 to 150. In this embodiment, label information indicating the download target is specified in first data specification unit 120, account information is specified in second data specification unit 130, attribute information is specified in third data specification unit 140, and member information is specified in fourth data specification unit 150. The attribute information and member information will be described later.

[0027] Returning to Figure 1, the browser 45 is a program used to browse websites. The browser 45 is launched by the user of the terminal 1, and when launched, has the function of displaying on the display 13a a web page provided by a web server (e.g., the label management server 3) indicated by a specified URL. The browser 45 may be supplied by the OS 21 vendor and incorporated into the OS 21, or it may be installed on the terminal 1 separately from the OS 21.

[0028] The print application 46 is an application program provided by the vendor of the label printer 2. The print application 46 has a function to send a print job including label data to the label printer 2 and cause the label printer 2 to print based on the label data. The label printer 2 that performs printing may be registered in advance in the print application 46, or may be selected during print settings. The print application 46 may also have a function to create and edit label data on the terminal 1.

[0029] The memory 32 of the label management server 3 stores various programs and data, including a web application program (hereinafter referred to as a "web app") 36. The web app 36 is an application program that can be used on the browser of the terminal 1 without being installed on the terminal 1. The web app 36 is an example of a "web program."

[0030] The terminal 1 can access the Web application 36 using the browser 45 or the browser function of the print application 46 and use the services provided by the Web application 36. For example, the Web application 36 can provide services such as registering label data uploaded, i.e., posted from the terminal 1 (hereinafter also referred to as "posted label data"), to the label management server 3 and downloading the registered label data from the label management server 3 to the terminal 1, on the condition that the terminal 1 is logged in.

[0031] The Web application 36 of this embodiment includes a front-end application 37 and a back-end application 38. The front-end application 37 and the back-end application 38 may be held by different servers.

[0032] The front-end application 37 has, for example, a web server function. The front-end application 37 can be directly accessed from the terminal 1. The front-end application 37 has prepared therein various types of page information to be displayed on the screen of the terminal 1.

[0033] The backend application 38 has a function separate from the web server function. Basically, the backend application 38 cannot be accessed directly from the terminal 1. The backend application 38 can access, for example, a user database (hereinafter referred to as "user DB 5") 5 or a label database (hereinafter referred to as "label DB") 6 via the interface 35 to store and search for information.

[0034] 3, the label DB 6 stores multiple pieces of information about label data that can be provided to users. The label data stored in the label DB 6 may be data prepared in advance by the vendor of the label printer 2, or may be posted label data posted by users who use the label management server 3. In the label DB 6, a record including a label ID 61, a user ID (creator) 62, label data 63, label supplemental information 64, and a label data posting date 65 is created for each piece of label data.

[0035] Information for identifying label data is stored in the label ID 61. The user ID of the user who posted the label data is stored in the user ID (creator) 62. For label data created by someone other than the user, the ID of an administrator may be stored in the user ID (creator) 62, or the user ID (creator) 62 may be left blank.

[0036] The label data 63 stores label data containing information constituting the label data in a predetermined storage format. The information constituting the label data includes, for example, information and layout of the objects constituting the label data. Examples of objects include text objects, image objects, frame objects, and table objects. Text, layout, and size are associated with and stored as text objects included in the label data. Furthermore, attributes can be associated with and stored as text objects. Attributes are information indicating the type of text that can be replaced with user information. Attributes include, for example, private information such as first name, last name, first name, phonetic reading, address, phone number, email address, postal code, and account name.

[0037] The label supplemental information 64 stores information received on the posting screen for posting label data. The label supplemental information 64 includes, for example, the label name, category, and an image showing an example of how the label is used. The label data posting date 65 stores information indicating the date the label data was posted.

[0038] As shown in Fig. 4, the user DB 5 can store user information about users who can use the services provided by the system 100. In the user DB 5, a record including a user ID 51, a user name 52, a password 53, a name 54, an address 55, a telephone number 56, and member information 57 is created for each user. The name 54, the address 55, and the telephone number 56 are examples of "attribute information." The user ID 51 and the user name 52 are examples of "user account" and "account information."

[0039] The user ID 51 stores information for identifying a user. The user name 52, password 53, name 54, address 55, and telephone number 56 store the username, password, name, address, and telephone number entered by the user at the time of user registration and used when using the system 100. The member information 57 can store at least one piece of information about a member registered by the user. The member information includes, for example, a member ID for identifying the member and member attribute information. The member attribute information is, for example, name, address, and telephone number. The user DB 5 may also store attribute information corresponding to attributes other than name, address, and telephone number, such as an email address or postal code. The same applies to member attribute information stored in the member information 57.

[0040] Next, the operational procedures executed in the system 100 of this embodiment will be described with reference to the drawings. Note that in this embodiment, each process other than user operations basically indicates the processing of the CPUs 11 and 31 in accordance with instructions written in programs such as the print application 46, front-end application 37, and back-end application 38. In this specification, various processes performed by the controllers 10 and 30 or the CPUs 11 and 31 in accordance with programs such as the OS 21, browser 45, print application 46, front-end application 37, and back-end application 38 may be described as if each program independently performs various processes, for convenience's sake. The processing by the CPUs 11 and 31 also includes hardware control using the API (application programming interface) of the OS. In this specification, the operation of each program will be described without a detailed description of the OS. Furthermore, the term "acquire" is used as a concept that does not necessarily require a request.

[0041] (Posting process) Referring to Figure 5, the posting process for posting label data to the label management server 3 will be described. Here, an example will be described in which user A (hereinafter referred to as "poster A") creates and posts label data. For ease of explanation, the reference numerals of the terminal 1 used by poster A and its components will be given the suffix "A". Terminal 1A is an example of a "first information processing device".

[0042] 5A, contributor A, for example, starts the print application 46A (A01) and creates label data (A02). When the print application 46A receives an instruction to create a label, for example, it opens an editing screen and accepts the selection of objects to be included in the label data and various settings for the selected objects.

[0043] For example, as shown in FIG. 5B, the print application 46A generates label data LB including a sock graphic object OB1 and a text object OB2 in response to a user operation. For example, the text "Back Bonito" and the attribute "Name" are stored in association with each other in the text object OB2. The text object OB2 may also be stored in association with the character size, font, and so on. Upon receiving a save instruction, the print application 46A saves the generated label data in memory 12A.

[0044] Thereafter, the print application 46A performs an upload operation (A03). For example, the print application 46A accesses the label management server 3 using its own browser function, and then, upon receiving an operation on the post button, requests the label management server 3 to send a posting screen using the communication IF 14A. The front-end application 37 provides a posting screen (not shown) to the print application 46A on the condition that poster A has logged in, and causes it to be displayed on the display 13aA of the terminal 1A. For example, upon receiving, on the posting screen displayed on the terminal 1A, instructions to specify the label data LB to be posted, input label supplemental information, and execute a new post, the front-end application 37 receives a posting instruction from the terminal 1A (A04). The posting instruction includes the label data specified on the posting screen.

[0045] When the front-end application 37 receives a posting instruction from terminal 1A via communication IF 34, it transfers the posting instruction to back-end application 38 (A05). The posting instruction includes the posted label data LB posted from terminal 1A, the label supplemental information entered on the posting screen, and the user ID of logged-in poster A. The back-end application 38 accesses the label DB 6 using the interface 35 and registers the posted label data LB of poster A in the label DB 6 (A06). A06 is an example of a "registration process."

[0046] 4, the backend application 38 creates a new label ID and creates a record in which the new label ID is stored in label ID 61 in the label DB 6. After that, for the record including the new label ID 61, the backend application 38 stores the user ID attached to the posting instruction, the posted label data LB of poster A, and the label supplemental information in user ID (creator) 62, label data 63, and label supplemental information 64, respectively. In addition, the backend application 38 stores the posting date of the posted label data in label data posting date 65.

[0047] When the registration of the label data is completed, the back-end application 38 notifies the terminal 1A of "registration complete" via the front-end application 37 (A07, A08). Upon receiving the "registration complete" notification, the terminal 1A displays, for example, a message indicating that the registration of the posted label has been completed (A09). This allows the poster A to know that the posting has been completed.

[0048] In this embodiment, the posting process is performed using the browser function of the print application 46A, but for example, the terminal 1A may perform the posting process using the browser 45A. That is, the poster A may log in to the label management server 3 via the browser 45A and display the posting screen on the browser 45A.

[0049] (Download and print) 6 to 10, the process of calling the print application 46 from a web page provided by the label management server 3 and downloading and printing label data to the terminal 1 will be described. Here, an example will be described in which the label management server 3 connected to the terminal 1 displays the label data registered in the label management server 3 on the browser 45 of the terminal 1 so that it can be viewed (label display process), and when it receives a selection of label data and a print instruction on the viewing screen, it calls the print application 46 of the terminal 1 (call process), and the called print application 46 downloads the selected label data to the terminal 1, replaces the text of the downloaded label data with user B's attribute information, and prints it (substitution print process). For ease of explanation, the reference numerals of the terminal 1 used by user B and its components will be suffixed with the letter "B." Terminal 1B is an example of a "second information processing device."

[0050] (Label display processing) 6, when the browser 45B of the terminal 1B accesses the label management server 3 (E01), the front-end application 37 acquires access display information from the back-end application 38 (E02). The access display information is, for example, latest information on label data and content data registered in the label management server 3. The front-end application 37 provides a web page including the access display information to the terminal 1B (E03), and causes the browser 45B to display it on the display 13aB (E04).

[0051] 7(A) includes a login button 312, a posted label display tab 321, a content display tab 322, and a label search field 323. When the posted label display tab 321 is operated, the web page 300 switches to a screen that displays label data registered in the label management server 3. For example, the screen displays the label data in order of arrival, with images of label data for which attribute information can be written and images of label data for which attribute information cannot be written mixed together. When the content display tab 322 is operated, the web page 300 switches to a screen that displays content data such as fonts registered in the label management server 3.

[0052] The web page 300 is provided with an operator 325 for setting search conditions for label data. When the front-end application 37 receives an operation of the operator 325 on the terminal 1A, it provides information for displaying the search condition setting screen 400 shown in Fig. 7(B) to the terminal 1A, and causes the browser 45B to display it on the display 13aB.

[0053] The search condition setting screen 400 can accept settings for the display order and the categories to be searched. The search condition setting screen 400 also has a replacement checkbox 401 for setting whether label data including text objects associated with attributes should be included in the search. The search condition setting screen 400 also has a search execution button 405 for issuing an instruction to search for posted label data according to the accepted search conditions.

[0054] For example, when the search execution button 405 is operated with the replacement checkbox 401 checked, as shown in FIG. 6, the front-end application 37 receives an instruction from the terminal 1B to search for label data that can replace the text (E11).

[0055] The front-end application 37 requests a list of label data for which text can be replaced from the back-end application 38 (E12). The back-end application 38 accesses the label DB 6 and extracts label data including text objects associated with attributes (E13). Steps E11 to E13 are an example of an "extraction process." The back-end application 38 creates a replaceable label list based on the extracted label data (E14). The replaceable label list includes, for each piece of extracted label data, an image showing an example of use and a label ID, for example.

[0056] The back-end application 38 passes the created replaceable label list to the front-end application 37 (E15). The front-end application 37 includes the replaceable label list in a web page and sends it to the terminal 1B (E16), and causes the browser 45B to display the web page on the display 13aB (E16).

[0057] As a result, for example, as shown in web page 300x in FIG. 7(C), images of label data including text objects associated with attributes are preferentially displayed on terminal 1B, making it easier for user B to select label data whose text can be rewritten.

[0058] The search condition setting screen 400 may also be provided with an attribute selection field for selecting an attribute. In this case, the front-end application 37 may assign the attribute selected in the attribute selection field to the request in E12, and the back-end application 38 may extract label data in which the attribute assigned to the request is associated with a text object in E13. For example, if "Name" is selected as the attribute, only label data including text objects associated with "Name" is extracted, and text objects associated with attributes other than "Name," such as "Address" or "Telephone Number," are not extracted. This narrows down the images of label data displayed on the web page 300x to those including the selected attribute, making it easier for the user to select label data.

[0059] When an image 350 corresponding to the posted label data LB of poster A is tapped among the images of label data displayed on the web page 300x, the front-end application 37 of the terminal 1B accepts the selection of label data (E21), as shown in FIG. 6. Note that multiple label data may be selected. The front-end application 37 requests the back-end application 38 to view the selected label data (E22). The request includes the label ID of the selected label data (posted label data LB in this embodiment).

[0060] The back-end application 38 accesses the label DB 6, extracts the record corresponding to the label ID attached to the label data viewing request, and acquires the viewing information required to display the viewing screen (E23). The viewing information may include, for example, a sample image of the specified label data, the recommended tape name, label width, label color, text color, and label ID. The viewing information may also include the label name, purpose, category, and the username of contributor A who created the label. The back-end application 38 passes the acquired viewing information to the front-end application 37 (E24).

[0061] The front-end application 37 includes the viewing information received from the back-end application 38 in a web page and sends it to terminal 1B, the requester of the label data viewing request (E25). When terminal 1B receives the web page using communication IF 14B, it causes browser 45B to display on display 13aB a viewing screen for viewing poster A's posted label data LB (E26).

[0062] For example, the viewing screen 500 shown in Fig. 8(A) displays information included in the viewing information. Furthermore, the viewing screen 500 includes a first operation button 501, a second operation button 502, and a third operation button 503. The first operation button 501 is an operator that instructs the user to download the label data to be viewed. The second operation button 502 is an operator that instructs the user to print the label data to be viewed. The third operation button 503 is an operator that instructs the user to return to the previous screen.

[0063] (Call processing) When the front-end application 37 receives an operation of the second operation button 502 on the terminal 1B, it receives a print instruction from the terminal 1B (E31) in a state in which the selection of the posted label data LB has been received, as shown in Fig. 9. E31 is an example of the "reception process."

[0064] If the user is not already logged in, the front-end application 37 performs login authentication (E33), and requests the back-end application 38 to transmit user information (E41) on the condition that user B is logged in. The request includes the account information used for login (user ID in this embodiment).

[0065] The back-end application 38 accesses the user DB 5, acquires user information corresponding to the user ID attached to the request (E42), and returns the acquired user information to the front-end application 37 (E43). The user information may be information including all information of the record associated with the user ID, or may be information including part of information of the record associated with the user ID (for example, the user ID, attribute information, and member information). E41 to E43 are examples of the "first attribute acquisition process" and the "second attribute acquisition process."

[0066] If member information is included, the front-end application 37 performs a member selection process (E51). E51 is an example of a "web-side member selection process."

[0067] Specifically, for example, the front-end application 37 displays a print target confirmation screen 550 shown in FIG. 8B on the terminal 1B. The print target confirmation screen 550 displays a first radio button 551, a second radio button 552, and a third radio button 553 along with a sample image of the selected post label data DB. The first radio button 551 is an operator for confirming that only the user himself / herself is to be printed. The second radio button 552 is an operator for confirming that the user has selected the print target. The third radio button 553 is an operator for confirming that the user himself / herself and all members included in the member information are to be printed. The print target confirmation screen 550 is provided with a display button 554 that becomes active when the second radio button 552 is selected. Furthermore, the print target confirmation screen 550 is provided with a print execution button 555 for instructing printing and a back button 556 for returning to the previous screen.

[0068] For example, when the display button 554 is operated with the second radio button 552 selected, the front-end application 37 displays a member selection screen 600 shown in FIG. 8(C). The member selection screen 600 is a screen for accepting the selection of the print target. The member selection screen 600 displays the name of the logged-in user (here, "Yamada Hanako") and the names of the members included in the member information of the user information (here, the names "Yamada Ichiro" and "Yamada Taro") along with check boxes 601a, 601b, and 601c. The member selection screen 600 includes a confirm button 603 and a cancel button 605.

[0069] For example, if user B wants to replace the name "Ura Katsuo" included in the label indicated by the posted label data LB with "Yamada Hanako" and "Yamada Taro" and print the replaced name, he or she checks check boxes 601a and 601c and taps confirm button 603. When the front-end application 37 accepts this operation on terminal 1B, it accepts the member selection, closes member selection screen 600, and displays print target confirmation screen 550 on terminal 1B.

[0070] Thereafter, when the print execution button 555 on the print target confirmation screen 550 is operated, the front-end application 37 accepts the selection of a member. In response to this, the front-end application 37 acquires the attribute information of the selected member, "Name (Yamada Taro), Address (***1), Phone Number (***2)," from the member information attached to the start instruction, as shown in Fig. 9 (E52). E52 is an example of "member attribute acquisition processing."

[0071] When the cancel button 605 on the member selection screen 600 is operated, the front-end application 37 closes the member selection screen 600 without accepting the selection of a member, and displays the print target confirmation screen 550. When the second radio button 552 is selected and no member is selected, the front-end application 37 does not accept a print instruction even if the print execution button 555 is operated. In this case, the front-end application 37 may display an error notification on the terminal 1B prompting the user to select a member.

[0072] On the other hand, for example, if user B wants to replace the name "Ura Katsuo" included in the label indicated by the posted label data LB with only his or her own name and print it, the user taps the print execution button 555 with the first radio button 551 selected on the print target confirmation screen 550. In this case, the front-end application 37 does not execute E52 shown in FIG. 9 and does not acquire member attribute information from the member information.

[0073] Also, for example, if user B wants to replace the name "Ura Katsuo" included in the label indicated by the posted label data LB with his / her own name and the names of all members and print it, he / she selects the third radio button 553 on the print target confirmation screen 550 and taps the print execution button 555. In this case, the front-end application 37 acquires the attribute information of all members from the member information at E52 shown in FIG.

[0074] In response to the operation of the print execution button 555 (E61), the front-end application 37 generates a URL scheme (E71). Specifically, the front-end application 37 writes, in the function specification section 110 of the URL scheme, the scheme name of the print application 46 and a print command for executing the function of downloading label data, replacing the text, and printing. The front-end application 37 writes, in the first data specification section 120 of the URL scheme, the label ID of the posted label data LB selected when the second operation button 502 was operated. The front-end application 37 writes, in the second data specification section 130 of the URL scheme, the account information used for login. The front-end application 37 writes, in the third data specification section 140, all attribute information included in the user information acquired in E43. In this embodiment, the name (Yamada Hanako), address (****), and phone number (****) are written in the third data specification section 140. The front-end application 37 describes all of the member attribute information acquired in E52 in the fourth data specification section 150. For example, if, in E51, "Yamada Taro" is selected as the member to be printed from among the members "Yamada Ichiro" and "Yamada Taro" included in the user information, all of the attribute information associated with the member ID of the selected "Yamada Taro" (in this embodiment, the name (Yamada Taro), address (***1), and telephone number (***2)) is described in the fourth data specification section 150.

[0075] In the member selection process, if the first radio button 551 is operated and only the user himself / herself is to be printed, the front-end application 37 creates a URL scheme in which the fourth data designation section 150 is blank or in which the fourth data designation section 150 does not exist. In the member selection process, if the third radio button 553 is operated and the user himself / herself and all members are to be printed, the front-end application 37 provides a fourth data designation section 150 for each member and creates a URL scheme in which member attribute information is described in each fourth data designation section 150. Furthermore, in the member selection process, if the user does not select himself / herself as the print target and only members are selected, the front-end application 37 creates a URL scheme in which the third data designation section 140 is blank or in which the third data designation section 140 does not exist and in which member attribute information is described in the fourth data designation section 150.

[0076] The front-end application 37 transmits the generated URL scheme to the terminal 1B (E72). The URL scheme is received by the OS 21B of the terminal 1B. The URL scheme is an example of a "call instruction." E72 is an example of a "print request process."

[0077] The OS 21B passes a start instruction to the print application 46B associated with the scheme name of the received URL scheme (E73). The start instruction includes the label ID, account information, and attribute information described in the first to third data specification sections 120, 130, and 140 of the URL scheme. If member attribute information is described in the URL scheme, the member attribute information is also added to the start instruction. The print application 46B is automatically started in response to the start instruction (E74).

[0078] When the third operation button 503 on the viewing screen 500 is operated, the front-end application 37 returns to the previous screen without accepting a print instruction or creating a URL scheme, and can accept reselection of label data. When the first operation button 501 on the viewing screen 500 is operated, the front-end application 37 accepts a download request instead of a print instruction, obtains the selected label data via the back-end application 38, sends it to terminal 1B, and stores it in a volatile storage area of ​​terminal 1B.

[0079] (Replacement printing process) 10, if the account information attached to the activation instruction does not match the account information registered in the print application 46B (OPT: account information mismatch), the print application 46B performs login authentication (E91), and if they match, sends a download request to the label management server 3 (E101). The download request includes the label ID attached to the activation instruction.

[0080] The front-end application 37 transfers the download request with the label ID attached to it to the back-end application 38 (E102). The back-end application 38 accesses the label DB 6, acquires the label data corresponding to the label ID attached to the request (E103), and returns it to the front-end application 37 (E104). The front-end application 37 transmits the label data to the terminal 1B (E105). In this embodiment, posted label data LB is transmitted. E105 is an example of a "download process."

[0081] When the print application 46B receives the posted label data LB using the communication IF 14B, it temporarily stores the posted label data LB in the memory 12. The print application 46B extracts attribute information corresponding to the attribute associated with the received label data from the attribute information and member attribute information attached to the launch instruction (E110). For example, the posted label data LB includes a text object OB2 associated with the attribute "name". The print application 46B is attached with all attribute information of logged-in user B (name (Yamada Hanako), address (****), and telephone number (****)) and all attribute information of the selected member "Yamada Taro" (name (Yamada Taro), address (***1), and telephone number (***2)). The print application 46B extracts the attribute information "Yamada Hanako" and "Yamada Taro" corresponding to the attribute "name" of the posted label data LB from this attribute information and member attribute information. E110 is an example of an "attribute information acquisition process".

[0082] The print application 46B replaces the text included in the posted label data LB with the attribute information extracted in E110 or the member attribute information (E111). For example, the print application 46B copies the posted label data LB stored in the memory 12, and replaces the text "Ura Katsuo" associated with the attribute "Name" in the copied label data with the name of logged-in user B, "Yamada Hanako," to generate first replaced label data. The print application 46B also copies the posted label data LB again, and replaces the text "Ura Katsuo" with the name of the selected member, "Yamada Taro," to generate second replaced label data.

[0083] The printing application 46B creates a print job for each of the generated replaced label data and sends it to the label printer 2B selected by the printing application 46B (E121). The label printer 2B executes printing for each print job (E122). In other words, the printing application 46B generates print data for the total number of attribute information and member attribute information attached to the startup instruction, and causes the label printer 2B to print based on each print data. As a result, one label is created on which an image of the first replaced label data containing the text "Yamada Hanako" is printed, and one label is created on which an image of the second replaced label data containing the text "Yamada Taro". E121 is an example of a "printing process".

[0084] After transmitting the print job, the print application 46B ends (E123). Upon ending, the print application 46B erases the submitted label data LB, the first replacement label data, and the second replacement label data stored in the memory 12.

[0085] As described above, when the Web application 36 incorporated in the label management server 3 of the first embodiment accepts from terminal 1B the selection of posted label data LB including a text object OB2 associated with the attribute "Name" and further accepts an instruction to print the selected posted label data LB, it calls the print application 46B of terminal 1B using a URL scheme including the label ID of the label data to be printed. Terminal 1B uses the print application 46B to download the posted label data LB to be printed, rewrites the text "Ura Katsuo" of the text object OB2 associated with the attribute "Name" contained in the downloaded posted label data LB to the attribute information of logged-in user B corresponding to that attribute, "Yamada Hanako," and causes the label printer 2B to print based on the rewritten label data. In this way, logged-in user B of terminal 1B simply selects the posted label data LB to be printed and issues a print instruction to automatically call the print application 46B of terminal 1B, and the text object OB2 of the posted label data LB is rewritten with his or her own information and printed. This saves logged-in user B the trouble of operating the print application 46B or editing the text object OB2, and allows him or her to easily print label data that includes private information.

[0086] In the first embodiment, the Web application 36 acquires attribute information of the logged-in user B and passes the attribute information to the print application 46B, which then rewrites the text of the text object in the label data with the attribute information.

[0087] (Second embodiment) Next, a web program, print program, server, and system according to a second embodiment will be described with reference to the drawings. In the system of the second embodiment, the print application 46 is called by a call instruction that does not include attribute information, and replaces the text of the label data with the attribute information it acquires. This differs from the first embodiment, in which the print application 46 is called by a call instruction that includes attribute information, and replaces the text of the label data with the attribute information provided by the web application 36. This section will focus on the differences from the first embodiment, and the same reference numerals as in the first embodiment will be used for configurations and processes that are common to the first embodiment, and descriptions will be omitted where appropriate.

[0088] 11, similarly to the first embodiment, when the front-end application 37 receives a print instruction for post label data LB (E31), it generates a URL scheme (E201) on the condition that the user logs in. E31 is an example of the "reception process."

[0089] Specifically, the front-end application 37 writes, in the function specification section 110 of the URL scheme, the scheme name of the print application 46 and a print command for executing the function of downloading label data, acquiring user information, replacing the text of the downloaded label data with attribute information of the user information, and printing it. The front-end application 37 writes, in the first data specification section 120 of the URL scheme, the label ID of the posted label data LB that was selected when the second operation button 502 was operated. The front-end application 37 writes, in the second data specification section 130 of the URL scheme, the account information used for logging in. In this embodiment, no information is written in the third data specification section 140 and the fourth data specification section 150.

[0090] The front-end application 37 sends the generated URL scheme to the terminal 1B (E202). This URL scheme is an example of a "call instruction." E202 is an example of a "print request process." The OS 21B passes a launch instruction to the print application 46B (E203), which launches the print application 46B (E204). The launch instruction includes the label ID and account information written in the URL scheme, but does not include attribute information or member attribute information. E204 is an example of a "label information acquisition process" or an "account acquisition process."

[0091] The front-end application 37 performs login processing if the account information attached to the startup instruction does not match the account information registered in the print application 46B (E91), and, provided that login is successful, requests the front-end application 37 to download label data (in this embodiment, posted label data LB) corresponding to the label ID attached to the startup instruction (E101). The front-end application 37 acquires posted label data LB via the back-end application 38 and sends it to the print application 46B (E102 to E105). The posted label data LB is stored in a volatile storage area of ​​the memory 12 and is erased when the print application 46B is terminated. E105 is an example of a "download process."

[0092] Furthermore, the print application 46B requests the front-end application 37 to send user information (E221). This request includes account information that matches the URL scheme and the print application 46B. The front-end application 37 transfers this request together with the account information to the back-end application 38 (E222).

[0093] The back-end application 38 accesses the user DB 5 and acquires user information corresponding to the account information attached to the request (E223). The user information may be all of the information included in the record corresponding to the account information, or may be only a portion of the information (for example, attribute information, member information). The back-end application 38 returns the acquired user information to the front-end application 37 (E224). The front-end application 37 transmits the user information to the terminal 1B (E225). E221 and E225 are "attribute information acquisition processing" This is an example.

[0094] If the received user information includes member information, the print application 46B performs a member selection process (E231). This member acquisition process is similar to the member selection process shown in E51 in Fig. 9 except that the screen is provided by the print application 46B, and therefore a detailed description will be omitted. E231 is an example of a "client-side member selection process."

[0095] The print application 46B acquires (E232) attribute information of the member selected in the member selection process of E231 from the member information included in the user information acquired from the label management server 3 in E225. E232 is an example of "member attribute acquisition process".

[0096] The printing application 46B replaces the text in the posted label data LB acquired in E105 (E111), then sends a print job including the replaced label data to the label printer 2B (E121), and causes the label printer 2B to print the replaced label data (E122). E121 is an example of a "printing process." After sending the print job, the printing application 46B terminates (E123).

[0097] The Web application 36 of the second embodiment described above passes the account information of login user B to the print application 46B, and the print application 46B uses the account information to obtain attribute information included in the user information of login user B obtained from the label management server 3, allowing the print application 46B to rewrite the text of text object OB2 in label data LB with the attribute information.

[0098] The embodiments disclosed herein are merely examples and are not intended to limit the scope of the present invention. Therefore, the technology disclosed herein can naturally be improved and modified in various ways without departing from the spirit and scope of the present invention. For example, the program used for posting and displaying the web page 300 and the viewing screen 500 may be either the print application 46 or the browser 45.

[0099] For example, the Web application 36 may call the print application 46B using a deep link instead of a URL scheme. A deep link is an example of a "call instruction."

[0100] For example, if print application 46B is already running when OS21B receives the URL scheme at E72 in FIG. 9 or E203 in FIG. 11, OS21B can have the already running print application 46B download and print the label data specified by the label ID included in the URL scheme.

[0101] For example, the Web application 36 may create a URL including a label ID, account information (user ID), and member ID at E202 in FIG. 11 . In this case, the print application 46B is launched in response to a launch instruction with the label ID, account information (user ID), and member ID attached at E230 in FIG. 11 . If the downloaded label data includes text objects with associated attributes, the print application 46B may request the Web application 36 to send attribute information at E110 in FIG. 11 . This request includes the user ID and member ID attached to the launch instruction and the attributes associated with the text objects in the downloaded label data. The Web application 36 accesses the user DB 5 and extracts a record including the user ID attached to the request. The Web application 36 then reads attribute information corresponding to the attributes attached to the request from the extracted record. The Web application 36 then reads attribute information corresponding to the member ID and the attributes attached to the request from the member information. The Web application 36 sends the read attribute information and member attribute information to the print application 46B. This allows the print application 46B to obtain attribute information corresponding to the attributes of the label data and member attribute information from the user information of the logged-in user. In this case, E110 is an example of an "attribute information acquisition process."

[0102] For example, if the Web application 36 can determine the attributes included in the selected label data before creating the URL scheme in E71 of Fig. 9, it can obtain the attribute information corresponding to the determined attributes directly from the user DB 5, or extract it from the user information obtained in E43. This process is an example of a "first attribute acquisition process" and a "second attribute acquisition process." This allows the Web application 36 to create a URL scheme that includes only the attribute information corresponding to the attributes included in the label data and call the print application 46B, thereby omitting E110 and reducing the load on the print application 46B.

[0103] For example, the label information included in the call instruction, such as the label information described in the first data specification section 120 of the URL scheme, may be a file path or URL indicating the storage location of the label data. In this case, the print application 46B directly accesses the file path or URL to download the label data.

[0104] For example, the call instruction (scheme) may include information indicating whether or not rewriting of the text object associated with the attribute is permitted. In this case, if rewriting is permitted (if not denied), the text of the text object may be rewritten, and if rewriting is not permitted (if denied), the text of the text object may not be rewritten.

[0105] For example, selection of label data by the Web application 36 (E21 in FIG. 6) or acceptance of a print instruction (E31 in FIGS. 9 and 11) may require login. In other words, the Web application 36 may be configured so that selection or print instructions cannot be made without logging in. In this case, E33 in FIG. 9 may be omitted.

[0106] For example, downloading label data using the printing application 46B requires login, and if the user is not logged in when the printing application 46B is started, login may be requested.

[0107] For example, the user DB 5 does not need to include the member information 57. However, the user DB 5 can register multiple pieces of member information in the member information 57, and in addition to the attribute information corresponding to the logged-in user, attribute information acquired from at least one piece of member information can also be included in the call instruction (URL scheme). For each piece of attribute information included in the call instruction, the label printer 2B can be caused to print label data in which the text of a text object associated with an attribute included in the label data to be printed has been rewritten with that attribute, thereby making it possible to print label data in which each piece of attribute information has been rewritten.

[0108] For example, E51 and E52 in Fig. 9 and E231 and E232 in Fig. 11 may be omitted. However, being able to select the member information to be printed increases the degree of freedom in printing.

[0109] For example, E11 to E16 in Fig. 6 may be omitted. However, by extracting label data containing text objects associated with attributes and accepting selection from among them, it becomes easier for the user to select label data into which attribute information can be written.

[0110] For example, the front-end application 37 may not write account information in the URL scheme at E71 in Fig. 9, and may omit E91 in Fig. 10. However, if the account information used by the print application 46 to log in to the Web application 36 matches the account information used by the print application 46 to log in to itself, the print application 46 can download the label data, replace the text, and print it, thereby preventing unauthorized printing by user impersonation.

[0111] For example, in FIG. 11, the print application 46B may download label data from the label management server 3 after acquiring the user information.

[0112] For example, the print application 46B may display a print preview screen to the user IF 13B before transmitting a print job.

[0113] In any sequence diagram disclosed in the embodiments, any of a plurality of processes can be executed in any order or in parallel as long as no contradiction occurs in the process content.

[0114] The processes disclosed in the embodiments may be executed by hardware such as a single CPU, multiple CPUs, or ASIC, or a combination thereof. The processes disclosed in the embodiments may also be realized in various ways, such as a recording medium on which a program for executing the processes is recorded, or a method. [Explanation of symbols]

[0115] 1 device 2. Label printer 3 Label Management Server 6 Label DB 9 Network 11 CPU 21 OS 31 CPU 36 Web Apps 46 Printing App 100 Label Data Sharing System

Claims

1. A web program executable by a server, the server being able to access a label database and a user database, the label database being able to register a plurality of label data, the label data being data that can be printed by a label printer, the label data being able to include text objects with attributes associated therewith, the user database being able to register a plurality of user information, the user information being information associated with a user account required for login, the user information being able to include attribute information corresponding to the attributes, In the server computer, When label data is uploaded from a first information processing device, a registration process is executed to register the uploaded label data in the label database; The computer of the server further comprises: executes a receiving process for receiving, from the second information processing device, a selection of at least one of the label data registered in the label database, the label data including the text object associated with the attribute, and an instruction to print the selected label data; The computer of the server further comprises: and executing a print request process for causing a label printer connected to the second information processing device to print based on the selected label data in response to receiving the print instruction for the selected label data from the second information processing device, wherein the print request process calls a print program installed on the second information processing device using a call instruction, and the call instruction for calling the print program includes label information necessary for downloading the selected label data, the print program called by the call instruction uses the label information included in the call instruction to download the selected label data to the second information processing device, obtains attribute information corresponding to the attribute associated with the text object included in the downloaded label data from the user information of the logged-in user registered in the user database, and causes the label printer to print based on the label data in which text shown in the text object associated with the attribute included in the downloaded label data has been rewritten with the obtained attribute information. A web program configured to:

2. 2. The web program according to claim 1, The computer of the server, executes a first attribute acquisition process to acquire attribute information corresponding to the attribute associated with the text object included in the selected label data from the user information of the login user registered in the user database; In the print request process, a call instruction for calling the print program includes the label information of the selected label data and the attribute information acquired in the first attribute acquisition process, and the print program called by the call instruction downloads the selected label data using the label information included in the call instruction, and causes the label printer to print based on the label data in which text shown in the text object associated with the attribute included in the downloaded label data has been rewritten with the attribute information included in the call instruction. A web program configured to:

3. 3. The web program according to claim 2, The user information registered in the user database may include at least one member information, and the member information may also include attribute information corresponding to the attribute; The computer of the server, executes a second attribute acquisition process for acquiring the attribute information from at least one of the member information included in the user information of the login user registered in the user database; In the print request processing, a call instruction for calling the print program includes the label information of the selected label data, the attribute information acquired in the first attribute acquisition processing, and the attribute information acquired in the second attribute acquisition processing, and the print program called by the call instruction downloads the selected label data using the label information included in the call instruction, and causes the label printer to print based on the label data in which, for each piece of attribute information included in the call instruction, text shown in the text object associated with the attribute included in the downloaded label data has been rewritten with the attribute information. A web program configured to:

4. 4. The web program according to claim 3, The computer of the server, executes a web-side member selection process for accepting a selection of member information to be printed from the member information included in the user information of the login user registered in the user database; In the second attribute acquisition process, the attribute information included in the member information selected in the web-side member selection process is acquired. A web program configured to:

5. 2. The web program according to claim 1, In the print request processing, the call instruction for calling the print program includes the label information of the selected label data and account information of the logged-in user, and the print program called by the call instruction downloads the selected label data using the label information included in the call instruction, obtains the user information of the logged-in user registered in the user database from the server using the account information included in the call instruction, obtains attribute information included in the obtained user information that corresponds to the attribute associated with the text object included in the downloaded label data, and causes the label printer to print based on the label data in which the text shown in the text object associated with the attribute included in the downloaded label data has been rewritten with the obtained attribute information. A web program configured to:

6. 2. The web program according to claim 1, The computer of the server, executes an extraction process from the second information processing device to extract label data that includes the text object associated with the attribute from the label data registered in the label database; In the receiving process, at least one selection is received from the label data extracted in the extraction process. A web program configured to:

7. A printing program executable by an information processing device connectable to a server and a label printer, wherein the server can access a label database and a user database, wherein a plurality of label data can be registered in the label database, the label data is data that can be printed by a label printer, and the label data can include text objects associated with attributes, wherein a plurality of pieces of user information can be registered in the user database, the user information is information associated with a user account required for login, and the user information can include attribute information corresponding to the attributes, The computer of the information processing device When activated by a call instruction from the server, the server executes a label information acquisition process that acquires label information included in the call instruction, and when the server receives a print instruction from the information processing device for label data that is registered in the label database and that includes the text object with which the attribute is associated, the server outputs the call instruction to the information processing device to call the print program, the call instruction including the label information necessary to download the label data specified as the object to be printed in the print instruction, The computer of the information processing device further a download process for downloading the label data designated as a print target in the print instruction using the label information acquired in the label information acquisition process; an attribute information acquisition process that acquires, from the user information of the logged-in user registered in the user database, attribute information corresponding to the attributes associated with the text object included in the label data specified as the print target in the print instruction; a printing process in which the label printer prints the label data in which the text shown in the text object associated with the attribute included in the label data downloaded in the downloading process has been rewritten with the attribute information acquired in the attribute information acquisition process; and Execute A printing program configured to:

8. 8. The printing program according to claim 7, In the attribute information acquisition process, the attribute information included in the call instruction is acquired, and the server includes in the call instruction, the attribute information corresponding to the attribute associated with the text object included in the label data specified as the print target in the print instruction, from the user information of the logged-in user registered in the user database. A printing program configured to:

9. 8. The printing program according to claim 7, The computer of the information processing device When activated by a call instruction from the server, the server executes the label information acquisition process and the account acquisition process for acquiring account information included in the call instruction, and the server includes the label information and the account information of the logged-in user in the call instruction, In the attribute information acquisition process, the account information acquired in the account acquisition process is used to receive from the server the user information of the logged-in user registered in the user database, and the attribute information included in the received user information and corresponding to the attributes associated with the text object included in the label data downloaded in the download process is acquired. A printing program configured to:

10. 10. The printing program according to claim 9, The user information registered in the user database may include at least one member information, and the member information may also include attribute information corresponding to the attribute; The computer of the information processing device executes a member attribute acquisition process for acquiring the attribute information from at least one of the member information included in the user information of the login user received from the server in the attribute information acquisition process; In the printing process, for each of the attribute information acquired in the attribute information acquisition process and the member attribute acquisition process, the label printer is caused to perform printing based on the label data in which the text shown in the text object associated with the attribute included in the label data downloaded in the download process is rewritten with the attribute information. A printing program configured to:

11. 11. The printing program according to claim 10, The computer of the information processing device executes a client-side member selection process for accepting selection of member information to be printed from the member information included in the user information of the login user received from the server in the attribute information acquisition process; In the member attribute acquisition process, the attribute information included in the member information selected in the client-side member selection process is acquired. A printing program configured to:

12. A server connectable to an information processing device via a network, The server a label database and a user database are accessible, a plurality of label data can be registered in the label database, the label data is data that can be printed by a label printer, and the label data can include text objects associated with attributes; a plurality of user information can be registered in the user database, the user information is information associated with a user account required for login, and the user information can include attribute information corresponding to the attributes; The server further comprises: When label data is uploaded from a first information processing device, a registration process is executed to register the uploaded label data in the label database; The server further comprises: executes a receiving process for receiving, from the second information processing device, a selection of at least one of the label data registered in the label database, the label data including the text object associated with the attribute, and an instruction to print the selected label data; The server further comprises: and executing a print request process for causing a label printer connected to the second information processing device to print based on the selected label data in response to receiving the print instruction for the selected label data from the second information processing device, wherein the print request process calls a print program installed on the second information processing device using a call instruction, and the call instruction for calling the print program includes label information necessary for downloading the selected label data, the print program called by the call instruction uses the label information included in the call instruction to download the selected label data to the second information processing device, obtains attribute information corresponding to the attribute associated with the text object included in the downloaded label data from the user information of the logged-in user registered in the user database, and causes the label printer to print based on the label data in which text shown in the text object associated with the attribute included in the downloaded label data has been rewritten with the obtained attribute information. A server configured to:

13. A system including a first information processing device, a second information processing device, and a server, wherein the first information processing device and the second information processing device are connectable to the server via a network, The server a label database and a user database are accessible, a plurality of label data can be registered in the label database, the label data is data that can be printed by a label printer, and the label data can include text objects associated with attributes; a plurality of user information can be registered in the user database, the user information is information associated with a user account required for login, and the user information can include attribute information corresponding to the attributes; The server When label data is uploaded from the first information processing device, a registration process is executed to register the uploaded label data in the label database; The computer of the server further comprises: executes a receiving process for receiving, from the second information processing device, a selection of at least one of the label data registered in the label database, the label data including the text object associated with the attribute, and an instruction to print the selected label data; The server further comprises: In response to receiving the print instruction for the selected label data from the second information processing device, a print request process is executed to cause a label printer connected to the second information processing device to print based on the selected label data, and in the print request process, a print program installed in the second information processing device is called, and label information required to download the selected label data is included in the call instruction for calling the print program; The second information processing device When the call instruction is received from the server, the print program is called, the label information attached to the call instruction is passed to the print program, and the print program called by the call instruction: a download process for downloading the label data designated as the print target in the print command using the label information included in the call command; an attribute information acquisition process that acquires, from the user information of the logged-in user registered in the user database, attribute information corresponding to the attributes associated with the text object included in the label data specified as the print target in the print instruction; a printing process in which the label printer prints the label data in which the text shown in the text object associated with the attribute included in the label data downloaded in the downloading process has been rewritten with the attribute information acquired in the attribute information acquisition process; and Execute A system configured as follows:

Images