KR20180133815A - Method and program for providing coworking service - Google Patents

Abstract

The present invention relates to a method for providing a collaboration service and a program thereof. According to an embodiment of the present invention, the method of providing a collaboration service comprises: a step (S200) of creating, by the service server, a project corresponding to the collaboration group; a step of receiving card data from a user client on a main board in the project (S400, card data receiving step); a step of receiving a label input request in the card data (S600, label input request step); a step (S800) of connecting the card data to an expansion board corresponding to the label; and a step (S1000) of displaying card data connected to the expansion board by a specific label.

Description

METHOD AND PROGRAM FOR PROVIDING COWORKING SERVICE [0002]

The present invention relates to a method and a program for providing a collaboration service, and more particularly, to a method and a program for providing a collaboration function in accordance with each industry group.

With the proliferation of smart devices such as smartphones and smart pads, EMS (Enterprise Mobility Service, enterprise mobile service) environments that can work in conjunction with enterprise legacy systems are spreading.

The enterprise-type mobile service environment enables quick and accurate field management of various enterprises, thereby improving the work efficiency and eliminating the time and cost wastage factor. Especially, the utilization in the business sales or production line is highlighted Trend.

In the meantime, there is an increasing tendency to work through collaborative work among various business participants inside and outside the company. In view of this, it is necessary to provide functions considering collaborations in the enterprise mobile service environment and various functions for efficient generation of collaborative products Has come.

However, in the existing enterprise mobile service environment, it is common to provide data input and display functions using general mobile web browsers or business applications, thereby enabling effective information exchange between internal and external business participants , And collaborative environment in which work products through collaborations can be easily provided in the form of electronic documents.

In addition, collaborative services that are commonly used in addition to collaborative services developed for specific companies are emerging. However, since the user interface of the collaboration service is fixed, there is a problem that it does not reflect characteristics that are different in each industry group.

The present invention provides a method and program for providing a collaborative service that provides an information providing page (i.e., a board) suitable for each industry group and allows the information providing page to be easily created so that the collaboration service can be used in accordance with each industry group 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.

A method of providing a collaboration service according to an exemplary embodiment of the present invention includes: generating a project corresponding to a collaboration group by a service server; Receiving card data from a user client on a main board in the project to generate a basic card, the card data being information input in a project; A label input request step of receiving a label input request in the card data; Connecting the card data to an expansion board corresponding to the label; And displaying card data connected to the expansion board by a specific label, wherein the expansion board is a specific type of board used for each situation or industry group.

According to another embodiment of the present invention, the card data display step displays an expansion card modified in a format corresponding to the extension board corresponding to the label.

Further, in another embodiment, the project includes one or more spaces, and the spaces correspond to one or more subgroups in the collaboration group.

According to another aspect of the present invention, there is provided a method for providing a new skin to a user, the method comprising the steps of: receiving, by a user included in the collaboration group, Wherein the purchase of the new skin is performed through a market in the collaboration service.

According to another embodiment, the expansion board is generated based on a form used in a specific field, and an expansion card included in the expansion board includes information to be displayed on the expansion board, Only in a specific format.

According to another embodiment of the present invention, there is further provided a method of displaying modified card data modified in one or more extension boards, when card data specific to the main board or the expansion board is modified by a specific user in the collaboration group , The main board and the extension board display the same information according to the board type in different types of basic card data and expansion card data.

According to another embodiment of the present invention, the card data includes related user information as a label on the corresponding card, and when the card data is modified, the card information is provided only to the user included in the related information.

In addition, in another embodiment, when the collaboration service is used for movie shooting, the base card is generated for each scene included in the scenario, the expansion board corresponds to a shooting schedule table, The expansion card is a card that is generated by merging a plurality of basic cards having a specific date set as a shooting schedule on a certain label, and the order number is given in the order of shooting date.

According to another embodiment, the card data receiving step receives a division request for scenario data and generates a basic card corresponding to each scene.

An updated published information providing program according to another embodiment of the present invention is combined with hardware to execute the above-mentioned method for providing a collaborative service, and is stored in a medium.

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

First, it provides an information providing page (ie, a board) suitable for each industry group and makes it easy to create the information providing page so that users of each industry group can perform efficient work.

Second, an extension board having a specific format can be easily created by adding a label necessary for adding the card data to a specific extension board. Users can solve the inconvenience of producing a separate form by using the data included in the basic card.

Third, since only one card data exists in the service server and is displayed differently by being connected to the basic card and the expansion card by the label, if the card data is modified in a specific basic card or expansion card, all connected cards are modified. Since the individual forms are created and used with the same information, if the information is modified in a certain form, the existing inconvenience of searching for and modifying the corresponding part of each form can be solved.

1 is a flowchart of a method of providing a collaboration service according to an embodiment of the present invention.
2 is an exemplary diagram of a basic card generated for each scene in the field of movie production according to an embodiment of the present invention.
3 is an exemplary diagram of a scene-specific basic card to which a certain label is added according to an embodiment of the present invention.
FIG. 4 is a view illustrating an example of a process of creating an extension card (daily shooting schedule) of a photography schedule based on a basic card in the field of movie production according to an embodiment of the present invention.
5 is a flowchart of a method of providing a collaborative service, further comprising a step of modifying a card associated with a modification of a specific basic card or an expansion card according to an embodiment of the present invention.
FIG. 6 is an exemplary diagram of an expansion card (daily shooting schedule table) generated by including various basic cards according to an embodiment of the present invention.
7 is a flowchart of a method of providing a collaboration service, which further includes adding a new skin to a project or a space 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.

A " collaboration group " as used herein refers to a group in an online service that is formed for performing a collaboration by including a plurality of users.

In this specification, 'sub-group' means a sub-group included in a specific collaboration group.

In this specification, a 'project' refers to a space created by a specific collaboration group for information exchange or the like for collaborative execution. For example, in the case of a group including a user involved in a specific movie production (for example, a staff, an actor, etc.), 'project' means a space where users of a group involved in a specific movie production perform information exchange do.

In this specification, 'Space' means one or more detailed spaces included in the project. In other words, 'space' refers to a user included in a specific collaboration group

In this specification, 'main board' means a user interface screen displayed in a manner that data inputted or uploaded by a user of a collaboration group is listed.

In the present specification, an 'extension board' refers to a user interface screen in which data input by a user of a collaboration group is created and displayed in a specific form. For example, an 'extension board' may be a user interface screen in a document format (e.g., a photographic schedule) commonly used in a particular industry group (e.g., film production industry).

In this specification, 'card data' is data displayed on a board (for example, a main board or an expansion board), and is a unit of data inputted or uploaded by a user. For example, 'card data' may correspond to a single post entered by a particular user.

In this specification, 'basic card' means a basic format in which card data inputted by a user is displayed on a board.

In the present specification, 'basic card data' means data provided to the basic card among the card data.

In this specification, 'expansion card' means a format (format) in which card data input by a user matches a specific expansion board.

In the present specification, 'expansion card data' means data provided to an expansion card among card data.

Hereinafter, a method and a program for providing a cooperative work service according to embodiments of the present invention will be described in detail with reference to the drawings.

1 is a flowchart of a method of providing a collaboration service according to an embodiment of the present invention.

Referring to FIG. 1, a method for providing a cooperative work service according to an exemplary embodiment of the present invention includes generating a project corresponding to a collaboration group by a service server (S200); Receiving card data from a user client on a main board in the project (S400: card data receiving step); Receiving a label input request in the card data (S600: label input request step); Connecting the card data to an expansion board corresponding to the label (S800); And displaying card data connected to the expansion board by a specific label (S1000). Hereinafter, a detailed description of each step will be described.

The service server creates a project corresponding to the collaboration group (S200). The service server receives a project creation request for performing a specific task in a collaboration service from a specific user, and creates a project corresponding to a specific task in the collaboration service. The service server can receive a request to create a project from a specific user via the web or application.

When creating a project, the user can invite members to be added to the collaboration group corresponding to the project. For example, the service server may provide a member addition page at the time of creating a project in a collaborative service application or a web page, and a user who creates a project (i.e., a first user) has a user or a contact subscribed to the collaboration service You can add an acquaintance. When adding an acquaintance (i.e., a second user) that is not subscribed to the collaboration service to the project, the service server acquires the contact information of the second user received from the client apparatus of the first user (e.g., telephone number, SNS account, E-mail address, etc.).

The service server receives the card data from the user client on the main board in the project (S400; card data receiving step). The card data is information to be input into the project by the user, and is information posted in the collaboration group. The service server receives the card data to be added to the project or space from the client device of the specific user included in the collaboration group.

The service server can receive card data in various ways. In one embodiment, the service server directly receives data to be created in the form of one base card 100 from a user. For example, the service server can receive card data from a user client in the form of receiving a bulletin board entry.

In another embodiment, in the card data receiving step (S400), the service server receives the scenario data from a specific user, receives the partition request for the scenario data, and stores the base card 100 corresponding to each scene . For example, in the case of using a collaborative service in the movie production field, the service server receives scenario data corresponding to the entire scenario file from the user (i.e., the first user) corresponding to the manager at the time of project creation. Thereafter, the service server divides the scenario data by each scene. The service server may divide the scene in units set by the user or divide the scenes based on the input identification data to distinguish the scenes in the scenario data. In this way, the service server generates a basic card 100 corresponding to each scene.

As shown in FIG. 2, the scene-specific basic card 100 generated based on the scenario data may include necessary information for each scene. For example, the service server can generate a detailed card or add an information label in the base card 100 for each scene by inputting information that the user should share in a collaboration group or subgroup for a particular scene have. The scene-specific basic card 100 can display various information related to the scene. For example, the basic card 100 for each scene may be inputted with a scene of shooting, a character, a shooting date, a conti, etc. of the scene. Each piece of information can be input in such a manner that a label is added in the basic card 100, as described later. As shown in Fig. 2, the base card 100 of a specific scene (S # 22A) can generate and provide information such as scene shooting location, characters, person dressing / costumes, auxiliary performers, etc. with respective labels or tabs .

The service server receives a label input request in the card data (step S600). The label corresponds to inputting specific information to each card. The service server can add the place information, the time information, the attendee information, and the like to the label corresponding to each user's label input request.

Various methods can be applied to the label input request. In one embodiment, the service server selects an additional button (e.g., a '+' button) displayed on the interface of the base card 100 or the expansion card 200, and then selects and adds a desired label type. In addition, in another embodiment, as the user drags and drops a particular card to a tab corresponding to a particular extension board, the user client sends a label input request, which is required for the base card 100 to be displayed on a particular extension board, Lt; / RTI > For example, in order to create a shooting schedule at the time of movie production collaboration, information about shooting schedules for each scene is required. Therefore, as shown in FIG. 4, when a user inserts a specific scene card (i.e., the base card 100) The user client can transmit a label input request to the service server for requesting addition of the shooting schedule label 110 necessary for adding the selected thin card to the shooting calendar table by dragging and dropping to the corresponding expansion board tab or the expansion board itself have.

The service server connects the card data to the expansion board corresponding to the label (S800; card data connection step). That is, when a label corresponding to information necessary for connecting card data to each extension board is added to the card, the service server connects the card data to the extension board matched with the label. As the label is added, a specific expansion board display of specific card data is activated. For example, the basic card 100 (i.e., the thin card) corresponding to each scene is set to be displayed only on the main board that displays the specific expansion boards in the order of the respective scenes, As the label for the schedule is added, the display in the shooting schedule of the basic card 100 is activated.

The expansion board is a specific type of board used for each situation or industry group. Since each industry group has an existing form for convenience of operation, an expansion board is provided in a form used by industry groups using collaboration services (for example, movie production industry, medical industry, etc.) To be maintained. For example, in the film production industry, when a photographer enters a photographing process, photographing is not performed in order of a scene, and a photographing schedule is produced in consideration of a photographing place and an actor schedule. It is possible to use the photography schedule form that was previously produced through the use of Excel, etc., in the collaboration service, so that it is possible to solve the inconvenience of adapting to the new style. That is, by using the expansion board corresponding to each industry group, the collaboration service can be used in a direction specific to each industry group, without using the fixed form fixed in the collaboration tool.

In addition, the expansion card 200 included in the expansion board can display only the information to be displayed on the expansion board among the data included in the basic card 100 in a specific format. The basic card 100 displayed on the main board may include a plurality of information, but all of the information may not be needed when using a specific expansion board. Accordingly, the service server can extract only the information necessary for the expansion board from among the card data included in the basic card 100, thereby configuring the expansion card 200. That is, the main board and the expansion board display the same information (i.e., card data) according to the board type by using different types of the basic card 100 and the expansion card 200.

Further, in another embodiment, the expansion board can be added through purchase within the collaboration service as described below. For example, the service server may include a skin sales market within the collaboration service, and as the user purchases an expansion board required for a particular industry group or detail situation, Can be added. In addition, if a specific user creates an extension board for a specific industry group or a detailed situation, it can be uploaded and sold in a skin sales market.

As shown in FIG. 3, one or more predetermined labels may be added to the basic card 100 (i.e., the thin card) at the request of the user. Since the photographing progress may be required at a plurality of places in order to photograph one scene, the photographing schedule to be photographed at each place can be added with a certain label. As the schedule label is added, the service server connects the corresponding scene card to the shooting plan card (i.e., the primary card) of the specific shooting date. 3, the service server stores the corresponding expansion card 200 number (for example, 35th, 75th, etc.) in the shooting calendar board together with the corresponding schedule label in the scene card (i.e., the basic card 100) ) Can be displayed.

The service server displays card data linked to the extension board by a specific label (S1000). Also, in the card data display step (S1000), the expansion card 200 modified in a format corresponding to the expansion board corresponding to the label may be displayed. For example, as shown in FIG. 4, the service server displays and provides the expansion card 200 in which each of the thin cards (the basic card 100) is changed to conform to the photography schedule, which is an expansion board.

In another embodiment, as shown in FIG. 4, in the daily shooting schedule card created based on the schedule label input to the scene card, which is the basic card 100, the user can select another user list The confirmation request can be transmitted only to the user who has not confirmed it. That is, the service server acquires the user client information for confirming the newly created or changed daily photography schedule, and generates and outputs the confirmed user list to the user. Accordingly, the user can send a confirmation request only to the other party who has not confirmed the shooting schedule, so that unnecessary contact can be reduced.

5, when specific card data in the main board or the expansion board is modified by a specific user in the collaboration group, the modified expansion card 200 data (S1200). ≪ / RTI > The main card 100 and the expansion card 200 displayed on the main board and the expansion board are connected by a label to display card data (i.e., basic card data) included in the basic card 100 in different formats , The card in the main board and one or more expansion boards can be modified at once by modifying the card data in a specific card.

As a result, a user who belongs to a collaborative group or a detailed group inputs information that should be shared at the time of collaboration, as card data to generate a basic card 100, and then adds a label necessary for adding the card data to a specific expansion board It is possible to easily create an extension board having a specific format. The users can solve the inconvenience of producing a separate form using the data included in the basic card 100. [

In addition, since only one card data exists in the service server and is displayed by being connected to the base card 100 and the expansion card 200 by a label and displayed differently, the card data is stored in the specific basic card 100 or the expansion card 200 If you do so, all connected cards will be modified. Since the individual forms are created and used with the same information, if the information is modified in a certain form, the existing inconvenience of searching for and modifying the corresponding part of each form can be solved. For example, in the case of a film production collaboration, when a schedule change occurs due to an actor schedule change, a shooting location change, a delay in previous shooting, etc., all the daily shooting plans related to one change can be found and individually modified, So that it is possible to eliminate the inconvenience that the user should be guided to.

Also, in another embodiment, the expansion card 200 may be formed in a format that includes one or more base cards 100. That is, the service server may create a single expansion card 200 by merging or listing a plurality of base cards 100. The service server creates specific expansion cards 200 by merging or listing the basic cards 100 including the same label information. For example, at the time of movie production collaboration, the basic card 100 may be a scene card generated for each scene, and the expansion card 200 may be a shooting schedule for each date (shooting schedule). By adding a specific photographing schedule to the basic card 100 as a label, the expansion card 200 is created by merging or listing the basic cards 100 to which a certain label is added on the same date. Accordingly, it is possible to easily generate the date-specific expansion card 200 included in the expansion board, which is a shooting calendar, and to easily modify the entire board by performing information correction in the main board or the expansion board.

For example, in the case of performing movie production collaboration, as shown in FIG. 6, the service server stores the basic card 100 (i.e., the thin card) photographed on the day in the daily shooting schedule card of a specific date, And displays it. That is, the service server extracts only the information necessary for the daily photography calendar card, which is the expansion card 200, among the information included in the basic card 100 corresponding to each scene, and displays the information in the expansion card 200. 6, the basic card 100 (i.e., the thin card) displayed in the expansion card 200 is a part of the entire card data, such as a schedule, a place in the movie, a situation, a shooting location, a number of cuts, And provides it.

In addition, at the time of shooting a movie, multiple scenes are photographed on the same date, so that the expansion card 200 can display a plurality of basic cards 100 (i.e., a thin card) at the same time, The user interface can be provided to sequentially check the cards. 5, the service server receives an operation of swiping the portion of the expansion card 200 in which the basic card 100 is displayed from the user to the left and right, and the service server transmits the other basic card 100 , A thin card) can be provided.

In addition, the daily shooting calendar card, which is the expansion card 200, can be displayed in accordance with the expansion card 200 by combining the card data included in the plurality of basic cards 100 shot at the same time. For example, as shown in FIG. 6, the service server may combine the information included in each of the thin cards to generate information to be included in the tabs such as detailed schedule, auxiliary display, and on-site schedule at the bottom.

In addition, the expansion card 200 may additionally include necessary information in addition to the information included in the basic card 100. For example, as shown in FIG. 6, the daily photography schedule card, which is the expansion card 200, may receive call time information not included in the scene card, which is the basic card 100, and may include the received call time information in a separate tab. Since the call time information is not related to each scene but is related to shooting of the corresponding date, the service server may separately provide a call time tab within the expansion card 200 and receive call time information of each performer from the manager .

7, in accordance with the purchase of a specific new skin in the project by the user included in the collaboration group, the service server stores the extension space included in the new skin, (S1400) adding any one of the expansion card 200 and the expansion card 200. [ The service server may provide a marketplace for purchasing skins within the collaboration service. The skin refers to a specific expansion board, an expansion card 200, an extension space, and the like, which are available when a collaboration service is used. As a user in a collaboration group purchases a new skin in the marketplace, the new skin can be applied within the project of the collaboration group. The new skin can be created by the service provider or another user and uploaded to the market. The market includes all the paths that can be accessed through the web or an app to add elements applicable to the service.

The expansion card 200 may be a card having a different format for displaying information in the main board or expansion board already purchased. That is, the expansion card 200 can be formed in a format that is easier to confirm information than a card used in a conventional collaboration service, or in a format capable of adding more data types (for example, moving pictures, pictures, etc.) .

The expansion board is a board in a form suitable for a specific industry group or situation in addition to a board form fundamentally provided to a collaboration service. As a new extension board addition request is made by the user, the service server can add the extension board to the project or space to which the user is added. This allows users to collaborate efficiently by adding expansion boards in the form needed to collaborate on specific industries. The expansion board may be provided including one or more expansion cards 200 having a format compatible with the expansion board.

The expansion space is a skin that includes one or more board configurations and expansion cards 200 that are specific to a specific subgroup. For example, the boards required to collaborate with a specific subset of financial groups that correspond to the finance team within a collaboration group may generally be defined. Accordingly, the service server can add a space specific to the detailed group that performs a specific task to the project according to the request for adding an extended space.

As new skins can be added, it is possible to guarantee diversity of work and various usability of users in one collaboration service. In addition, by providing specialized skins for each industry group, it is possible to improve efficiency of business by using collaboration service regardless of industry group.

In another embodiment, the card data includes related user information as a label on the card, and the service server provides a correction notification only to the user included in the related information when the card data is modified. If a collaborative service provides an unnecessary notification to a user included in a collaborative group, a problem occurs that the user becomes insensitive to the notification of the collaboration service and does not react quickly. Therefore, only a user who needs specific information guidance is targeted You need to provide a notification. To this end, the service server may add related user information to the card data, and notify the user included in the related user information only when the card data is input or modified.

For example, at the time of movie production collaboration, a basic card 100 (i.e., a thin card) corresponding to a specific scene adds a user (for example, an actor, a shooting team, etc.) can do. If the card data of the scene card is modified due to the change of the shooting location or schedule of the scene, the service server can notify the user included in the related user information that there is a correction to the scene.

Hereinafter, a method of providing a cooperative work service according to embodiments of the present invention will be described in detail.

When the collaboration service is used for movie production / shooting, the basic card 100 is generated for each scene included in the scenario. The basic cards 100 (i.e., thin cards) generated for each scene can be listed in the order of the scenes on the main board. That is, the main board may correspond to the movie scenario, and each of the scene cards may be generated as the scenario data is uploaded to the service server by the user.

In addition, the scene card may include a plurality of pieces of information related to each scene (information necessary for shooting the scene). For example, the scene card may include a shooting place, a shooting schedule, a contest, a shooting actor, etc. as card data, and each piece of information may be added to the card in the form of a label.

One of the expansion boards may correspond to a photography schedule. The expansion card 200 in the expansion board corresponding to the shooting schedule is an imaging schedule for each shooting date, and the order number is given in the shooting date sequence. The expansion card 200 included in the shooting calendar is a card generated by merging or listing a plurality of base cards 100 having a specific date set as a shooting schedule on a certain label. That is, the service server displays the expansion card 200 on the shooting calendar extension board by inputting the shooting date / time (i.e., adding the shooting schedule label) to the scene card (i.e., the base card 100) by the user . The service server can transform and display the scene card (i.e., the basic card 100) in a form suitable for displaying on the shooting calendar. In addition, the service server collects the thin cards photographed on the same date and generates them as one expansion card (200).

Accordingly, since the collaboration service including the collaboration service method according to the embodiments of the present invention is used at the time of film production, users do not have to separately create a shooting schedule based on the scenario and the information about each scene. If you add only schedule information to a scene card created for each scene, a shooting schedule is automatically created. If you change the shooting schedule of a specific scene, the shooting schedule can be automatically changed. That is, when the photographing date of a scene corresponding to a specific basic card 100 is changed, the service server automatically changes the expansion card 200 including the basic card 100 (i.e., the shooting schedule card of a specific date) .

As described above, the method for providing a collaborative service according to an embodiment of the present invention may be implemented as a program (or application) in order to be executed in combination with a computer, which is 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: Basic card
110: Label
200: Expansion card

Claims (10)

Creating a project corresponding to the collaboration group by the service server;
Receiving card data from a user client on a main board in the project to generate a basic card, the card data being information input in a project;
A label input request step of receiving a label input request in the card data;
Connecting the card data to an expansion board corresponding to the label;
And displaying card data connected to the expansion board by a specific label,
Wherein the expansion board is a specific type of board used for each situation or industry group. The method according to claim 1,
Wherein the card data connection step comprises:
And displaying the expansion card modified in a format corresponding to the extension board corresponding to the label. The method according to claim 1,
The project includes one or more spaces,
Wherein the space corresponds to one or more subgroups in the collaboration group. The method according to claim 1,
Adding one of an extension space, an extension board, and an expansion card included in the new skin in the project according to the purchase of a new skin by the user included in the collaboration group in the project and,
Wherein the purchase of the new skin is performed through a market within the collaboration service. The method according to claim 1,
The expansion board includes:
It is generated based on the form used in a specific field,
Wherein the expansion card included in the expansion board includes:
Wherein only the information to be displayed on the extension board is displayed in a specific format from the data included in the basic card. The method according to claim 1,
And displaying the modified card data in the one or more expansion boards when specific card data in the main board or the expansion board is modified by a specific user in the collaboration group,
Wherein the main board and the expansion board display the same information according to a board type in different types of basic card data and expansion card data. The method according to claim 1,
The card data includes the related user information as a label on the card,
Wherein when the card data is modified, a correction notice is provided only to the user included in the person information. The method according to claim 1,
When the collaboration service is used for movie shooting,
The basic card is generated for each scene included in the scenario,
The expansion board corresponds to a photography schedule,
Wherein the expansion card included in the photography calendar is a card generated by merging a plurality of basic cards having a specific date set as a photography schedule on a predetermined label and an order number is assigned in the order of shooting date. The method according to claim 1,
Wherein the card data receiving step comprises:
And receives a division request for the scenario data to generate a base card corresponding to each scene. 9. A collaborative service provision program stored in a medium for executing the method of any one of claims 1 to 9 in combination with a computer which is hardware.

Images