JP5532738B2 - Network system - Google Patents

Description

  The present invention relates to the fields of a network system, a server device, and a groupware program.

  In recent years, the spread of groupware environment has enabled smooth transmission and sharing of information. For example, in an office environment such as a company, a groupware system is widely used to improve business efficiency. The groupware system (collaboration system) provides various tools and functions such as e-mail, bulletin board, schedule management, and task management, and users perform information management, information transmission, and information sharing in units of individuals or group members. Can do. Such a groupware system is generally configured by connecting a server device that provides a function of the groupware system and a plurality of client terminals used by a user via a network.

  In such a groupware system, various types of information are handled, but the problem that this type of system should be pursued is how easily information useful to the user can be accessed. Specifically, for example, improvement and improvement of UI (user interface) visibility, intuitive operability, information diversity, information linkage between a plurality of functions, and the like are required.

  In this regard, for example, from the viewpoint of diversity of information, Patent Document 1 describes a personal information management system that manages schedules, work items, addresses, requested items, and the like of each worker in the group, and is managed on the groupware system side. There has been proposed an information management system that can match groupware information. According to the present invention, information that has been conventionally managed by a personal information management system can be handled centrally by a groupware system, and various information that is convenient for the user can be accessed from the groupware.

  Further, for example, from the viewpoint of UI visibility and intuitive operability, Patent Document 2 proposes a group work support device that provides a place for discussion on a network so that group work can be efficiently performed. Yes. In the discussion, a technique is disclosed that facilitates identification and classification of the content of the speech by expressing the content of the participant's speech in a sticky note format and changing the position of the sticky note or coloring it.

  However, in the information management system described in Patent Document 1, when synchronizing other necessary items such as work items and requested items, it is necessary to deal with each system (software) managing personal information. Come. In addition, since it is originally based on the concept of dual management, it is essential to operate with a plurality of types of systems (software), and it is difficult to provide simpler and clearer user operations. In other words, there is still room for improvement in terms of operability.

  There is also a system that manages personal information such as personal schedules, work items, and requested items on the groupware system side, but the functions such as schedules, work items, and requested items are realized independently. Therefore, the situation remains that the individual functions can be used within the same operability. For example, the items displayed in the function views such as bulletin boards and schedules have data and formats corresponding to the respective function views. Therefore, when information needs to be set in another function view based on information in a certain function view, it is necessary to set information having the same contents again. This means that if it is necessary to set up his / her schedule based on the information posted on the bulletin board, it is necessary to re-enter his / her schedule information while checking the posted contents on the bulletin board. That is, in order to use different functions despite the same groupware, a plurality of setting operations are required, and there is a problem in terms of operability and information linkage.

  In addition, the group work support apparatus described in Patent Document 2 only provides one function, and is intended to facilitate UI visibility and intuitive operability within the one function. Needless to say, the collaboration in the group work is not limited to the discussion function, and the discussion is only one event in the group work from the individual (or each member) participating in the discussion. That is, since there is no continuity between the discussion function and other group work functions, there is a problem in terms of information linkage. For this reason, a load occurs in preparation for using the discussion function.

  An object of the present invention is to provide a network system, a server device, and a groupware program that link various information between functions of groupware and improve user operability in view of the above problems. . More specifically, various information used by each function of the groupware (for example, transmission information, schedule information, task information, etc.) is managed so as to be seamlessly linked between the functions, and has a consistent operability. The purpose of the groupware is to realize efficient information sharing.

  In order to solve the above problems, a network system according to the present invention is a network system in which a client device and a server device that provides a groupware function to the client are connected via a network, and the server device includes: Storage means for storing information relating to a window, which is a work field for realizing a groupware function, information relating to an image object to be displayed superimposed on the window, and data attached to the image object; and the storage means And transmitting means for transmitting information relating to the window, information relating to the image object, and data attached to the image object to the client device, wherein the storage means includes data attached to the image object. Superimposed The client device can store all of the data attached to the image object in a data item regardless of a plurality of the data attached to the image object, stored in association with the displayed window. Is based on information related to the display object, window display means for displaying the plurality of windows on the display means based on information related to the window transmitted by the transmitting means, and information related to the image object transmitted by the transmitting means. An image object display means for superimposing the image object on the window and displaying it on the display means, and an image object on the first window displayed by the display means from the first window to the second Operating means for moving or copying onto windows And an update request means for making an update request for data attached to the image object when the image object is moved or copied by the operation means, and the update request means makes an update request. In this case, the storage means stores the data attached to the moved or copied image object in the data item in association with the second window while inheriting the data.

  In order to solve the above problem, in the network system, the second window is a bulletin board that displays shared information, and the image object display means displays the image object that has been moved or copied as the image object. Along with the data related to the bulletin board among the data attached to the object, it is superimposed on the window of the bulletin board and displayed on the display means.

  In order to solve the above problem, in the network system, for each window, the window has authority setting means for setting user access authority including at least whether or not window browsing is possible. The image object displayed in the screen is moved or copied between users having the user access authority.

  In order to solve the above problem, in the network system, the window display means causes the display means to display a notepad window which is a work field for temporarily holding an image object, and It is possible to move or copy an image object on a window or any one of a plurality of windows onto a mutual window while inheriting data attached to the image object.

  In order to solve the above problem, in the network system, the client device inherits the image object when the image object is moved or copied from the first window to the second window. Complementing means for complementing the deficient data based on the difference between the data incidental to the image object and the data to be used in the second window is provided.

  In addition, what applied the arbitrary combination of the component of this invention, expression, or a component to a method, an apparatus, a system, a computer program, a recording medium, etc. is also effective as an aspect of this invention.

  According to the present invention, it is possible to provide a network system, a server device, and a groupware program that link various information between functions of groupware to improve user operability.

The network block diagram of the groupware system 100 which concerns on this invention is shown. An example of the hardware constitutions of the server apparatus 1 which concerns on embodiment of this invention is shown. An example of the hardware constitutions of the client terminal 2 which concerns on embodiment of this invention is shown. 2 is a functional block diagram illustrating a configuration of main functions of an embodiment of a server device 1 and a client terminal 2. FIG. It is a figure which shows the structure of the main functional components of one Embodiment of the server apparatus. The example of the basic screen of the groupware which concerns on this invention is shown. An example of a tag creation screen for creating a tag is shown. An example of the structure of tag data is shown. An example of a bulletin board / window 900 is shown. An example of a bulletin board creation screen is shown. An example of a bulletin board / window 900 is shown. An example of a tag creation screen for creating a tag is shown. An example of a bulletin board / window 900 is shown. An example of a matrix window 1400 is shown. The matrix creation screen is shown. An example of a matrix window 1400 is shown. An example of a tag creation screen for creating a tag is shown. An example of the matrix window 1400 An example of a schedule window 1900 is shown. An example of a weekly schedule window 2000 and a daily schedule window 2100 is shown. An example of a tag creation screen for creating a tag is shown. An example of a schedule window 1900 is shown. The example of the basic screen of the groupware which concerns on this invention is shown. An example of the tag data e is shown. An example of the tag data g is shown. An example of the tag data h is shown. An example of the tag data i is shown. It is a figure explaining the copy of the tag g. An example of new tag data is shown. An example of new tag data is shown. An example of a screen prompting input of data values of essential items is shown. An example of new tag data is shown. An example of new tag data is shown.

  DESCRIPTION OF EMBODIMENTS Embodiments for carrying out the present invention will be described in each embodiment with reference to the drawings. In describing the present invention, an example in which the present invention is applied to a groupware system which is an embodiment of the network system of the present invention will be described below.

[Constitution]
(network)
FIG. 1 shows a network configuration diagram of a groupware system 100 according to the present invention. In the groupware system 100 according to the present invention, a server device 1 and a client terminal 2 are connected via a network 3.

  The server device 1 is a groupware server according to the present invention, and includes a DB (Data Base) or the like and provides various groupware functions to the client terminal 2. The client terminal 2 is a so-called user terminal. Information is shared between the client terminals 2 via the server device 1. The client terminal 2 is preferably configured by a PC (Personal Computer), but is not limited thereto, and may be configured by an information processing device such as a PDA (Personal Digital Assistants) or a mobile phone. The network 3 includes a wired network and a wireless network, and includes, for example, a LAN (Local Area Network) or a WAN (Wide Area Network).

  FIG. 1 shows an example of a network configuration for explaining an embodiment of the present invention, and the server device 1 and the client terminal 2 may be constructed on different networks as long as they can be accessed. Furthermore, an internal functional unit and DB, which will be described later, may be constructed on different servers.

(Server device hardware)
FIG. 2 shows an example of the hardware configuration of the server apparatus 1 according to the embodiment of the present invention. The server device 1 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a communication device 14, and an auxiliary storage device 15, which are connected to each other via a bus line 16. The

  The CPU 11 is composed of a microprocessor and its peripheral circuits, and is a central processing unit that operates in accordance with various programs and performs various types of information processing and arithmetic processing, and controls each part of the server device 1 or the whole.

  The ROM 12 is a memory for storing a predetermined read-only control program, and stores, for example, basic programs and parameters for operating the server device 1.

  The RAM 13 is a memory used as a work area when the CPU 11 executes programs stored in the ROM 12 or the auxiliary storage device 15 to perform various controls and operations.

  The communication device 14 is a communication device that is connected to the network 3 and implements communication that the server device 1 performs with the client terminal 2.

  The auxiliary storage device 15 is a large-capacity storage device configured by, for example, a nonvolatile hard disk. The auxiliary storage device 15 stores programs for realizing various operations and a database storing various data. The program includes, for example, an OS (Operating System) which is a basic program for operating the server device 1, a control program for controlling the communication device 14, a groupware program for realizing the groupware system according to the present invention, And other programs. The database is an information database used in the groupware system according to the present invention, for example. Screen data such as a function view and a tag (electronic tag) is generated and provided to the client terminal 2 by a groupware program executed by the CPU 11. Information from the client terminal 2 is stored in a database.

  The server device 1 can also include a display device configured with a display device and an input device configured with a mouse and a keyboard for server management and maintenance (not shown).

(Hardware of client terminal)
FIG. 3 shows an example of the hardware configuration of the client terminal 2 according to the embodiment of the present invention. The client terminal 2 includes a CPU 21, a ROM 22, a display 24, a keyboard 25, a mouse 26, a communication device 27, and an auxiliary storage device 28, and is connected to each other via a bus line 29.

  The CPU 21 is composed of a microprocessor and its peripheral circuits, and is a central processing unit that operates according to various programs and performs various types of information processing and arithmetic processing, and controls each part of the client terminal 2 or the whole.

  The ROM 22 is a memory that stores a predetermined read-only control program, and stores, for example, basic programs and parameters for operating the client terminal 2.

  The RAM 23 is a memory used as a work area when the CPU 21 executes programs stored in the ROM 22 and the auxiliary storage device 28 to perform various controls and operations.

  The display 24 is a display device including a display device such as a CRT (Cathode Ray Tube) display, a liquid crystal display, or a plasma display. The display 24 displays characters and images. In the present embodiment, the display 24 displays a screen defined by screen data such as a function view and a tag transmitted by the server apparatus 1, or character information and images input by the user. Can be displayed.

  The keyboard 25 includes character keys for inputting characters, numbers, symbols, and the like, and function keys for specifying various functions such as space, delete, and backspace. By depressing these various keys, input of character information and numerical information and specification of functions are performed from the keyboard 25. In this embodiment, the keyboard 25 is used to input sticky note contents and set names of various function views.

  The mouse 26 is a pointing device, and when the mouse 26 is moved, a mouse pointer, a tag, and the like displayed on the display 24 are moved along with the movement. The mouse 26 also includes buttons such as a left button and a right button. The mouse 26 is placed on an object such as a tag or icon, a radio button, a check box, or a combo box displayed on the display 24 by moving the mouse pointer. By operating, functions corresponding to these objects can be selected. In the present embodiment, the mouse 26 is used to operate objects such as tags, icons, radio buttons, check boxes, combo boxes, and various function views provided by the server apparatus 1.

  The communication device 27 is a communication device that is connected to the network 3 and realizes communication that the client terminal 2 performs with the server device 1. The client terminal 2 communicates with the server device 1 via the communication device 27 to receive screen data such as a function view and a tag and transmit data input by the user.

  The auxiliary storage device 28 is a large-capacity storage device configured by, for example, a nonvolatile hard disk. In the auxiliary storage device 15, for example, an OS that is a basic program for operating the client terminal 2, a program that controls the communication device 27, and a browsing program that uses the groupware service provided by the server device 1 ( For example, various programs and data such as a web browser program and a dedicated viewer program) and a kana-kanji conversion program are stored. Among these programs, the browsing program is a program for realizing the viewer function of the groupware.

  When a web browser is applied as the browsing program, the CPU 21 displays a browser screen on the display 24 by this browser function. The browser screen includes a URL input field for inputting a URL (Uniform Resource Locator) for specifying a connection destination website, and displays a screen defined by the screen data transmitted by the server device 1. The CPU 21 connects the client terminal 2 to the website specified by the URL input in the URL input field using the browser function, interprets the screen data received from the server device 1, and displays a function view, a tag, etc. Display the screen on the browser screen.

  Further, the CPU 21 can transmit information input from the browser screen by the user to the server device 1 using the browser function. For example, by clicking an image object such as an icon, a radio button, a check box, a button, or a tag displayed on the browser screen with a mouse operation, a signal indicating that these objects are selected is transmitted to the server device 1. Alternatively, character information can be input from the input field displayed on the browser screen and transmitted to the server device 1. In addition, various files such as an image file, a text file, a file used in an application such as a word processor or a spreadsheet stored in the auxiliary storage device 28 can be designated on the browser screen and transmitted to the server device 1.

  By causing the CPU 21 to execute the web browser program in this way, the user can send and receive information to and from the server device 1 in both directions. In the present embodiment, the CPU 21 provides various groupware functions provided by the server device 1 to the user using a browser function.

(Server device and client terminal functions)
The main functions of the server device 1 and the client terminal 2 according to the embodiment of the present invention will be described. Since the server apparatus 1 according to the embodiment of the present invention is a groupware server as described above, it provides various general groupware functions to the client terminal 2 via a network. For example, the client terminal 2 accesses the server apparatus 1 and displays function views such as “bulletin board”, “schedule”, and “matrix”. The client terminal 2 operates each functional view displayed on the display screen or the like, and performs individual or group operations while performing information management, information transmission, information sharing, and the like for each individual or group member.

  FIG. 4 is a functional block diagram showing a configuration of main functions of one embodiment of the server device 1 and the client terminal 2. As shown in the figure, the server device 1 includes a storage unit 101 and a transmission unit 102. The client terminal 2 includes a window display unit 201, an image object display unit 202, an operation unit 203, and an update request unit 204. Since more details will be described later, each function will be briefly described here. FIG. 4 is a functional block diagram for explaining the present invention for convenience. As described above, since the server device 1 according to the present invention is a groupware server, various functions for realizing the groupware function are shown. Of course, it has general functions (not shown). Further, as described above, the client terminal 2 is a client terminal as described above, and thus naturally has various general functions for operating the groupware function (not shown).

  First, the storage unit 101 of the server device 1 includes information on a window, which is a work field for realizing the groupware function, information on an image object to be displayed superimposed on the window, and data attached to the image object. It has a function to memorize. The window corresponds to, for example, a function view window, and the image object corresponds to, for example, a tag. The data attached to the image object is, for example, data information associated with the tag. That is, the storage unit 101 stores display information and data required for using groupware on the client terminal 2 side. These information and data are transmitted to the client terminal 2 and displayed on the display screen in a display form that allows the user to suitably use the groupware function.

  Here, the storage unit 101 stores the data attached to the image object in association with the window displayed in a superimposed manner, and the image object is attached regardless of the plurality of data attached to the image object. All data can be stored in data items. Specifically, first, since each function view has its original role, there is a difference in information required for each function view. In the case of a functional view such as a schedule, time information is indispensable. On the other hand, in the case of a functional view such as a matrix, time information is not necessarily indispensable. Rather, position information indicating the importance of a task is essential. Therefore, when the storage unit 101 is configured by a DB, the DB 101 is constructed in a schema so that all data to be held can be stored, regardless of the functional view on which the image object is arranged. For this reason, all the data can be stored regardless of which functional view the image object is placed on. This is because various information used for each function view can be used seamlessly on any function view. This point and details will be described later again. In the following embodiment, the storage unit 101 will be described as the DB 101.

  The transmission unit 102 has a function of transmitting information related to the window, information related to the image object, data attached to the image object, and the like stored in the storage unit 101 to the client terminal 2. These information and data are transmitted to the client terminal 2 and displayed on the display screen in a display form that allows the user to suitably use the groupware function.

  Next, the window display unit 201 of the client terminal 2 has a function of causing a display unit (for example, the display 24) to display a plurality of windows based on the information regarding the window transmitted from the server device 1. Specifically, for example, functional views of “bulletin board”, “schedule”, and “matrix” that are functional views are displayed on the display 24 of the client terminal 2. The client terminal 2 can display a plurality of function views simultaneously on the display 24. The user uses these function views displayed on the screen of the client terminal 2, and the user performs information management, information transmission, information sharing, and the like for each individual or group member.

  The image object display unit 202 has a function of superimposing the image object on the window and displaying it on the display unit based on the information related to the information about the image object transmitted from the server device 1. Specifically, “sticky note” as an example of an image object is displayed on each function view. If the “Bulletin Board” function view is displayed on the tag, bulletin information to be posted is held. In the “schedule” function view, schedule information to be managed by individual users and groups is held. In the “matrix” function view, task information to be managed by individual users and groups is held.

  The operation unit 203 has a function of moving or copying the image object on the first window displayed by the display unit from the first window to the second window. Specifically, the function of moving or copying the above-mentioned sticky note between a plurality of function views displayed on the screen of the client terminal 2 is provided. At that time, the data (including a plurality of data items) attached to the tag is inherited so that it can be used in the function view of the movement destination. Details of this point will be described later again.

  The update request unit 204 has a function of requesting the server device 1 to update data attached to the image object when the image object is moved or copied. When a pre-update request is made, the storage unit 101 of the server device 1 attaches the data in association with the second window of the movement destination while inheriting the data attached to the image object that has been moved or copied. Store data in data items.

  These functions are actually realized by the computer by the programs executed by the CPU 11 and the CPU 21 described above.

(Functional component)
Next, functional components specifically implemented in the server device 1 according to the embodiment of the present invention will be described. FIG. 5 is a diagram illustrating a configuration of main functional components of one embodiment of the server device 1. The server device 1 according to the embodiment of the present invention has the following functional components (functional programs) in order to more specifically realize the functions of the functional units described above. The server device 1 as an embodiment provides a function view of “bulletin board”, “schedule”, and “matrix” to the client terminal 2 with respect to the function view. Other functional views can also be provided. Hereinafter, each functional component will be described.

  The display component 501 is a component that performs screen control related to input / output to the client terminal 2 and performs general display of a basic screen (basic window) of the groupware function. Various operation instructions are given to various components through operations on the basic screen by the display component 501. For example, the user can use the groupware function in general by the server device 1 by giving a tag creation instruction to the tag component 502 or an instruction to display a bulletin board on the bulletin board component 511 through an operation on the basic screen. It can be done.

  The sticky note (image object) component 502 creates various functional views and creation of sticky notes (image objects) freely arranged on the memo pad, displays information contents attached thereto, and operates the sticky note image image between the functional view and the memo pad. It is a component that performs control such as data setting (for example, movement) and operation. Details of the data attached to the tag will be described later.

  The memo pad component 503 is a component that displays a memo pad field, which is a temporary work field that temporarily holds sticky notes (image objects). Since sticky notes can be freely pasted and placed in the memo pad, it can be used as a space for organizing information before being placed in each function view, a storage place for a ToDo list whose details have not been determined, and the like.

  The DB access component 504 is a component that performs data search, update, addition, and deletion processing on the above-described DB 101 storing data in response to a request from another component.

  The function view 510 includes a bulletin board component 511, a matrix component 512, a schedule component 513, and the like. As described above, other functional components may be included depending on the groupware function.

  The bulletin board component 511 is a component that sets the authority of a user who can create, view, and operate a bulletin board that is a component of the groupware function. The bulletin board is used as an information bulletin board by placing (pasting) a sticky note (image object) on the bulletin board.

  The matrix component 512 is a component of creation of a groupware function matrix and a function view on the basic screen. The matrix is used for task management and the like by placing (pasting) sticky notes as task information to be performed on the matrix.

  The schedule component 513 is a component that displays a groupware function schedule. The schedule is used for schedule management and the like by placing sticky notes on a calendar-type schedule table such as day, week, month, year. The schedule component 513 can also transmit a tag of the schedule table as a message to the user or group. Further, by selecting a schedule table, it is possible to select and display display targets such as individual user schedules, other user schedules, and group schedules.

  The hardware of the server device 1 and the client terminal 2, each functional block, and the functional components of the server device 1 have been described above as the configuration of the groupware system 100 that is an embodiment of the network system of the present invention. This will be described more specifically with reference to specific screen examples.

[Embodiment 1: Overview]
First, in the first embodiment, an outline of the groupware according to the present invention (basic screen, function view, notepad, sticky note, sticky note data) and an operation summary of the sticky note (creation, editing, movement, etc.) will be described. In addition, each of the function views will be described individually in embodiments 2 to 5 described later.

  The user can operate the basic screen 600 on the client terminal 2 to use the entire groupware function. For example, information browsing and information posting on the bulletin board, schedule management of individuals or group members on the schedule table A groupware function provided by the server device 1 such as task management in a matrix can be used.

  When a web browser is applied as a browsing program for the client terminal 2, a browser screen is displayed on the display 24. The browser screen 600 includes a URL input field 640 for inputting a URL for specifying a connection destination website, and a screen defined by the screen data transmitted by the server device 1 is displayed.

  The basic screen 600 is roughly divided into a function view window 610 and a notepad window 620. The function view window 610 is a main window that can use the groupware function provided by the server device 1 while switching or simultaneously displaying various function views. In FIG. 6, a function view of the bulletin board 611 is displayed, and sticky notes a to d as postings are posted in the bulletin board window. In addition, since a plurality of bulletin boards can be created even if referred to as a bulletin board, the bulletin board to be referred to can be switched by a switching operation. However, as will be described later, there are bulletin boards that are not displayed depending on the authority of the user. Further, regarding the function views of other schedules 612 and matrix 613, if the function view selection tabs 611 to 613 are operated, the function views can be switched or simultaneously displayed (referred to as a multi-window format).

  The memo pad / window 620 is used as a temporary work field for temporarily holding sticky notes. In Notepad, sticky notes that have been newly created, moved or copied from the function view can be temporarily placed, so the organization space and details of information prior to placement in each function view are determined. It can be used as a storage place for no ToDo list. In the memo pad / window 620 of FIG. 6, sticky notes e and f are placed, and these sticky notes e and f can be moved or copied on various function views.

  When a new sticky note is created, a sticky note as an image object can be created on each function view or memo pad by pressing a sticky note creation (icon) 630. Next, creation of a sticky note and the like will be described.

(Creating a sticky note)
In the present embodiment, a tag (electronic tag) is an information transmission medium for transmitting information handled by groupware. In general, sticky notes are known as small papers used for purposes such as organizing documents. Since the sticky notes made of paper are coated with a weak adhesive, you can write and take notes on the sticky notes and stick them to any place. In the present embodiment, such a paper sticky note image is applied as a groupware information transmission medium so that the groupware can be used intuitively from the viewpoint of improving UI and operability. Accordingly, it is needless to say that the sticky note of this embodiment is merely an example of an image object and is not limited to an image object called a sticky note.

  FIG. 7 shows an example of a tag creation screen for creating a tag. When creating a tag, the user performs, for example, a left click operation on the tag creation (button) 630 in FIG. 6 on the screen (display screen) of the client terminal 2 using the mouse 26. Then, a tag creation screen 700 shown in FIG. 7 is displayed. When the title input field 701 and the content input field 702 are input and the confirmation 703 is pressed, a sticky note is created (registered), and the sticky note is pasted and displayed on the work fields on the function views 611 to 613 and the memo pad 620. Is done.

  The function view 611 to 613 or the notepad 620 to be placed on the notepad 620 may be specified by a target function view or notepad on the pointing device, for example, or specified in the tag creation screen 700 You may be able to do it.

  On the other hand, when a cancel button 704 is pressed on the tag creation screen 700, the tag creation can be canceled.

  The sticky note creation screen 700 shown in FIG. 7 is an example of a sticky note creation screen when a sticky note is created on a memo pad. This is because there is a difference in the required items input by each function view, and the tag creation screen is also slightly different depending on each function view. The tag creation screen in each function view will be described separately in the description of each function view.

  The sticky note creation operation includes a sticky note creation instruction function, a sticky note display function of the display component 501 in the functional component configuration (FIG. 5), a sticky note creation function, a content display function, an input setting function, and a function view 510 of the sticky note component 502. This is performed using the function view components 511 to 513 and the sticky note pasting function of the memo pad component 503. Further, the tag data is registered in the DB 101 by the additional function of the DB access component 504.

(Sticky note data)
Here, data attached to the created sticky note (image object) will be described. Hereinafter, this is referred to as sticky note data for convenience.

  FIG. 8 shows an example of the structure of tag data. A sticky note created by the sticky note component 502 has a data structure as shown in the figure. Since the sticky note according to the present invention can be created and arranged on any functional view and memo pad, all data items can be stored in advance so that they can be arranged on any work field. Data structure. When one sticky note is created on the above-described sticky note creation screen 700, these data items are stored in the DB 101 for each sticky note.

  In the example of the tag data structure in FIG. 8, columns of “item name (data item name)”, “item description”, “notepad”, “bulletin board”, “matrix”, and “schedule” are shown. “Item name” indicates the name of each data item, and “Description of item” describes the description of the item. “Memo pad”, “Bulletin board”, “Matrix”, and “Schedule” indicate whether each item (data item) is indispensable or optional in each work field where a tag can be placed. For example, items Nos. 6, 7, 9, and 10 are data items indicating the placement position and shape (size) of sticky notes on the work field. Due to the nature of the data items, “notepad” and “bulletin board” ”And“ Matrix ”function views are essential information. In the absence of these data items, it is impossible to determine where and what size tag should be placed on the work field. On the other hand, in the function view of “schedule”, as described later, sticky notes are arranged in a calendar (calendar) format schedule table such as day, week, month, year, etc., and therefore, such information is not particularly necessary. Therefore, it is optional. The meaning of “arbitrary” means that when the tag is used in the “schedule”, the value of the arbitrary data item is not referred to (used), but the value may be held as the data item. In this regard, each item (each data item) is displayed and controlled in a display format corresponding to each function view or memo pad by each function view component 510 or memo pad component 503.

  The description of each “item name” will be temporarily transferred to the “item description” column in FIG. 8 and will be described as appropriate in the embodiments described below.

  Immediately, referring back to the creation of the above-mentioned tag, description will be given with reference to FIG. For example, if a sticky note is created on a memo pad, No. 1, 2, 5-7, 9, 10, 18-21, and 23, which are at least essential items, are set in the sticky note data. If the title input field 701 and the content input field 702 are input (FIG. 7), Nos. 3 and 4 are also set. Then, the tag data is registered in the DB 101 by the additional function of the DB access component 504. Note that Nos. 6, 7, 9, 10, and 23 (open) are mandatory items on the sticky note data, but a predetermined value may be set as a default value when the sticky note is created (can be changed later). Also, Nos. 1, 2, 5, and 18 to 21 are automatically acquired and input even if they are not directly input by the user.

(Example of tag editing and content display)
Refer to FIG. 6 again. When editing a sticky note created in the notepad window 620 or the function view window 610 or displaying the contents of the sticky note, the user uses the mouse 26 to double-click the sticky notes a to f in FIG. Click operation. Then, the tag creation screen 700 of FIG. 7 is displayed. Since the tag is edited, some information is input to the title input field 701 and the content input field 702.

  When editing a tag, the user edits the title input field 701 and the content input field 702, and presses the confirmation 703 to reflect the edited contents. The tag editing operation is performed using the tag display function of the display component 501 in the functional component configuration (FIG. 5), the content display function of the tag component 502, and the input setting function. Further, for example, Nos. 3, 4, 20, and 21 in the structure example of the tag data in FIG. 8 are updated at least, and the tag data on the DB 101 is updated by the update function of the DB access component 502.

  When displaying the contents of a sticky note, the user performs, for example, a double-click operation on the sticky notes a to f in FIG. Then, the tag creation screen 700 of FIG. 7 is displayed. Since it is a case where the contents of the sticky note are displayed, some information is input in the title input field 701 and the content input field 702, and the user confirms the displayed information. Further, when a cancel 704 is pressed on the tag creation screen 700, the tag creation screen 700 can be closed. The content display operation is performed using the tag display function of the display component 501 in the functional component configuration (FIG. 5), the content display function of the tag component 502, and the search function of the DB access component 502.

(Movement of sticky note, copy operation example)
When moving the sticky note, the user uses the mouse 26 to move the sticky note, for example, by dragging the sticky notes a to f in FIG. The movement can be performed by the same operation (for example, drag and drop operation) in the same function views 611 to 613, in the same memo pad 620, or between the function views 611 to 613 and the memo pad 620. When moving a sticky note between the function views 611 to 613, a movement operation is performed after displaying a plurality of function views at the same time. The movement operation is performed using the movement function of the tag component 502 in the functional component configuration (FIG. 5) and the tag pasting function of each function view 510 or the tag pasting function of the memo pad component 503. In addition, No. 5 (in the case of movement between function views or notepads), 6, 7, 20, and 21 in the structure example of the tag data in FIG. 8 is updated at least, and the tag on the DB 101 is updated by the update function of the DB access component 502. Data is updated.

  When copying (copying) a tag, the user performs, for example, a right click operation on the tags a to f in FIG. A menu box is displayed. In the menu box, for example, contents of operation instructions for a tag such as “copy”, “paste”, “delete”, and the like can be selected. The user can copy the tag by selecting “Copy”, right-clicking on any destination, displaying the menu window again, and selecting “Paste”. The copy operation is performed using the processing selection function of the tag component 502 in the functional component configuration (FIG. 5) and the tag pasting function of each function view 510 or the tag pasting function of the memo pad component 503. Further, Nos. 2 to 4, 8 to 17, 22, and 23 in the structure example of the tag data in FIG. 8 are copied, Nos. 1, 5, 6, 7, and 18 to 21 are newly set, and an additional function of the DB access component 502 Thus, new tag data on the DB 101 is registered.

(Operation example of tag deletion)
When deleting a tag, the user performs, for example, a right click operation on the tags a to f in FIG. A menu box is displayed. In the menu box, for example, contents of operation instructions for a tag such as “copy”, “paste”, “delete”, and the like can be selected. The user can delete the tag by selecting “Delete”. The tag that has been displayed until then is hidden after the deletion. The deletion operation is performed using the tag display function of the display component 501 and the tag component 502 process selection function in the functional component configuration (FIG. 5). In addition, the deletion flag “1: non-display” is set in No. 23 in the structure example of the tag data in FIG. 8, and the tag data on the DB 101 is updated by the delete function of the DB access component 503. The sticky note data whose deletion flag is “1: non-display” may be deleted from the DB 101 itself after a predetermined period.

  As described above, in the first embodiment, the overview of the groupware according to the present invention (basic screen, function view, notepad, sticky note, sticky note data) and the operation summary of the sticky note (creation, editing, movement, etc.) are described. It was. As described above, in the groupware according to the present invention, regarding the operation of the sticky note, the operation of the sticky note is performed with the same (common) operability as described above, regardless of each function view and the notepad in the basic screen. It can be carried out. Next, each function view will be explained individually.

[Embodiment 2: Bulletin board]
Next, a “bulletin board” functional view (hereinafter sometimes simply referred to as a bulletin board) constituting one of the functional views will be described.

(Example of creating bulletin board)
FIG. 9 shows an example of a bulletin board / window 900. The bulletin board / window shown in the figure is in an initial state in which no bulletin board is created. When creating a new bulletin board, when a bulletin board creation (icon) 901 provided in the bulletin board / window 900 is left-clicked, for example, a bulletin board creation screen 1000 shown in FIG. 10 is displayed. On the bulletin board creation screen 1000, the user inputs the name of the bulletin board to be created in the bulletin board name 1001 column. In addition, a user who is permitted to browse from the user list 1002 is selected and dragged, and dropped on the browsing target user list 1003. The user list 1002 displays a list of users who can use the groupware according to the present invention in advance, and only the users set (registered) in the browsing target user list 1003 from among these users are being created here. Can be viewed. When a user group consisting of a plurality of users is set, the user list is displayed in the user list 1002 in units of groups, and can be set in the browsing target user list 1003 by the same operation. Here, for example, “XX project bulletin board” is input to the bulletin board name 1001, and “user001” and “usergroup002” are set to the browsing target user list 1003.

  When the confirmation (button) 1004 in the bulletin board creation screen 1000 is pressed after the setting is completed, the bulletin board creation screen 1000 is closed, and a new bulletin board is created and displayed in the bulletin board / window 900 as shown in FIG. Is done. When a plurality of bulletin boards are created, a bulletin board to be displayed can be selected from the selection box 902. At this point, no sticky note (posting information) has been created, so no sticky note is posted on the bulletin board. On the other hand, when cancel 1005 is pressed, the bulletin board creation screen 1000 is closed and the creation of the bulletin board is cancelled.

  The bulletin board creation operation is performed using the bulletin board display function of the display component 501 and the bulletin board property setting function of the bulletin board component 511 in the functional component configuration (FIG. 5). The bulletin board property of the bulletin board component 511 is set, and a new bulletin board is finally registered in the DB 101 by the additional function of the DB access component 503.

(Example of creating sticky notes)
FIG. 12 shows an example of a tag creation screen for creating a tag. When creating a sticky note on a bulletin board, as described above, the user designates a target bulletin board function view with a pointing device, for example, and then performs a left click operation using the mouse 26 to create the sticky note creation 630 in FIG. Do. Then, a tag creation screen 1200 shown in FIG. 12 is displayed. Then, a title input field 1201 and a content input field 1202 are input. Since the tag is a tag on the bulletin board, a posting date 1205, a poster 1206, and a posting deadline 1207, which are essential items, are input on the tag data. The posting date 1205 is a column for inputting the date when the tag is posted on the bulletin board. This may be automatically entered. A poster 1206 is a column for inputting a user who posted the tag. Since the user is recognized here, it may be automatically input. The posting deadline 1207 is a field for inputting a deadline for posting the tag on the bulletin board. When the time limit elapses, the tag is automatically deleted from the bulletin board. Finally, when the confirmation 1203 is pressed, a sticky note is created (registered) and a new sticky note is displayed on the bulletin board. Here, for example, it is assumed that a sticky note is newly created by the following input.
Title entry field 1201: First meeting notice content entry field 1202: The first meeting will be held upon the launch of the project. Members must participate. Date: 2009/7/10, Time: 10:00, Location: First meeting room. If you do not participate, please contact this project leader in advance.
Posted date 1205: 2009/7/1
Posted 1206: △△
Posting deadline 1207: 2009/7/11
The sticky note creation operation on the bulletin board includes a sticky note creation instruction function, a sticky note display function of the display component 501 in the functional component configuration (FIG. 5), a sticky note creation function of the sticky note component 502, a content display function, an input setting function, and a bulletin board component. This is performed using the 511 sticky note pasting function. Further, the tag data is registered in the DB 101 by the additional function of the DB access component 504.

  Referring to FIG. 8 again, when a sticky note is created on the bulletin board, at least essential items Nos. 1, 2, 5 to 7, 9, 10, 11 (posting date), 12 (poster), 13 (Posting deadline), 18 to 21, 23 are set. Usually, No. 3 (title) and 4 (content) are also set. Then, the tag data is registered in the DB 101 by the additional function of the DB access component 504. Nos. 6, 7, 9, 10, and 23 are indispensable items, but a predetermined value may be set as a default value when creating a sticky note. Nos. 1, 2, 5, and 18 to 21 are automatically acquired and input even if they are not directly input by the user.

  FIG. 13 shows an example of a bulletin board / window 900 on which a tag is created. As shown in the figure, the newly created sticky note g and the input title and poster are displayed and pasted on the bulletin board. When checking the tag g pasted on the bulletin board in more detail, when the user double-clicks the tag g, for example, the tag creation screen 1200 of FIG. 12 is displayed. Since the contents of the tag are displayed, the information as described above is input in the title input field 1201, the content input field 1202, the posting date 1205, the poster 1206, and the posting deadline 1207, and the user displays the contents. This information can be confirmed.

  The content display operation is performed using the tag display function of the display component 501 in the functional component configuration (FIG. 5), the content display function of the tag component 502, and the search function of the DB access component 502.

(Example of bulletin board)
Reference is again made to FIG. 13 to describe an operation example of information sharing on the bulletin board. Since the bulletin board name “XX project bulletin board” is set to “usergroup002” in the browsing target user list 1003, user members registered in “usergroup002” can receive “XX project bulletin board” from each client terminal 2. Can be browsed.

  A member (referred to as member B) other than the bulletin board creator (referred to as member A) confirms the contents of the tag g posted on the “XX project bulletin board” posted by member A. Thereafter, when the member B needs to correct or add to the content of the tag, the member B can edit the tag g. As described above, when confirming the tag g pasted on the bulletin board in more detail, when the member B double-clicks the tag g, for example, the tag creation screen 1200 of FIG. 12 is displayed. Then, for example, corrections or additional explanations of items described in the content input field 1202 are described. When the editing operation is completed, the tag g on the “XX project bulletin board” is updated. In the updated tag, when the details of the tag are confirmed, the information of the updater is displayed. Alternatively, the detailed property (sticky note data list) of the sticky note g can be referred to. Then, the updater is updated from member A to member B. Accordingly, in the tag data of the tag, No 4 (content), 20 (update date), and 21 (updater) are updated by the update function of the DB access component 502.

  Further, when there is an item that member B wants to transmit to member A or other members, a new tag can be created. As described above, for example, a left click operation is performed on the tag creation 630 of FIG. Then, a tag creation screen 1200 shown in FIG. 12 is displayed. Then, a title input field 1201 and a content input field 1202 are input. Since the tag is a tag on the bulletin board, a posting date 1205, a poster 1206, and a posting deadline 1207, which are essential items, are input on the tag data. When the creation operation is completed, a new sticky note (not shown) is posted (arranged) on the “XX project bulletin board” with the name of the poster as member B. Accordingly, new tag data is registered by the additional function of the DB access component 502.

  In this way, information can be easily shared and opinions can be exchanged easily by pasting and editing sticky notes on a bulletin board between users (seamless information cooperation and efficient information sharing).

[Embodiment 3: Matrix]
Next, a “matrix” function view (hereinafter sometimes simply referred to as a matrix) constituting one of the function views will be described.

(Matrix creation operation example)
FIG. 14 shows an example of the matrix window 1400. The matrix window shown in the figure is in an initial state in which no matrix is created. When creating a new matrix, when a matrix creation (icon) 1401 provided in the matrix window 1400 is left-clicked, for example, a matrix creation screen 1500 shown in FIG. 15 is displayed. On the matrix creation screen 1500, the user inputs the name of the matrix to be created in the matrix name 1501 column. A matrix display format (2-axis, 4-axis, table format, etc.) is selected from the display format selection 1502, and an axis name or item name corresponding to the selection is input to the axis / item name input 1503. Then, a user to be permitted to browse is selected and dragged from the user list 1504 and dropped on the browsing target user list 1505. A list of users who can use the groupware according to the present invention is displayed in advance in the user list 1504, and only the users set (registered) in the browsing target user list 1505 from these users are being created here. Can be viewed. Moreover, the setting to the browsing object user list 1505 by a group unit is possible. Here, for example, “XX Project ToDo Management” is input to the matrix name 1501, “2-axis format” is selected from the display format selection 1502, and “importance” and “emergency” are input to the axis / item name input 1503. It is assumed that “user001” and “usergroup002” are set in the browsing target user list 1505.

  When the confirmation 1006 in the matrix creation screen 1500 is pressed after the setting is completed, the matrix creation screen 1500 is closed, and a new matrix is created and displayed in the matrix window 1400 as shown in FIG. When a plurality of matrices are created, a matrix to be displayed can be selected from the selection box 1402. At this point, since no sticky note (posting information) has been created, no sticky note is pasted on the matrix. On the other hand, when cancel 1507 is pressed, the matrix creation screen 1500 is closed and the creation of the matrix is cancelled.

  The matrix creation operation is performed using the bulletin board display function of the display component 501 and the matrix property setting function of the matrix component 512 in the functional component configuration (FIG. 5). The matrix property of the matrix component 512 is set, and a new matrix is finally registered in the DB 101 by the additional function of the DB access component 503.

(Example of creating sticky notes)
FIG. 17 shows an example of a tag creation screen for creating a tag. When creating a sticky note in the matrix, as described above, the user designates a target matrix function view with a pointing device, for example, and then performs a left click operation using the mouse 26 to create the sticky note creation 630 in FIG. Do. Then, a tag creation screen 1700 shown in FIG. 17 is displayed. Then, a title input field 1701 and a content input field 1702 are input. Also, a pasting date 1703 and a pasting person 1704, which are essential items in the tag data, are input. The pasting date 1703 is a column (automatic input is possible) for inputting the date when the tag is pasted on the matrix. The pasting person name 1704 is a field (automatic input is possible) for inputting the user who pasted the tag on the matrix. Finally, when the confirmation 1705 is pressed, a sticky note is created (registered) and a new sticky note is displayed on the matrix. Here, for example, it is assumed that a sticky note is newly created by the following input.
Title input column 1701: Specification creation content input column 1702: Creation of specification. Incorporate hearings from the design department.
Pasting date 1703: 2009/7/2
Paster 1704: △△
Referring to FIG. 8 again, when a sticky note is created on the matrix, at least essential items Nos. 1, 2, 5 to 7, 9, 10, 14 (pasting date), 15 (pasting person), 18 21 to 23 are set. Usually, No. 3 (title) and 4 (content) are also set. Then, the tag data is registered in the DB 101 by the additional function of the DB access component 504. Nos. 6, 7, 9, 10, and 23 are indispensable items, but a predetermined value may be set as a default value when creating a sticky note. Nos. 1, 2, 5, and 18 to 21 are automatically acquired and input even if they are not directly input by the user.

  FIG. 18 shows an example of a matrix window 1400 in which a tag is created. As shown in the figure, the newly created sticky note h and the title and paster to which it was input are displayed and pasted on the matrix. Since the sticky note can be freely moved, the initial position of the sticky note after creation may be pasted at a predetermined position such as near the upper right of the screen or in the center. When confirming the tag h pasted on the matrix in more detail, when the user double-clicks the tag h, for example, the tag creation screen 1700 of FIG. 17 is displayed. Since the contents of the sticky note are displayed, the above-described information is input to the title input field 1701, the content input field 1702, the pasting date 1703, and the pasting person 1704, and the user displays the contents displayed. I can confirm.

  The content display operation is performed using the tag display function of the display component 501 in the functional component configuration (FIG. 5), the content display function of the tag component 502, and the search function of the DB access component 502.

(Example of matrix)
FIG. 18 is referred to again in order to explain an operation example in which information is shared and opinions are exchanged in a matrix. Since “usergroup002” is set in the browsing target user list 1003 for the matrix name “XX project ToDo management”, the user member registered in “usergroup002” can receive “XX project ToDo from each client terminal 3. "Management" can be viewed.

  A member (member B) other than the bulletin board creator (member A) confirms the position and content of the tag h posted on the “XX Project ToDo Management” posted by the member A. From the arrangement position of the sticky note h on the matrix in FIG. 18, it can be seen that the member A determines that the task of “specification creation” is a task with high urgency and importance. However, as a member B who is a supervisor, when it is determined that the importance is high but the urgency is not high, the member B moves the placement position of the tag h. At this time, the editing operation can be performed at the same time, and the reason and supplementary items can be described in the content input field 1700 (FIG. 17). When member A browses “XX Project ToDo Management” again, the location is moved, the content entry field 1700 is edited, or the updater (supervisor) is member B The task of the tag h can be reconsidered. Accordingly, in the sticky note data of the sticky note, No 4 (content), 6 (X coordinate of the sticky note), 7 (Y coordinate of the sticky note), 20 (update date), and 21 (updater) update the DB access component 502. Needless to say, it is updated by the function.

  In this way, users can easily share information and exchange opinions by pasting sticky notes on the matrix (moving placement positions) and editing each other (seamless information collaboration and efficient exchange) Information sharing).

[Embodiment 4: Schedule]
Next, a “schedule” function view (hereinafter sometimes simply referred to as a schedule) constituting one of the function views will be described.

(Example of schedule display format selection)
FIG. 19 shows an example of a schedule window 1900. In the schedule window 1900 shown in the figure, a monthly schedule table is displayed. The user can switch the display of the schedule table by selecting a calendar type (monthly, weekly, daily) from the display switching 1901 in the schedule window 1900. In the case of the schedule function view, unlike the bulletin board and matrix examples described above, since calendar information is registered in the DB 101 in advance, it is not necessary to create the schedule table itself. FIG. 20 also shows an example of a weekly schedule window 2000 and a daily schedule window 2001, respectively.

  The display format selection operation uses a schedule display function of the display component 501 in the functional component configuration (FIG. 5), a display target selection function, a monthly display function, a weekly display function, and a daily display function of the schedule component 513. Done.

(Example of creating sticky notes)
FIG. 21 shows an example of a tag creation screen for creating a tag. Description will be made with reference to the schedule window 1900 in FIG. 19 again. When creating a sticky note in the schedule, for example, a left click operation is performed on the sticky note creation 630 in FIG. Then, a tag creation screen 2100 shown in FIG. 21 is displayed. Then, a title input field 2101 and a content input field 2102 are input. Also, the scheduled start date and time 2103, the scheduled end date and time 2104, and the disclosure setting 2105 are input. The scheduled start date 2103 is a column for inputting the scheduled start date and time of the schedule. The scheduled end date 2104 is a column for inputting the scheduled end date and time of the schedule. The disclosure setting 2105 is a setting column for setting whether to disclose the schedule to users other than the user. Finally, when the confirmation 2106 is pressed, a sticky note is created (registered) and a new sticky note is displayed on the designated date in the schedule table. When the designated date spans multiple days, for example, a large sticky note that includes a plurality of designated dates is displayed on the schedule table. Here, for example, it is assumed that a sticky note is newly created by the following input.
Title input field 2101: Meeting content input field 2102: For creating specifications. Second conference room reserved.
Scheduled start date and time 2103: 2009/7/6 15:00
Scheduled end date and time 2104: 2009/7/6 17:00
Release setting 2105: Release The sticky note operation on the schedule table includes a sticky note creation instruction function, a sticky note display function of the display component 501 in the functional component configuration (FIG. 5), a sticky note creation function, a content display function, and an input setting of the sticky note component 502. This is performed using the function and the tag pasting function of the schedule component 513. Further, the tag data is registered in the DB 101 by the additional function of the DB access component 504.

  Referring to FIG. 8 again, when a sticky note is created on a schedule, No. 1, 2, 5, 16 (scheduled start date and time), 17 (scheduled end date and time), and 18 to 23 are set. Is done. Usually, No. 3 (title) and 4 (content) are also set. Then, the tag data is registered in the DB 101 by the additional function of the DB access component 504. No22 is an indispensable item, but a predetermined value (public or non-public) may be set as a default value when creating a sticky note. Nos. 1, 2, 5, and 18 to 21 are automatically acquired and input even if they are not directly input by the user.

  FIG. 22 shows an example of a schedule window 1900 in which a tag is created. As shown in the figure, a title to which a newly created sticky note i is input is displayed and pasted on a specified date in the schedule table. When confirming in more detail the sticky note i pasted on the specified date, for example, when the user double-clicks the sticky note i, the sticky note creation screen 2100 of FIG. 21 is displayed. Since the contents of the tag are displayed, the title input field 2101, the content input field 2102, the scheduled start date and time 2103, the scheduled end date and time 2104, and the public setting 2105 are input with the above information, and the user can The displayed information can be confirmed. The content display operation is performed using the tag display function of the display component 501 in the functional component configuration (FIG. 5), the content display function of the tag component 502, and the search function of the DB access component 502.

  In this example, the operation example of creating a sticky note has been described taking the schedule table (monthly display) as an example, but for the creation of a sticky note on the schedule table for weekly display and day display, it is also possible to create a sticky note. it can.

(Example of schedule)
In order to explain an example of schedule arrangement operation by sticking a tag in the schedule, FIG. 22 will be referred to again. In the monthly schedule table, a sticky note i with a schedule of “meeting with the design department” is pasted on 7/6.

  When changing the schedule, the sticky note i is moved to, for example, 7/13 by a drag-and-drop operation. Then, the sticky note i arranged on 7/6 is pasted and displayed on the schedule change date, for example, 7/13 (not shown). In this way, the schedule change operation can be performed by an easy operation.

  Further, if the tag i is set to be public, other members can view the schedule. In this way, you can easily display your own schedule contents on other users' schedules by manipulating the sticky note publishing settings (efficient information sharing). Can be useful.

[Embodiment 5: Cooperation of tag data]
As described in the first embodiment, the sticky note that has been described so far can be moved and copied across the function views and the notepad. At this time, the sticky note data is linked. In the fifth embodiment, a number of examples will be described in detail, and each function view of sticky notes, movement between notepads, etc., and cooperation of sticky note data will be described in detail. As described above, since the sticky note according to the present invention corresponds to all data items of any functional view and memo pad in the sticky note data structure, the sticky note can be moved by the same operation between the functional view and the memo pad. And copying can be performed seamlessly.

  FIG. 23 shows an example of a basic screen of groupware according to the present invention. Although it is almost the same as the basic screen 600 shown in FIG. 6, the basic screen 2300 of FIG. 23 is partially changed in display format to explain the fifth embodiment. Specifically, since a sticky note is moved between function views, a plurality of function views are simultaneously displayed (referred to as a multi-window format). Each function view is displayed by adopting the function view taken up in Embodiments 2 to 4 described so far.

  As described above, the basic screen 2300 is roughly divided into a function view window and a notepad window. In the function view window, various function views described so far are displayed. The memo pad / window is used as a temporary work field for temporarily holding sticky notes. In the notepad, you can temporarily place a sticky note that has been newly created or moved (or copied) from the function view, so the organization space and details of information prior to placement in each function view are determined. It can be used as a storage place for ToDo lists that have not been used. Also, if there is a priority or the like for the sticky note, the arrangement positions on the notepad can be arranged from the top in the priority order.

  Referring to FIG. 23 again, in this screen 2300, a notepad 620, a bulletin board (functional view) 900, a matrix (functional view) 1400, and a schedule (functional view) 1900 are displayed at the same time, and sticky notes e, g, h, i is pasted (arranged).

Here, the sticky note data corresponding to the sticky notes e, g, h, i (referred to as sticky note data e, g, h, i, respectively) are confirmed. The tag data e, g, h, i that each function view has
It is managed on the DB 101 by the sequence number (No 1). For example, the memo pad 620 manages the tag data e, and the bulletin board 900 manages the tag data g.

  24-27 show examples of sticky note data e, g, h, i. The data values are as specific as possible in the second to fourth embodiments. Each sticky note data has a data value for at least the required items.

(Cooperation example 1)
First, as cooperation example 1, an example of moving a sticky note between bulletin board 900 and matrix 1400 will be described. Specifically, a tag is copied from the bulletin board 900 to the matrix 1400.

  In the basic screen 2300 of FIG. 23, the sticky note g on the bulletin board 900 relates to the “announcement of the first meeting” (title). For example, since it is the first meeting for the start of the XX project, When the user thinks that it is very important as a task that all members gather once and have a meeting, sticky note g is pasted (copied) on the “XX Project ToDo Management” matrix and task management It can be performed.

  When copying a sticky note, the same operation as described above can be performed. The user performs, for example, a right click operation on the tag g on the bulletin board 900 using the mouse 26. A menu box is displayed. Select “Copy”, right-click on the destination in the matrix 1400 to display the menu window again and select “Paste” to copy the tag g. It can be performed. FIG. 28 is a diagram for explaining a copy of the tag g. It can be seen that the tag g is copied from the bulletin board 900 to the matrix 1400.

  As the tag g is copied, new tag data is registered in association with the matrix function view by the additional function of the DB access component 502. FIG. 29 shows an example of new tag data. Nos. 1, 5, 14, 15, and 20 are automatically input, and the tag data of the copy source are inherited as they are for 2 to 4, 18, 19, and 21 to 23. Here, No14 (pasting date) and 15 (pasting person) are indispensable data items in the matrix function view, but have data values because they are arbitrary data items in the bulletin board function view. There may not be. Actually, the tag data g does not have data values No. 16 (scheduled start date and time) and 17 (scheduled end date and time) (FIG. 25). Therefore, as the tag g is copied, the data values of these essential items are automatically input because they are data values that can be automatically acquired.

(Cooperation example 2)
As cooperation example 2, an example of moving a tag between the matrix 1400 and the bulletin board 900 will be described. Specifically, the tag is copied from the matrix 1400 to the bulletin board 900.

  In the basic screen 2300 of FIG. 23, the tag h on the matrix 1400 relates to the task “specification creation” (title). For example, the specification creation work is a joint work (or sharing) of a plurality of members. If it is created in (work), there may be a case where it is desired to make other members know about the “include the hearing contents of the design department” described in the task contents on the bulletin board 900 which is the “XX project bulletin board”. is there. Note that “usergroup002” is set in the bulletin board 900 as a browsing target user list, so that other members can browse the bulletin board.

  When copying a sticky note, the same operation as described above can be performed. The user performs, for example, a right click operation on the tag h on the matrix 1400 using the mouse 26. A menu box is displayed. After selecting "Copy", right-clicking on the destination on the bulletin board 900 to display the menu window again and selecting "Paste" to copy the tag h Can be performed (not shown).

  As the tag h is copied, new tag data is registered in association with the matrix function view by the additional function of the DB access component 502. FIG. 30 shows an example of new tag data. Nos. 1, 5, and 20 are automatically input, and the tag data of the copy source are inherited as they are for 2 to 4, 14, 15, 18, 19, 21, and 23. Note that No. 11 (posting date), 12 (poster), and 13 (posting deadline) are mandatory data items in the bulletin board function view, but are data values because they are optional data items in the matrix function view. May not have. Actually, the tag data h does not have data values No. 11 (posting date and time), 12 (poster), and 13 (posting deadline) (FIG. 26). Accordingly, the essential data items can be complemented by displaying a screen that prompts the user to input the data values of the essential items in accordance with the copy operation of the tag h.

  FIG. 31 shows an example of a screen prompting input of data values of essential items. If the posting date / time, poster, and posting deadline are not entered on the screen, copying is canceled. As shown in the figure, the posting date and time and the poster can be provisionally input because they are data values that can be automatically acquired.

(Cooperation example 3)
As cooperation example 3, an explanation will be given by taking an example of moving a sticky note between the bulletin board 900 and the schedule 1900. Specifically, a sticky note is copied from the bulletin board 900 to the schedule 1900.

  In the basic screen 2300 of FIG. 23, a sticky note g on the bulletin board 900 is related to “Notice of the first meeting” (title). Please be sure to participate.Date: 2009/7/10, Time: 10:00, Place: First Conference Room. If you are not participating, please contact this project leader △△ in advance. ” Yes. That is, since the date and time of the first meeting is posted, there is a case where it is desired to register this as a schedule in the schedule table.

  When copying a sticky note, the same operation as described above can be performed. The user performs, for example, a right click operation on the tag g on the bulletin board 900 using the mouse 26. A menu box is displayed. Select "Copy", then right-click on the destination on the schedule 1900 (on the calendar date) to display the menu window again and select "Paste". Thus, the tag g can be copied (not shown).

  As the tag g is copied, new tag data is registered in association with the schedule function view by the additional function of the DB access component 502. FIG. 32 shows an example of new tag data. Nos. 1, 5, and 20 are automatically input, and the tag data of the copy source is inherited as it is for 2 to 4, 11, 12, 13, 18, 19, 21, and 23. Here, No. 16 (scheduled start date and time), 17 (scheduled end date and time), and 22 (public flag) are indispensable data items in the schedule function view, but are optional data items in the bulletin board function view. May not have data values. Actually, the tag data g does not have data values No. 16 (scheduled start date / time), 17 (scheduled end date / time), and 22 (public flag) (FIG. 25). Accordingly, with the copy operation of the tag g, the essential data items can be complemented by displaying a screen that prompts the user to input the data values of these essential items, as described above (not shown).

  Here, the operation example of copying a sticky note has been described by taking a schedule table (monthly display) as an example, but copying of a sticky note on the weekly and daily display schedule tables can be performed in the same manner.

(Cooperation example 4)
As cooperation example 4, an explanation will be given by taking an example of moving a sticky note between memo pad 620 and schedule 1900. Specifically, the sticky note is moved from the memo pad 620 to the schedule 1900.

  In the basic screen 2300 of FIG. 23, it is assumed that the tag e on the memo pad 620 relates to the “group meeting” (title), but no other information is input. This is because, although a “Group Meeting” is scheduled, a specific date and time has not yet been decided. It is considered that the state is held on the book 620. Here, since the date and time of the “group meeting” has been determined, the tag e is moved on the calendar of the schedule 1900. In this cooperation example 4, it is more appropriate to move the tag than copying.

  When moving a sticky note, the same operation as described above can be performed. The user uses the mouse 26 to move the sticky note, for example, by dragging the sticky note e on the note pad 620 and drop it on the destination on the schedule 1900 (on the calendar date). e can be moved (not shown). Further, by editing the moved sticky note e, information such as a meeting place can be added.

  With the movement operation of the tag e, the tag data on the DB 101 is updated by the update function of the DB access component 502. FIG. 33 shows an example of new (updated) tag data. Nos. 5 and 20 are automatically input, and 1 to 3, 18, 19, 21, and 23, the tag data of the movement source is inherited as it is. Here, No. 16 (scheduled start date and time), 17 (scheduled end date and time), and 22 (public flag) are indispensable data items in the schedule function view, but are optional data items in the bulletin board function view. May not have data values. Actually, the tag data e does not have data values No. 16 (scheduled start date / time), 17 (scheduled end date / time), and 22 (public flag) (FIG. 25). Accordingly, in accordance with the movement operation of the tag g, the essential data items can be complemented by displaying a screen that prompts the input of the data values of these essential items, as described above (not shown).

  Needless to say, it is possible to move or copy the sticky note on the note pad 620 to the bulletin board 900 or the matrix 1400 as other function views in the same manner. It is up to the user to move it.

[Summary]
In the above description of the embodiment, the movement and copy operation of sticky notes and the cooperation of sticky note data between each function view and memo pad, between each function view and memo pad have been described. A sticky note (image object) is a common information holding medium, and in order to be able to freely create and place it on any functional view and memo pad, the sticky note data can store all data items in advance. Data structure. Therefore, in the groupware function provided by the server device 1 according to the embodiment of the present invention, the tag data is linked, and in any function view and memo pad, or the tag operation that spans between them In this case, the user can handle a wide variety of information with the same and intuitive operability. In this regard, in the past (groupware system, etc.), the compatibility of information in each function view becomes a problem, the same information is input again, or depending on each function view, the operation for compatibility is troublesome. It took a lot of time and a different operation was required.

  That is, according to the present invention, it is possible to provide a network system, a server device, and a groupware program that link various information between functions of groupware and improve user operability. More specifically, various information used by each function of the groupware (for example, transmission information, schedule information, task information, etc.) is managed so as to be seamlessly linked between the functions, and has a consistent operability. As a result, groupware can achieve efficient information sharing.

  Note that the present invention is not limited to such specific embodiments, and various modifications and changes can be made within the scope of the gist of the present invention described in the claims. Since the sticky note corresponds to all the data items of any functional view and memo pad in the sticky note data structure, the sticky note can be moved and moved between the functional views and memo pads other than those shown in the embodiment by the same operation. You can make a copy.

DESCRIPTION OF SYMBOLS 1 Server apparatus 2 Client terminal 3 Network 101 Storage part 102 Transmission part 11, 21 CPU
12, 22 ROM
13, 23 RAM
14, 27 Communication device 15, 28 Auxiliary storage device 16, 29 Bus line 24 Display 25 Keyboard 26 Mouse 201 Window display unit 202 Image object display unit 203 Operation unit 204 Update request unit 501 Display component 502 Sticky note component 503 Notepad component 504 DB Access component 510 Functional component 511 Bulletin board component 512 Matrix component 513 Schedule component

Japanese Patent No. 4057171 JP 2004-310272 A

Claims (4)

A network system in which a client device and a server device that provides a groupware function to the client device are connected via a network,
The server device
Storage means for storing information about a window that is a work field for realizing a groupware function, information about an image object to be displayed superimposed on the window, and data attached to the image object;
Transmission means for transmitting information relating to the window stored by the storage means, information relating to the image object, and data incidental to the image object to the client device;
The storage means stores the data attached to the image object in association with the window displayed in a superimposed manner, and the image object is stored on any one of the plurality of windows. Can be stored in the data item.
The client device is
Display means;
Window display means for causing the display means to display a plurality of windows based on information about the window transmitted by the transmission means;
An image object display means for superimposing the image object on the window and displaying the image object on the display means based on the information about the image object transmitted by the transmission means;
Operating means for moving or copying the image object on the first window displayed by the display means from the first window to the second window;
When the image object is moved or copied by the operation means, the missing data is complemented based on the difference between the data attached to the inherited image object and the data to be used in the second window. Complementary means to
Update request means for requesting the server device to update data attached to the image object when the image object is moved or copied by the operation means;
When an update request is made by the update requesting means, the storage means inherits the data attached to the moved or copied image object and associates it with the second window in the data item. Storing,
A network system characterized by The second window is a bulletin board displaying shared information,
The image object display means superimposes the moved or copied image object on the bulletin board window together with the data related to the bulletin board from the data attached to the image object, and causes the display means to display the image object. ,
The network system according to claim 1. For each window, there is authority setting means for setting user access authority including at least whether or not window browsing is possible,
In a window in which user access authority is set, an image object displayed in the window is moved or copied between users having user access authority,
The network system according to claim 1, wherein: The window display means causes the display means to display a notepad window that is a work field for temporarily holding an image object,
It is possible to move or copy an image object on the window of the memo pad or a plurality of any of the windows to a mutual window while inheriting data attached to the image object,
The network system according to any one of claims 1 to 3, wherein:

Images