JP2023135746A - Information processing system, printer, and program - Google Patents

Abstract

To reliably back up data generated on a printer.SOLUTION: An information processing system includes a server, a computer device, and a printer. The printer includes: a storage 32 for storing layout data and reference data to be referred for printing; a data editing unit which edits the reference data on the basis of operation input of a user, and records on a storage unit, or updates edited data obtained by editing the reference data; an automatic backup processing unit which periodically backs up the edited data stored in the storage to the computer device; and a manual backup processing unit which backs up the edited data stored in the storage unit to an external storage apparatus in response to user operation. The server includes a data recording unit which records, on the storage unit, edited data to be backed up, when there is a difference between edited data obtained through the latest editing on the printer and edited data obtained through the previous editing.SELECTED DRAWING: Figure 9

Description

The present invention relates to an information processing system, a printer, and a program.

BACKGROUND ART Conventionally, content printed by multiple printers has been centrally managed by a server so that there is no discrepancy in the content printed on labels etc. attached to products at multiple chain stores. The printing data that is centrally managed in this way is updated regularly or irregularly.
For example, in Patent Document 1, a management server acquires registered image data stored in the connected representative printer from a connected representative printer, and based on the acquired registered image data, transfers information to other printers other than the representative printer. It is disclosed that the identity of the registered image data stored by a representative printer and the registered image data stored by other printers is maintained by updating the stored registered image data.

Japanese Patent Application Publication No. 2013-210727

By the way, even if the printing contents of multiple chain stores are centrally managed by a server, some stores have their own products, and it is necessary to print data for printing labels to be affixed to such unique products. It may be created by a store representative and saved on the printer. However, if the printer that stores the data created by the store breaks down, the data created for the store's unique products will be lost.

Therefore, an object of the present invention is to enable reliable backup of data created in a printer.

One aspect of the present invention is an information processing system that includes an information processing device and a printer that can communicate with the information processing device.
The printer includes:
a storage unit that stores layout data indicating a layout when printing, and reference data that is associated with the layout data and is referred to when printing;
a data editing unit that edits the reference data based on a user's operation input, records edited data that is the edited reference data in the storage unit, or updates the edited data in the storage unit at any time;
a first backup processing unit that periodically backs up edited data in the storage unit to the information processing device;
A second backup processing section is provided that backs up the edited data in the storage section to an external storage device in response to a user's operation.
The information processing device includes:
A data recording unit is provided for recording edited data to be backed up in a storage unit when there is a difference between edited data resulting from the latest editing of the printer and edited data resulting from the previous editing.

According to an aspect of the present invention, it is possible to reliably back up data created in a printer.

FIG. 1 is a system configuration diagram of an information processing system according to an embodiment. FIG. 3 is a diagram illustrating an example of a project file creation screen of the information processing device according to the embodiment. FIG. 3 is a diagram illustrating a procedure for displaying a call table definition in the information processing device according to the embodiment. FIG. 3 is a diagram illustrating a procedure for displaying a call table in the information processing device according to the embodiment. FIG. 3 is a diagram showing a procedure for displaying a kanji table and a store name table in the information processing device according to the embodiment. FIG. 3 is a diagram illustrating a procedure for uploading a project file to a server in the information processing apparatus according to the embodiment. FIG. 3 is a diagram showing an operation procedure of the printer according to the embodiment. 1 is a diagram showing a hardware configuration of an information processing system according to an embodiment. FIG. 1 is a functional block diagram of an information processing system according to an embodiment. 2 is an example of a sequence chart when a label is issued by a printer in the information processing system according to the embodiment. FIG. 3 is a diagram illustrating a procedure for editing a call table in the printer according to the embodiment. FIG. 3 is a diagram illustrating an example of the configuration of a storage directory in the printer according to the embodiment. FIG. 7 is a diagram illustrating a display example of an object property setting section when each table is selected on the project file creation screen of the information processing apparatus according to the embodiment. 7 is a flowchart illustrating processing when the printer according to the embodiment refers to a table. FIG. 3 is a diagram illustrating a procedure for setting automatic backup in the printer according to the embodiment. FIG. 2 is a diagram illustrating an example of the configuration of a storage directory in a server according to an embodiment. 7 is a sequence chart when performing automatic backup processing of an edited table in the information processing system according to the embodiment. FIG. 3 is a diagram illustrating a procedure for setting manual backup in the printer according to the embodiment. FIG. 3 is a diagram illustrating a procedure for restoring data in the printer according to the embodiment. FIG. 7 is a diagram illustrating another configuration example of a storage directory in the server according to the embodiment. 7 is a sequence chart when performing automatic backup processing of differential data of an edited table in the information processing system according to the embodiment.

The "storage device" in the present disclosure may be a memory or storage built into the printer, or a device external to the printer (for example, an external device such as an HDD (Hard Disk Drive) or a USB (Universal Serial Bus) storage). storage device or database server).
"Reference data" in the present disclosure may be any data that is referenced when printing. For example, data that refers to layout data and text that are referenced when printing, data that is referenced when calling character data to be printed, and data that indicates the distribution destination of layout data that is used when printing. Can be mentioned. Further, setting information and the like that are referred to when printing can also be reference data.

(1) System Overview Hereinafter, an information processing system 1, which is an embodiment of the information processing system of the present invention, will be described with reference to FIG. FIG. 1 is a system configuration diagram of an information processing system 1 according to this embodiment.

As shown in FIG. 1, in the information processing system 1 of this embodiment, a computer device 2 and a plurality of printers 3-A, 3-B, 3 -C, 3-D, 3-E, . . . are connected to the server 5.
In the example of this embodiment, the information processing system 1 is a system operated by a sales company that operates a plurality of stores, and for issuing labels to products sold at each store. In this embodiment, a case will be explained in which the place where the label is issued is a store, but in reality, the label may be issued at a factory or the like.

A computer device 2 is located at the distributor's headquarters. The computer device 2 (hereinafter referred to as "PC2" as appropriate) is, for example, a computer device such as a personal computer or a tablet terminal. Each store is equipped with at least one printer. For example, printers 3-A, 3-B, 3-C, 3-D, and 3-E are placed at store A, store B, store C, store D, and store E, respectively. In the following description, when referring to matters common to a plurality of printers, the term "printer 3" will be used.
At the headquarters, the basic layout design of the label is designed using PC2. Each store issues labels to be attached to products based on the label layout design provided by the headquarters.

The PC 2 has a label creation application program (hereinafter referred to as "label creation application") that creates a project file that includes data regarding the label layout design, data for each item included in the label, various settings, store information, etc. ) is installed. A project file created by executing the label creation application is distributed from the PC 2 to the printer 3 via the server 5 as a format file. That is, the project file is uploaded as a format file from the computer device 2 to the server 5 in response to a predetermined operation by the user, and is downloaded from the server 5 to the printer 3 at a predetermined timing.

A label issuing application program (hereinafter referred to as "label issuing application" as appropriate) that issues labels based on a format file is installed in the printer 3. By running the label printing application, you can select printing data that specifies the label layout design, data of each item included in the label, etc., or edit the selected printing data as necessary, and create a printout based on the printing data. Labels can be issued. An employee of the store attaches the label issued by the printer 3 to the product in the store.
The project file and publication data will be described later.

(2) Flow until label issuance Next, with reference to FIGS. 2 to 7, a series of flows from the creation of a project file by the PC 2 to the issuance of a label by the printer 3 will be described.
FIG. 2 is a diagram showing an example of a project file creation screen of the PC 2. As shown in FIG. FIG. 3 is a diagram showing a procedure for displaying a call table definition on the PC 2. FIG. 4 is a diagram showing a procedure for displaying a call table on the PC 2. FIG. 5 is a diagram showing a procedure for displaying a kanji table and a store name table on the PC 2. FIG. 6 is a diagram showing a procedure for uploading a format file to the server in the PC 2. FIG. 7 is a diagram showing the operating procedure when issuing a label in the printer 3.

(2-1) Creating a project file FIG. 2 is an example of the PC screen G1 (project file creation screen) displayed on the PC 2 when the label creation application is started. On the project file creation screen, the user can design the label to be issued by the printer 3 by setting objects to be placed in the printable range of the label.

In the label creation application, data is managed by project files. The project file is a file indicating a management unit of data created by the label creation application, and is distributed to each printer 3 via the server 5 as a format file.

As shown in FIG. 2, the PC screen G1 includes a group of instruction buttons 101, a group of object buttons 102, a design window 103, a project setting section 104, and an object property setting section 105.
In the project setting section 104, data included in the project file is displayed in a hierarchical structure. As shown in this hierarchical structure, the project file includes a call table, layout data, a kanji table, and a store name table. Although not shown, the project file further includes each table information file. The table information file is a file containing information regarding various settings for each table.

The call table is data for printing a label in the label issuing application of the printer 3. The call table is an example of reference data for referring to layout data and text that are referred to when the printer 3 performs printing.
The layout data is design data for issuing a label by the printer 3 in combination with the call table, and is displayed on the design window 103 of the PC screen G1 during editing, for example.
The kanji table is a table for converting input numerical values into registered character data. Character data can be registered in association with registration numbers in the kanji table. For example, by setting a kanji table to be referenced when inputting characters into a character string object, which will be described later, it is possible to specify a registration number instead of inputting character data. The kanji table is an example of reference data for calling text when printing based on layout data.
In the store name table, information corresponding to the printer ID (printer identification information) of the printer located at the store to which the format file is delivered is registered. The store name table is an example of reference data including the printer ID of the printer 3 that prints based on the layout data.

Although FIG. 2 shows a case where one kanji table and one store name table are set, this is not the case. Multiple kanji tables and multiple store name tables can be set. For example, it is possible to set Kanji table 1, Kanji table 2, Kanji table 3, etc., store name table 1, store name table 2, store name table 3, etc.

The design window 103 corresponds to a label creation/editing area, and a label is designed by performing operations to place and move objects within this creation/editing area. In other words, the design window 103 is a window for designing a label layout. In the example of this embodiment, an object OBJ1 corresponding to the "product name" item, an object OBJ2 corresponding to the "name" item, an object OBJ3 corresponding to the "content amount" item, and a date and time object corresponding to the "expiration date" item A case is illustrated in which a label including four objects, object OBJ4, is designed.
When the button b2 ("input screen") is operated, a window (not shown) for inputting a character string or code included in each object is displayed instead of the design window 103. If the button b1 (“Layout”) is operated while the window is displayed, the screen returns to the design window 103.

The object button group 102 is used to select and move an object on the design window 103 or to newly set an object. In the object button group 102, a character string object, a price object, a barcode object, a date/time object, a graphic object, etc. can be selected as objects. Various settings for the object can be performed in the object property setting section 105.
In the example shown in FIG. 2, various settings for the selected object OBJ1 can be performed in the object property setting section 105. For example, the item name (“product name” in this example) in the object property setting section 105 sets the item used in the layout design in the design window 103. "Fixed" or "At the time of issue" can be selected as the input method. If "Fixed" is selected as the input method, it indicates that the value set in the "Data" field (in this example, "Chicken Cutlet Sandwich") is set to be printed, and the input method is "Issue". If "time" is selected, it indicates that the initial value set in the "data" column can be changed in the label issuing application of the printer 3.

By operating the buttons in the instruction button group 101, it is possible to read the project file from the storage, save the project file in the storage, or upload the project file to the server 5 as a format file. .

Next, the call table, kanji table, and store name table will be explained with reference to FIGS. 3 to 5.
To register data to be printed on a label in the call table, it is necessary to define the data in advance. In order to define the data, as shown in FIG. Display W1. The call table definition data TL1 of the window W1 shows an example in which four item names, "product name", "name", "content amount", and "expiration date" are defined. In the record corresponding to each item name of the call table definition data TL1, values of fields such as "Number of Digits", "Number of Digits Check", "Character Type Check", etc., are input, for example.

The values of each field such as "Number of digits", "Number of digits check", "Character type check", etc. correspond to each item name input by the user from the viewpoint of label layout, consistency of display contents on the label, etc. It is provided to check the character string, but it is not required.
The value in the "number of digits" field indicates the maximum number of digits in the character string corresponding to each item name. The value in the "Number of digits check" field indicates whether or not the character string corresponding to the item name is checked in the call table, or whether the number of digits in the character string corresponding to the item name is the value in the "Number of digits" field. Indicates whether the following is checked. The value of the "character type check" field indicates whether or not the character type (number or character string other than numbers) of the character string corresponding to the item name is checked, and the designation of the character type if checked.
When the user performs input in window W1 and creates call table definition data TL1, the item name to be printed on the label is registered in the call table (that is, the item is defined).

After creating the call table definition data TL1, the user registers print data in the call table. As shown in FIG. 4, by operating the "call table" in the project setting section 104 (for example, by double-clicking or right-clicking and selecting "open" (see FIG. 3)), the call table TL2 is is displayed.
In addition to fields for the four item names defined in call table definition data TL1 (see Figure 3), "product name,""name,""contents," and "expiration date," call table TL2 includes fields for "call table". "No." and "Layout specification" fields are provided.

Each record of the call table TL2 indicates a label layout for issuing one label and data (character string) of each defined item name. The data of each record is hereinafter referred to as "issue data." The user can associate the label layout with the character strings corresponding to each item name by inputting the character strings corresponding to each item name in the call table TL2. Note that the call table TL2 does not need to have a plurality of records, and may only have one record (that is, one piece of issued data).
In call table TL2, call No. The issued data is specified by In the label issuing application of the printer 3, the call No. The publication data is called by

In the call table TL2, the value of the "layout specification" field is a value indicating one or more layout data created in the design window 103 (see FIG. 2). In this example, if two layout data items have been created: [1] Content display label and [2] Deadline label, the value of the "Layout specification" field will be set as follows: This indicates whether the layout data is supported.

For example, in the label design in the design window 103 shown on the PC screen G1 in FIG. 2, the call number of the call table TL2. :Issuance data corresponding to the record of 1 (invocation name: "chicken cutlet sandwich") is displayed.
In this example, the label design in the design window 103 is the call number. : Corresponds to the value of the "layout specification" field ([1] content display label) of the record corresponding to 1. The character string in the object OBJ1 corresponding to the product name is the call number in the call table TL2. : Corresponds to the value of the "product name" field of the record 1. The character string in the object OBJ2 corresponding to the name is the call number in the call table TL2. : Corresponds to the value of the "Name" field of the record 1. The character string in the object OBJ3 corresponding to the content capacity is the call number in the call table TL2. : Corresponds to the value of the "content capacity" field of the record 1.

Call no. The value of the "expiration date" field of the record corresponding to :1 indicates the maximum number of digits of the date in object OBJ4, which is a date and time object corresponding to the expiration date. In the label design of the design window 103, the reference date or current date of the PC 2, for example, is displayed as the date in the object OBJ4 corresponding to the expiration date.

As described above, by registering data in the call table TL2, the user of the PC 2 can design labels with different layouts or labels with the same layout but with different printing contents for each item. For example, in the example shown in FIG. : The issue data corresponding to each of 1 to 3 corresponds to labels that have the same layout ([1] content display label) but have different printed content for each item. Call no. The issue data corresponding to :100 is the call number. : Corresponds to a label with a different layout from 1 to 3 ([2] deadline label).

As shown in FIG. 5, the kanji table TL3 can be displayed by operating (for example, double-clicking) the "kanji table" in the project setting section 104.
In the illustrated example, each record of the kanji table TL3 includes the values of the "registration number" and "character data" fields. The value of the "registration number" field is, for example, a number specified when inputting characters into a character string object. The value of the "character data" field is character data that is input when the corresponding registration number is specified.

As shown in FIG. 5, the store name table TL4 can be displayed by operating (for example, double-clicking) the "store name table" in the project setting section 104.
In the illustrated example, each record in the store name table TL4 includes values in the fields of "registration number,""storename,""address," and "telephone number." The registration number is a value that identifies the printer 3 to which the format file is to be delivered, and is associated with the printer ID (printer identification information). Since a plurality of printers 3 may be installed depending on the store, the registration number and store name do not necessarily correspond one-to-one. The example in FIG. 5 shows that two printers 3 with registration numbers 6 and 7 are installed at store F. Although not shown in FIG. 5, it is possible to add a new registration number record to the store name table TL4 or delete an existing record from the store name table TL4 based on a predetermined user operation.
The store name table TL4 is data for specifying the printer 3 to which the format file is delivered, and the "address" and "telephone number" fields for each store are not necessarily required.

As described above, the label creation application of the PC 2 creates layout data, a call table, a kanji table, and a store name table. Then, by operating the output button in the instruction button group 101, a project file including layout data, a call table, a kanji table, a store name table, and each table information file is uploaded to the server 5 as a format file.
Specifically, when the output button in the instruction button group 101 is operated, a data output window W2 is displayed as shown in FIG. In the output destination selection section 204 of the window W2, the storage within the PC 2 ("Devices and Drives") or the server 5 ("Server") can be selected as the output destination. Here, when "server" is selected, a window W3 is displayed. In window W3, by inputting the address (URL) corresponding to the server 5, login ID, and file name of the project file and operating the OK button, the format file corresponding to the project file is uploaded (window W4 ). Note that in window W3, authentication using a password may be performed for security.
In the example shown in FIG. 6, a format file with the file name "sandwich" is uploaded to the server 5.

(2-2) Issuing a label The procedure for issuing a label in the printer 3 is as follows.
First, the label issuing application of the printer 3 is activated and an operation is performed to download a format file from the server 5. Next, as shown in the printer screen g1 of FIG. 7, the user selects "sandwich" from among the downloaded format files as the format file corresponding to the label that the user wants to issue.
The printer screen g2 that is displayed next displays the call number in the selected format file. It includes an input box bx1 for inputting. The call number entered here. is the call number in the call table (see FIG. 4) in the format file. corresponds to For example, the call number is entered in the input box bx1. :003, the call number in the call table in FIG. The issue data of the record corresponding to :003 is called and the printer screen g3 is displayed.

The printer screen g3 displays the call No. as an initial value. The value of each item of the issue data corresponding to :003 is displayed on the issue data display section 206. In the issue data display section 206, the value corresponding to the expiration date is the reference date of the printer 3.
When the confirm button is operated on the printer screen g3, a printer screen g4 is displayed. The printer screen g4 includes a preview button b4, a confirm button b5, an input box bx2 for inputting the number of copies to be issued, and an input box group 207.
The input box group 207 consists of input boxes corresponding to each item of issue data. If the data input method in the label creation application is set to "at the time of issue" (see object property setting section 105 in FIG. 2), the user can select the input box and operate the software keyboard SK, for example. Strings can be edited.
A label is issued by operating the confirm button b5 on the printer screen g4. Note that a preview image of the label can be displayed by operating the preview button b4 before issuing the label.

As will be described later, the user of the printer 3 can individually edit the call table, kanji table, and store name table included in the format file downloaded by the printer 3.
In the following, the call table, kanji table, and store name table included in the format file immediately after being distributed by the PC 2 and downloaded by the printer 3 from the server 5 will be referred to as "master call table", "master kanji table", and "master kanji table", respectively. It is also written as "master store name table." The master call table, master kanji table, and master store name table are sometimes collectively referred to as a "master file."
In addition, the tables after the master call table, master kanji table, and master store name table have been edited by the user of the printer 3 are appropriately labeled "edited call table,""edited kanji table," and "edited Store name table". The edited call table, edited kanji table, and edited store name table may be collectively referred to as an "edited table" or "master edit file."

(3) Configuration of Information Processing System 1 Next, with reference to FIG. 8, the configurations of the PC 2, printer 3, and server 5 included in the information processing system 1 will be described.

(3-1) PC2
As shown in FIG. 8, the PC 2 includes a control section 21, a storage 22, an operation input section 23, a display section 24, a LAN interface 25, and a USB interface 26.

The control unit 21 is mainly composed of a microprocessor, and controls the entire PC 2. For example, the microprocessor included in the control unit 21 loads and executes a label creation application program recorded in the storage 22, and displays the execution result on the display unit 24.
The storage 22 is a nonvolatile memory, and may be, for example, an SSD (Solid State Drive) such as a flash memory. In addition to the label creation application program, the storage 22 stores project files created by running the label creation application, printer IDs of the printers 3 placed in each store (printer IDs corresponding to registration numbers in the store name table), etc. Remember.
The project file includes layout data, a call table, a kanji table, a store name table, and each table information file. Here, the call table, kanji table, and store name table are each examples of reference data.

By executing the label creation application, the control unit 21 may set whether or not the master file can be edited. The setting of whether or not the master file can be edited will be described later.

The operation input unit 23 includes, for example, an input device such as a pointing device and a touch panel. When the display section 24 includes a display panel for touch panel input, the display section 24 constitutes a part of the operation input section 23 .
The display unit 24 includes, for example, a liquid crystal display panel, and displays the execution results of the label creation application.
The LAN interface 25 is a communication interface that communicates with the server 5.
The USB interface 26 is an interface for direct communication with the printer 3.

(3-2) Printer 3
As shown in FIG. 8, the printer 3 includes a control section 31, a storage 32 (an example of a storage section), an operation input section 33, a display section 34, a transport section 35, a printing section 36, a LAN interface 37, and a USB interface 38. Equipped with

The control unit 31 is mainly composed of a microprocessor, and controls the entire printer 3 . The storage 32 is a nonvolatile memory, for example, an SSD such as a flash memory.
For example, the microprocessor included in the control unit 31 loads and executes the firmware and label issuing application program recorded in the storage 32.
The control unit 31 requests the server 5 to transmit a format file, receives the format file transmitted in response to the request via the LAN interface 37, and stores it in the storage 32. The timing at which the control unit 31 requests the server 5 to transmit the format file is not limited, but may be, for example, when the printer 3 is started, at a predetermined time every day, or when a predetermined download operation is performed by the user. The timing etc.

The storage 32 stores the printer ID of the printer 3 in addition to firmware and a label issuing application program. This printer ID corresponds to the registration number of the store name table recorded on the PC 2.
The storage 32 stores one or more format files downloaded from the server 5.

By executing the firmware, the control unit 31 converts the issued data into bitmap data for printing (print data), and sequentially sends line data, which is data for each line of print data, to the printing unit 36. The conveying unit 35 and the printing unit 36 perform printing based on line data that is sequentially sent out.
The transport section 35 includes a platen roller, a motor drive circuit, and a stepping motor (not shown), and transports the continuous paper within the printer 3. For example, based on a transport request from firmware, a motor drive circuit drives a stepping motor that controls rotation of a platen roller, thereby transporting continuous paper.
The printing unit 36 includes a thermal head and a head drive circuit (not shown). The head drive circuit prints on the continuous paper label by selectively passing current through each heating element of the thermal head based on line data.

The operation input section 33 includes a touch panel input provided on the display panel of the printer 3 and its input circuit.
The display unit 34 has a display panel, and displays the execution results of the label issuing application on the display panel.
The LAN interface 37 is a communication interface that communicates with the server 5.
The USB interface 38 is an interface for direct communication with the computer device 2.

(3-3) Server 5
The server 5 includes a control section 51, a storage 52, and a communication section 53.
The storage 52 is, for example, a large capacity storage device such as an HDD, and stores the format file sent from the PC 2 in association with the login ID.
The control unit 51 is mainly configured with a microprocessor, and controls the entire server 5 by executing a server program. The control unit 51 controls the communication unit 53 to transmit a format file in response to a request from the printer 3, for example.
The communication unit 53 is a communication interface that communicates with each of the PC 2 and the printer 3.

This will be further explained with reference to FIG. FIG. 9 is a functional block diagram of the printer 3 and server 5 of the information processing system 1.
Referring to FIG. 9, by executing the label issuing application, the control unit 31 of the printer 3 includes a data updating unit 311, a data editing unit 312, a print control unit 313, an automatic backup processing unit 314, a manual backup processing unit 315, It functions as a backup generation setting section 316 and a restore processing section 317.
The control unit 51 of the server 5 functions as a data recording unit 511 and a data deletion unit 512 by executing a server program.

In the printer 3, the layout data and master files (i.e., master call table, master kanji table, master store name table) recorded in the storage 32 based on the format file downloaded from the server 5 are updated regularly or irregularly. be done. At this time, the data update unit 311 updates the layout data and master file in the first storage area of the storage 32 with the layout data and master file received from the computer device 2 via the server 5 at the data update timing. The timing of data update is not limited, but may be, for example, when the printer 3 is started, at a predetermined time every day, or when a user performs a predetermined download operation.

When the user edits the master file included in the downloaded format file, the storage 32 stores the edited master edit file (that is, at least one of the edited call table, edited kanji table, and edited store name table). ). At this time, the master edit file is recorded in a storage area (second storage area) different from the storage area (first storage area) in which the original master file is stored in the storage 32. That is, the data editing unit 312 edits the master file in the first storage area of the storage 32 based on the user's operation input, and records the edited master edited file in the second storage area of the storage 32.

In one embodiment, permission to edit the master file can be set by a label creation application on the PC 2. The printing control unit 313 performs printing based on the master editing file when editing of the master file is set to be permitted, and prints based on the master file when editing of the master file is set to be prohibited. Printing is performed based on the

In one embodiment, the master edit file created by the user of the printer 3 can be backed up to the server 5 and external USB storage in case the printer 3 fails.
The automatic backup processing unit 314 (an example of a first backup processing unit) periodically backs up the master editing file in the storage 32 to the server 5.
The manual backup processing unit 315 (an example of a second backup processing unit) backs up the master editing file in the storage 32 to an external USB storage in response to a user's operation.

In one embodiment, the printer 3 can be restored based on backed up data (backup data).
The restore processing unit 317 restores the printer 3 based on backup data stored in an external USB storage or the server 5.

As will be described later, in automatic data backup, the server 5 does not record the data to be backed up in the printer 3 as is, but records it if there is a difference from the previous backup data. When the data to be backed up is a master edit file, the data recording unit 511 stores the master edit file based on the latest edit if there is a difference between the master edit file based on the latest edit on the printer 3 and the master edit file based on the previous edit. Record the file in storage 52.

The backup generation setting unit 316 sets the maximum number of master editing files stored in the storage 52 of the server 5 based on the operation input by the user of the printer 3.
The data deletion unit 512 deletes the master edit file recorded in the storage 52 in the past based on the maximum value set by the backup generation setting unit 316. That is, in the storage 52, master editing files that are old backup data are sequentially deleted.

Referring to FIG. 10, the label issuing operation is as follows.
In response to the user's operation, the label creation application of the PC 2 transmits a format file including each table (master file) to the server 5 (step S2). The server 5 stores the format file received from the PC 2 in the storage 52 (step S4).
The server 5 transmits the format file to the printer 3 in response to a request from the printer 3 (for example, a request for data update) (step S6), and the printer 3 saves the received format file in the storage 32 (step S8). ).

After that, as shown in FIG. 7, the printer 3 reads the format file selected according to the user's operation (step S10), and reads the format file selected according to the user's operation (step S10). (Step S12). Next, the printer 3 receives the input call number. The issuing data called by is displayed as shown on the printer screen g3 (FIG. 7) (step S14), and the label becomes ready to be issued. Once the format file is obtained from the server 5, the label issuing application of the printer 3 can print each call number even in an offline environment. It is possible to issue a corresponding label.

(4) Management of edited tables Next, management of edited tables in the printer 3 will be explained with reference to FIGS. 11 to 14.
As described above, the format file downloaded by the printer 3 includes a call table, a kanji table, and a store name table (that is, a master file). This master file is data that corresponds to labels that are commonly used in all stores managed by the headquarters. On the other hand, the user of the printer 3 at the store can edit the master file and save it in the storage 32 as a master edited file. This allows store users to create and save data for printing labels to be affixed to store-specific products when the store has its own products.

FIG. 11 is a diagram showing, as an example, a procedure when a user of the printer 3 in a store edits a call table (master call table).
Referring to FIG. 11, when the "master edit" item is selected on the printer screen g5 related to settings, the screen switches to the printer screen g6, and a screen for editing the master file (master edit) for each format file appears. In master editing, the master call table, master kanji table, and master store name table can be edited individually. Here, for example, when an operation is performed to select the master call table as an object to be edited, a printer screen g7 for editing the master call table is displayed.
For example, if you select "New Registration" on the printer screen g7, a new call number will be added to the master call table. You can add corresponding publication data. In other words, it is possible to create an edited call table in which new issue data is added to the master call table. In this case, new issue data can be created by the user inputting values for each item included in the issue data, as displayed on the printer screens g8 to g9.

Although not shown, if you select "Copy and register new" on the printer screen g7, you can create a new copy by copying the issue data included in the master call table and changing the values of some items. Issue data is possible. When selecting "Change" on the printer screen g7, it is possible to change some items of the issue data included in the master call table. When selecting "Delete" on the printer screen g7, it is possible to delete at least one issue data included in the master call table. In either case, a new master edit file is created by editing the master file.
Although FIG. 11 shows the procedure for editing the master call table, the master kanji table and master store name table can also be edited individually in the same way.

FIG. 12 shows an example of the structure of a directory in the storage 32 of the printer 3 according to the embodiment.
As mentioned above, the master edit file created as shown in FIG. storage area).

As shown in FIG. 12, the storage 32 includes a FormatFiles folder, a History folder, a LocalTables folder, a Logs folder, and a Settings folder.
The FormatFiles folder is a folder that stores layout data, a master call table, a master kanji table, and a master store name table for each format file.
The Histories folder is a folder containing publication history files for each format file. The issuance history file includes, for example, data on past label issuance history (contents such as when and how many labels were issued).
The LocalTables folder is a folder that stores an edited call table, an edited Kanji table, and an edited store name table for each format file.
The Logs folder is a folder in which error information that occurs in the label issuing application is recorded for later troubleshooting.
The Settings folder is a folder containing setting information files.

As shown in FIG. 12, in the storage 32, master files (master call table, master kanji table, and master store name table) and master edit files (edited call table, edited kanji table, and edited store name table) are saved in different folders. That is, the master file and the master edit file are stored in different storage areas of the storage 32.
Note that if the master editing file is further edited, the master editing file already in the LocalTables folder will be overwritten and saved.

When updating data, the control unit 31 of the printer 3 overwrites and updates the master file included in the corresponding format file in the FormatFiles folder of the storage 32 with the master file included in the format file downloaded from the server 5. When this data is updated, the master editing file in the LocalTables folder of the storage 32 is not updated. Therefore, in the information processing system 1 of the embodiment, when updating the data of the printer 3 based on the format file received from the PC 2 via the server 5, the master editing file that is the data edited by the printer 3 is updated. You can prevent it from being deleted.

In one embodiment, the label creation application on the PC 2 at the headquarters may be able to set whether or not master editing can be performed on the printer 3 at the store.
FIG. 13 shows a display example of the object property setting section 105 when each table is selected on the project file creation screen of the PC 2 according to the embodiment. FIG. 13 shows the display state of the object property setting section 105 when a call table, a kanji table, and a store name table are each selected in the project setting section 104 from the left. As shown in FIG. 13, edit permission buttons 211 to 213, which are buttons for "permit master editing in Print", are provided for each table. By operating this button, it is possible to set whether or not to permit master editing by the label issuing application of the printer 3.

Settings made using the edit permission buttons 211 to 213 are reflected in the edit permission flags included in each table information file. The label issuing application of the printer 3 refers to the editing permission flags in each table information file included in the format file received via the server 5, and determines whether editing is permitted or prohibited individually for the call table, kanji table, and store name table. Determine. That is, the label issuing application obtains each table information file from the server 5, and does not permit master editing if the edit permission flag included in each obtained table information file indicates that editing is not allowed.
By determining whether or not to allow editing, the headquarters can determine, on a table by table basis, which tables are allowed to be edited on the store side and which tables are not allowed to be edited.

If a plurality of kanji tables or a plurality of store name tables are provided, it is possible to set whether or not master editing is allowed for each table. For example, if Kanji table 1, Kanji table 2, Kanji table 3, etc. are set, the corresponding table No. (1, 2, 3, . . .) can be specified to individually set whether or not to allow master editing. By individually setting whether or not to allow master editing, stores can flexibly set the degree of freedom to issue their own labels.

Next, referring to FIG. 14, there is shown a flowchart illustrating a process for determining a table to be referred to when issuing a label based on the issuing data in the printer 3. The flowchart in FIG. 14 is executed by the control unit 31 of the printer 3.
As shown in FIG. 12, when the master file is edited using the printer 3 in the store, the master file and the master edited file coexist. In that case, the priority of the table to be referred to when reading issue data from the corresponding format file and issuing a label is defined by the flowchart of FIG. 14.

In FIG. 14, for example, if any format file is selected on the printer screen g1 in FIG. The permission flag is read (step S22). As described above, the editing permission flag is a flag indicating whether master editing is permitted for each table, and is set for each of the call table, kanji table, and store name table.

Each process of steps S24 to S30 is sequentially performed for each table with reference to the editing permission flag (step S32). Specifically, when the editing permission flag corresponding to the table to be processed indicates "permission", the LocalTables folder in the storage 32 is referred to with priority. That is, if there is an edited table in the LocalTables folder (step S26: YES), the control unit 31 refers to the edited table in the LocalTables folder (step S28).
If the editing permission flag corresponding to the table to be processed indicates "not permitted" in step S24, or if there is no edited table in the LocalTables folder (step S26: NO), the control unit 31 edits the table in the FormatFiles folder. (that is, the master call table, master kanji table, or master store name table) (step S30).

As shown in the flowchart of FIG. 14, when the printer 3 issues a label based on the issue data, if an edited table exists in the LocalTables folder, the edited table is referred to preferentially. Therefore, users of printers 3 in stores must update the data for labels that are used universally in all stores managed by the headquarters, while at the same time updating the data for labels that are Labels to be affixed to products can also be issued.

As described with reference to FIG. 13, allowing the headquarters to set whether or not to permit master editing using the printer 3 at the store has the following advantages.
For example, some retail stores may change their operations such that all tables are centrally managed at the headquarters from a certain point. In that case, even if the headquarters wishes to issue labels based on the master file at all stores, if the master editing file is in the printer 3 of the store, the master editing file will not be printed as shown in the flowchart of FIG. Priority is given to reference and master file is not referenced. Therefore, by allowing the head office to set whether or not to allow master editing using the printer 3 at the store side for each table, even if there is a master editing file, the master file (data in the FormatFiles folder) It can be controlled so that it is referenced preferentially.

In one embodiment, the control unit 31 deletes from the storage 32 the master editing file corresponding to the format file deleted from the printer 3 at the data update timing.
At the time of data update, format files that are no longer needed at all stores managed by the headquarters may be deleted. In such a case, the printer 3 deletes any format file stored in the storage 32 based on an instruction from the PC 2 via the server 5. At this time, the format file to be deleted and the master editing file created based on the format file are stored in different folders, so even after the format file is deleted, they cannot be stored in the storage 32 as they are. It is possible. However, even if the master editing file remains alone, it cannot be used and it takes up space in the storage 32, so it is preferable to delete it.

As described above, according to the information processing system 1 of one embodiment, the printer 3 communicates with the server 5 a master file that is subject to data update, and a master file that is edited by the user of the printer 3. The master editing files created by doing this are respectively recorded in different storage areas of the storage 32. Therefore, the store can prevent the master editing file used for the store's own products from being deleted from the printer 3 at the time of data update, while maintaining the function of updating the master file with the headquarters.

(5) Backup and Restore of Master Edit File Next, backup and restore of data in the printer 3 will be explained with reference to FIGS. 15 to 19.
If the printer 3 breaks down, for example, the master editing files (edited call table, edited kanji table, and edited store name table) created by the store user will be lost. It is configured to ensure reliable backup. Automatic backup and manual backup are available as backup methods. Note that, as described later, the data to be backed up is not limited to the master editing file.
In the following description, data recorded in the backup destination server 5 or USB storage through backup processing by the printer 3 may be referred to as "backup data."

Automatic backup refers to backing up data by transmitting and recording data to the server 5 periodically (for example, at a predetermined time every day) or when the printer 3 is started. Since the automatic backup is performed without the user's awareness, it is possible to avoid problems in the restoration of the printer 3 due to the user forgetting to manually back up data.

Manual backup refers to backing up data by the user performing an operation himself/herself to record data in the printer 3 onto a USB storage.
Manual backup is provided for the following reasons: First, when a user uses the printer 3 without connecting to the server 5, it is more convenient for the user of the printer 3 to be able to back up the data manually. Second, when a service person from the manufacturer or agency of the printer 3 comes to investigate the cause of a malfunction in the printer 3 at a store, the printer 3 data can be backed up to a USB storage device and taken home. , so that the problem can be resolved quickly.
Further, by performing manual backup, there is an advantage that kitting work for a plurality of printers 3 can be easily performed using a USB storage. For example, settings for a large number of printers 3 can be configured by repeatedly backing up data on the first printer 3 to a USB storage and restoring the second printer 3 using the data backed up to the USB storage. The burden of kitting work is reduced.

As described later, in manual backup, all data to be backed up is backed up, but in automatic backup, backup is performed when there is a difference between the data to be backed up and the previous backup data.

Note that the data backup destination is not limited to the USB storage or the server 5, but may be the internal storage 32 of the printer 3. By using the storage 32 as a data backup destination, it becomes possible to easily restore the data if the user makes a mistake in changing the settings or changes the master file.

(5-1) Automatic backup Next, automatic backup will be further explained with reference to FIGS. 15 to 17.
FIG. 15 shows a procedure for setting automatic backup in the printer 3.
Referring to FIG. 15, when the item "external storage cooperation management" is selected on the printer screen g10 related to settings, the screen switches to the printer screen g11. Next, when the item "Cooperation target data" is selected, a printer screen g12 is displayed, and details of downloading and uploading of data between the server 5 and the printer 3 can be set. Note that the printer screen g12 can be displayed when "external storage cooperation" is enabled in the "external storage cooperation management" of the printer screen g11.
On the printer screen g12, the "Upload" item includes the "[Backup] Master Edit File" and "[Backup] Settings Information File" items, which enable automatic backup of the master edit file and the settings information file, respectively. A button is provided for setting whether to disable or disable. By operating this button to the valid position, you can perform automatic backup of the master editing file and setting information file individually. Although not shown, the timing for automatic backup (for example, a predetermined time every day) can be set by a user operation.

The data to be automatically backed up is, for example, a format file, a master editing file (edited call table, edited kanji table, edited store name table), and setting information file.

FIG. 16 shows an example of the structure of a directory in the storage 52 of the server 5 according to the embodiment.
As shown in FIG. 16, the storage 52 includes a FormatFiles folder, a Logs folder, a BackupFiles folder, and a Settings folder.
The FormatFiles folder is a folder containing format files uploaded from the PC2.
The Logs folder is a folder containing publication history files uploaded from the printer 3.
The BackupFiles folder is a folder containing data backed up for each printer ID (for example, “0001-SX-5555”) of the printer 3 that can be connected to the server 5.
The Settings folder is a folder containing setting information files.

As shown in FIG. 16, a folder (YYYYMMDD-hhmmss folder) indicating the time when automatic backup was performed for a specific printer 3 is automatically generated in the BackupFiles folder. For example, if automatic backup is performed at 21:08:38 on April 25, 2022, the automatically generated folder name will be "20220425-210838".
The YYYYMMDD-hhmmss folder has a LocalTables folder and a Settings folder. The LocalTables folder contains data backed up by master editing files for each format file. The Settings folder contains backed up settings information files.

Automatic backup is performed periodically, for example, and at this time, the printer 3 uploads the master editing file stored in the LocalTables folder to the server 5. If there is a difference between the master edit file uploaded last time and the master edit file uploaded this time, the server 5 creates a folder (YYYYMMDD-hhmmss folder) indicating the time of the latest upload, and stores the files in the YYYYMMDD-hhmmss folder. The master editing file uploaded this time is recorded (see Figure 16).

Next, automatic backup processing in the information processing system 1 will be described with reference to FIG. 17.
FIG. 17 is a sequence chart when performing automatic backup processing of an edited table in the information processing system 1.

The sequence chart in FIG. 17 also includes data update processing by the printer 3. That is, at the data update timing, the printer 3 transmits a data update request to the server 5 (step S38). In response to the data update request, the server 5 transmits the update data of the format file (including the update master file, for example) to the printer 3 (step S40), and the printer 3 performs data update processing based on the update data. (Step S42). In the data update process, for example, the master file stored in the storage 32 is overwritten and updated by the master file included in the update data.

When the preset automatic backup time comes, the printer 3 transmits the master editing file and/or setting information file stored in the storage 32 to the server 5 (step S44). The transmitted file follows the settings on the printer screen g12 in FIG. 15.
The server 5 determines whether there is differential data between the data (master edit file or setting information file) at the time of the previous automatic backup (for example, the previous day) and the data (master edit file or setting information file) received in step S44. A judgment is made (step S46). As a result, if there is a difference between both files or either file, the server 5 generates a YYYYMMDD-hhmmss folder (see FIG. 16) based on the time when the files were received in step S44, and The data (master editing file and setting information file) received in step S44 is recorded in the -hhmmss folder as new backup data (step S48). The setting information file received in step S44 is recorded as is in the YYYYMMDD-hhmmss folder.
In one embodiment, the server 5 deletes old backup data (step S50). That is, if old backup data is stored forever, it will compress the capacity of the storage 52, so it is preferable to delete old backup data one by one.

(5-2) Manual Backup Next, manual backup will be further explained with reference to FIG. 18.
FIG. 18 is a diagram showing a procedure for setting manual backup in the printer 3. Note that when performing the procedure shown in FIG. 18, it is assumed that the USB storage serving as the backup destination is connected to the printer 3.
Referring to FIG. 18, when the "system management" item is selected on the printer screen g13 related to settings, the screen switches to the printer screen g14. Next, when the user selects the "backup/restore" item, a printer screen g15 is displayed. Here, when the "backup" item is selected, a backup screen is displayed as shown in printer screen g16. The printer screen g16 includes an input area 301 for the user to input comments.

Comment input in the input area 301 is useful when restoring the printer 3. When manual backup is performed multiple times, a comment (text) is associated with the data backed up each time. That is, the control unit 31 of the printer 3 receives text input by the user when backing up the master edit file, and associates the input text with the master edit file to be backed up. As a result, when there is a plurality of backup data, the user can select data to be used for restoration from among them according to the content of the comment. For example, by entering "data after XX settings" as a comment, it becomes easier to select data when restoring.

In the case of manual backup as well as automatic backup, a YYYYMMDD-hhmmss folder is generated in the backup destination USB storage, and the backup data is recorded in the YYYYMMDD-hhmmss folder. At this time, the generated YYYYMMDD-hhmmss folder and the text input in the input area 301 are associated.
Manual backup is not limited to master editing files and setting information files, but targets all folders.

(5-3) Restoration Next, the procedure for restoring (recovering) the printer 3 based on data backed up by automatic backup or manual backup will be described with reference to FIG. FIG. 19 shows a procedure for restoring data in the printer 3. Note that when the backup data is stored in a USB storage, it is assumed that the USB storage is connected to the printer 3.

Referring to FIG. 19, when the "restore" item is selected on the settings-related printer screen g15, the screen switches to the printer screen g17. The printer screen g17 is configured such that the user can operate a selection button 302 for selecting the printer 3 to be restored and a selection button 303 for selecting backup data. Note that, in order to ensure the safety of manual backup, it is preferable that the printer screen g15 (setting screen) be displayed when authentication using the user's ID and password is successful.

With the selection button 303, it is possible to select the name of the YYYYMMDD-hhmmss folder of the server 5, which is the automatic backup destination, or the name and comment of the YYYYMMDD-hhmmss folder of the USB storage, which is the manual backup destination.
When the OK button is operated after selecting the printer 3 to be restored and the backup data, a printer screen g18 is displayed as a restoration confirmation screen. The selection button 303 displays the name of the selected YYYYMMDD-hhmmss folder along with the associated text (e.g. "Evacuation"), so if multiple backup data exist, the user can select the desired backup data. It's easy to do.
A checkbox group 304 is provided on the printer screen g18. The checkbox group 304 allows the user to select a folder (at least one of the FormatFiles folder, LocalTables folder, and Settings folder) to be used during restoration among the YYYYMMDD-hhmmss folders. When the OK button is operated on the printer screen g18, restoration is executed.

In addition, in FIG. 19, the printer screen g15 related to settings has an item "backup generation setting", and by selecting this item, it is possible to set the generation of backup data to be saved in the server 5. For example, any value from 1 to 9 can be selected as the generation setting. That is, the control unit 31 of the printer 3 sets the maximum number of backup data stored in the storage 52 of the server 5 based on the user's operation input. This maximum value is notified to the server 5, for example, when automatic backup is executed.
For example, if "3" is selected as the generation setting, it means that three times' worth of backup data will be saved. In step S50 of FIG. 17, the server 5 determines the backup data to be deleted based on the value of the backup generation setting acquired from the printer 3. That is, the control unit 51 of the server 5 functions as a data deletion unit that deletes backup data recorded in the storage 52 in the past based on the maximum value set by the printer 3.
Backup generation settings can be made for both automatic backups and manual backups. By setting the backup generation, backup data that is too old to be needed at the time of restoration will not be stored in the backup destination, so the capacity of the storage 52 or USB storage will not be overwhelmed.

As explained above, in the information processing system 1 of one embodiment, the printer 3 automatically backs up data to the server 5 periodically, and also stores data in a USB storage based on the user's own operation as needed. Since manual backup is performed, it is possible to reliably back up data created in the printer, such as master editing files. At that time, automatic backup saves data on the server 5 only when the data is changed by editing on the printer 3, so it does not take up the capacity of the server 5. Manual backup saves the data on the server 5 only when the data is changed by editing on the printer 3. Users can directly connect a USB storage to the printer 3 for backup, and it is also convenient for service personnel to download data from the printer 3 when diagnosing a failure of the printer 3.

In automatic backup, the master edit file may be backed up as differential data. That is, automatic backup is performed periodically, for example, and at this time, the printer 3 uploads the master editing file stored in the LocalTables folder to the server 5. The server 5 records data (difference data) indicating the difference between the master edit file uploaded last time and the master edit file uploaded this time. At that time, the server 5 generates a folder (YYYYMMDD-hhmmss folder) indicating the current upload time, and records the difference data in the YYYYMMDD-hhmmss folder.
FIG. 20 shows an example of the structure of a directory in the storage 52 of the server 5 according to an embodiment. The difference from FIG. 16 is that differential data is stored in the storage 52 as backup data. In FIG. 20, the difference between the current edited call table and the previous edited call table is referred to as a "differential call table," and the difference between the current edited kanji table and the previous edited kanji table is referred to as a "difference kanji table." The difference between the current edited store name table and the previous edited store name table is referred to as a "difference store name table."
Since the master file is known in the server 5, the latest master edited file can be reproduced at the time of restoration, which will be described later, based on the master file and one or more pieces of differential data that are automatically backed up each time.

FIG. 21 is a sequence chart showing automatic backup processing when backing up differential data. In FIG. 21, steps S38 to S44 are the same as in the sequence chart of FIG. 17, so repeated explanation will be omitted.
When the server 5 receives the master edit file from the printer 3, it extracts differential data between the latest file already backed up in the storage 52 and the master edit file received in step S44 (step S52). The server 5 generates a YYYYMMDD-hhmmss folder (see FIG. 20) based on the time when the file was received in step S44, and records the difference data in the generated YYYYMMDD-hhmmss folder (step S54). The setting information file received in step S44 is recorded as is in the YYYYMMDD-hhmmss folder.
In one embodiment, the server 5 deletes old differential data (step S56). That is, if old differential data is stored forever, it will compress the capacity of the storage 52, so it is preferable to delete old differential data one by one.

Although one embodiment of the information processing system, printer, and program of the present invention has been described above in detail, the present invention is not limited to the above embodiment. Moreover, various improvements and changes can be made to the embodiments described above without departing from the spirit of the present invention.

1... Information processing system 2... Computer device 21... Control unit 22... Storage 23... Operation input unit 24... Display unit 25... LAN interface 26... USB interface 3... Printer 31... Control unit 311... Data update unit 312... Data editing unit 313...Print control section 314...Automatic backup processing section 315...Manual backup processing section 316...Backup generation setting section 317...Restore processing section 32...Storage 33...Operation input section 34...Display section 35...Transportation section 36...Printing section 37... LAN interface 38...USB interface 5...Server 51...Control section 511...Data recording section 512...Data deletion section 52...Storage 53...Communication section 101...Instruction button group 102...Arrangement setting button group 103...Design window 104...Project setting section 105...Object property setting section 204...Output destination selection section 206...Issuance data display section 207...Input box group 211-213...Edit permission/denial button 301...Input area 302, 303...Selection button 304...Check box group OBJ1-OBJ4...Object SK...Software keyboard TL1...Call table definition data TL2...Call table TL3...Kanji table TL4...Store name table

Claims (6)

An information processing system including an information processing device and a printer capable of communicating with the information processing device,
The printer includes:
a storage unit that stores layout data indicating a layout when printing, and reference data that is associated with the layout data and is referred to when printing;
a data editing unit that edits the reference data based on a user's operation input, records edited data that is the edited reference data in the storage unit, or updates the edited data in the storage unit at any time;
a first backup processing unit that backs up the edited data in the storage unit to the information processing device periodically or when starting the printer;
a second backup processing unit that backs up the edited data in the storage unit to an external storage device in response to an operation by a user;
The information processing device includes:
comprising a data recording unit for recording edited data to be backed up in a storage unit when there is a difference between edited data by the latest editing of the printer and edited data by the previous editing;
Information processing system. The printer includes a setting unit that sets a maximum number of edited data to be backed up by the information processing device based on a user's operation input,
The information processing device includes a data deletion unit that deletes edited data recorded in the past in the storage unit based on the maximum value set by the setting unit.
The information processing system according to claim 1. The second backup processing unit receives text input by the user when backing up the edited data, and associates the input text with the edited data to be backed up.
An information processing system according to claim 1 or 2. The printer includes a restore processing unit that performs restoration based on the edited data backed up in the storage device,
The restore processing unit displays the edited data backed up in the storage device together with associated text when performing the restore.
The information processing system according to claim 3. A printer capable of communicating with an information processing device,
a storage unit that stores layout data indicating a layout when printing is performed by the printer; and reference data that is associated with the layout data and is referred to when printing;
a data editing unit that edits the reference data based on a user's operation input, records edited data that is the edited reference data in the storage unit, or updates the edited data in the storage unit at any time;
a first backup processing unit that backs up the edited data in the storage unit to the information processing device periodically or when starting the printer;
a second backup processing unit that backs up the edited data in the storage unit to an external storage device in response to a user operation;
printer with. A program executed on a printer capable of communicating with an information processing device,
The printer includes:
comprising a storage unit that stores layout data indicating a layout when printing is performed by the printer, and reference data that is associated with the layout data and is referred to when printing,
The program causes the computer to
a data editing unit that edits the reference data based on a user's operation input, records edited data that is the edited reference data in the storage unit, or updates the edited data in the storage unit at any time;
a first backup processing unit that backs up the edited data in the storage unit to the information processing device periodically or when the printer is started; and
a second backup processing unit that backs up the edited data in the storage unit to an external storage device in response to a user operation;
A program to function as

Images