TWI792057B - Computer-implemented systems and methods for digitizing attachment data - Google Patents

Abstract

Disclosed embodiments provide systems and methods for defining, inserting, and digitizing attachment data. A method defining, inserting, and digitizing attachment data comprises receiving, from a user device, a request for inserting an attachment to a first document, preparing an interface for defining an attribute, receiving the defined attribute, and preparing a data structure comprising a definable input corresponding to the received defined attribute. The method further comprises transmitting the prepared data structure to a user device, receiving an updated data structure from the user device, and digitizing the defined input based on a data format associated with the attribute. The method further comprises generating an attachment including the digitized input and an electronic document by inserting the generated attachment to the first document.

Description

Computer-implemented system and method for digitizing attached data

The present disclosure generally relates to computerized systems and methods for manipulating electronic records. Specifically, embodiments of the present disclosure relate to an inventive and non-traditional computer-implemented method for efficiently manipulating metadata incorporated in attachments to electronic records by defining, inserting, and digitizing the metadata. Systems, methods and user interfaces.

Paper negotiable instruments and records (contracts) often require appendices to specify information associated with the contract. For example, an attachment to a sales contract may include metadata setting forth a list of products and corresponding prices associated with the sales contract. As the acceptance and need for electronic records becomes more common, a process needs to be created for inserting metadata into such attachments.

In the past, electronic systems that allowed the insertion of metadata in annexes to contracts typically required the development of tools for each new contract. For example, if a party wants to add an attachment including a product list to an RTS contract, a new tool capable of inserting metadata (ie, product identifier (ID) and name) is required. In addition, a new server is required to store and reuse the input data. The new server will digitize the metadata and implement a method of storing the digitized metadata for each contract. because The system needs to be customized for each new contract and is therefore cumbersome.

Accordingly, there is a need for improved methods and systems for manipulating electronic records by defining, inserting and digitizing metadata incorporated in attachments to electronic records.

One aspect of the present disclosure pertains to a computer-implemented system for defining, inserting and digitizing attachment data. The computer-implemented system may include one or more memory devices storing instructions. The computer-implemented system may also include one or more processors configured to execute the instructions to perform operations. The operations may include: receiving a request from a user device to insert an attachment into the first file, the attachment including at least one definable attribute; preparing an interface including one or more attributes defining the attribute an input, the attributes including an attribute name and a data format; and responding to the received request by presenting the interface in a web browser in the user device. The operations may further include: receiving the definable attributes from the interface; preparing a data structure including definable inputs corresponding to the received definable attributes; sent to the user device in response to the attributes received. The operations may further include: receiving the data structure from the user device; digitizing the defined input based on the data format associated with the attribute; and generating the digitized input and generating an electronic file by inserting the generated attachment into the first file.

Another aspect of the present disclosure relates to a method for defining, inserting and digitizing attachment data. The method may include: receiving from a user device an attached A request to insert an attachment into a first file, the attachment including at least one definable attribute; preparing an interface, the interface including one or more inputs for defining the attribute, the attribute including attribute name and data format ; and responding to the received request by presenting the interface within a web browser in the user device. The method may further include: receiving the definable attribute from the interface; preparing a data structure including definable inputs corresponding to the received definable attribute; sent to the user device in response to the attributes received. The method may further include: receiving the data structure from the user device; digitizing the defined input based on the data format associated with the attribute; and generating the digitized input and generating an electronic file by inserting the generated attachment into the first file.

Yet another aspect of the present disclosure relates to a computer-implemented system for defining, inserting and digitizing attachment data. The computer-implemented system may include a database and one or more memory devices storing instructions. The computer-implemented system may also include one or more processors configured to execute the instructions to perform operations. The operations may include: receiving a request from the first user device to insert an attachment into the first file, the attachment including at least one definable attribute; preparing an interface including a or more inputs, the attributes including attribute names and data formats; and responding to the received request by presenting the interface in a web browser in the user device. The operations may further include: receiving the defined attributes from the interface; preparing a data structure, the data A structure includes definable inputs corresponding to the received attributes; and responding to the received attributes by transmitting the data structure to the first user device. The operations may further include: receiving the data structure from the first user device; digitizing the defined input based on the data format associated with the attribute; and generating the digitized and generating an electronic file by inserting the generated attachment into the first file. The operations may further include: receiving a request from a second user device to access the stored attachment; retrieving the stored attachment from the database; and transmitting the retrieved attachment to The second user device.

Other systems, methods, and computer-readable media are also discussed herein.

100: computer system/system/computer

102: Central processing unit (CPU) or processor

104: memory unit/memory

106: Read-only memory (ROM)

108: Basic Input/Output System (BIOS)

110: Random Access Memory (RAM)

112: Operating system (OS)

114: Application

116:Code/programmable code

118: program

120: Hard disk drive/hard disk

122: busbar

126: memory device

128, 206: Network

130: Display

136:Mobile device

138: action command

202: user device

204: Web browser

208:Server

212:Online self-help tools

216:Interface database

218:Create interface

220: Editor interface

222: Upload interface

224: Download interface

226: Save interface

234:Preview interface

300: Process/Method

301: square/step

302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312: steps

400: User Interface/Interface

401, 402, 407, 408, 409, 410: input

403: indicator

404, 405, 411, 412: buttons

406, 601, 602, 603, 604: definable attributes/properties

500: Attributes can be defined

501: identification code

502: attribute name

503: display name

504: data format

505: Default value

600:Data structure

700: Attachments

701, 702, 703, 704: attributes

FIG. 1 is a block diagram of an exemplary computer system consistent with the disclosed embodiments.

2 illustrates a logic diagram of an exemplary system for defining, inserting, and digitizing attachment data, consistent with disclosed embodiments.

3A is an exemplary flowchart of a process for defining, inserting, and digitizing attachment data, consistent with disclosed embodiments.

3B is a sequential exemplary flowchart of a process for defining, inserting, and digitizing attachment data, consistent with disclosed embodiments.

4 is an exemplary user interface of a mobile device displayed on a web browser for defining an attachment including one or more attributes, consistent with disclosed embodiments.

FIG. 5 illustrates exemplary definable attributes received from the exemplary user interface in FIG. 4 .

FIG. 6 illustrates an exemplary data structure including definable inputs corresponding to each of the definable attributes prepared by the server in FIG. 2 .

7 illustrates an exemplary attachment including attributes incorporated into digitized input.

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers will be used in the drawings and the following description to refer to the same or like parts. While several exemplary embodiments are set forth herein, various modifications, adaptations, and other implementations are possible. For example, substitutions, additions or modifications may be made to components and steps shown in the drawings, and the illustrative arrangements set forth herein may be modified by substitution, reordering, removal or addition of steps of the disclosed methods. method. Therefore, the following detailed description is not limited to the disclosed embodiments and examples. Rather, the true scope of the invention is defined by the appended claims.

Embodiments of the present disclosure relate to systems and methods configured to monitor logistics. The disclosed embodiments provide innovative technical features that allow the definition, insertion, and digitization of metadata incorporated in attachments to electronic archives. For example, the disclosed embodiments can: prepare an interface defining attributes of an accessory and transmit the interface to a user device; receive definable attributes from the user device; prepare an interface including An input data structure may be defined and the data structure transmitted to the user device; an updated data structure is received from the user device; the defined input incorporated into the updated data structure is digitized; and longitude The digitized input is stored in the database. The updated data structure may be appended to the first file in the form of a table or the like. Any digitized input incorporated into the data structure may provide information associated with the first file. For example, if the first file is about a sales contract in the form of a Microsoft Word document, the attachments may include a list of products in the form of a Microsoft Excel spreadsheet with each item in the product. One (digitized input) associated information, and disclosed embodiments may insert a spreadsheet into the first file.

FIG. 1 illustrates a block diagram of an exemplary computer system 100 consistent with the disclosed embodiments. Components of the system 100 may include a central processing unit (Central Processing Unit, CPU) or processor 102 , a memory unit 104 , and a bus 122 interconnecting system components including the memory 104 and the CPU 102 . Computer system 100 may include computer-readable media, such as volatile computer storage media or non-volatile computer storage media (e.g., random Access memory (random access memory, RAM), read-only memory (read-only memory, ROM), electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), fast Flash memory or other memory technology, compact disc-ROM (CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage device or any other suitable medium).

The bus 122 can be a suitable type of bus structure, such as a memory bus or memory controller, a peripheral bus, and a bus using a suitable bus architecture. Regional bus. By way of example and without limitation, such architectures may include an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (Enhanced ISA, EISA) bus, Video Electronics Standards Association (VESA) regional bus and Peripheral Component Interconnect (PCI) bus - also known as Mezzanine bus.

Memory 104 may include computer readable media such as read only memory (ROM) 106 and random access memory (RAM) 110 . Typically stored in ROM 106 is a basic input/output system (BIOS) 108 containing basic routines that facilitate the transfer of information between components within computer system 100 . Additionally, RAM 110 may contain an operating system (OS) 112, applications 114, other code 116 executable by one or more different programs, and programs 118. RAM 110 typically contains data and/or program modules that are immediately accessible by CPU 102 and/or are currently being operated on by CPU 102 .

The hard disk drive 120 can be a removable/non-removable computer media and a volatile/non-volatile computer media. The hard disk drive 120 can read from and write to the non-removable, non-volatile magnetic media and memory device 126 . Other removable/non-removable computer storage media and volatile/non-volatile computer storage media that may be used in the exemplary computer system 100 include, but are not limited to, magnetic tape cartridges, flash memory cards, digital versatile disks, digital video tapes , solid-state RAM and solid-state ROM. discussed above and illustrated in Figure 1 The discs and their associated computer media provide storage for computer readable instructions, programmable code, data structures, program modules, and other data for the computer system 100 . In FIG. 1 , a hard disk 120 is illustrated as storing an operating system (OS) 112 , one or more applications 114 , other programmable code 116 , and programs 118 .

The memory device 126 may be an optical disk drive or a magnetic disk drive that reads from or writes to a removable and non-volatile storage medium (eg, an optical disk or a magnetic disk).

A user may enter commands and information into the computer system 100 through an input device such as a keyboard and mouse, a trackball or touch pad, an electronic digitizer, or a microphone. Other input devices may include a joystick, game pad, satellite dish or scanner. These and other input devices may be connected to CPU 102 via an input interface coupled to bus 122 or via other interfaces or bus structures such as parallel ports, game ports, or universal serial bus (USB). A display (Graphical User Interface, GUI) 130 or other type of video device may also be connected to the bus 122 via an interface such as a video interface. In addition, an output device (such as a speaker or a printer) may be connected to the bus 122 via an output The interface is connected to the bus bar 122 .

Computer system 100 may be operated in a networked environment using network 128 and mobile device 136 . Mobile device 136 may be used by users who want to manipulate metadata incorporated in attachments of electronic files. The computer system 100 may also include a personal computer (PC), server, router, network PC, peer-to-peer device or other common network nodes. The mobile device 136 may include a handheld device, a tablet device, or a user end device. The network 128 shown in FIG. 1 may include a local area network (LAN), a wide area network (WAN), or other types of networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet. In a networked environment, programmable code and applications can be stored on remote computers. For example, FIG. 1 illustrates action commands 138 stored on mobile device 136 . It should be appreciated that the network connection shown is exemplary and other means of establishing communication between the computer and mobile device 136 may be used.

2 depicts a logic diagram of an exemplary system for manipulating metadata incorporated in attachments of electronic archives, consistent with disclosed embodiments. In various embodiments, the user device 202 may be the mobile device 136 or any other computing device, such as the computer system 100 of FIG. 1 . The user device 202 can be operatively coupled to one or more servers 208 via the network 206 .

Network 206 may be a suitable network, such as a local area network (LAN), wide area network (WAN), or other type of network. Web browser 204 may execute on computer 100 (as shown) or mobile device 136 (not shown), and web browser 204 may include functionality to receive data typed at user device 202, which is Part of a self-service tool consisting of several graphical user interfaces (GUIs). In general, the web browser 204 can be implemented using interpreted or executable software code (eg, core components, applications, scripts, libraries, objects containing methods, etc.). The particular implementation of web browser 204 is not intended to be limiting. Web browser 204 can be configured to display an interface, such as the interface described herein, to communicate with the disclosed system for manipulating metadata incorporated in attachments of electronic records. system to interact. Those skilled in the art should appreciate that additional interfaces may also be used to interact with the disclosed system.

Server 208 may be a suitable computer system or computing device, such as computer system 100 of FIG. 1 . In some instances, the server 208 may be a part of a cloud computing platform (eg, Microsoft Azure, etc.). In various examples, server 208 may be configured to host at least one of online self-service tool 212 or interface database 216 .

Interface database 216 may include creation interface 218 , editor interface 220 , upload interface 222 and download interface 224 . Creation interface 218 may enable user device 202 to create documents or files in interface database 216 , and editor interface 220 may enable a user to edit documents or files stored in interface database 216 . The upload interface 222 can enable the user device 202 to upload files or files in the interface database 216 , and the download interface 224 can enable the user device 202 to download files or files stored in the interface database 216 .

The interface database 216 may also include a plurality of save interfaces 226 and a plurality of preview interfaces 234 . The save interface 226 enables the user device 202 to save files or files in the interface database 216 , and the preview interface 234 enables the user device 202 to preview files or files stored in the interface database 216 . Other interfaces (not shown) displayed to the user device 202 and interacted with the online self-service tool 212 may be contemplated. Each of the interface and associated modules for displaying the interface may include suitable executable software code, such as a core component, application program, link library, object containing methods, or other type of executable software code. User device 202 may benefit from Use one or more of the interfaces to manipulate metadata.

FIG. 3A is an exemplary flowchart of a process 300 for manipulating metadata incorporated in attachments to electronic archives, consistent with disclosed embodiments. This exemplary method is provided as an example. The method 300 shown in FIG. 3A can be performed by the server 208 or otherwise implemented. For example, the method 300 described below can be implemented by the server 208 . Each block shown in FIG. 3A represents one or more procedures, methods, or subroutines in exemplary method 300 . Referring to FIG. 3A , example method 300 may begin at block 301 .

In step 301 , the server 208 may receive a request from the user device 202 to insert an attachment into a first file (eg, an electronic file). Although the user device 202 is mentioned in explaining the method of FIG. 3A , it should be noted that devices with similar capabilities and components of the computer system 100 may implement the method shown in FIG. 3A as appropriate. An attachment may include at least one definable attribute (metadata). The definable attributes set forth in more detail below with respect to FIG. 4 may set forth the information incorporated in the appendix. The user device 202 can use the web browser 204 displayed on the user device 202 to send a request to insert the attachment into the first file. For example, web browser 204 can provide a user interface for requesting insertion of an attachment, and user device 202 can configure controls implemented in the user interface to request insertion. The control may be in the form of a button that user device 202 may press or click to request insertion.

A user associated with the user device 202 can also use the web browser 204 displayed on the user device 202 to select the first file to be inserted as an attachment. In some embodiments, web browser 204 may enable user device 202 to select a first file. In another embodiment, web browser 204 may enable user device 202 to automatically The files stored in the interface database 216 select the first file.

In step 302, the server 208 may prepare an interface including one or more inputs for defining attributes. The attributes may include a Stock Keeping Unit (SKU) identification code (ID), a SKU name, a seller's item ID, or a seller's item name. An interface may include one or more elements for defining attachments and properties. Elements associated with attributes may include at least one of attribute names or data formats. Data formats can include strings, integers, floats, and characters. The one or more inputs correspond to the elements and are provided with blank input fields that can be defined by a user associated with user device 202 when typing data into the blank input fields. An exemplary interface including inputs for defining attachments and properties is illustrated in FIG. 4 and will be discussed in more detail.

In step 303 , the server 208 may respond to the request received from step 301 by presenting the user interface prepared in step 302 in the web browser 204 in the user device 202 . A user associated with the user device 202 may use the web browser 204 displayed on the user device 202 to define attributes by inputting elements corresponding to the elements included in the attribute in the user interface Type data into the fields. After defining the attributes by entering data on the user interface, the user device 202 may transmit the definable attributes to the server 208 . For example, a user associated with user device 202 may Controls implemented in the user interface are configured to send the defined properties to the server 208 . The controls may be in the form of buttons or selectable elements that a user can press or click to transmit defined properties.

In step 304 , the server 208 may receive the definable attributes transmitted from the user device 202 from the interface presented in step 303 . Exemplary definable attributes are depicted in Figure 5 and will be discussed in more detail. When definable attributes are received, the server 208 may implement an indicator for the received definable attributes. The indicator may indicate that the received definable attribute is linked or connected to the first profile selected in step 301 .

In some embodiments, the server 208 may enable the user device 202 to use the web browser 204 to edit the first file. The server 208 can provide the editor interface 220 to the user device 202, and the user device 202 can edit the first file intended to insert the attachment.

In some embodiments, server 208 may enable user device 202 to request insertion of data corresponding to received definable attributes by using controls implemented in editor interface 220 . For example, a user associated with user device 202 may configure controls implemented in editor interface 220 displayed on web browser 204 to request insertion of data after editing a file. Controls can be in the form of buttons or selectable elements that a user can press or click to request insertion. In another embodiment, the server 208 may enable the user device 202 to insert data without any request. For example, when the server 208 receives definable attributes in step 304, the server 208 can automatically convert the received The received definable attributes are treated as a request to insert data and the data structure is prepared in step 305.

In step 305, the server 208 may prepare a data structure including definable inputs corresponding to the received definable attributes. The data structure may include a spreadsheet, table, worksheet, grid, list, chart, array, hash, linked list, text file, or any suitable structure that enables the user device 202 to enter data to define one or more attributes. format. An exemplary profile structure including definable attributes is illustrated in FIG. 6 and discussed in more detail below.

In step 306 , the server 208 may respond to the received attributes by transmitting the prepared data structure to the user device 202 . In some embodiments, server 208 may enable user device 202 to define an input corresponding to a definable attribute by using web browser 204 to enter data into the input. For example, the server 208 may enable the user device 202 to define the input by providing the user device 202 with the editor interface 220 . In another embodiment, the server 208 may enable the user device 202 to define an input by enabling the user device 202 to download a data structure, define the input by typing data into the data structure, and The updated data structure is uploaded or transmitted to the server 208 . For example, the server 208 may provide the user device 202 with a download interface 224 for downloading data structures and an upload interface 222 for uploading updated data structures. FIG. 6 illustrates an exemplary data structure 600 including four attributes 601-604. The user device 202 may enter information via the web browser 204 in the user device 202 as indicated by the top row comprising attributes 601-604. material. In the exemplary data structure 600, six inputs are provided to the user device 202 for each attribute 601-604. Other numbers of inputs may be provided to the server 208 and the user device 202 may define other numbers of attributes by adding or subtracting the number of definable attributes using the interface prepared in step 303 .

In step 307 , the server 208 may receive the data structure from the user device 202 . When the server 208 receives the data structure, the server 208 may digitize the defined input incorporated in the data structure in step 308 based on the data format associated with the definable attributes. The server 208 may digitize the defined input by converting the defined input into a digital form that can be processed by a computer. For example, if the server 208 receives an attribute with a "SKU ID" attribute name and an integer data format in step 304 (as shown in the first row of FIG. 5 ) and further receives a data structure in step 307 Input "9925305" (as shown in the second column of the attachment 700 in FIG. 7 ), the server 208 can convert "9925305" into an integer. In another example, if the server 208 receives an attribute with a "SKU name" attribute name and a string data format in step 304 (as shown in the second column of FIG. 5 ) and further receives in step 307 To the defined input "ABC Block Car Set" in the data structure (as shown in the second column of the attachment 700 in FIG. 7), the server 208 can convert the "ABC Block Car Set" into a string.

The server 208 may also determine whether the defined input matches the data format before digitizing the defined input. If the server 208 determines that the defined input does not match the data format, in some embodiments, the server 208 may not digitize the defined input. For example, if the word "ABCDE" is defined to match the integer data format The input of the associated attribute, the server 208 may not convert "ABCDE" into a digital form, because "ABCDE" cannot be converted into an integer. In another embodiment, when the defined input does not match the data format, the server 208 may digitize a default data value associated with the corresponding attribute.

In some embodiments, if the received data structure includes undefined input, the server 208 may digitize the default data value. For example, if the default data value is 100 and the data format is an integer for undefined input, the server 208 may convert 100 to an integer.

In step 309 , server 208 may generate an attachment including the digitized input from step 308 . For example, server 208 generates exemplary attachment 700 (in table form) in which all inputs corresponding to attributes 701-704 are digitized based on the data format associated with the attributes.

In step 310, the server 208 may construct the electronic file by inserting the attachment generated from step 309 into the first file. For example, server 208 may insert the generated attachment by inserting at the end of the first file a link associated with the generated attachment that, when actuated, enables user device 202 to view the generated attachment. the above attachment. In another example, the server 208 can insert the generated attachment by appending it at the end of the first file. For another example, the server 208 can insert the generated attachment by embedding the generated attachment into the first file.

In step 311 , the server 208 may store the electronic file generated from step 310 in the interface database 216 . In some embodiments, server 208 may The generated electronic files are automatically stored in the interface database 216 . In another embodiment, the server 208 can enable the user device 202 to save the generated electronic file by providing the save interface 226 to the user device 202 . When all data incorporated in an attachment is digitized, the attachment and data can be easily retrieved by the user device 202 or another user device with access to the server 208 . Attachments can be inserted into another file. In step 312 , the server 208 may transmit the generated electronic file to the user device 202 .

4 illustrates an exemplary user interface 400 of a user device 202 displayed on a web browser 204 to define an attachment including one or more attributes, consistent with disclosed embodiments. Interface 400 may include inputs 401 and 402 , indicators 403 , buttons 404 and 405 . The exemplary user interface 400 is shown as defining a "trade-in" attachment that includes the attribute (metadata) of the SKU name, but those skilled in the art will appreciate that the user interface can be implemented to define other types of Attachments and properties.

The user can enter data in inputs 401 and 402 to define attachments. For example, as shown in FIG. 4 , the user may enter the attachment name "Sale-Sale Product" in input 401 and the display name "ABC Sale Product" in input 402 . Indicator 403 may provide the value type of the attachment. In some embodiments, the value type can be "single" or "multiple" and can be updated based on whether sub-attachments exist. For example, the indicator 403 may indicate that the value type of the attachment is multi when there is a sub-attachment, and further indicate that the value type of the attachment is single when there is no sub-attachment. The server 208 can take into account the value type to retrieve and use definable properties. For example, for attachments of distinct type In other words, the server 208 can use the properties defined by the interface 400 for the current attachment. In another example, for multi-valued attachments, the server 208 can retrieve and use the attributes contained in the sub-attachments.

User interface 400 can receive a press of button 404 to add a sub-accessory. When user interface 400 receives a press, user interface 400 may provide one or more inputs for defining sub-accessories. Adding sub-attachments assists in combining two different attachments into one. In some embodiments, the two attachments are stored in the interface database 216 . For example, there may be various types of attachments per contract, such as an attachment (Appendix A) including item ID and item name as attributes and another attachment (Appendix B) including discount rate and activity as attributes. The combination of Attachment A and Attachment B may be required to produce an Attachment (Appendix C) that includes attributes from both Attachment A and Attachment B. In such a case, Annex C may include Annexes A and B as sub-annexes. The attributes of Annex C can be defined again using definable attributes from each of Annex A and Annex B. Rather than redefining similar or frequently used attributes, attributes from other stored attachments can be reused. Attachment C includes two sub-attachments, so indicator 403 is updated to be many, and server 208 can retrieve and use definable attributes associated with the two sub-attachments (eg, Attachment A and Attachment B).

User interface 400 may receive a press of button 405 to add definable attribute 406 . The definable attributes 406, when defined by the user interface 400, can provide information associated with the first file. For example, if the first dossier is a sales contract for one or more products, an attachment to the sales contract may provide a list of products and may define Defined attributes may describe attributes of each of the products, such as SKU name, SKU ID, seller item name, seller item ID, and the like. When user interface 400 receives a press, the user interface may generate inputs 407 - 410 and button 411 to define attribute 406 . For example, as shown in FIG. 4 , the user can enter the attribute name "SKU name", the attribute display name "ABC SKU name", the data format "string" and the default value to define the attribute 406 . Attribute 406 may be deleted when button 411 is pressed. User interface 400 may receive a press of button 412 to transmit definable attribute 406 to server 208 as discussed above with respect to FIG. 3A .

FIG. 5 illustrates exemplary definable attributes 500 received from user interface 400 of FIG. 4 consistent with disclosed embodiments. The receipt of definable attributes is discussed above with respect to step 304 in FIG. 3A. The definable attribute 500 may include an identification code 501 , an attribute name 502 , a display name 503 , a data format 504 and a default value 505 . The server 208 can assign the identifier 501 to the definable attribute. For example, if the server 208 receives four definable attributes, the server 208 can assign four different identification codes to each of the four definable attributes. Once the server 208 assigns the ID 501, the server 208 can link or concatenate the attribute name 502, display name 503, data format 504, and default value 505 to each attribute's ID 501. The server 208 can link or connect the definable attribute 500 to the first file.

FIG. 6 illustrates an exemplary data structure 600 that includes each of the definable attributes 601-604 prepared by the server 208 in step 305 in FIG. 3A , consistent with the disclosed embodiments. The corresponding definable input (eg, blank box). As discussed above, the user can use the web browser 204 to download Load the data structure 600 to enter data into the blank boxes to define the inputs corresponding to the definable attributes.

FIG. 7 illustrates an example accessory 700 including attributes 701-704 incorporating digitized input. Each attribute 701-704 includes one or more inputs that were digitized in step 308 in FIG. 3B. As discussed above, attachment 700 may be stored in interface database 216 as part of step 311 (FIG. 3B), and attachment 700 may be retrieved or accessed by user device 202 or other users. Exemplary attachment 700 provides a list of products included in the "Trade in Products" attachment (defined in FIG. 4 ), where each of the products is set forth by SKU ID, SKU name, seller item ID, and seller item name.

Although the disclosure has been shown and described with reference to certain embodiments thereof, it should be understood that the disclosure may be practiced in other environments without modification. The foregoing description has been presented for purposes of illustration. The above description is not exhaustive and is not limited to the precise forms or embodiments disclosed. Various modifications and adaptations will be apparent to those skilled in the art after consideration of the description and practice of the disclosed embodiments. Additionally, although aspects of the disclosed embodiments are described as being stored in memory, those skilled in the art will understand that such aspects can also be stored on other types of computer-readable media, such as secondary storage devices (For example, on a hard disk or CD ROM or other form of RAM or ROM, USB media, DVD, Blu-ray or other optical drive media.

Computer programs based on the written description and disclosed methods are within the skill of an experienced developer. Various programs or program modules may be created using any technique known to those skilled in the art, or various programs or program modules may be designed in conjunction with existing software Program mods. For example, .Net Framework, .Net Compact Framework (and related languages, such as Visual Basic, C, etc.), Java, C++, Objective-C, HTML, HTML/AJAX combination, XML or including Java applets HTML to design program sections or program modules.

Furthermore, while illustrative embodiments have been described herein, those skilled in the art will recognize, based on this disclosure, that there are equivalent elements, modifications, omissions, combinations (eg, combinations of aspects between various embodiments), scope of any and all embodiments adapted and/or altered. Limitations in claims should be interpreted broadly based on the language employed in claims and not limited to the examples set forth in this specification or set forth during the prosecution of the claim. Said examples should be considered non-exclusive. Furthermore, the steps of the disclosed methods may be modified in any way, including by reordering steps and/or inserting or deleting steps. It is therefore intended that the specification and examples be considered as illustrative only, with a true scope and spirit being indicated by the following claims and their full range of equivalents.

100: computer system/system/computer

102: Central processing unit (CPU) or processor

104: memory unit/memory

106: Read-only memory (ROM)

108: Basic Input/Output System (BIOS)

110: Random Access Memory (RAM)

112: Operating system (OS)

114: Application

116:Code/programmable code

118: program

120: Hard disk drive/hard disk

122: busbar

126: memory device

128: Network

130: Display

136:Mobile device

138: action command

Claims (20)

A computer-implemented system for digitizing attachment data, comprising: one or more memory devices storing instructions; and one or more processors configured to execute the instructions to perform operations comprising: receiving from a user device a request to insert an attachment into a text file, the attachment including at least one definable attribute; preparing an interface, the interface including one or more inputs for defining the at least one definable attribute, the at least one definable attribute defining attributes including attribute names and data formats; responding to the received request by presenting the interface in a web browser in the user device; receiving the at least one definable properties; preparing a data structure including definable inputs corresponding to the received at least one definable property; and processing the received at least one definable property by transmitting the data structure to the user device responding with a definable attribute; receiving the data structure from the user device; converting the definable input into a default data type based on the data format associated with the at least one definable attribute; and digitizing the definable input by determining that the definable input is not in the same format as the data format; generating a table wherein input is digitized based on a data format associated with the definable attribute; generating a link to the table; and generating an electronic file by appending the link to the end of the text file . The computer-implemented system as claimed in claim 1, wherein the at least one definable attribute further includes at least one of a display name or a default data value. The computer-implemented system of claim 2, wherein when the received data structure does not define the at least one definable attribute, the default data value is digitized into the definable input. The computer-implemented system as claimed in claim 1, wherein the at least one definable attribute is at least one of product name, SKU ID, SKU name, vendor item ID, or vendor item name. The computer-implemented system as claimed in claim 1, wherein the operations further include: storing the generated electronic file and transmitting the generated electronic file to the user device. The computer-implemented system as claimed in claim 1, wherein said interface prepared includes a selectable element for adding a new attribute and a selectable element for deleting said at least one definable attribute. The computer-implemented system of claim 1, wherein the data structure is an array, hash, linked list, text file or table. The computer-implemented system as claimed in claim 1, wherein the operation is more It includes judging whether the definable input matches the data format before digitizing the definable input. The computer-implemented system as claimed in claim 1, wherein the user device is a computer or a mobile device. The computer-implemented system as claimed in claim 1, wherein the data format includes string, integer, floating point and character. A method for digitizing attachment data, comprising: receiving a request from a user device to insert an attachment into a text file, the attachment including at least one definable attribute; one or more inputs for defining a definable attribute, the at least one definable attribute including attribute name and data format; and responding to the received input by rendering the interface in a web browser in the user device Respond to the request; receive the at least one definable attribute from the interface; prepare a data structure including definable inputs corresponding to the received at least one definable attribute; transmitting the data structure to the user device in response to receiving the at least one definable attribute; receiving the data structure from the user device; by The data format converts the definable input into a default capital type and by determining the definable input digitizing the definable input if the input is not in the same format as the data format; generating a table in which the input is digitized based on the data format associated with the definable attribute; generating a link to the table; and An electronic file is generated by appending the link to the end of the text file. The method according to claim 11, wherein the at least one definable attribute further includes at least one of a display name or a default data value. The method of claim 12, wherein when the received data structure does not define the at least one definable attribute, the default data value is digitized into the definable input. The method according to claim 11 further includes: storing the generated electronic file and sending the generated electronic file to the user device. The method as claimed in claim 11, wherein said interface prepared includes selectable elements for adding new attributes and selectable elements for deleting said at least one definable attribute. The method of claim 11, wherein the data structure is an array, hash, linked list, structured text file or table. The method according to claim 11, further comprising determining whether the definable input matches the data format before digitizing the definable input. The method as claimed in claim 11, wherein the user device is a computer or a mobile device. The method according to claim 11, wherein the data format includes string, integer, floating point and character. A computer-implemented system for digitizing attached data, comprising: a database; one or more memory devices storing instructions; and one or more processors configured to execute the instructions to perform operations comprising: receiving a request from a first user device to insert an attachment into a text file, the attachment including at least one definable attribute; preparing an interface including one or more elements for defining the at least one definable attribute input, the at least one definable attribute includes an attribute name and a data format; responding to the received request by presenting the interface in a web browser in the first user device; from the The interface receives the at least one definable attribute; prepares a data structure including definable inputs corresponding to the received at least one definable attribute; by sending the data structure to the first The user device responds to the received at least one definable attribute; receiving the data structure from the first user device; by converting the definable input into a default data type based on the data format associated with the at least one definable attribute and by determining the digitizing the definable input is not in the same format as the data format; generating a table in which the input is digitized based on the data format associated with the definable attribute; generating a link to the table ; generating an electronic file by appending the link to the end of the text file; storing the attachment in the database; receiving a request to access the stored attachment from a second user device ; retrieving the stored attachment from the database; and transmitting the retrieved attachment to the second user device.

Images