KR101865906B1 - Method and program for providing updated information - Google Patents

Abstract

The present invention relates to an updated publication information providing method and program.
According to an embodiment of the present invention, there is provided an updated method of providing a posting information, the method comprising: displaying a plurality of card data groups included in a specific board by a service server, the card data including data representing posting information in a specific format , And the board is a page for displaying one or more card data groups in a list (S200); Receiving an update request for a specific card data group from a user client (S400); Generating correction card data with the correction data received according to the update request (S600); And a step (S800) of accumulating the modified card data in the card data group on the existing card data and creating a screen so that only the modified card data is displayed to the user client.

Description

METHOD AND PROGRAM FOR PROVIDING UPDATED INFORMATION [0002]

More particularly, the present invention relates to a method and a program for providing a revision history while providing only the latest information when the post information is revised.

Recently, a plurality of services (e.g., collaborative services, etc.) sharing posting information among a plurality of users have appeared. In such a posting information sharing service (that is, the bulletin board service), when a change occurs, the existing posting is directly modified, and the new posting is written as "correction".

However, there is a problem that it is difficult to check what has changed in the existing posting even if the modification is indicated in the existing posting. In addition, there is a problem in that, when a new post is input with the modified contents, a connection relation with an existing post is not generated, and a user reading a new post is difficult to understand.

Therefore, in the case where a post is updated, there is a need for a method that allows the user to accurately recognize the latest information and easily grasp the change history.

Korean Patent No. 10-1368680 (February 24, 2014)

The present invention provides an updated publication information providing method and a program for providing updated latest information only to a user as it exposes only the latest information on the screen by accumulating the card data including the modified publication information in the existing card data do.

The problems to be solved by the present invention are not limited to the above-mentioned problems, and other problems which are not mentioned can be clearly understood by those skilled in the art from the following description.

According to an embodiment of the present invention, there is provided an updated method of providing a posting information, the method comprising: displaying a plurality of card data groups included in a specific board by a service server, the card data including data representing posting information in a specific format And the board is a page that lists and displays one or more card data groups; Receiving an update request for a specific card data group from a user client; Generating correction card data with the correction data received according to the update request; And accumulating correction card data in the card data group on the existing card data to generate a screen so that only the correction card data is displayed to the user client, wherein the card data group includes at least one card And is formed by adding or modifying the card data as an accumulated group of data.

In another embodiment, the service server receives a request to provide a history of a specific group of card data from a user client; And arranging a plurality of card data accumulated in the card data group or providing a correction history in chronological order.

According to another embodiment, a card data group in which a plurality of card data is accumulated is characterized in that an image in which a plurality of card data are stacked is displayed and displayed on a board.

According to another embodiment of the present invention, the modified card data generation step may include storing the comment data input to the existing card data in correspondence with the existing card data, and providing the modified card data in a state in which the comment data is not included .

According to another embodiment of the present invention, when receiving a request to merge a specific first card data group with a second card data group, the first card data group and the second card data group are accumulated to form a stack, And merging the group of the card data.

In addition, in another embodiment, upon receiving a separation request for one or more specific card data in the card data group from the user client, the service server separates one or more card data to generate a separate card data group, The method comprising the steps of:

According to another embodiment of the present invention, the update request receiving step receives a request to add a label to a specific card data group from a specific user, and the modified card data generating step stores information corresponding to the label in the card data The card data group is displayed on a separate board corresponding to the label in a format corresponding to the separate board, and information necessary for displaying the label on a separate board is input And a separate board displaying step, which is a part for performing a separate board display.

In another embodiment, the service server further includes dividing the data corresponding to the card data group into a plurality of data and distributing the data in the cloud storage space of the accounts held by the users in the group.

According to another embodiment, the distributed storage step may include generating a plurality of divided data for each card data in the card data group, separating the file data included in the card data from the card configuration data, And the card configuration data includes information on the tag information on the file data and information on the arrangement of the file data connected through the tag information on the card.

The updated posting information providing program according to another embodiment of the present invention is combined with hardware to execute the above-mentioned updated posting information providing method, and is stored in the medium.

According to the present invention as described above, the following various effects are obtained.

First, the user can check only the updated information through the board, so that the user can not be confused with the information before the modification.

Second, the user can easily check the history of change of the publication information.

Third, at the time of editing the posting information (that is, the card data), existing comments are also matched with the existing posting information, and the comment is provided in the corrected card data in the initialized state. It is possible to prevent confusing users who check.

Fourth, through the simple merge of the card data group, users can easily leave only the remaining task or posting information that should be continuously announced, so that only the information necessary for a plurality of users can be displayed on the board and delivered.

1 is a flowchart of a method of providing updated posting information according to an embodiment of the present invention.
2 is an exemplary diagram of a board in which card data and card data groups are displayed according to an embodiment of the present invention.
3 is an exemplary diagram illustrating a stacked image according to an embodiment of the present invention, in which a card data group includes a plurality of card data.
4 is a flowchart illustrating a method of providing updated posting information that further includes providing a revision history according to an embodiment of the present invention.
5 is an exemplary view of an interface screen providing a modification history according to an embodiment of the present invention.
FIG. 6 is a flowchart of an updated method of providing a posting information, which further includes merging a plurality of card data groups according to an embodiment of the present invention.
FIG. 7 is an exemplary diagram for performing card data group merging through drag and drop of an image of a card data group displayed on a board according to an embodiment of the present invention.
FIG. 8 is a flowchart illustrating an updated method of providing broadcast information, which further includes the step of separating one or more card data in a specific card data group according to an embodiment of the present invention to generate a separate card data group.
FIG. 9 is a flowchart illustrating an updated method for providing posting information, which further includes connecting card data to a separate board using a label according to an exemplary embodiment of the present invention.
10 and 11 are flowcharts of an updated method of providing broadcast information, which further includes distributing one or more pieces of card data to a plurality of cloud storages according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention, and the manner of achieving them, will be apparent from and elucidated with reference to the embodiments described hereinafter in conjunction with the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. To fully disclose the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

Unless defined otherwise, all terms (including technical and scientific terms) used herein may be used in a sense commonly understood by one of ordinary skill in the art to which this invention belongs. Also, commonly used predefined terms are not ideally or excessively interpreted unless explicitly defined otherwise.

The terminology used herein is for the purpose of illustrating embodiments and is not intended to be limiting of the present invention. In the present specification, the singular form includes plural forms unless otherwise specified in the specification. The terms " comprises "and / or" comprising "used in the specification do not exclude the presence or addition of one or more other elements in addition to the stated element.

In this specification, 'card data' means a user interface that displays the publication information inputted in the service in a specific format. The 'card data' may have a different format depending on the situation (for example, the type of board on which the card data is displayed) that should display the publication information.

In this specification, 'card data group' means a group formed by accumulating one or more card data. That is, the 'card data group' is a group in which one or more pieces of card data for specific publication information are accumulated. The 'card data group' may accumulate card data for one publication information, or may accumulate card data for a plurality of publication information.

In the present specification, 'new card data' means card data that is newly input. A new card data group can be generated as new card data is input.

In the present specification, 'correction card data' refers to card data added as the existing card data included in a specific card data group is modified.

In this specification, 'board' means an interface in which one or more card data groups are arranged and displayed.

Hereinafter, an updated publication information providing method and program according to embodiments of the present invention will be described with reference to the drawings.

1 is a flowchart of a method of providing updated posting information according to an embodiment of the present invention.

Referring to FIG. 1, an updated publication information providing method according to an embodiment of the present invention includes displaying a plurality of card data groups 100 included in a specific board (S200; card data display step) ; Receiving an update request for a specific card data group 100 from a user client (S400); Generating correction card data with the correction data received according to the update request (S600); And accumulating the modified card data in the card data group 100 on the existing card data, and creating a screen so that only the modified card data is displayed to the user client (S800). Hereinafter, a detailed description of each step will be described.

The service server displays a plurality of card data groups 100 included in a specific board (S200: card data display step). The card data 200 is data in which the publication information is displayed in a specific format in each board, and the board is a page that lists and displays one or more card data groups 100. That is, as shown in FIG. 2, the service server sequentially displays the card data groups 100, which are the publication information for a specific group, on the board. The service server can display the card data groups 100 in the order in which they are created or updated, and can display the card data groups 100 in a predetermined order of publication.

In one embodiment, the card data group 100 is formed by adding or modifying the card data 200 as an accumulated group of one or more card data 200 for specific publication information. The card data 200 may be additionally formed in a specific card data group 100 in various ways. For example, new card data 200 is generated as a specific user newly inputs the publication information to initially form the card data group 100. Also, as described later, correction card data can be added in the card data group 100 as the user modifies the specific card data 200. [ 7, the service server receives a merge request of a plurality of card data groups 100 from the user (for example, the third card data group 100 is divided into the first card data group 100 100) to the specific card data group 100 by adding all the cards of the third card data group 100 to the first card data group 100 by performing the drag and drop with respect to the specific card data group 100 The card data 200 can be added.

The service server receives an update request for a specific card data group 100 from the user client (S400). That is, in order to modify the publication information included in the specific card data group 100, the service server receives the update request from the user client and receives data (that is, correction data) for correcting the existing publication information from the user client . The service server may receive the entire modified posting information or only the data for the modified part in the existing posting information.

The service server generates correction card data with the correction data received according to the update request (S600). At this time, the service server may match the existing comment data inputted to the existing card data (that is, the existing publication information) with the existing card data, and store the modified card data in a state in which the comment data is not included. When the posting information is modified but the comment data remains intact, users who check the modified posting information may be confused because of the conflict between the modified posting information (i.e., the correction data) and the existing comment contents. Matches the existing comment data with the existing card data, stores the corrected card data in which the comment is initialized, and receives a new comment on the corrected card data.

The existing comment data can be confirmed at the time of checking existing card data while confirming the history of the card data 200 included in the card data group 100 as described later. That is, when the service server lists the accumulated card data 200 in response to a history provision request for the card data group 100, the service server can display the existing comment data inputted for each card data 200 .

The service server accumulates the correction card data in the card data group 100 on the existing card data, and creates a screen so that only the correction card data is displayed to the user client (S800). That is, the service server displays the modified card data on the screen without displaying the existing card data on the board. As shown in FIG. 3, the card data group 100 in which a plurality of card data 200 are accumulated can be displayed on the board by generating an image in which a plurality of card data 200 are stacked. The user can recognize that the card data 200 displayed on the current screen is modified through the stacked image. The service server displays only the correction card data on the screen and does not display the existing card data, so that the user can be provided with only the latest data to provide accurate information.

In another embodiment, as shown in FIG. 4, the service server receives (S1000) a request to provide a history for a specific card data group 100 from a user client; And a step (S1200) of arranging a plurality of card data 200 accumulated in the card data group 100 or providing a correction history in chronological order. The user may want to check the posting information prior to the correction card data and may want to compare what has been changed with the existing posting information. Accordingly, the service server receives a request for providing a history for a specific card data group 100 from the user (S1000), searches for and provides a plurality of card data 200 included in the card data group 100 (S1200) .

The service server can display the revision history in various ways. In one embodiment, the service server can display a plurality of card data 200 pertaining to the card data group 100 in chronological order. 5, the service server may sequentially display the revision histories of the card data 200 belonging to the card data group 100. In this case, For example, as shown in FIG. 5, the service server uploads the most-recently-uploaded correction card data, and displays the modified user and correction items in chronological order by the correction history of each card data 200, respectively.

In this case, when a specific user (for example, a user corresponding to the administrator) wants to return the card data 200 before the correction, the service server returns the card data 200 at the time point selected by the user .

6, when receiving a request to merge a specific first card data group 100 with a second card data group 100, the first card data group 100 and the second card data group 100 are merged, (S1400) merging the first and second card data groups 100 into one stack and providing the second card data groups 100 as one stack. The service server can receive a merge request of the card data group 100 from the user in various ways. In one embodiment, the service server may select a plurality of card data groups 100 to be merged by providing the in-board card data group 100 setting page to the user client. 7, the service server stores the specific card data group 100 (the third card data group 100 in Fig. 7) to another card data group 100 (the first card data group 100 in Fig. 7) (Drag & Drop) to the mobile terminal 100 to receive the merge request.

At this time, the service server can accumulate a plurality of card data groups 100 requested to be merged in various orders. In one embodiment, the service server may merge the card data 200 in the plurality of card data groups 100 requested to be merged in the order of time in which the card data 200 are created. Thereby, the user can select a plurality of card data 200 (that is, the first card data group 100 and the third card data group 100) included in the merged card data group 100 (i.e., the first card data group 100 and the third card data group 100 in FIG. 7) It is possible to confirm the card data 200 created in the first place and the plurality of correction card data generated in accordance with a plurality of modifications) in the created order.

In another embodiment, the service server stacks or accumulates the card data 200 in accordance with the operation type input from the user. For example, the card data group 100 (i.e., the third card data group 100) specified by the user may be grouped into another card data group 100 (i.e., , The service server loads the plurality of cards (100) of the third card data group (100) onto the plurality of card data (200) of the first card data group (100) The data 200 can be stacked. In this way, the service server exposes the latest modification card data of the third card data group 100 displayed on the top in accordance with the stacking of the card data 200 on the board. As another example, when the folder concept is applied to the card data group 100 and the service server drags and drops the third card data group 100 into the first card data group 100 as shown in FIG. 7, The latest modification card data of the first card data group 100 is exposed on the board as the plurality of card data 200 included in the group 100 is absorbed by the first card data group 100. [

8, when the service server receives the one or more card data 200 from the user client by receiving a separation request for the specific one or more card data 200 in the card data group 100, (S1600) of generating a separate card data group 100 and displaying it on the board. For example, when a user desires to separate a specific one or more card data 200 and create a separate card data group 100, the user may select one or more card data The user can select the card data group 200 and drag it to the outside to request creation of another card data group 100. The service server extracts the card data 200 requested to be generated by the user from the separate card data group 100 and generates an image of the separate card data group 100 on the board. The service server does not display a stacked image when only one card data 200 is requested to be separated and displays a stacked image on one side of the image of the card data group 100 when a separation request is received for a plurality of the card data 200 Can be displayed.

Further, in another embodiment, the service server may add new information through addition of a label in the card data 200. [ The label is an interface assigned to input specific information in the card data 200. [ More specifically, in the method of adding a label in the card data 200, the update request receiving step (S400) receives a request to add a label to a specific card data group (100) from a specific user, Step S600 generates modified card data in which the information corresponding to the label is added to the card data 200. [

According to another embodiment, the card data group 100 may be displayed on a separate board corresponding to the label in a format corresponding to the separate board, (S1800), which is a part of the display screen. The label may be used to transfer specific card data 200 of a basic board (for example, a board that simply lists card data group 100 corresponding to the publication information) to another expansion board (for example, Board) to form a connection relationship. When a new label is added to the card data 200 by the user, the service server can display the corresponding card data 200 in the extension board corresponding to the label. For example, when a certain label of the publication information in the card data 200 is added to the specific card data 200, the service server stores the card data 200 in an extension board for performing a calendar function or a calendar function And displays the publication information in the card data 200 of the corresponding format.

In another embodiment, the service server further includes a step S2000 of dividing the data corresponding to the card data group 100 into a plurality of data and distributing the data in the cloud storage space of the accounts held by the users in the group (S2000) . For example, the service server divides the individual card data included in the card data group into a plurality of divided data (i.e., generates a plurality of divided data for each card data in the card data group) . That is, when the correction data is generated as the specific card data group is modified, the service server divides the correction data corresponding to the accumulated one card into a plurality of divided data and distributes the data in a plurality of cloud storage spaces.

In one embodiment, each card data may include file data such as images, moving images, and text, and the service server may separately store and separately store the card configuration data and the file data. That is, the service server generates a plurality of pieces of file data (for example, data of images, moving images, etc.) included in the correction data (that is, the card data updated and added) and distributes the data to the respective cloud storage spaces And generates card configuration data as a plurality of pieces of divided data and stores them in the respective cloud storage spaces. The service server can link the file data to the card data specified by the tag information.

Specifically, the card configuration data may correspond to a card data UI image displayed on a user client screen or an information arrangement structure for card data configuration. For example, the card configuration data may include tag information for file data that is divided and stored in a plurality of cloud accounts, and may include information about placement of file data connected through the tag information.

11, the distributed storage step S2000 includes a step (S2010) of requesting the service server to access each of the cloud servers by the user and perform log-in, in a specific manner of distributing the card data 200, ; Receiving token data from the cloud server (S2020; token data receiving step); And storing the plurality of divided data generated by dividing the service internal data inputted on the online into the cloud storage of the users included in the group (S2030: internal data storing step).

The service server requests the user to access each of the cloud servers and perform login (S2010). In one embodiment, the service server directly receives the ID and the password of the cloud service from the user, transmits the ID and password to the cloud server, and proceeds to log in. That is, the service server receives one or more cloud account information from one or more users (e.g., a plurality of users included in the group if the service is a service storing information of a specific group), and transmits the cloud account information from each user to the requested cloud server Account information can be transmitted.

In another embodiment of the method of performing login to each cloud service by the user, the service server connects and connects the login page of each cloud service according to the request of the user's cloud account login on the service application screen or the service web page screen can do. Then, the account information (i.e., ID and password) input by each user is directly transmitted to the cloud server without being stored in the service server. To this end, the service server may include a third party client application programming interface (API) that provides each cloud service accessible from another service.

In an embodiment, when a plurality of users use a service as a group, the service server receives one or more cloud accounts held by each user from a plurality of users. For example, in the case of providing a collaboration service between a plurality of users, in order to form a storage space for storing group data to be shared by a plurality of users or data input in the service, The above cloud accounts are available. The storage spaces of a plurality of cloud accounts provided from the respective users are combined and used as a space for storing information when a service is provided.

The service server receives and stores the token data from the cloud server (S2020; token data receiving step). The token data allows the service server to access the cloud storage space of a specific user. The service server can access to the storage space corresponding to each account in the cloud server without storing the account information of each cloud account by receiving and storing the token data corresponding to the account information of each user. In this way, the service server stores token data corresponding to the number of connected cloud accounts.

The token data provided by the cloud server may, in one embodiment, be authorized to access the entire directory of accounts provided to the service server. Further, in another embodiment, it may be authorized to access only the directory where data of a specific service is stored. For example, the token data may be set to be accessible only to a specific directory in which the partition data generated by the service server is stored, as described later. The range of account storage space accessible by the token data may be determined according to the cloud service settings or user settings.

The service server divides and stores the plurality of divided data generated by dividing the service internal data inputted on the online into the cloud storage of the users included in the group (S2030: service internal data storing step). The service internal data is data input in the service, and may correspond to the card data 200 corresponding to the posting information input and modified by the user. The service server transmits the divided data to each user's cloud account based on the token data for the plurality of cloud accounts. For example, when a plurality of users, such as a collaborative service, uploads service internal data (for example, a file or a post to be shared among a plurality of users) in a group space provided on-line, It is possible to divide the uploaded service internal data into a plurality of divided data and to distribute the divided data to each of the cloud accounts.

The service server can divide the service internal data in various ways and transmit it to the storage space corresponding to each account. In one embodiment of the method of dividing the service internal data, the service server can compress (i.e., divide and compress) specific internal data of the service. Specifically, the service server performs a primary encryption by compressing the service internal data, and performs a secondary encryption for dividing the data into a specific number of files to generate a plurality of divided data. In another embodiment, the service server divides specific service internal data into a plurality of detailed data, and compresses the detailed data to generate divided data. This makes it impossible to confirm the information contained in the service internal data even if the divided data stored in the cloud account of a specific user is leaked by hacking or the like.

In another embodiment, when only one partition data for a specific service internal data is generated in the service internal data storage step (S2030), if the partition data included in a specific cloud account is lost, the service internal data is restored The service server generates and distributes the same divided data in a redundant manner. Specifically, the step of duplicating the service internal data to generate the first service internal data and the second service internal data, Generating the same first division data and a plurality of second division data by applying the same division method to the first service internal data and the second service internal data; And distributing and storing the same data in the plurality of first divided data and the plurality of second divided data such that the types of users or cloud services do not overlap each other.

The service server duplicates the service internal data and generates the first service internal data and the second service internal data. That is, the service server replicates specific service internal data uploaded by the user and generates two copies of the service internal data. For example, the service server can set the original data uploaded by the user as internal data of the first service, and the replicated data replicated to the original data as the internal data of the second service.

Thereafter, the service server applies the same division method to the first service internal data and the second service internal data to generate a plurality of identical first divided data and a plurality of second divided data. That is, the service server applies the same partitioning scheme (for example, the same compression scheme and the same partitioning data size) so that the first partitioned data and the second partitioned data form a specific pair. Accordingly, even if one of the first divided data and the second divided data constituting a pair is lost, it can be restored using the pair data (divided data constituting a pair).

Thereafter, the service server divides and distributes the same data in the plurality of first divided data and the plurality of second divided data so that the types of users or cloud services do not overlap. If the user or the divided data pair that is paired with the account having the same cloud service type is stored, the pair data can be lost simultaneously due to the departure / withdrawal of the user or the service termination / server down of the cloud service. Accordingly, the first divided data and the second divided data are distributed and stored in an account in which the types of users or cloud services do not overlap.

As described above, the updated publication information providing method according to an embodiment of the present invention may be implemented as a program (or application) to be executed in combination with a computer as hardware and stored in a medium.

The above-described program may be stored in a computer-readable medium such as C, C ++, JAVA, machine language, or the like that can be read by the processor (CPU) of the computer through the device interface of the computer, And may include a code encoded in a computer language of the computer. Such code may include a functional code related to a function or the like that defines necessary functions for executing the above methods, and includes a control code related to an execution procedure necessary for the processor of the computer to execute the functions in a predetermined procedure can do. Further, such code may further include memory reference related code as to whether the additional information or media needed to cause the processor of the computer to execute the functions should be referred to at any location (address) of the internal or external memory of the computer have. Also, when the processor of the computer needs to communicate with any other computer or server that is remote to execute the functions, the code may be communicated to any other computer or server remotely using the communication module of the computer A communication-related code for determining whether to communicate, what information or media should be transmitted or received during communication, and the like.

The medium to be stored is not a medium for storing data for a short time such as a register, a cache, a memory, etc., but means a medium that semi-permanently stores data and is capable of being read by a device. Specifically, examples of the medium to be stored include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like, but are not limited thereto. That is, the program may be stored in various recording media on various servers to which the computer can access, or on various recording media on the user's computer. In addition, the medium may be distributed to a network-connected computer system so that computer-readable codes may be stored in a distributed manner.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, You will understand. Therefore, it should be understood that the above-described embodiments are illustrative in all aspects and not restrictive.

100: Card data group 200: Card data

Claims (10)

The service server displays a plurality of card data groups included in a specific board, wherein the card data is data in which the publishing information is displayed in a specific format in each board, and the board is a page that lists and displays one or more card data groups A card data display step of displaying the card data;
Receiving an update request for a specific card data group from a user client;
Generating correction card data with the correction data received according to the update request;
And accumulating the modified card data on the existing card data in the card data group so that only the modified card data is displayed on the user client,
Wherein the card data group is formed by adding or modifying the card data as a cumulative group of one or more card data for specific publication information,
Wherein the correction card data is displayed at the top of the sequentially accumulated card data group so that the history can be confirmed. The method according to claim 1,
The service server receiving a request to provide a history of a specific card data group from a user client; And
Further comprising the steps of: listing a plurality of card data accumulated in said card data group or providing correction history in chronological order; The method according to claim 1,
Wherein the card data group in which a plurality of card data are accumulated generates an image in which a plurality of card data are piled up and displays the created image on the board. The method according to claim 1,
The modified card data generation step includes:
Wherein the comment data inputted to the existing card data is matched with the existing card data and stored, and the modified card data is provided without comment data. The method according to claim 1,
When a request for merging a specific first card data group with a second card data group is received, the first card data group and the second card data group are stacked and formed into one stack and provided; ≪ / RTI > The method according to claim 1,
Further comprising the step of separating one or more card data and creating a separate card data group and displaying it on the board when the service server receives a separation request for a specific one or more card data in the card data group from the user client , How to provide updated posting information. The method according to claim 1,
Wherein the update request receiving step comprises:
Receiving a request to add a label to a specific card data group from a specific user,
The modified card data generation step includes:
And generates correction card data in which information corresponding to the label is added to the card data,
And displaying the card data group on a separate board corresponding to the label in a format corresponding to the separate board, wherein the label is a part for inputting information necessary for displaying on a separate board To provide updated posting information. The method according to claim 1,
The service server further dividing the data corresponding to the card data group into a plurality of pieces and distributing the divided pieces of data in the cloud storage space of the account held by the users in the group. 9. The method of claim 8,
In the distributed storage step,
Generating a plurality of divided data for each card data in the card data group,
The file data included in the card data is separated from the card configuration data, and is generated as a plurality of divided data and distributedly stored in each of the cloud storage spaces.
Wherein the card configuration data includes tag information for the file data and information about placement of file data connected through the tag information on a card. A computer-implemented updated publication information providing program, coupled to a computer, the computer being hardware, for executing the method of any one of claims 1 to 9.

Images