Program, information processing device, and label data sharing system

Abstract

To provide a program, an information processing device, and a label data sharing system for facilitating posting of label data suitable for being shared, in a system for utilizing label data.SOLUTION: In a label data sharing system 100, a client application 13, which is a program to be executed by a terminal 12, is configured to edit label data including multiple pieces of object data and attribute data, and upload the edited label data to a label management server 22. The client application 13 calculates, for the label data to be edited, an evaluation value indicating complexity of the label data, based on at least one of the object data and the attribute data included in the label data. The client application 13 determines whether to make a proposal for posting, based on the calculated evaluation value, and makes a proposal, when the determination is affirmative, to a user to post the label data.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The technical field disclosed in this specification relates to a program, an information processing device, and a label data sharing system used in a system that utilizes label data. [Background technology]

[0002] Conventionally, a system for utilizing content data is known in which a server for storing 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 point 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] JP 2002-99746 A Summary of the Invention [Problem to be solved by the invention]

[0005] In recent years, a system has been considered in which a user who has created label data used to print labels with a label printer can upload the label data to a server, and another user can download and use the label data from the server. In such a system, it is desirable to encourage many users to post label data, but label data with a simple structure can be easily created without downloading, and if such label data is also posted, management of the label data on the server becomes cumbersome. Patent Document 1 describes having users select photo data to post, but does not describe any measures to encourage users to post content such as photo data, so there is room for improvement. [Means for solving the problem]

[0006] A program made to solve the above-mentioned problems is a program executable by a computer of an information processing device, and is capable of causing the computer to execute an editing process to edit label data, the label data being data that can be printed by a label printer, and the label data being capable of including a plurality of object data and label attribute data, and is further capable of causing the computer to execute a calculation process to calculate an evaluation value indicating complexity based on at least one of the object data and the attribute data included in the label data to be edited, and a determination process to determine whether or not to suggest posting based on the evaluation value calculated in the calculation process, and is further configured to cause the computer to execute a proposal process to suggest posting of the label data to be edited when it is determined in the determination process that posting should be suggested, and to execute an upload process to upload the label data edited in the editing process to a server when an upload instruction for the label data edited in the editing process is received.

[0007] The program having the above configuration calculates an evaluation value indicating the complexity of the edited label data based on its content, and when it is determined that a posting should be suggested based on the evaluation value, suggests posting of the label data to the user. Thus, with the program having the above configuration, it is expected that the posting of label data with a complex structure suitable for posting will be made.

[0008] An apparatus, a system, and a control method for implementing the functions of the above-mentioned program, as well as a computer-readable storage medium storing the program, are also novel and useful. Effect of the Invention

[0009] According to the technology disclosed in this specification, a technology is realized that promotes the posting of label data suitable for sharing in a system that aims to utilize label data. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is an explanatory diagram illustrating a label data sharing system. [Diagram 2] FIG. 11 is a sequence diagram illustrating an example of a procedure of a posting process. [Diagram 3] FIG. 11 is a sequence diagram illustrating an example of a procedure of a printing process. [Figure 4] FIG. 13 illustrates an example of an editing screen. [Diagram 5] FIG. 13 is a diagram illustrating an example of a change in arrangement. [Figure 6] 13 is a flowchart showing an example of a calculation process procedure. [Figure 7] FIG. 13 is a diagram showing an example of label data to be posted. [Figure 8] FIG. 11 is an explanatory diagram illustrating an example of object index information. [Figure 9] FIG. 11 is an explanatory diagram showing an example of attribute index information. [Figure 10] 13 is a flowchart illustrating an example of a procedure for a post recommendation process. [Figure 11] FIG. 13 is a diagram showing an example of a screen display. [Figure 12] FIG. 11 is a sequence diagram illustrating an example of a procedure for a download printing process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] An embodiment of a label data sharing system will be described in detail with reference to the accompanying drawings. This embodiment discloses a label data sharing system that connects a server and a plurality of information processing devices via a network to share label data used for printing labels with a label printer.

[0012] The label data sharing system (hereinafter abbreviated as "system") 100 of this embodiment shown in FIG. 1 is a system provided to a user by, for example, a vendor (manufacturer) of a label printer. The system 100 comprises a terminal 12 and a label management server 22, which are connected via an Internet line 21. The terminal 12 is a terminal owned by the owner or user (hereinafter referred to as "user") of the label printer. The terminal 12 can be connected to a label printer 11. The label management server 22 is an example of a "server." The Internet line 21 is an example of a "network." Note that only one terminal 12 is shown in FIG. 1, but in reality, many terminals 12 are connected to the label management server 22.

[0013] The label printer 11 is a printing device that includes, for example, a thermal transfer print head and prints on a rolled tape while unwinding it. The label printer 11 prints an image on the stored tape and transports the tape based on, for example, a print job received from the terminal 12, and causes the printed portion to protrude outside the machine. A label having a predetermined label length and label width is created by the tape protruded outside the machine. The label length is the length in the direction in which the label is discharged from the label printer 11. The label width is the length in the direction perpendicular to the label length. The label printer 11 can be used by replacing multiple types of tape corresponding to the model.

[0014] The label printer 11 is connected to the terminal 12 by wireless LAN communication such as Wi-Fi (registered trademark) or short-range wireless communication such as Bluetooth (registered trademark). The label printer 11 and the terminal 12 may also be connected by wire using the USB communication standard.

[0015] The label management server 22 is a device having at least a storage function and a communication function. The label management server 22 can execute various functions by executing a server program 221. The server program 221 has a web server function that provides a web page in response to a request from a terminal 12. The server program 221 can accept label data posted from a large number of terminals 12 connected via the Internet line 21. The server program 221 can also store label data created by parties other than users, such as the vendor of the label printer 11. Thus, a wide variety of label data is stored in the label management server 22. The server program 221 has a function to transmit label data in response to a request from the terminal 12.

[0016] The label management server 22 has a function of storing object index information 229, attribute index information 230, and evaluation threshold 231, and providing them to the terminal 12. As described later, the object index information 229 stores conditions for determining an increase in an object individual evaluation value for each object data constituting the label data. As described later, the attribute index information 230 stores conditions for determining an increase in an attribute evaluation value for each attribute data set in the label data. The object index information 229 and the attribute index information 230 are examples of "evaluation conditions". The evaluation threshold 231 is information for determining whether or not to suggest a post. The object index information 229 and the attribute index information 230 will be described in detail later. Each function of the server program 221 will be described later.

[0017] The label management server 22 is connected to a user database (hereinafter referred to as "user DB") 25 and a label database (hereinafter referred to as "label DB") 26. The label management server 22 in this embodiment is connected to the user DB 25 and the label DB 26 via a wired LAN 24. The user DB 25 and the label DB 26 may be included in the label management server 22, or may be included in a server different from the label management server 22. The user DB 25 and the label DB 26 may also be included in different servers.

[0018] The user DB 25 stores a user ID, a user name, and a password in association with each user who uses the terminal 12. The user ID is identification information for identifying a user who can use the system 100, and specifies the user who uses the terminal 12. The user name is the name or nickname of the individual or group (corporation) of the user. The password is a password set by each user stored in the user name. In addition, the user DB 25 may register personal information for each user, such as an email address or a telephone number.

[0019] The label DB 26 stores multiple pieces of label data that can be printed by the label printer. The label data may be label data uploaded, i.e., posted, from the terminal 12 to the label management server 22 by a user who uses the label data sharing system 100 of this embodiment (hereinafter referred to as "posted label data"), or may be label data registered in the label management server 22 by the vendor of the label printer 11.

[0020] The label DB 26 stores the label ID, user ID (creator), label data, and posting date for each piece of label data in association with each other. The user ID (creator) may be the user name (creator). In the system 100 of this embodiment, the label ID is a serial number sequentially assigned to each piece of label data registered in the label management server 22. The user ID (creator) is the user ID of the user who posted the data using the system 100. The user ID (creator) of label data created by someone other than the user may be the ID of the administrator, the ID of the vendor who created the data, or may be left blank.

[0021] The label data includes, for example, object data and attribute data. The object data includes, for example, the type of object, parameters set for each object, and the arrangement of each object. The attribute data includes, for example, the label width, label length, tape color, and character color of the label. The posting date is information indicating the date on which the label data was posted.

[0022] The terminal 12 is an information processing device having a communication function, a storage function, a display function, and an operation function. The terminal 12 in this embodiment is configured by a personal computer, but may also be configured by a tablet or a smartphone.

[0023] In the terminal 12, a communication interface (hereinafter referred to as "communication IF") 123 and a user interface (hereinafter referred to as "user IF") 124 are electrically connected to a controller 120 including a CPU 121 and a memory 122. The terminal 12 is an example of an "information processing device." The CPU 121 is an example of a "computer." The controller 120 may be an example of a "computer." Note that the controller 120 in FIG. 1 is a collective term for hardware and software used to control the terminal 12, and does not necessarily represent a single piece of hardware actually present in the terminal 12.

[0024] The CPU 121 of the terminal 12 executes various processes according to the programs read from the memory 122 and based on the user's operation. The memory 122 stores various programs such as a client application program (hereinafter referred to as a "client application") 13. The client application 13 is an example of a "program". The memory 122 can store various data such as the label data 400. The memory 122 is also used as a working area when various processes are executed. A buffer provided in the CPU 121 is also an example of a memory. Note that an example of the memory 122 is not limited to a ROM, RAM, HDD, etc. built into the terminal 12, but may be a storage medium that can be read and written by the CPU 121, such as a recording medium such as a CD-ROM, a DVD-ROM, or a USB memory.

[0025] The client application 13 is an application program provided by the vendor of the label printer 11. The client application 13 has a function for creating and editing label data on the terminal 12. The client application 13 has a function for posting, i.e. uploading, the created label data to the label management server 22 while logged in to the label management server 22. The client application 13 has a function for downloading label data from the label management server 22. The client application 13 has a function for storing posted information 19, which is information indicating that the label data has been posted, in the label management server 22 that the client application 13 has uploaded.

[0026] The client application 13 has a function for printing label data using the label printer 11. The client application 13 has a function for evaluating the complexity of created or edited label data, and for suggesting posting of highly rated label data. The client application 13 has a function for storing proposed information 18, which is information indicating that the label data has been proposed, in the label data proposed for posting. Thus, the terminal 12 can be an example of a "first information processing device" and also an example of a "second information processing device". Each function of the client application 13 will be described later.

[0027] Next, the operation of the system 100 will be described. Each processing step in this embodiment basically indicates processing by the CPU 121 according to instructions written in programs such as the client application 13. Processing by the CPU 121 also includes hardware control using the API of the OS. In this specification, the operation of each program will be described without a detailed description of the OS. For convenience of explanation, the subject of each process may be the terminal 12 or the label management server 22.

[0028] When the client application 13 succeeds in logging in to the label management server 22, the terminal 12 becomes able to use the services of the system 100. When the client application 13 of this embodiment succeeds in logging in to the label management server 22, the client application 13 acquires the object index information 229, the attribute index information 230, and the evaluation threshold 231 from the label management server 22 and stores them in the memory 122. The timing for acquiring the object index information 229, the attribute index information 230, and the evaluation threshold 231 may be at the time of logging in or at regular timing during logging in. At least one of the object index information 229, the attribute index information 230, and the evaluation threshold 231 may be acquired from the label management server 22, and the rest may be stored in the client application 13 in advance. The process of acquiring at least one of the object index information 229, the attribute index information 230, and the evaluation threshold 231 from the label management server 22 is an example of an "acquisition process".

[0029] (Normal posting process) 2, a normal posting process in which a user opens the posting screen and posts label data will be described. The client application 13 of the terminal 12 saves the label data 400 created via the editing screen in the memory 122. The memory 122 can store multiple pieces of label data, such as label data created by the client application 13 and label data downloaded from the label management server 22.

[0030] For example, when the client application 13 receives a posting screen display instruction to display a posting screen while logged in to the label management server 22 (A01), the client application 13 displays a saved label list screen that displays a selectable list of label data stored in the terminal 12. When the client application 13 receives an operation to select one piece of label data to be uploaded from the displayed list of label data (A02), the client application 13 requests the label management server 22 to display a posting screen (A03). In response to the request, the label management server 22 provides the client application 13 with web page information corresponding to the posting screen (A04). The client application 13 causes the user IF 124 to display the posting screen based on the web page information (A05).

[0031] When the new post button displayed on the posting screen is operated in a state in which the client application 13 has accepted the selection of the label data 400 to be uploaded, the client application 13 accepts an upload instruction (A12). The client application 13 uploads the label data selected in A02 to the label management server 22 (A13). This upload instruction includes the user ID of the logged-in user and the label data 400 selected in A02.

[0032] The label management server 22 stores the received label data 400 in the label DB 26 (A14). Specifically, the label management server 22 creates a new label ID, associates the received user ID and label data 400 with the new label ID, and stores them in the label DB 26.

[0033] When the registration of the posted label data 400 is complete, the label management server 22 notifies the terminal 12 of the completion of registration (A15). The client application 13 stores the posted information 19 in the posted label data 400 and updates it (A16). The client application 13 also causes the terminal 12 to display a message indicating that the registration of the posted label data 400 is complete (A17). This allows the user to know that the posting is complete.

[0034] In addition, the label data 400 in which the posted information is stored may be made unselectable in the next and subsequent A02 in order to avoid duplicate posting. Methods for making it unselectable include not displaying it on the saved label list screen, or displaying it as unselectable. Examples of methods for displaying it as unselectable include displaying it in a grayed-out state, or displaying it normally but not accepting a selection operation.

[0035] (About printing process) The printing process will be described with reference to Fig. 3. Here, a case will be described in which user A causes label printer 11A to print label data created on terminal 12A. Terminal 12A is an example of a "first information processing device."

[0036] 3, the client application 13A displays an editing screen and accepts the creation of new label data (C01). In C01, for example, the client application 13A may accept editing of label data that has been downloaded from the label management server 22 or created on the terminal 12A and saved in the terminal 12A. C01 is an example of an "editing process." Details of the editing process will be described later.

[0037] When the client application 13A receives a print instruction for the label data to be edited (C11), it sends a print command to the label printer 11A (C12). The created label data is attached to the print command. The label printer 11A prints the received label data in accordance with the print command (C13).

[0038] The client application 13A executes a calculation process at the time of printing (C20). The calculation process is a process of calculating a label complexity evaluation value that indicates the complexity of the label data based on at least one of the object data and attribute data included in the label data to be edited. The label complexity evaluation value is an example of an "evaluation value." When a print instruction is given, there is a high possibility that editing of the label data will be completed and the contents will be finalized, so by calculating the label complexity evaluation value at that time, it is expected that the reliability of the label complexity evaluation value will be increased and appropriate suggestions will be made.

[0039] The client application 13A may execute the calculation process, for example, when a save instruction is received by operating the save button 313. When a save instruction is received, there is a high possibility that editing of the label data will be completed and the contents will be finalized, so by calculating the label complexity evaluation value at that timing, it is expected that the reliability of the label complexity evaluation value will be increased and appropriate suggestions will be made.

[0040] Furthermore, the client application 13A may execute a calculation process every time an editing operation of label data is accepted. In this case, the client application 13A may store a previous calculation result and reflect an evaluation value based on a new editing operation in the previous calculation result. This allows the client application 13A to shorten the calculation time per time and to immediately suggest posting when a print instruction is accepted. Details of the calculation process will be described later.

[0041] The client application 13A further executes a post recommendation process based on the label complexity evaluation value calculated in the calculation process (C21). The post recommendation process is a process of suggesting the posting of complex label data to the user who created the label data. The details of the post recommendation process will be described later.

[0042] (About editing process) 4 on the terminal 12A and accepts an operation for editing the label data. The editing screen 300 includes, for example, a function selection area 310, a label data display area 320, an attribute setting area 330, and an object setting area 340.

[0043] The function selection area 310 is an area for selecting a function. For example, the function selection area 310 displays a group of object selection buttons 311 for selecting objects to be included in the label data, a print button 312 for instructing printing of a label, and a save button 313 for instructing saving of the label data.

[0044] Label data 400 being edited is displayed in the label data display area 320. The label data 400 includes a label area 401 that shows the outer shape of the label, and a print area 402 that shows the printing range. Object data is displayed in the label data 400 in response to user operations.

[0045] The attribute setting area 330 is an area for setting parameters for various setting items included in the attribute data. The attribute setting area 330 includes, for example, a printer selection field 331 for selecting a printer, a label width setting field 332, a label length setting field 333, and a label color setting field 334. In each of the setting fields 332, 333, and 334, parameters may be automatically input by acquiring capability information from the label printer 11A selected in the printer selection field 331, or the user A may manually input the parameters. The attribute setting area 330 also includes a check box 335 for receiving an instruction to fix the label length.

[0046] The object setting area 340 is an area for setting parameters for various setting items of an object selected using the object selection button group 311. The display of the object setting area 340 is switched based on the type of the selected object. For example, when a text object is selected using the object selection button group 311, a setting screen corresponding to the text object is displayed in the object setting area 340. For example, the object setting area 340 displays a font selection field 341 for selecting the type of font, a decoration setting field 342 for setting decorations such as bold, italics, underline, and strikethrough, and a character decoration setting field 343 for receiving settings for character decoration.

[0047] For example, user A selects an object to be included in the label data from the object selection button group 311. The selected object is displayed in its initial position in the label data display area 320. For example, as shown in Fig. 4, when text is selected from the object selection button group 311, a text object 501 is displayed in its initial position. User A may maintain the position of the text object 501 in the label data display area 320 at its initial position, or may shift it from its initial position.

[0048] The following describes how to change the placement of an object. Here, the text object 501 is used as an example, but objects other than text can also be processed in the same way. As shown in Fig. 4, the initial position of the text object 501 is determined by the coordinates 501a, 501b, 501c, and 501d in the label width direction.

[0049] For example, when the text object 501 itself is moved as shown in Fig. 5(a), or when the text object 501 is enlarged or reduced as shown in Fig. 5(b) and Fig. 5(c), any one of the coordinates 501a to 501d is displaced from the initial position. Therefore, in this embodiment, it is possible to determine whether the position of the text object 501 has been changed from the initial position based on the coordinates 501a to 501d.

[0050] The initial position may be stored by either the client application 13 or the server 22. When the client application 13 stores the initial position, the client application 13 may determine a change in the placement and include the result in the object data. When the server 22 stores the initial position, the client application 13 may include placement information including the coordinates of the object in the object data.

[0051] User A can set parameters for each setting item of an object in the object setting area 340 shown in FIG. 4 to design the print contents of the object. The parameters set for each setting item may be initial values ​​or parameters changed from the initial values. For example, in the case of a text object 501, parameter changes include changes to the font type, character size, character decoration, character modification, etc. Character decorations include, for example, underline, strikethrough, bold, etc. Character modifications include, for example, "hollowing out" which prints text with a hollowed-out edge, and "reverse" which reverses the tape color and character color. User A can include various designed object data in the label data by sequentially selecting multiple objects and setting parameters and positions.

[0052] User A sets parameters and whether or not to execute functions for each setting item of attribute data in the attribute setting area 330, and designs the entire label. The parameters set for each setting item may be initial values, or parameters changed from the initial values. For example, a parameter change for the type of tape may be a color change to change the tape color and text color from the general black and white. For label settings, for example, a size change to change the label width and label length from the initial values, or a setting to fix the label length. For example, a setting for whether or not to execute a function may be a setting to execute divided printing. User A can include the designed attribute data in the label data by setting parameters for each setting item such as the tape color, text color, and tape width.

[0053] When the client application 13A accepts the operation of the save button 313, it saves the label data 400 displayed in the label data display area 320 in a memory area for the client application 13A provided in the terminal 12A. This completes the creation of the label data. In the case of editing the label data, the edited label data is saved by overwriting the previously saved label data.

[0054] (About calculation processing) The calculation process of C20 shown in Fig. 3 will be described with reference to Fig. 6. Here, the case where the client application 13A executes the calculation process on the label data 400x shown in Fig. 7(A) will be described as an example.

[0055] First, the CPU 121 of the terminal 12A extracts object data included in the label data (S31). For example, the CPU 121 extracts object data of a text object 501x, object data of a frame object 502, object data of a clip art object 504, object data of a table object 507, and object data of a two-dimensional code object 508 from the label data 400x shown in Fig. 7(A).

[0056] The CPU 121 calculates an object individual evaluation value for the i-th object data from among the object data extracted in S31, based on the object index information 229 (S32).

[0057] 8, the object index information 229 stores an object base value 2292, object content information 2294, and an object coefficient 2295 in association with each other for each object type 2291. The object type 2291 indicates the type of object data. The object types 2291 include, for example, text, symbol mark, clip art, figure, frame, image, two-dimensional code, and table.

[0058] The object base value 2292 is a base value when calculating an individual object evaluation value. The impact on the complexity of the label differs depending on the type of object. The object base value 2292 is set to a higher value for objects that increase the complexity of the label. In this embodiment, the object base value of each object is set based on text that is commonly used in label data. For example, symbol marks, clip art, and figures are set to have higher object base values ​​than text. Furthermore, frames, images, two-dimensional codes, and tables are set to have higher object base values ​​than symbol marks, clip art, and figures.

[0059] The object content information 2294 indicates the content of the object data for which the object individual evaluation value is to be increased. The object content information 2294 includes, for example, the content of parameters set in the object data being changed from their initial values, and the content of the arrangement of the object data being changed from its initial position. Parameters set in the object data include, for example, font, style, character decoration, and size for a text object; line type and fill for a graphic object; and color balance (brightness, contrast, etc.) for an image object.

[0060] The object coefficient 2295 is information indicating an accumulated amount by which the object basic value is multiplied when calculating a content evaluation value. The content evaluation value indicates the effect that the contents included in the object data have on the complexity of the label, and the complexity of the label differs depending on the setting contents of the object. Therefore, the object coefficient 2295 is set to a higher accumulated amount as the contents of the object data increase the complexity of the object, and the object individual evaluation value increases. For example, character decoration that inverts the tape color and the character color tends to stand out more than a change in the font of the text and increase the complexity of the label. Therefore, a higher accumulated amount is stored in the object coefficient 2295 for "character decoration" than for "font change". Note that the object coefficient 2295 may be information indicating an amount to be added to the object individual evaluation value.

[0061] For example, the CPU 121 extracts the object data of the text object 501x ​​as the first object data, and calculates an object individual evaluation value.

[0062] In the text object 501x ​​shown in Fig. 7(A), for example, the text "coffee" is input, and the font type parameter is changed from the initial value "font 1" to "font 2." In the object index information 229 in Fig. 8, the "font change" is associated with an object coefficient of "x2." Therefore, the CPU 121 multiplies the object base value "1" by "2" to calculate a content evaluation value of "2" for "font change."

[0063] For example, the text object 501x ​​shown in Fig. 7(A) is displaced from its initial position. In the object index information 229 in Fig. 8, an object coefficient of "x2" is associated with "arrangement change". Therefore, the CPU 121 multiplies the object base value "1" by "2" to calculate a content evaluation value of "2" for "arrangement change".

[0064] For example, in the text object 501x ​​shown in FIG. 7A, the parameter of character decoration is changed from "none" to "reverse", and the tape color and character color are reversed. In the object index information 229 in FIG. 8, an object coefficient "×3" is associated with "character decoration". Therefore, the CPU 121 multiplies the object base value "1" by "3" to calculate a content evaluation value of "character decoration" of "3". The object coefficient of "character decoration" is set higher than the object coefficients of "font change" and "layout change". Therefore, the content evaluation value can be set to a value that reflects the effect that the content of the object has on the complexity of the label.

[0065] For example, CPU 121 calculates an object individual evaluation value of "7" for text object 501x ​​by adding the content evaluation value of "font change" of "2", the content evaluation value of "layout change" of "2", and the content evaluation value of "character decoration" of "3" calculated as above. The object individual evaluation value is calculated based on the parameters and layout set for text object 501x. Therefore, the more changes have been made to the parameters and layout of an object, the higher the object individual evaluation value will be. Also, since the object coefficient differs depending on the content of the change, the object individual evaluation value will be a value appropriate to the content of the object.

[0066] 6, the CPU 121 judges whether or not the object individual evaluation values ​​have been calculated for all the object data extracted from the label data 400x (S33). For example, the label data 400x has not calculated the object individual evaluation values ​​for the objects 502, 504, 507, and 508 other than the text object 501x ​​(S33: NO). In this case, the CPU 121 adds 1 to i (S37), returns to the process of S32, and calculates the object individual evaluation value of the next object data.

[0067] For example, CPU 121 extracts the object data of table object 507 as the second object data, and calculates an object individual evaluation value. In object index information 229 in Fig. 8, the object base value of the table object is set to "2", and an object coefficient of "x2" is associated with the rearrangement of the table object. CPU 121 therefore multiplies the object base value "3" by "2" to calculate a content evaluation value of "6" for "arrangement change".

[0068] The object base value of a table object is set higher than the object base value of text. Therefore, even if the table object 507 has the same object coefficient as the text object 501x, the table object 507 can obtain a higher content evaluation value for "layout change" than the text object 501x. Therefore, the content evaluation value can be set to a different value depending on the type of object.

[0069] For example, the ruled lines of table object 507 have been changed from the initial parameters. CPU 121 calculates a content evaluation value of "6" for "ruled line change" in the same manner as above. CPU 121 adds the content evaluation value of "6" for "layout change" and the content evaluation value of "6" for "ruled line change" to calculate an object individual evaluation value of "12" for table object 507.

[0070] The table object 507 and the text object 501x ​​have different object base values, parameter settings for calculating the content evaluation value, and object coefficients. Therefore, the object individual evaluation value can be a value that reflects the characteristics of each object, such as the type of object and the content of the object data.

[0071] After calculating the object individual evaluation value of the table object 507, the CPU 121 calculates the object individual evaluation value for the next object in the same manner as described above. That is, the CPU 121 calculates the object individual evaluation value for each object included in the label data 400x. It is assumed that the parameters of the frame object 502, the clip art object 504, and the two-dimensional code object 508 in this embodiment are not changed, but their arrangements are changed. In this case, the CPU 121 calculates an object individual evaluation value of "6" for the frame object 502, an object individual evaluation value of "4" for the clip art object 504, and an object individual evaluation value of "6" for the two-dimensional code object 508 based on the object index information 229 in FIG. 8 in the same manner as described above.

[0072] After calculating the object individual evaluation values ​​for all object data extracted from label data 400x (S33: YES), CPU 121 calculates an object overall evaluation value by adding up the object individual evaluation values ​​calculated for each type of object included in label data 400x (S34). In this embodiment, the object overall evaluation value of "35" is calculated by adding up the object individual evaluation value "7" of text object 501x, the object individual evaluation value "12" of table object 507, the object individual evaluation value "6" of frame object 502, the object individual evaluation value "4" of clip art object 504, and the object individual evaluation value "6" of two-dimensional code object 508. Thus, the object overall evaluation value of label data 400x increases according to the number and type of objects included in label data 400x.

[0073] 6, the CPU 121 extracts attribute data included in the label data 400x, and calculates an attribute evaluation value based on the extracted attribute data (S35). The attribute evaluation value is calculated based on the attribute index information 230.

[0074] 9, for example, the attribute index information 230 stores attribute content information 2302 and an attribute coefficient 2303 in association with each other for each attribute type 2301. The attribute index information 230 includes an attribute basic value 2304. The attribute basic value 2304 is a basic value when calculating an attribute evaluation value. In this embodiment, the attribute basic value 2304 is common to all attribute types, but may differ depending on the attribute type.

[0075] Attribute type 2301 is information indicating the type of attribute data. Attribute type 2301 includes, for example, tape type, label settings, and special print settings. Attribute content information 2302 indicates the content of the attribute data for which the attribute evaluation value is calculated. For example, the attribute content information 2302 for tape type includes tape color and special processing. For label settings, it includes label width and label length. For special print settings, it includes a setting to perform divided printing. Divided printing is a printing method in which label data is printed in multiple batches.

[0076] The attribute coefficient 2303 is information indicating an accumulated amount by which the attribute basic value is multiplied when calculating the attribute evaluation value. The complexity of the label differs depending on the content of the attribute data. Therefore, the attribute coefficient 2303 is set so that the more complex the content of the label is, the higher the accumulated amount is set, and the attribute evaluation value increases. For example, split printing is often applied to special designs or uses, and the label tends to be more complex than when the tape color is other than black and white. Therefore, a higher accumulated amount for "split printing ON" than "not black and white" is stored in the attribute coefficient 2303. Also, for example, a tape that has been specially processed, such as laminated, may be more valuable than a tape with a color other than black and white. Therefore, a higher accumulated amount for "special processing" than "not black and white" is stored in the attribute coefficient 2303. The attribute coefficient 2303 may be information indicating an added amount to be added to the attribute evaluation value.

[0077] For example, the label data 400x includes attribute data for fixing the label length. In the attribute index information 230 shown in FIG. 9, the attribute basic value "1" and the attribute coefficient "×1.5" are stored in association with "fixed label length". The CPU 121 multiplies the attribute basic value "1" by "1.5" to calculate the attribute evaluation value "1.5" corresponding to "fixed label length". Since the attribute coefficient differs depending on the content of the attribute data, the attribute evaluation value is a value suitable for the content of the attribute data. In this embodiment, the CPU 121 sets the attribute evaluation value "1.5" corresponding to "fixed label length" as the attribute evaluation value.

[0078] 6, the CPU 121 calculates a label complexity evaluation value indicating the complexity of the label data based on the object overall evaluation value calculated in S34 and the attribute evaluation value calculated in S35 (S36). For example, the CPU 121 multiplies the object overall evaluation value "35" by the posted attribute evaluation value "1.5" to calculate a label complexity evaluation value of "52.5".

[0079] For example, suppose that posted label data in which the tape color and character color are set to something other than black and white in addition to the contents of the label data 400x shown in FIG. 7(A) is posted to the server 22. In this case, the CPU 121 reads out the attribute basic value "1" corresponding to "not black and white" of "tape type" from the attribute index information 230 shown in FIG. 9 and the attribute coefficient "×1.5" and multiplies them to calculate an attribute evaluation value "1.5" corresponding to "not black and white". In this case, the CPU 121 adds the attribute evaluation value "1.5" corresponding to "fixed label length" and the attribute evaluation value "1.5" corresponding to "not black and white" to calculate an attribute evaluation value "3". In this case, the label complexity evaluation value acquired by the posted label data is "105", which is the value obtained by multiplying the object individual evaluation value "35" by the attribute evaluation value "3". Thus, the label complexity evaluation value increases as the number and types of attribute data increase, and becomes a value appropriate for the complexity of the label.

[0080] On the other hand, suppose that label data 400y (see FIG. 7(B)) including settings that enable divisible printing in addition to the contents of label data 400x shown in FIG. 7(A) is posted to the server 22. In this embodiment, the number of divisions is set to "3" in the divisible printing settings, and label area 401y of label data 400y includes images 405a, 405b, and 405c of three tapes with fixed lengths, with each object arranged.

[0081] The CPU 121 reads out the attribute basic value "1" corresponding to "divided printing ON" from the attribute index information 230 shown in FIG. 9 and multiplies the attribute coefficient "×2" by the attribute basic value "1" corresponding to "divided printing ON" to calculate an attribute evaluation value "2" corresponding to "divided printing ON". The CPU 121 adds the attribute evaluation value "1.5" corresponding to "fixed label length" and the attribute evaluation value "2" corresponding to "divided printing ON" to calculate an attribute evaluation value "3.5". In this case, the label complexity evaluation value acquired by the label data 400y is "122.5", which is the product of the object individual evaluation value "35" and the posted attribute evaluation value "3.5". Thus, the label complexity evaluation value varies depending on the content of the attribute data, and is a value appropriate to the complexity of the entire label.

[0082] (About post recommendation processing) The post recommendation process of C21 shown in Fig. 3 will be described with reference to Fig. 10. Here, the case where a post is proposed for the label data 400x created or edited by user A based on the label complexity evaluation value of the label data 400x will be described as an example.

[0083] The CPU 121A of the terminal 12A first determines whether the post has been proposed (S10). If the proposed information 18 is stored in the label data 400x, the CPU 121A determines that the post has been proposed (S10: YES). In this case, the CPU 121A does not propose the post of the label data 400x and ends the post recommendation process.

[0084] When the proposed information 18 is not stored in the label data 400x, the CPU 121A determines that the posting has not been proposed (S10: NO). In this case, the CPU 121A determines whether or not the posting has been proposed (S11).

[0085] For example, when the label data 400x is created and saved in the memory 122A, and then posted to the label management server 22 by normal posting processing, the posted information 19 is stored in the label data 400x. In this case, the CPU 121A determines that the data has been posted (S11: YES), does not suggest posting the label data 400x, and ends the posting recommendation processing.

[0086] If the posted information 19 is not stored in the label data 400x, the CPU 121A determines that the label data 400x has not been posted (S11: NO), and determines whether the label complexity evaluation value calculated in the calculation process for the label data 400x is greater than the evaluation threshold value 231 obtained from the label management server 22 (S12). S12 is an example of a "determination process".

[0087] When the CPU 121A determines that the label complexity evaluation value is equal to or less than the evaluation threshold value (S12: NO), the label data is simple and there is a low possibility that another user will download and use the label data even if the label data is posted to the label management server 22. Therefore, the CPU 121A does not suggest posting the label data and ends the posting recommendation process.

[0088] When the CPU 121A determines that the label complexity evaluation value is greater than the evaluation threshold (S12: YES), the configuration of the label data is complex, and it is expected that another user will download and use it. Therefore, the CPU 121A causes the user IF 124A of the terminal 12A to display a posting recommendation screen that suggests posting the label data 400x (S13). S13 is an example of a "suggestion process."

[0089] For example, the posting recommendation screen 511 shown in FIG. 11(A) includes a suggestion section 512, an image 513 of label data, an OK button 514, and a cancel button 515. The suggestion section 512 displays, for example, a message suggesting posting of label data. The image 513 displays an image of the proposed label data. The OK button 514 is an operation object that accepts an instruction to approve the posting. The OK button 514 is associated with the URL of the posting screen 350. The cancel button 515 is an operation object that accepts an instruction not to approve the posting.

[0090] As shown in FIG. 10, after displaying the post recommendation screen, the CPU 121A judges whether or not there is permission to post (S14). For example, if the user A does not want to post the label data 400x, the user A operates the cancel button 515. When the CPU 121A receives the operation of the cancel button 515, it judges that there is no permission to post (S14: NO). In this case, the CPU 121A closes the post recommendation screen 511 (S23). After storing the proposed information 18 in the label data 400x (S24), the CPU 121A ends the post recommendation process without displaying the post screen. This causes the terminal 12A to return to the edit screen. By storing the proposed information 18 in the label data 400x, it is possible to avoid repeated posting suggestions for the label data 400x for which the user A does not wish to be suggested for posting.

[0091] The process of S24 may be omitted. In this case, for example, even if User A does not permit posting due to time constraints, he / she can permit posting again later, and can permit posting at any timing.

[0092] In response to this, when the CPU 121A receives an operation of the OK button 514, it determines that the posting is permitted (S14: YES). In this case, the CPU 121A closes the posting recommendation screen 511 (S15) and stores the proposed information in the label data 400x (S16). S16 is an example of a "proposal storage process."

[0093] In response to the permission of posting, the CPU 121A displays a posting screen 350 on the user IF 124A of the terminal 12A as shown in FIG. 11B (S17). The posting screen 350 displays a label name input field 353, a label description input field 354, a tape type setting field 355, an example photo image setting field 356, and a new posting button 361. The client application 13A inputs a label name indicating the name of the label data 400x, a description of the label, a model number of a tape suitable for printing the label, and a photo image indicating an example of how to use the label in the label name input field 353, the label description input field 354, the tape type setting field 355, and the example photo image setting field 356. The client application 13A accepts these as supplemental information for the label data 400x. The supplemental information is displayed, for example, on a label search screen for searching for labels registered in the label management server 22, and helps the user select a download target. The supplemental information is not limited to this embodiment. The configuration of the posting screen 350 is the same as the posting screen displayed in A05 of FIG.

[0094] Since the label data to be posted is already determined to be the label data 400x, the posting screen 350 displayed via the posting recommendation screen 511 is displayed in a state in which the label data 400x to be printed is selected, without the need to perform the process of A02 shown in Fig. 2. In this case, the posting screen 350 may display an image 352 of the label data 400x. S17 is an example of a "screen display process".

[0095] The CPU 121A, which has displayed the posting screen 350, judges whether an upload instruction has been received (S18). The CPU 121A waits until an upload instruction is received (S18: NO). The CPU 121A receives an upload instruction by operating the new posting button 361 displayed on the posting screen 350 (S18: YES). In this case, the CPU 121A uploads the label data 400x to the label management server 22 (S19). S20 is an example of an "upload process".

[0096] After completing upload of the label data 400x, the CPU 121A stores and updates the posted information in the label data 400x (S20). S20 is an example of a "posting storage process." The CPU 121A closes the posting screen 350 (S21) and ends the posting recommendation process.

[0097] (Download process) The process of downloading posted label data will be described with reference to FIG. 12. In the system 100, many terminals 12 are connected to the label management server 22, and many label data are registered in the label management server 22. Here, an example will be described in which user B uses terminal 12B, one of the many terminals 12, to download posted label data 400x posted by user A. For ease of explanation, the reference characters for users, terminals, and their components are suffixed with the letter "B." Terminal 12B is an example of a "second information processing device." Note that the download target may be label data registered by a party other than the user, such as a label printer vendor.

[0098] For example, the client application 13B of the terminal 12B has a function of displaying, on the user IF 124B of the terminal 12B, a server usage button that accepts an instruction to use the label management server 22 while it is running. When the client application 13B accepts an instruction to use the server by operating the server usage button (B01), it transmits a usage request to the label management server 22 (B02). In response to the request, the label management server 22 provides web page information for a label search screen to the client application 13B (B03), and causes the terminal 12B to display the label search screen (B04).

[0099] For example, the label search screen displays thumbnail images of label data registered in the label management server 22. The client application 13B accepts the selection of the posted label data 400x to be downloaded by an operation of selecting an image corresponding to the posted label data 400x from among those images (B20).

[0100] When the client application 13B accepts the selection of the download target, it causes the user IF 124B to display a download screen provided by the label management server 22 (B21). The download screen includes a download execution button. In response to the operation of the download execution button, the client application 13B accepts a download instruction to instruct transmission of the posted label data 400x selected as the download target (B22). The client application 13B transmits the download instruction to the label management server 22 (B23).

[0101] The image displayed on the label search screen is associated with the label ID of the corresponding label data. When the label management server 22 receives the download instruction, it reads out the posted label data 400x from the label DB 26 based on the label ID associated with the image selected in B20 (B24). The label management server 22 transmits the read out posted label data 400x to the terminal 12B (B25).

[0102] The client application 13B of the terminal 12B receives the posted label data 400x using the communication IF 123B and stores it in the memory 122B (B26). The processes of B22 to B26 are an example of a "download process." This allows user B to use the posted label data 400x uploaded by user A. In other words, the posted label data 400x is shared. User B may select multiple label data on the label search screen and download them all at once to the terminal 12B.

[0103] As described above, the client application 13 of this embodiment calculates a label complexity evaluation value indicating complexity based on the contents of the edited label data 400x, and when it is determined that posting should be suggested based on the label complexity evaluation value, suggests posting of the label data 400x to the user. Therefore, according to the client application 13 of this embodiment, it is expected that label data with a complex configuration suitable for posting will be posted. As a result, the client application 13 can realize a technology that promotes posting of label data suitable for sharing in the system 100 that aims to utilize label data.

[0104] Furthermore, when a print instruction is given for label data altered by the editing process, the client application 13 in this embodiment executes a post recommendation process, i.e., a judgment process and a proposal process, so that the reliability of the judgment of label complexity is improved, and appropriate suggestions can be made.

[0105] Furthermore, since the client application 13 in this embodiment acquires the object index information 229, the attribute index information 230, and the evaluation threshold 231 from the label management server 22, the object index information 229, the attribute index information 230, and the evaluation threshold 231 can be managed by the label management server 22. Therefore, the label management server 22 can set the level of complexity of the label data and manage the quality of the shared label data.

[0106] Note that the embodiments disclosed in this specification are merely examples and do not limit the present invention in any way. Therefore, the technology disclosed in this specification can be naturally improved and modified in various ways without departing from the gist of the technology. For example, the client application 13 may have information on proposed label data and information on posted label data in addition to the label data 400. In the above embodiment, the post recommendation process (determination process and proposal process) is executed when there is an instruction to print the label data edited in the editing process, but it may be executed when there is an instruction to save the label data edited in the editing process. In this case, it is expected that the accuracy of the label complexity determination will be improved and appropriate proposals will be made.

[0107] For example, when the client application 13 displays a list of the label data 400 stored in the terminal 12, the list screen may be provided with a print button. In this case, the client application 13 may receive a print instruction and execute the determination process and suggestion process without going through the edit screen. This allows the client application 13 to suggest posting not only the label data being edited, but also the label data stored in the terminal 12.

[0108] For example, in the posting recommendation process of Fig. 10, S14 to S18 may be omitted, and if there is consent to posting (S14: YES), the label data may be automatically uploaded to the label management server 22 (S19). In this way, the label data can be posted immediately without switching to the posting screen, which promotes the posting of complex label data. In this case, it is preferable that the supplemental information entered on the posting screen is stored in the label DB 26 in association with the label data after uploading. However, if there is consent to posting (S14: YES), even if the posting screen is displayed and then the upload is performed, the effort required for posting is reduced, and posting of label data is easier than manually displaying the posting screen on the terminal 12 and uploading the label data as shown in Fig. 2, for example.

[0109] In the above embodiment, in the process of A06 shown in Fig. 2, the label complexity evaluation value may be determined based on the contents of the label data other than the object data. However, the more objects included in the label data, the more complex the label data tends to be. Therefore, by assigning an individual object evaluation value to each object data included in the label data, the more objects there are, the higher the label complexity evaluation value becomes, and posts are suggested for label data that includes many objects.

[0110] For example, the processes of S32, S33, and S37 in FIG. 6 may be omitted, and an object individual evaluation value may be assigned to each object data by a method other than the object type. For example, an object overall evaluation value or a label complexity evaluation value to be assigned to the label data may be calculated based on the number of object data included in the label data. In this case, weighting according to the type or content of the object data may or may not be performed. However, the influence on the label complexity differs depending on the object type. For example, text is simple, but images tend to have more complex labels than text. Therefore, by making the value to be increased as the object individual evaluation value different depending on the object type, it is expected that suggestions for postings will be made for label data containing objects with more complex labels.

[0111] 6 may be omitted, and the object overall evaluation value or label complexity evaluation value may be made different by a method other than the contents of the object. For example, even if the number of object data included in the label data is the same (five), label data including five types of object data may be assigned a higher object overall evaluation value or label complexity evaluation value than label data including five pieces of one type of object data. This is because label data including a wide variety of objects may have increased complexity.

[0112] For example, objects other than text objects may not acquire higher object individual evaluation values ​​than text objects. For example, the object base value of objects other than text may be smaller than the object base value of text. However, text objects are basic objects and have lower complexity than other objects. Therefore, for example, by making the object base value of objects other than text objects higher than that of text objects and enabling them to acquire high object individual evaluation values, it is expected that posts will be suggested for label data that includes objects other than text objects.

[0113] For example, in S32 of Fig. 6, if parameters set in object data are changed from the initial values, such as a change in font type or character decoration, the content evaluation value may not be calculated, and the object individual evaluation value may be less likely to increase. However, if parameters of object data are changed, the complexity of the label tends to increase. Therefore, if parameters of object data are changed, the object individual evaluation value assigned to the object data may be increased, and it is expected that posts will be suggested for label data including objects whose parameters have been changed from the initial values.

[0114] For example, in the process of S32 in Fig. 6, if the arrangement of object data has been changed from the initial value, the content evaluation value may not be calculated, and the object individual evaluation value may be less likely to increase. However, if the arrangement of object data has been changed from the initial position, the complexity of the label tends to increase. Therefore, if the arrangement of object data has been changed from the initial position, by increasing the object individual evaluation value that is increased based on the object data, it is expected that posts will be suggested for label data that includes objects whose object arrangement has been changed from the initial value.

[0115] The processes of S35 and S36 in FIG. 6 may be omitted, and the attribute evaluation value or label complexity evaluation value may not increase based on the attribute data included in the label data. For example, the attribute evaluation value may not increase based on the tape type included in the label data. Also, for example, the same addition amount or integration amount may be stored in the attribute coefficients of "not black and white" and "special processing", which are examples of the contents of "tape type" shown in FIG. 9. In this way, the attribute evaluation value can be made constant regardless of which tape type is set. However, the value of the label may differ depending on the type of tape. For example, wide tapes, tapes that have been specially processed, and tapes of colors other than black and white tend to be expensive. Label data that specifies such tapes tends to be complicated due to the editor's preferences. Therefore, by increasing the attribute evaluation value according to the type of tape or the contents of the tape type included in the label data, it is expected that submission suggestions for complex label data will be made.

[0116] Also, for example, it is not necessary to increase the attribute evaluation value based on attribute data that fixes the label length. However, when the label data includes attribute data that sets the label length, there is a tendency for the label design to become more complex due to the attention to detail. Therefore, when there is attribute data that sets the label length, by increasing the label complexity evaluation value, it is possible to expect suggestions for posts for complex label data.

[0117] Also, for example, the attribute evaluation value does not have to be increased based on the attribute data that performs divided printing. However, when the posted label data includes attribute data that indicates that divided printing is to be performed, the complexity of the label tends to increase. Therefore, when there is attribute data that performs divided printing, by increasing the attribute evaluation value, it is possible to expect posting suggestions for complex label data.

[0118] All of the object index information 229, the attribute index information 230, and the evaluation threshold 231 may be stored in advance in the client application 13. In this case, the load of the client application 13 communicating with the label management server 22 is reduced. However, by setting the object index information 229, the attribute index information 230, and the evaluation threshold 231 on the label management server 22 side, the label management server 22 can adjust what kind of label data is proposed.

[0119] The object index information 229, attribute index information 230, and evaluation threshold 231 may be obtained not only when login is successful, but also when a calculation process or a judgment process is executed, or each time label data is printed or saved. However, by obtaining the object index information 229, attribute index information 230, and evaluation threshold 231 when logging in to the label management server 22, the frequency of the obtaining process can be reduced and the communication load can be reduced compared to obtaining the information each time printing or saving is performed.

[0120] S10 and S16 in Fig. 10 may be omitted. However, since the user may find it annoying if the same proposal is repeated many times, it is preferable to store proposed information 18 for proposed label data and not make posting suggestions multiple times.

[0121] A15 in Fig. 2 and S11 and S20 in Fig. 10 may be omitted. However, since a user may be confused if a posting suggestion is made for label data that has already been posted, it is preferable to store posted information 19 for posted label data and not make duplicate posting suggestions.

[0122] 10 may be displayed in a state where the label data 400x to be edited is not selected as the label data to be uploaded. However, the client application 13 causes the terminal 12 to display the posting screen 350 in a state where the label data 400x is selected as the label data to be uploaded, thereby eliminating the need to select label data when posting label data and facilitating the posting of complex label data.

[0123] The posting screen 350 displayed in the posting recommendation process in Fig. 10(B) does not have to accept supplemental information. However, supplemental information can be input when posting normal label data, and the client application 13 can avoid missing supplemental information by accepting the supplemental information in S17.

[0124] The label management server 22 may be composed of a front-end server having a web server function and a back-end server having a function other than the web server function. For example, the front-end server may receive download requests and upload requests by using the web server function, while the back-end server may manage the label data.

[0125] In any sequence diagram disclosed in the embodiment, any of a plurality of processes can be executed in a different order or in parallel as long as no contradiction occurs in the process contents.

[0126] The processes disclosed in the embodiments may be executed by hardware such as a single CPU, multiple CPUs, ASIC, or a combination thereof. The processes disclosed in the embodiments may be realized in various forms, such as a recording medium having a program for executing the processes recorded thereon, or a method. [Explanation of symbols]

[0127] 11. Label Printer 12 Terminal 21 Internet connection 22 Label Management Server 13 Client Apps 100 Label Data Sharing System 121 CPU 122 Memory

Claims

1. A program executable by a computer of an information processing device, The computer includes: An editing process for editing label data can be executed, the label data being data that can be printed by a label printer, and the label data can include a plurality of object data and label attribute data, The computer further comprises: a calculation process for calculating an evaluation value indicating complexity based on at least one of the object data and the attribute data included in the label data to be edited; a determination process for determining whether or not to propose a post based on the evaluation value calculated in the calculation process; It is possible to execute The computer further comprises: executing a suggestion process for suggesting posting of the label data to be edited when it is determined in the determination process that posting is to be proposed; The computer further comprises: when an instruction to upload the label data edited in the editing process is received, executing an upload process to upload the label data edited in the editing process to a server; A program that is structured as follows.

2. The program according to claim 1, The computer includes: executing the determination process and the proposal process when a print instruction is given for the label data edited in the editing process; A program that is structured as follows.

3. The program according to claim 1, The computer includes: executing the determination process and the suggestion process when an instruction to save the label data edited in the editing process is received; A program that is structured as follows.

4. The program according to claim 1, The computer includes: It is possible to execute a screen display process for displaying a posting screen that can receive a selection of label data to be uploaded and an instruction to upload the label data selected as the upload target, The computer further comprises: executing the screen display process to display the posting screen in a state in which the label data edited in the editing process is selected as the label data to be uploaded after the suggestion process is executed; A program that is structured as follows.

5. The program according to claim 1, In the calculation process, Increasing the evaluation value for each object data included in the label data edited in the editing process. A program that is structured as follows.

6. The program according to claim 4, In the calculation process, increasing the evaluation value for each object data included in the label data edited in the editing process by a value that varies depending on the type of object; A program that is structured as follows.

7. The program according to claim 4, In the calculation process, increasing the evaluation value for each object data included in the label data edited in the editing process when a parameter set for the object data has been changed from an initial value or when a position of the object data has been changed from an initial position; A program that is structured as follows.

8. The program according to claim 4, The attribute data of the label includes a type of tape, In the calculation process, Incrementing the evaluation value by a different value based on the type of tape indicated in the attribute data included in the label data edited in the editing process. A program that is structured as follows.

9. The program according to claim 4, The attribute data of the label includes a length of the label; In the calculation process, In a case where the attribute data indicating the length of the label is included in the label data edited in the editing process, the evaluation value is increased. A program that is structured as follows.

10. The program according to claim 1, The computer includes: It is possible to execute an acquisition process for acquiring, from the server, at least one of an evaluation condition for determining an amount of increase in the evaluation value for each of the object data or the attribute data and an evaluation threshold for determining whether or not to propose the data; When the evaluation conditions are acquired in the acquisition process, the calculation process calculates the evaluation value based on at least one of the object data and the attribute data included in the label data edited in the editing process, using the evaluation conditions acquired in the acquisition process; When the evaluation threshold value is acquired in the acquisition process, In the determination process, it is determined that a post is to be suggested when the evaluation value calculated in the calculation process is greater than the evaluation threshold value acquired in the acquisition process. A program that is structured as follows.

11. The program according to claim 10, The computer includes: When login to the server is successful, the acquisition process is executed. A program that is structured as follows.

12. The program according to claim 1, A computer of the server, executing a proposal storage process for storing, when a proposal is made to post the label data, proposed information indicating that the label data has been proposed in association with the proposed label data; The computer further comprises: When the proposed information is stored for the label data edited in the editing process, the proposal process is not executed. A program that is structured as follows.

13. The program according to claim 1, The computer includes: executing a posting storage process for storing, when the label data is uploaded to the server, posted information indicating that the label data has been posted in association with the uploaded label data; The computer further comprises: When the posted information is stored for the label data edited in the editing process, the suggestion process is not executed. A program that is structured as follows.

14. The information processing device includes: An editing process for editing label data can be executed, the label data being data that can be printed by a label printer, and the label data can include a plurality of object data and label attribute data; The information processing device further comprises: a calculation process for calculating an evaluation value indicating complexity based on at least one of the object data and the attribute data included in the label data to be edited; a determination process for determining whether or not to propose a post based on the evaluation value calculated in the calculation process; It is possible to carry out The information processing device further comprises: When it is determined in the determination process that a posting is to be proposed, a proposal process is executed to propose posting of the label data to be edited; The information processing device further comprises: when an upload instruction for the label data edited in the editing process is received, an upload process is executed to upload the label data edited in the editing process to a server. It is configured as follows.

15. A label data sharing system comprising a first information processing device, a second information processing device, and a server, the first information processing device and the second information processing device being connectable to the server via a network, The first information processing device, A method for editing label data, the label data being printable by a label printer, the label data being capable of including a plurality of object data and label attribute data, The first information processing device further comprises: calculating an evaluation value indicating complexity based on at least one of the object data and the attribute data included in the label data to be edited; It is possible to determine whether to suggest a post based on the calculated evaluation value; The first information processing device further comprises: If it is determined that posting is to be proposed, proposing posting of the label data to be edited; The first information processing device further comprises: uploading the edited label data to the server when an upload instruction for the edited label data is received; The server, The label data uploaded to the server can be registered, The second information processing device is It is possible to select one of the label data registered in the server, The second information processing device further comprises: downloading the selected label data from the server when a download instruction for the selected label data is received; A label data sharing system configured to:

Images