1. project management system to manage projects of users by project desktops -and user attributes of the project including a server (2) connected by a network (5) to a plurality of user terminals (1) operated respectively by the users; a database (3) for storing contents contained in those projects for each of projects participated in by some or all of the users, and a communication controller (4) for transmitting prescribed pages to the user terminals (1), and receiving operation messages from the pages, characterized in that wherein the database (3) includes: a project user table (254) in which user attributes, for projects, of leader or members of the projects, set for each of those projects are recorded; and a project contents table (258) in which the user attribute-oriented access rights are recorded for each set of contents belonging to projects, and wherein the server includes: a project desktop sheet generator (10) for reading contents data (40, 44, 46) from the database (3) in response to operation messages received by the communication controller (4) and generating, for each project, a page as a project desktop (30) for displaying or accessing all contents (40, 44, 46) belonging to the project; the project desktop sheet generator (10, 131) comprises functions (50, 54, 56) for generating a project desktop (30) containing, as the contents (40, 44, 46), a text section (32) for displaying text, a forum section (36) for recording and displaying user statements, and a bookshelf section (38) for managing files transferred from user terminals (1); a project-oriented user attribute controller (14) for determining the user attributes relating to projects which are objects of those communications via the communication controller (4) by using the project user table (254); and a contents-oriented access controller (16) for controlling display and operation content pertaining to several contents (40, 44, 46) of t he project desktop (30), based on the user attributes determined for projects of accessing users (S11, S12) and on the user attribute-oriented access rights (S13) recorded in the project contents table (258), wherein the contents-oriented access controller (16, 152) comprises function for permitting a write to the contents to the user having the write attribute, and for permitting a read to the contents to the user having the write attribute.

2. The system as claimed in claim 1, wherein the database (3) includes a project table (252) in which are recorded the user attribute-oriented access rights for the ' project desktop (30) overall; and wherein, the server (2) includes a project-oriented access setting unit (153) for setting access rights to the project desktop (30) based on user attributes determined by the project-oriented user attribute controller (14).

3. The system as claimed in claim 2, wherein the project contents table (258) has contents order data wherein are recorded display order of contents belonging to that project in the project desktop (30); wherein, the project desktop sheet generator (10, 131) includes: a contents section drawing function (131 A) for reading out contents (40, 44, 46) based on the contents order data and sequentially drawing a contents section (32, 36, 38) in accordance with access rights set by the contents-oriented access controller (16); and a synthesis control function (131B) for effecting control to synthesize the contents sections (32, 36, 38) drawn by the contents section drawing function (131 A) in order according to the contents order data as a single-page project desktop (30).

4. The system as claimed in claim 1, wherein the database (3) includes a document table (260) in which are stored the locations where document files transmitted via the bookshelf section (38) of the project desktop (30) are stored, and a document folder table (262) in which are stored virtual deployment positions in the bookshelf section (38) for the document files managed by that document table (260); wherein, the server includes a document manager (140) for storing the document files transmitted via the bookshelf section (38) in the document table (260) and deploying those document files in a virtual directory in the bookshelf section (38); and wherein, the document manager includes a document operation control function (141) for copying and deleting document files in accordance with user attribute-orienfed access rights set by the contents-oriented access controller (16) and for "submitting those document files for downloading to the user terminals (1).

5. The system as claimed in claim 4, wherein the server includes: a save target setting unit (171) for setting one or a plurality of the plurality of projects as save targets; an archive file archiving controller (172) for archiving contents contained in the one or the plurality of project desktops (30) set by the save target setting unit (171), in one archive file; and an archive file transmission controller (173) for transmitting archive files archived by the archive file archiving controller, in response to operations at the user terminals, to those user terminals; and wherein the archive file archiving controller includes: a project desktop page generator (174) for generating project desktop pages (30) wherein contents content displays or links to portions of contents (40, 44, 46) are written with a prescribed markup language, for each of the projects, in accordance with access rights set by the contents-oriented access controller (152); a file storage function (175) for storing image data used in that project desktop page (30) and document files stored in the document table (260) in an associated folder; and an archive compression function (176) for storing the project desktop page (30) and content of the associated folder in one archive.

6. The system as claimed in claim 1, wherein the database (3) includes: a project contents table (258) in which are stored lists of the projects and contents contained in those projects; a document table (260) in which are stored locations where document files transmitted via the bookshelf section (38) of the project desktop (30) are stored; and a document folder table (262) in which are stored virtual deployment positions in the bookshelf section (38) for document files managed by that document table 1260); and wherein the server includes: a search unit (161) for implementing searches, in response to operations at the user terminals (1), across the various projects, of contents (40, 44, 46) in those projects and of document files managed by the document table (260), and specifying contents titles or document titles as search results; a first project specifying unit (162) that references the project contents table (258) using contents titles searched out by that search unit (161), and specifies projects to which those contents belong; a second project specifying unit (163) that references the document table (260) and the document folder table using document titles searched out by the search unit (161), and specifies projects to which those documents belong; and a list transmission controller (164) for transmitting a list of projects specified by the first and second project specifying units (162, 163) to the user terminals, as search results of the search unit (161), in a condition of being linked to the project desktop (30).

7. The system as claimed in claim 6, wherein the list transmission controller includes functions for determining (C11) user attributes of users who performed the search operations for the specified projects, and for removing projects (C12, C14) which cannot be displayed to those users from the specification results.

8. The system as claimed in claim 1, wherein the database (3) includes a project user table (254), for each of the projects, wherein is stored a list of users belonging to that project; wherein the server includes a personal desktop generator (132) for generating an individual personal desktop for each of the users; and the personal desktop generator (132) includes: a list of projects belonged to section generator (132A) for referencing the project user table (254), when personal desktop display requests are received from users, and generating a list of projects belonged to section that displays a list of the projects which those users belong to; and a modification notification function (132B) that, when there has been a modification made to the contents of a project in the project list, adds and indication of the presence or absence of that modification to that project list section.

9. The system as claimed in claim 8, wherein the server (2) includes a project list page generator (133) for generating the project list as a project list page; and that project list page generator (133) includes a user name adding function (133A) that references the project user table and adds names of users belonging to projects to each of several projects respectively on that project list page.

10. The system as claimed in claim 9, wherein the server (2) includes a user list page generator (134) for generating a list of the users as a user list page; and that user list page generator (134) includes a project name adding function (134A) for referencing the project user table and adding names of projects to which users belong to each of various users respectively in that user list page.

11. A project management system to manage projects of users by project desktops and user attributes of the project substantially as herein described with reference to the foregoing description and the accompanying drawings.

SYSTEM AND METHOD FOR PROJECT MANAGEMENT
Technical Field
This invention relates to a project management system, and particularly to a project management system for
supporting project, related information management, Background Art
Conventionally, when a company is engaged in a project involving the development of a new product or advertising initiative, or a new research initiative is undertaken by a university or other research institution, the work of deciding the details of such projects is done mainly through the exchange of written documents or aurally in conferences. In recent years, with the development and proliferation of information technology, functions have been provided for holding electronic forums, managing the progress of groups, and sharing electronic document files. Project members make use of information technology, in conjunction with the carrying on of the project, to utilize electronic forums and store document files that share a directory specified by groupware.
In Japanese Patent Application Laid-Open No. A-8-30577/1936, for example, techniques are disclosed for maintaining the integrity of information on the manager side and on the person-in-charge .side when the project x.anaaer takes such discretionary actions as adding jobs or changing persons in charge. In Japanese Patent Application Laid-Open We. A--11 ~ 1439 12/1 999 , moreover, techniques are disclosed for using various indexes for searching document collections corresponding to electronic ior'j;r,s.
Unfortunate!y however, ;n the conventional.examples " ;-.1 <;-d ,-ii-;rvrt, statements and document, file's celatin-: -to1 a ' single prciecl mus-.. be -.uanaged using respectively different, software packages. -Also, when multiple projects are being
carried on in parallel, in order to store or read out necessary document files or participate in an electronic forum, the electronic location where such operations are conducted must first be searched out,-project by project.
When forums and document management are conducted project: by project, furthermore, because the participating members and their roles will be different in each project, there is a problem because user oriented access rights management becomes complicated and troublesome.
Disclosure of Invention
An object of the present Invention is to overcome the difficulties associated with u->; conventional examples, and more particularly to provide a system and method for project management that are capable of easily managing the registration and searching of information relating to projects.
Another object of the present invention is to provide a system and method for project management that, in cases where multiple users having pre assigned log-in' IDs participate in multiple projects within an organization such as a company or research laboratory, are capable of managing the sharing of information for each of the projects and supporting the management of project advance.
The present invention comprises a server connected through a network to a plural ;>.•/ of user terminals (or client computers) controlled respectively by a plurality of users, and a database wherein are stored contents belonging to projects, project by project, participated in by some or all of the plurality-of users.
The "server, , moreover.' ccrprises a,communication cunt, tv- ^ e I" i or trans;r.it ting a prescribed page to a user terminal and also receiving operation messages from the page or -executed buttons on the paae, ana .1 project desktop sheet
generator (PJ-DT sheet generator) for reading out contents data from the database in accordance with operation messages received by that communication controller and generating pages for displaying or accessing all the contents belonging to those projects, project by project, as project desktop sheets (PJ-DT sheets). The server also comprises an access controller for controlling communications with user terminals when there has been an access made via the communication controller for the content of the contents, in unit of project desktop containing these contents. In this manner the problems noted earlier are to be resolved.
The database, for each project, stores the contents belonging to that project. The contents consist of various kinds of data and files handled in that project, such as project title data, text data, list data, image data, voice data, document files, statements made in forums, scrap books, schedule data, update history data for information for each project, and chart data (member lists) for members belonging to that project.
The access controller, when content of the contents has been accessed, as in a contents content search, or a project access by user name when there is a member list, controls communications with the user terminals in units of project desktops including those contents. The access controller may also be configured so that it generates a link tc a project desktop containing the contents at issue, in situations where a project is retrieved. Or, .,:. a situation where a project has b~en specified, and the contents thereof are to be displayed, the access controller may be configured so that it causes the project desktop sheet generator (PJ-DT sheet generator) tc generate a'rroieot- desktop.
n-.e access controller, ^hen contents have been searched to; ex.f.nple, causes a project desktop title [PJ-DT title) ooma: inncj those oonu-u s to re displayed as the search
results. The display of that project desktop title can be made a link for displaying that project desktop. Or, when a list of projects to which some user belongs is to be displayed, it is only necessary to cause a list of project desktop names to be generated with that user name made the contents of the project. when a display instruction has been received for some project desktop, after (a) project desktop(s) has/have been specified from various entrances the access controller causes the project desktop sheet generator to generate the project desktop selected and specified by the display instruction.
The project desktop sheet generator (PJ-DT sheet generator) reads out contents data from the database and also generates pages for displaying or accessing all of the contents belonging to a program at issue, program by program, as project desktop sheets. Thus a user, using a project desktop, can view all information (contents) relating to that project, and can also input or register new information relating thereto.
For example, when a list c: project titles, the search results of a full text search of a document file, the names of contents disp". .-ayed on individual desktops cr the like user by user, or a project title that is one type of contents has or have been operated on so that such may be displayed, the project desktop sheet generator ;PJ-DT sheet generator) generates a project desktop in .-.'hich are aggregated the content.- belonging to the project, as controlled by the access controller. Thus it i.s easy to effect management, project: by project, in crder to register, update, or review dat:a '- ;:iles used !" a project, in units of project desktops" even-when iiuil t i.pl e project s are running in parallel
:v. the present: invention, the access control ler -performs centre; to cause the project ues,;u>p sheet generator to generate a project desktop when, the contents of a project
have been accessed, as in an access from a list of project names, a search of contents content, or an access by user name when there is a member list, etc. Thereupon, the project desktop sheet generator reads out contents data from the database, and also generates pages, project by project, for displaying or accessing the entire contents belonging to those projects, as project desktop sheets. Thus, a user, using a project desktop, can view all of the information (contents) relating to that project, or input or register new information relating thereto.
For example, when a list of project titles, the search results of a full text search of a document file, the names of contents displayed on individual desktops or the like user by user, or a project title that is one type of contents has or have been operated on so that such may be displayed, the project desktop sheet -jenerator can generate a project desktop in which are aggregated the contents belonging to the project, as controlled by the access controller.
In this manner, with the present invention, an outstanding project management system not previously available can be provided that can easily manage information project by project, for the purpose of registering, updating, and viewing data and files used in projects, in project desktop units, even when multiple projects are running in parallel.
Br.1 e: Description
rig. 1 is a block diagram representing the configuration of one embodiment aspect of the present invention,-
rig. 2 is an explanatory diagram, representing one example of a project desktop sheet usad in the embodiment v'': a i jgr.-unmed in Vig. l
Fig. 3 is a block diagram representing a detailed configurational example of the project desktop sheet generator (K'1~DT sheet generator) indicated in Fig. l •
Fig. 4 is an explanatory diagram representing a conf igurational. example, etc., in a case where contents are being searched, with Fig. 4(A) being a diagram representing a detailed configurational example of the access controller diagrammed in Fig. 1, and Fig. 4(B) being a diagram representing an example of a display format for search results;
Fig. s is a flowchart representing an example of project-related information management in this embodiment aspect ,-
Fig. 6 is a flowchart representing one example of a processing routine for generating a project desktop sheet (PJ-DT sheet) ,-
Fig. 7 is a block diagram representing an example configuration of hardware in this embodiment aspect, with Fig. 7(A) being a diagram of one example of server hardware resources, and Fig. 1 (B) being a diagram of an example configuration when the network is made the internet or an intranet;
Fig. 8 is a block diagram of an example configuration of one example according to the present invention,-
Fig. 9 is an explanatory diagram showing how the pages are to be connected according to the example diagrammed in Fig. 8 ,-
Fiq. :i (i is an explanatory diagram representing one example of a project desktop sheet in this example;
Via. 11 is an explanatory diagram representing a continuation of the project desktrp sheet diagrammed in .Fig
Fig. 12 is an explanatory diagram showing the relationship between user attributes and attribute-oriented access rights for a project in this example;
Fig. 13 is an explanatory diagram of one example of a data structure used in the configuration diagrammed in Fig.
8;
Fig. 14 is a flowchart representing one example of user attribute determination processing in the configuration diagrammed in Fig. 8 ,-
Fiq. 15 is an explanatory diagram representing a specific project desktop display example in this example; Fia. 16 is a flowchart representing one example of a project desktop display processing routine in the configuration diagrammed in Fig. 8;
Fig. 17 is an explanatory diagram of one example of a page for producing a project desktop in this example, with Fiq. 17(A) being a diagram representing one example of a page for project production and Fig. 17(B) being a diagram representing one example of an initial screen on the project desktop in this exampje;
Fiq. 18 is an explanatory diagram of one example of a text, entry page for inputting text;
Fig. 19 is an explanatory diagram of one example of a project editing page;
Fig. 20 is an explanatory diagram representing an example of adding A bookshelf section to a project desktop in this example;
Fia. 21 is a clock diagram representing an example co:u io,.rat i on of the save controller and search controller i ndicated in F ig. S ; .
y-,,.,. 22 13 an explanatory diagram representing an ex.r,,p -- ,v the di.H'-av of search r^^ults Cor 'document content or tlu- "ike in thi:-, example;
Fig. 23 is a flowchart representing one example of a search processing routine according to this example;
Fig, 24 is an explanatory diagram representing one example of saving a project desktop sheet in this example,
with Fig. 24(A) being a diagram of an example page for selecting the project to be saved and Pig. 24 (B) being a diagram of an example page for downloading a saved project desktop file (bookshelf file);
Fig. 2b is a flowchart representing one example of a save process in:; routine according to this example;
Fig. 26 is an explanatory diagram of one example of a project; list page according to this example;
Fig. 27 is an explanatory diagram of one example of a project list page according to this example;
Fig. 28 is an explanatory diagram of one example of a member list according to this example;
Fig. 29 is an explanatory diagram representing the general course of processes up until a project desktop is completed according to this example;
Fig. 30 is an explanatory diagram representing an example of accessing a project desktop according to this example; and
Fig. 31 is a flowchart representing an example of using the project management system according to this example.
§£J?t._Mgie -or Carrying Out: che Invention An embedment aspect cf the present invention is described now with reference tc the drawings. Fig. 1 is a block diagram representing the configuration of one embodiment aspect of the present invention. The project management pyst enr according to' this- embodiment 'aspect is a systeiv that .-> ,:ppo: '. s activities in units of member projects. This system .-cmp r i seo a server : tc, which are connected, by a net.wo.rV. b, a p".',: ra". ; I y of user terminals 1 operated
respectively by a plurality of. users, and a database (DB) 3 wherein are stored contents belonging project by project to projects participated in by some or all of the plurality of users.
The server 2, moreover, comprises a communication controller 4 for transmitting a prescribed page to the user terminals 1 and also receiving operation messages from the page or executed button on the page, a project desktop sheet generator (PJ-DT sheet generator) 10 for reading out contents data from the database 3 in accordance with operation messages received toy the communication controller 4 and generating pages for displaying or accessing all the contents belonging to those projects, project by project, as project desktop sheets (PJ-DT sheets), and an access controller (or PJ-DT oriented access controller} 12 for controllina communications with user terminals, v:hen there has been an access made via the communication controller 4 for the content of the contents, in unit of. project desktop containing those contents.
20 The user terminals 1 are computers such as personal computers, or portable terminals 1A such as portable telephones. These user terminals comprise displays, and display pages written in a page description language such as a markup language (ML, HTML or XML). The server 2 generates this page information (ML pages), and transmits the same to the user terminals l via the communication controller 4. The pages generated by the server 2 comprise user interface such as execution buttons for operations, such as edit buttons setting buttons, and links. The users manipulate the edit buttons and ! inks -me the like on pa.-es transmitted from the serve- ~ to . ,11 spl .iy new pages, iiplcad or download-document ir.e?,-, -ind e::eri vM.-icus sev.unos relating to access rights and Liu- o i splay , ei u .
The network b is an information transmission medium such as the internet, an intranet, or a dedicated intra-organizational network or the like. The communication controller 4 consists of hardware and software for controlling communications between the user terminals 1 using a prescribed communications protocol. The server 2 is a computer for executing the server software.
The project desktop sheet generator 10 constitutes a portion of the functions of the server 2 for generating various pages. The project desktop comprises sections such as a member list section 42 that is a list of project members and a bookshelf section 46 that constitutes document managing contents, as diagrammed in Fig. 2. In this embodiment aspect, this project desktop is produced for each project. In this system, contents necessary to a project are input or registered, and contents search results are displayed, in unit of project desktop, as diagrammed in Fig. 2.
In this embodiment aspect, when access is made to contents via the communication controller 4, the access controllei 12 controls communications with the user terminals 1 in un.it. of project desktop that contain those contents. The access controller 12, when contents contained in a project are accessed, generates the project desktop containing those contents, and also displays a link. The access controller 12 also controls write or read access for each user to i.he project desktop overall, based on access right.., established in project desktop units. Thus the unified management cf information pertaining tc projects is made possible, and, even 1:1 cases where multiple users are - partic ipat i:r,i in many projects, users can easily access necessary information while the: access rights to- information pert a i :i i :i j to the project? are be i no- controlled;
A:i nun. • -;.:ct ion to access contents is transmitted, for ex.-imp"!-. , v.l-.e:! a: i <-:: j t butt, on or link or the like has been

clicked on at a user terminal 1, from that user terminal 1 to the communication controller 4. The generic term execution button is used here for the control operation displays, such as the edit, buttons, operation buttons, and links to other pages, that are displayed on the project desktop and in the contents sect i ons .
Links to other pages effected in HTML, for example, are execution buttons. By these execution buttons, other page names and program (script/ names for driving the server 2 are defined; the communication controller 4 receives those program namer; and necessary values and inputs them to the server 2. In the server 2, when an access is made to project contents, the access controller 12 responds. At that time,1 the access controller 12 causes the project desktop sheet generator 10 to generate a project desktop such as that diagrammed in Fig. 2, for example.
As indicated in rig. 2, a project desktop 30 contains a plurality of sets of contents. In the contents are contained such items -is the project title, the text section for managing texts representing particulars of the project, the member list section 42 for managing the member list 42 that lists the members participating in the project, a forum section 36 for managing a forum 44, a bookshelf section 38 for managing various kinds of file groups 46, a scrap book section (not shown), a bulletin beard section (not shown), a schf-cr.'e o: oalenc . — CL^C:: 'not shown' for managing the proje...-! 3..-h~dule, and a muln. text section for managing texts, graphics a:io files , ncz she .•.;-:'• . :.:i the calendar section, provision m.-w be m.ide for cav.sina the project calendar tc intei^'t '.vith calendars for each ;:3er. These vari cus types pi" tv<:n r-.u •: sections ar? aa.-^d to rhe prc-ject desktop by .the pjc-.ic-.-!. ':-;«,::e: ov .rexbers. -:ach .-.-ntents section is an inner w i ndo'.v in ,-i project, desktop sheet.
The project desktop sheet generator 10, when it generates a project desktop, reads out contents contained in that project desktop from the database 3 and generates contents sections. Then, each contents section is synthesized in a single-page sheet as diagrammed in Fig. 2 and that is made the project desktop 30. Thus the project desktop sheet generator 10, as diagrammed in Fig. 3, comprises a text section generator 50 for managing text for making summary descriptions of the project, and the like, a member list section generator 52 for generating, as contents, a member list section for T.anaging a list of members included in the project, and a forurr. section generator 54 for generating a forum section, as contents, for recording or displayina the statements or replies of users, in accordance with user attribute-oriented access rights managed by a contents--oriented access controller.
The project desktop sheet generator 10 also comprises a bookshelf section manager 56 for managing, as contents, both the bookshelf section 38 for registering or downloading document files, and the document files 46 registered in that bookshelf section 38, in accordance with the user attribute-oriented access rights managed by the contents-oriented access controller 16.
The project desktop sheet generator 10 may also comprise a scrap book section manager 58 in which to paste news articles and images and the like pertaining to the project. These 1'auctions may be made so that they are sequentially provided in conjunction with the course of the development of the protect management system. In an example wherewith the pro.)ecL desktop title is appended to a personal desktop or
-,,,.,( rhe :neiri-er list 42 becomes mandatory. It is
be- tev^i, moreover, that the bookshelf section 38 plays a
:11,uoi :ole in supporting project activities. The various
,.,.,.,.,,,-, .motion generators SO, '.>:: 58 add operation or
execution buttons such as the edit buttons 31 indicated in Fiq °. or links, etc., to the sections in accordance with prescribed access rights, etc.
In the example diagrammed in Fig. 3, the project desktop sheet generator 10 comprises an access rights registration manager 59 that, when the various contents are generated, prompts the user doing that generation operation to set the use1- attribute-oriented access rights to those contents.
v.'r.en the edit buttons 31 indicated in Fig. 2 are operated, the server 2 transmits a page for making additions to the content of the project desktop or the contents sections, or display-related settings and the like, to the user terminal. By creating such a project desktop as this f0r each project, the current status of a plurality of projects can be recognized at a glance. In the example diagrammed in Fig. 2, furthermore, there is no need to v-intlv use multiple software packages in order to conduct work relating to a project. A new file can be registered in the bookshelf section 38, for example, and a summary thereof ,.v. .]-.. like given as a statement in the forum 44, so that the contents sections are used in an integrally associated fashion and not as individual functions. That being so, it is possible to concentrate on the work required in advancing the prelect, without needing to spend time in switching or stav-t-i-10 up software, or in retrieving a suitable location or
the "ike.
•••;•---eover, in .;eneratin.; user-oriented pages (called here person.-.: desktops'', and in displaying search results after searching for objects that are the content of the various -o-ite-us (si;cr. as .:i project title, member name, full text of 3 ,-;,-v- T->nt •>--" i ste red in the bookshelf section, or a
, „.,-.]( if ^ u- in i :oru:i'> , those operations are not based on t be several contents, but are performed in units of project ;,. .-:'„• t o :•••-; like that diagrammed in rig. ?,. Thus, because it is
possible to specify the project to which the contents belong that came up as search results, it also being possible to effect processing so as to continually display a list of projects to which that user belongs on his or her personal desktop, it becomes easy to access information pertaining to those projects.
Thus, in this embodiment aspect, when an access has been made to contents, the access controller 12 controls communications with the user terminal 1 in units of project desktops containing those contents. The access controller 12 also cause:; the content, of contents to be displayed in project desktop units, not only when a project desktop display instruction has-been effected, but also when those contents have been searched for, or when a list of project titles is displayed, or when a list of users is displayed, or when a personal desktop is displayed, or otherwise when access is made to such contents as a project title or member list. In other words, when a display request or search has been made using information, relating to a project, already registered as a key, the access controller 12 causes such information to be displayed on the basis of a project desktop diagrammed in Fig. 2. In a preferred embodiment aspect, this project-desktop-based display also comprehends cases where the project desktop title is displayed as a link-based opera t ion but ten.
In this embodiment aspect, the server 2, as diagrammed in l-'ig. 1, comprises a project-oriented user attribute detector 14 for determining user attributes for projects, of the leader: or a member or the like of a project, which are set for users .project by project, and communicated via the communication controller ~, and the contents-oriented access c-oni ro" 1 er 16 that is for ronl re". : : ng the content of • operations on a p:rjeot desktop based on the user attributes dt'i e nr, i ned by that project oriented user attribute detector
14 and on the access rights for each user attribute predetermined for each of the sets of contents for the
projects.
The user attribute is a user role for a project, such, for example, as that of a log-in user who has logged onto the server 2 diagrammed in Fig. 1, or, when a certain project is in view, that of a member participating in that project, or that of a leader who, among such members, plays a central role in that project. For example, a certain user might be a member in project A, both a member and the leader in project E, and a non-member, non-participating log-in user in project C. User attribute/ are set for each project. With respect to users during a session communicated via the communication controller 4, as concerning a project; which a user tries to access daring that session, the project-oriented user attribute detector 14 determines the user attributes, such as leader or member c;r the like, for that project, which have been set project by project beforehand.
Also, in a preferred embodiment aspect, user-oriented access rights are set for each set of contents of a project. The setting of these access rights, moreover, is not made by user name, but rather on the basis of user attributes. Accordingly, settings are made for members, such as to allow reads but disallow writes, for example, whereupon any user, so long as he or she is a member, can use those access rights. Thus, by centre]]!-:: the access rights to the various contents on the basis of project - oriented user attributes, it becomes easy to se^. access rights, and the setting and use of such > ights is made easy to under stand by project pa;•!. :c i pants and information registering parties. Thus a propel :e:^der i r; Vo> to trance viooess rights i':v .i definite •:,,:ne' '.-.• i i.h.o-..: V pe-orming onercur- operations.
I'!:,' contents oriented access controller 16 controls the -••:H;--H o: op-Mt • ,-:i3 done en the project desktop, bas-i'fis.7 coin roller 16 cont: X s thf access, to' contents sections bv ;:-'.<:'• .-it l rib1..! e, ;;peeii i.\:t'. . y by li'miting t_he functions of the eri; I buttons U indicated in .-'.ig. 2, operation buttons, O! pj cii-u'-t i on h •. :t I •.•".! :* or '.. ':'•.- 'ike. 1'hus user attribute-
oriented security management is made possible that does not involve setting access rights for each individual file.
In a preferred embodiment aspect, furthermore, a save function for saving a project desktop may be comprised. In the example diagrammed in Fig. 1, the server 2 comprises a save target, selector 18 for setting one or more projects of a plurality of targets as save targets, an archive file upload manager 20 for archiving the contents included in the one or more of the project desktops set by the save target selector 18, in one archive Pile, and an archive file download manager 22 for transmitting an archive file archived by that archive file upload manager 20, i.n response to an operation at a user terminal, to that user- terminal.
In this exaa.p.e, saving is dene in project desktop units in uhe course of p.--eject advance and at the completion stage and the like. By saving in units of project desktops, a project desktop can oe used to make an announcement to the outside, and all information pertaining to a project can be saved in one place. When this saving is done such that information is saved as page information using a markup language, a home page can be effected to the outside by registering that project desktop on a web serve:'.
In the example diagrammed in Fig. l, moreover, because the file group 46 accumulated in the bookshelf section is saved i.n an integrated manner, files pertaining to the prciect desktop are archived. This archiving is particularly us?" v.l when there is a bookshelf section 33. That is, the archive: file uplcai manager 20 archives the cc:r.e:rts (:•: •".'.-.- s i ned in one ;:v more project desktops set by the save t.i.vet ,::; rt : e- v I.. o r '. ::-, i-:i one archive file. When a single .p ; „- - tV-t. de.vk! op ; .-•• t •.:• be saved, f cr -" example , a vage ,--. •• * :;i:v.;i I hi: '•-.:•: -i 11 pro;-ct deskt.op, a pa^e • hat ,-•,.-, \\<~~[\r store;-- : n .it .u e:\~eni s and the 1 ike document: ! •. lr":-, held in t'r.e ::<')ok5hel : section 38, and i'.r.av.e files and
the like used in displaying the project desktop are archived in a single folder. When that is done, the archive file uploa.; manager 20 rewrites a link to a page wherein the document files, images files, and/or statements and the like are described. In a preferred example, the archive file upload manager 20 may comprise a compression function for compressing archived files.
'['he archive file download manager 22 transmits archive files archived by the archive file upload manager 20 to user terminals in response to user terminal operations. Such transmission may be done by rendering an archive file into a downloadable condition and then prompting the user to effect a download operation, or by saving that archive file on a floppy disk and sending it by mail.
rig. 4 (A) is a block diagram representing an example case where various contents of multiple projects are searched i..:ansversely. In the example diagrammed in Fig. 4 (A) , the access controller 12 comprises a contents search function 60 for searching one cr a plurality of sets of contents containing data that match data entered at a user terminal, a project identify function 62 for identifying the projects to which the .several -intents searched by the contents search function 60 belong to, and a PJ-DT list transfer function 64 for transmitting a list of project desktops of projects identified by the project identify function 62, to user terminals, as search results.
The contents search function 60 performs ruli text searches and the , i-;e of text in a text section, statements i:i a- forum, and document files registered in the bookshelf section, for: example. The project identify, function 62 ident i:'icjs :» project tc which certain contents belong, namely •cnt-:;!;-; ;;:M : o!>-d o; the content s-sea r:oh function 60, from those content.:-1, o: • : om the- elements configuring those contents. And t.he PJ-DT 1 i ;u. transfer function 64 transmits
a list of project desktops of projects identified by tne project identify function 62, to user terminals, as search results. Ki.g. 4 (H) is an explanatory diagram of one example of such search results. Here, a project list 68 is displayed that has a document file containing the text characters AAA. The user, from these search results, can access both that document file itself, and the project, desktop that is a list of information relating to the project wherein that document file was created. By displaying the project desktop containing those searched contents, it becomes easy for a user to acre.-:.-: information exhibiting a high correlation with the search target, and also easy for that user to comprehend the process by which that document file or text data were created and the purpose for such creation.
-ig. 'j, is a flowchart representing an example of project-related information management (project management method' with the configuration diagrammed in Fig. l, etc. in the example diagrammed in Fig. 5, the project management system diagrammed in Fig. 1, etc., is used to support the generation and management of project-related data. First, the contents contained in each project are registered, proje-.-f by project .'step SI: project - cri ented contents registration step). Following that, when one or a plurality of sets of registered contents have been searched or accessed by a -.v.ember belonging to the project (step S2), those several con ten i.._. or a list of projects including that member is genera led step So: project list ^-^rat ion step). Then, when :. proie.M. display request has been made by a user in respc:.:;-.' u~. the project list generated by the project list gener ;''i on .step So, a page icr displaying or accessing all contr-'HH ccv.n.alne.:. in that, 'prelect, ;s generated as a project do-:;'-.1 ; ' :-.'. -T s- : rr~°t—t- •ies'-.top -T-'iera t i on step' .
There are two cases for an access which will be the object of generating a project list in step S3, namely the case where one or a plurality of sets of registered contents .have been searched, and the case where access has been made concerning members belonging to a project. The display of a project desktop list resulting from members being accessed includes, for example, cases where the titles of projects to which members belong are displayed when a member list is generated, cases where a list of projects to which a certain user or users belong is displayed on user-oriented desktops, and cases where a search was made with a specific user name, etc. Oc:il.&riL3 are searched in the same way as in the case diagrammed in Fig. 4.
','ig. 6 is a flowchart representing one example of the project desktop (PJ-DT) generation process S4. in the project desktop generation step S4, as diagrammed in Fig. 6, first, the log-in ID and the like of the user who made the display request are identified [step Sll), and, following thereupon, the user attribute is determined to establish whether or not that user is a member of the project in view in the display request (step S12: project-oriented user attribute determination step). Then a display and an ;;jje:ui. io.. are determined for allowing that user access to the several contents according to the user attribute-oriented access rights predetermined for each set of project contents requested to be displayed and to the attribute of the user who made that display request .step S13: contents-oriented right;; oeterxina t .i :::i step1.. Then, the contents sections are generated 1:1 accordance with the rights relating to display and- operations- determined in that contents-oriented rights de terminal. :,?•., step, and a -ag.e wherein those-contents secM.;:.:u; ,.v . ate. /=: aten : == .ienern.ee as -a ptcject desKtop
iat crated p,-jge generation stepi
In step Sll, log-in IDs and user IDs and the like in the session are fetched from the system. In step S12, from such user ID or log in ID, the user attribute of a leader or member or the like for the project for which display is being requested is determined. Display requests include cases where a link to a project desktop based on the project title has b-en operated, as well as cases where the project title is displayed as search results. In a particular example, for instance, in a case where a project leader has completely prohibited access to the project desktop by anyone other than a member, provision is made so that no link to that project desktop is displayed even assuming that a search has been made in the contents or the like.
In step S14, when a project desktop is actually generated, the Generation of the several contents of the project desktop is controlled in accordance with the user attricute oriented access rights determined for each project and for each set of contents. In step S15, the project desktop is generated, by integrating the contents sections generated in step S14, and by, for example, synthesizing the first page of all of the contents.
- Th-,.::;, by the project activity support method based on this embodiment aspect, information is registered and viewed in units of project desktops, and security management is implemented by setting access rights based on user attributes for ev..-h project and for e v.-h set of contents. Thus, even when :v..i!ti.p:e projects are being run in parallel, information necess.'iry to each project can be easily registered and viewed while .-cntro"; ling access rights with simple operations
--'.-;. '-•' >---.' is .M olcck 'diagram of an example configuration of ha .:w.-i re ••eqour.-es in this embodiment aspect. As diao' •. vii'.e.-i in rig. ';A>, the server 2 in the project mana--.. vm system .-iccc r.ii :KI to this embodiment aspect comp: '.it',-; hardware resources that include a CPU "0 fa-

performing arithmetic computations in accordance with a prescribed program, a main memory unit 72 for providing the CPU 70 with memory area, an auxiliary memory unit 74 such as a hard disk, and a disk drive 76 for reading data and programs from A memory medium 78 such as a CD-ROM, as well as a display device and input device and the like (not shown). In the auxiliary memory unit 74, contents content, and information relating to user attribute-oriented access rights set by project, are stored as the database 3.
The CPH indicated in rig. 7 (A) executes a project activity support program, and thereby the server 2 indicated in Fig. 7(A) functions as the project management system diagrammed in Fig. 1. The project activity support program is contained in the memory medium 78, and is transported to the disk drive 76 of the server 2. The CPU 70 controls the disk drive 76 and installs the project activity support program contained in the memory medium 78 in the auxiliary memory unit 74. Provision may also be made so that the project dctivity support program, in whole or in part, is downloaded from another server via the network 5. in addition to a compiled program, the project activity support program contains a script for driving the database and generating prescribed page data as well as image files and the like needed in producing the page data.
Tl>- project activity support program comprises the following instructions as instructions for causing the CPU 70 of the server 2 to operate. Specifically, a project-oriented rontentr. re:; istrat ion instruction that causes contents contained, in projects to be registered project by project, a 'project 1 iiu. generation in 3 cruet: ion for causing a.list of project:--' 1 o be generated, .../hen c:ie or a plurality of sets of registered uontem .:-; has be-:: marched, or- access has been r..i ".I.•-.--. iing -rcM-iier^ be", .-no ing to a project, which iiu-lude.-. those ,-o:u ents or r.eir.L:^: s, and a project desktop

generation instruction for causing a page to be generated as a project desktop, when a project display request has been
made by a user based on a project list generated by the server in response to such a project list generation instruction, that page being a page for displaying or accessing all of the contents included in that project. The CPU 70 implements the processing diagrammed in Fig. 5 by executing those instructions. Furthermore, by having the project desktop generation instruction comprise instructions corresponding to each process step indicated in Fig. 6, the CPU 70 will implement the processes indicated in Fig. 6. Furthermore, by having the project activity support program comprise instructions corresponding tc the parts and functions indicated in Fig. 1, etc., the server 2 will operate as the prelect management system diagrammed in Fig. i, etc.
When the language "instructions for causing the CPU to operate" -is used here to operate the CPU 70 or server 2, one or both ot: two types of instructions are in view, namely instructions that by themselves cause the CPU 70 or the like to operate, and instructions that cause the CPU 70 to operate in dependence on a database management system (DBMS) or an operating system (OS) stored beforehand in the auxiliary memory unit 74, or the like. The "project-oriented contents registration instruction," for example, in order to cause contents contained in projects to be registered by project, may be only an instruction for generating a registration page and p.i;-..-:'i n-; 'hat ;;;;-.lerated page tc a program controlling commt::! u~vu j c:is wi.Lr the. user terminals 1. In that case, there v, i 1 1 be case:- v/here all of the programs required for rey i ;-;' •-:' i.ri ' 'O'-iterv. s by prciect are :vot contained in the :]ien:o: •. 'iv-ii :-.. v '"•!, ,'^t cr.ly .-; proqr.v.i for aenera t1 :K: reqi;-' :.ii..;.-;: paqi-:? : .-• rent .a L r.ed the-.v. ; n . These options are
determined according to the relationships with the operating
system in the server 2.
In the example diagrammed in Fig. 'I, moreover, a single server 2 and a single CPU are provided, but one server may be provided comprising a plurality of CPUs, or provision may be made for dispersing the load over a plurality of servers. File management may be conducted, at the server by making the access rights for contents data by project only a root (super user), causing the program to operate by root rights, and effecting actual contents-oriented security by edit button functions or: the like. Also, if the database 3 is under the control of the server 2, then that database 3 may be created by other computers or in ether disk units.
Fig. 7(B) is a block diagram of an example configuration of the server 2 when the internet is used as the network. This server 2 comprises a web server 80 that controls communications by http, a ^B manager 82 that issues SQL text and the like to the database following a script input via the web server and returns search results as part of the page information to the wee server 80, and a database (DB) 3. The server 2 may also comprise a mail server 84 that does such tasks as transmitting electronic mail to the user terminals 1 under the control of the web server 80 or the DB manager 82, automatically responding to received electronic mail, and register ing the content written in received electronic mail to the DB 3. V.'ith the example that comprises the mail server 84, it is possible, when a predetermined change has occurred in a project desktop, for -xatrple, to perform such tasks as transmitting electronic T_~ • 1 tc affected members, to effect registration'10 a bookshelf section with electronic -mail .including a:i attached file tc set electronic mail addresses for each proioot de^'r-.i.cp, or co accept questions concerning a
ror ',.:-.;•• outside, et o . Provision may also •••••'- '.'l-=i]l •; v:rrr ions to make it possible tc
send and receive electronic mail to and from log- in users from within a web page. In that case, the web mail functions should be made accessible from personal desktops.
..... Overall Configuration ----
Examples of the present invention are described next. Fig. 8 if-; a block diagram of an example configuration of one example based on the present invention. In a preferred example, a page generation controller 130 for generating pages for project desktops and the like, a document management unit 140 for managing documents, an access cont: •;! Lft ••" ISO for • -.nag ing access rights that accord with project -ori ented and contents- oriented user attributes, a search controller 160 for controlling searches of project contents, and a save controller 170 for controlling the saving of project desktops are comprised.
In this example, in particular, the server 2 comprises a communication controller 4 for transmitting prescribed pages to user terminals and receiving operation information for those pages, and a project desktop sheet generator 131 for reading contents data from the database 3 in response to the operation in forma ti en received by the communication controller 4 and generating pages, as project desktops, pro j eel by project, for displaying or accessing all the content:', belonging to those projects. This project desktop sheet generator 131 comprises functions for generating a project • if-oktop 30 cf. . Fig. 1J) that contains, as contents, a text sect ion 32 : ..• r displaying text 40, a forum section 36 for recording and displaying ..ser statements 44, and a • books're1 : sr.'Lion-"- for m.jnaj'ing f-iles 46 transferred from user3. '. :i this ex-, vple, bf-cai.se the forum section 36 and the book.-;!::-.; .••--••' t ion • :; are p; cv ided in a project desktop that
project can be managed integrally and easily, without having to switch so f t wa r e .
Fig. 9 is an explanatory diagram that represents a typical connection scheme for the various pages. Diagrammed here is the overall configuration (total package) in a preferred example. Advantages arising from relationships between the configuring elements are described individually. First of all, from the top page of the project management system, a user- is ,hle to access a project list page 100 for displaying a list of projects, a user list page 101 for displaying a list of users having log-in IDs, a search page 102 for searching project contents, a save page 103 for saving one or a plurality of project desktops, and a personal desktop page 104 that constitutes an individually oriented page for log -in users. These can also be accessed from a project desktop.
In the pages 100, 101, 102, 103, and 104 are provided links to project desktops. In the user list page, for example, the titles of projects to which the users belong can be incorporated as links. By making contents search results the project to which those contents belong, that becomes a link to the project, desktop. Even when saves are implemented using the save page 103, project desktop titles are displayed for selecting projects. Provision may also be made so that, in the personal desktop na:,-e 104, a list of projects to which that individual belongs is displayed, and, when that project desktop is updated, the fact that that personal desktop page 104 war-: updated is di si; laved.
l-'"0:i' >-hrJ t--oie,-r list page 100, a project add/delete page 110 can be redd out in order to add a new project or deleir a:i -x > si i :iq project. etc. Provision may also be made so th.il , 1:1 the persona: desktop page 104, a web mail page
<••-(,:
>-.i:'e>d ,:P for ;r.a;iag.i:u, web mail. Various types of
pages may also be provided that are oriented toward visitors havinq no log-in ID or systems managers or the like.
In the project desktop "id, as described earlier in terms of an embodiment aspect, a text section 32, forum section 36, and bookshelf section 38 are comprised. In addition, a table of contents flection 33 that is a list of titles of contents in a project desktop, or a member list section 34 that is a list o: neiv.bers belonging to that project, may be provided. In thi.; example, these contents sections are produced by project leaders and, when permitted by a leader, by members, ••in. 10 and 11 are explanatory diagrams that represent one example of a project desktop in this example. A summary description of the functions implemented in this example will now be given while referencing the graphical user interface diagrammed in Fig. 10 and ll. The specific techniques for implementing these functions and the data structures and the like used in conjunction therewith will be described subsequently. The project desktop, to begin with, has a project title 201. In this example, there are three display stages available as contents section display formats, namely a ..;.;!. .;./.- "full display (full size)," an "abbreviated display (n.=i:ne only)" that displays cnly the names of contents and not the contents themselves, and an "intermediate display (scroll)" that is intermediate therebetween, causes displays in a slightly smaller' display area, and adds a scroll bar (not /u.Gwru to the contents section. The titles of the displ^v .nodes will be different for different contents. For a te:-a .u-ction, for example, these titles are made "full

none," while for a forum a-v:'e frame (expand)," "small one." •
.e- prcviect desktop has an expand •:uirety of the several contents t.h.-st : :v. ieot u:'skt-0[>. and an omit button 203. for
causing a display, conversely, where content is omitted. The project desktop sheet generator 10 controls the drawing of the contents sections in response to operations of that expand button 202 and omit button 203. A desktop setting button 204 is an operation button for generating a page for setting a desktop. With that desktop setting page, such tasks as new contents generation are performed.
H>ich set of contents comprises a title therefor, a displ^v format selection list 207 for selecting the display format, an edit button 2,06 for causing a page to display for editing the content and the like of that contents section, a link button 205 linked to the head of the project desktop, and the content of thos.e contents. In the example diagrammed in Fig. 10, a table qf contents section 41 displays the titles of each contents section according to a "one column list" designation. The title or the text section is "project content," moreover, and a description of the content thereof is registered using text data. The registration, updating, and deletion of these text data are performed with a text data edit page that is displayed when the edit button is operated.
In the member list section 34, two leaders are registered, namely Makoto Wada, the first ranking leader, and Yuichiro Yamada, the second. The addition and deletion of members are performed with a member edit page that is displayed by that edit button. In this example, the member of the first rank is made the leader. A leader has the authority to determine access rights to each contents section. This r.inkinq can be edited using a member list edit page that is caKed up by a member list section edit button.
. ::i the r-orum ;;e."t ion ?6, the display format far the. forum it-nr'-r is i mri ~;re;H.~,: with 3 display format selection list indic,iU--d by t l-.r- :.;y;r,m'. rO'/ wh i ". e the statement display form.!', is i-v.p I e:r.eiu-ii by -.-> statement display format selection
list 214 indicated by the symbol 214. Also provided are a new button 212 for causing a page to display for making a new statement., and a search button 213 for generating a page for searching statement content. For replying to a statement, provision may Le ;r -j'ie so that a reply button is deployed in a page i or displaying statement content. A setting button 211 is also p-'ovided fcr activating a page for performing various settings p-rlainan^ to the forum section 36.
['he :orum contents 44 comprise a forum control area 44A wherein various operation buttons are deployed, a notice displav a -\?a 44B for displaying text for communicating information relating to the forum to users, and a statement display area 44C for displaying the titles and content of statement, content .
As diagrammed in Fig. 11, the bookshelf section 46 comprises .1 d^j-'i.ent management control area 46A, and a document file name display area 46B for displaying file names of docir,r,si!it files actually registered in a virtual directory structure. This virtual directory structur in which the project desktop is made the root directory, within a plural -i t v of folders is defined hierarchically-is for mana:,; ;-,:: ,.K;O...:: =nt files according tc document type and so forth. The display ;ormats in the document file name display area 4gH follow tl r •, -lection made with a display format selection list 2: i'he ^.ize of the display in the bookshelf section is ixpleme: ri using the display format selection list :'.''•• indicates > pig. 11 by the symbol 207.
• ••, t .=>. -md addin-i member lists to each project desktop based on lists of members belonging to projects contained in the project user tab - 254.
in general, it ./ill be a leader who adds a contents section to a project desktop. And, when producing a contents section, "> prompt is made to specify the access rights for that new1-.- produced -:on,tents section. The initially set (defa.-Vti access rig'u'.s may be displayed, for example, so that a selection thereof can be made.
In order to limit the access rights to an entire project desktop, moreover, the database 3 may be provided with a project table 252 wherein are recorded user attribute-oriented access rights to Lhe entire project desktop, and the server may be provided with a project-oriented access setting unit 153 for setting access rights to that project desktop based on user attrib .u.es determined by the project-oriented user attribute detecLor.
Fig. 1.2 is an explanatory diagram showing the relationship between attribute-oriented access rights and user attributes for i project in an example wherein an internal network in ;* company or university or the like is used. In Liu's examp". e, users are classified into system managers, project U'J lear.ers, PJ members, registered users (i.e. •ir.ers having '. 7 •. i n IDs), a^d general visitors having •no lo.;-. i :i "". Projer' :ie?-;Lop "lists and member ..lists can be di sp1 rr/e.:. i r- all user.. >;-r an entire project desktop, the svsle:r n\,-.:. i^er .rmd i .-. - !V ". :-:.=ider are fixed at t l-.e

modification enabled (full access) ((o)) security level. The PJ leader and system manager can set the project desktop access ri.ihts for P.; members. There are three settings possible. namely updating enabled (write) (O) , display enabl • i - id) (A), and display disabled (none) (x) in the example diagrammed in Fig. 12, general visitors are mandatori". y disabled from updating.
"i-.e system manager and PJ leader can also modify access right.; sellings for contents, being able to make settings by user attribute according to the contents section, such as disab: ing such operations as downloading and copying in the bookshelf section. As diagrammed in Fig. 12, in this example, no ao-ess rights are determined for any particular user having a personal leg in ID. Access rights are determined solely according to the roles played by users in a project. Thus ^ PJ leader is able to perform adequate access management without performing onerous setting work, Furth--• ".re :-^, there 13 no need to reset the access rights even when ". og-in users are added or deleted, or members are added to 01 removed from a project, etc.
rig. 13 is an explanatory diagram of one example of a data structure used in the configuration diagrammed in Fig. 8. The data structure diagrammed in Fig. 13 represents project activity support dai a used in the project management system diagramed in Fig. ?. These data are stored in a hard disk, for trXciT.plfc, and cc:,stitute a database. The project activity suppo • -i.it:--. comprise sue!- user information as user IDs, log-:in '•;--'- :-''^3, log- i passwords, and user contact information i'oi ^ p. .r,,: ily of 3f,!'s, together v. i th a user table 250 where.-, those pieces of information are respectively stored. il' _ by v-he contents-oriented access cc:it:v-'. 7. •-•• '.'::"!, • and - i sy::' hes: s control function 131B for sviu.ht--:-; i .' i ".•: and con'.. .•;.>• ~ : :wi t lu- contents sections drawn bv
the contents section drawing function 131A, in the order of the contents order data, as a single-page project desktop.
The contents section drawing function controls access by making settings to en-ible or disable the use of contents section edit buttons arid the like in accordance with the access rights, and also draws the content of contents as portions of a page, in the display format set with the display format selection list 207 or the like. The synthesis contro: function 1313 produces a single-page project desktop by synthesizing contents sections in the order designated in the contents order da1..a. Provision may also be made so that the synthesis control i ,notion 131B, after contents synthesis is complete, transmit-: that project desktop to user terminals Or provision 'nay be - ,de so that the synthesis control function 1MB sequentially generates contents sections in an order following the contents order data, and transmits contents sections piecemeal, after the generation thereof is complete, to the user terminals 1. These contents order data can be modified or ^plated with a desktop setting page that is displayed by the ~;oeration of the desktop setting button 204. f.n general, su.:h updating is performed by the leader. When : ::•- It-ider is al'owed to write member access rights to the project desktop, r,e:r.bers can also edit those contents order data. These oDitents order data are constituted as one set LOL" each project "D. However, with respect tc the contents in one project desktop, provision may be :r.ade so that, in oases when- .-/hat various members are interested in
ontent ^ order data are defined for each member, s a f: :.;ch.n:~t tep;:eser;ting one example of a
dete." r i nat ion processing routine in the -i i aqi _-! r; e.',i In rig. 8. The processing steps
di.i-:: •. :-:n-->'i ;'' :•'i g . . • jo:\r,t i.tute tl~.br detailed operations o'f t_hr: t jt'c: M lente: isev attribute search unit I1-', indicated
In the example diagrammed in Fig. 14, first, the user ID of a user in a session making access to a project desktop (PJ-DT) is fetched from the system (step Al). Following that, a determination is made as to whether or not this user is logged in (step A2), and, if not logged in, that user is determined to be a general visitor as diagrammed in Fig. 12 (step A3) . If that user- is logged in, on the other hand, then the project user table 254 is read out on the basis of the project ID of the project being accessed (step A4), and a determination is made as tc whether or not that log-in user is a. member of that project (step AS) . If not a project member, he or she is determined to be a registered user as diagrammed in Fig. 12 (.step A6) .
If that user is ..a project member, on the other hand, user order data are read out from the project user table, and a determination is made as to whether or not that user is the leader of that project by determining whether or not the rank data for that user are l (step A7). if not the project leader, the log-in user in that session is determined to be a project member (step A8). If the rank data are 1, then that user is determined to be the leader (step A9). By this flowchart diagrammed :.n Fig. 14, the user attributes of users accessing a project desktop are determined uniformly.
Fig, 15 is an explanatory diagram of a specific example of a project desktop display in this example. In the example diagrammed in Fig. 15, the project desktop is displayed with a browser for displaying HTML pages. In the upper portion of the project desktop are fields for entering the user name and password, and (that i .3 where log-in and log-out operations are performed.
"Home'" is a lin< to, the hcxe page of the project management system. "Project list" is a link to the project list paye 10) diagra.n:r.ed in :-jg. 9. Similarly, "user list," "persona1. dr-.V-ucp," i.id "-rare):." are, respectively, links to
the user list page 101, the personal desktop page 104, and the search page 102. In the example diagrammed in Fig. 15, research being done on ~> certain subject in a research laboratory in a university constitutes the project.
In the example diagrammed in Fig. 15, in the text section 3:> that provides a summary of the project, a summary of the co:T ent of thi research is written by the leader. The members a\:e made up of a researcher (in an electrical engineer! v; researcl 1 a':,oratory) who serves as the leader, an overseein; instructor, personnel working in the same research laboratory, research^ rs //ith a cooperating company (Dolphin Net), and resting assistants. ^.A the like. In the forum, which has been named the Question Box by the leader, such thing.--; as A'l-.Lch prcgramir i ng language to use are discussed. The examples of document files registered for this project include a case of adoption at Company A and a document relating to reducing the- v.eight of CV cables.

In the example diagrammed in Fig. 15, the research content; is shown as text only, but provision may also be made for pisting images or imbedding links to a document file. rig. 16 is a flowchart representing one example of a process iru; routine :"or displaying the project desktop (PJ-DT) diagrammed in Fig. 15. etc., with the configuration diagrammed in Fig. 8. In the example diagrammed in Fig. 16, first, l.lie user attribute of the user accessing the project desktop i3 determined according to the processing routine diagra:r.:t>,ed in Fig. 14 (step El). Following that, the project •'.-.". if:; referenced, and the access rights to the project ii- ::v,e r *t trie '.- e .vr_e determined (step B2 > . If the •. i .-•. .-•;.:oh that >MT;eot display is disabled, the user ]'. ,:; 'not i f ied :i\ :•.:•. '.inable-to-display error and •. i :: • i :• I e rim : < 5'. e : .
;\ i lie otl'.er h.-i-.--., project display is enabled, then '•i'i i-'' '-'ii >s -:• * ie •'•••'• '. •-- whether or not the display and
updating (writing to) of the various contents are enabled. First, the contents display order data in the project contents table 256, and the type of contents to be displayed
and the contents display order are specified (step B4). Following that, the project contents table 258 is referenced, and the access rights to the contents to be displayed are determined based on the user attribute (step B5). Then the contents display format is set according to the access rights (step B6). Whether or not an operation button can be used is controlled, for example. Following that, the content of the contents is read out from the DB 3, according to the display format determined by various settings, and the contents section is drawn as part of the page (step B7). The: process for drawing this contends section will be different for different contents, therefore the configuration may be made such that separate program routines are called up for each.
'.-,'hen the drawing of the contents is complete, the contents display order data are referenced, a determination is made as to whether or not there are next contents (step B8), and, ii there are next contents, the processing is repeated from step B4. If there are no longer any next contents, on the other hand, the contents sections are synthesized in the order c~ production (step B9) .
New Project and Contents Production
Fig. I'i is an explanatory diagram of one example of a page for producing a project desktop with this example. Fig, 17 (A) represents an a.-:a:r,ple of a project production page, and Fig. 17 (B) an example of an initial screen in a project desktop with this exvnpie. As diagrammed in Fig. 17(A), when a new project is to oe produced, the user is prompted to enter a prciect title, furigana ;'Japanese phonetic characters) to facilitate varipus sorts for Japan^^ language, and des igti.-u 1 ons of contents to be included in- the project desktop. 1:> tli is example, amcno the contents, the table of
contents, summary text, and member list are made contents that are contained in the project desktop at the time of initial establishment. When the save button is operated in the condition diagrammed in Fig. 17(A), the project desktop diagrammed .in Fig. 17 (B) is generated. That which is written in the table of contents section is automatically generated In the example diagrammed in Fig. 17, no entries are made in the summary text section.
Fig. 18 is an explanatory diagram of one example of a text editing page for adding text data (text section) to the project desktop, or updating those text data, in this example. This text editing page is'displayed when the edit button in the text section 32 has'been operated. Accordingly, the operation of the edit button in this text section is disabled for users who cannot update text. In the example diagrammed in Fig. 18, the user is prompted to enter a summary text title, a text section display mode, and content. When the user in the session is a leader, security designations are accepted, as diagrammed in Fig. 18. Provision may also be made :cr displaying a record (log) of modifications made in these text contents to date. When the save button is operated in the condition diagrammed in Fig. 18, updating to the text section 32 indicated by the symbol 32 in Fig. 15 is effected.
Fig. 19 is an explanatory diagram, of one example of a project editing page. This project editing page is displayed by operating the desktop edit cutten indicated in Fig. 15. When edit.i no the project desktop, it is possible to modify -the project title and to add cr delete contents. As in the case .iiagra'.nii-ed in :-i ;.. r3, the leader will be prompted -to crake ..:ser at. I ::ibu1:e -or Lented security .settings . Fig. 20 is an exr'-.ITI.-U-: y diac: JM representing an example" where a bookshelf P-.-t-ion i;-; -id dec to the project desktop in this example. A.; diagra:v.iv;d in Kir:. ?.Q. etc., because the project
desktop will grow as the project progresses, a professor in a research laboratory can ascertain how each research project is progressing by viewing each of the project desktops, for example, and can provJde guidance appropriate to each situation. in an example where >-^<-- user terminals 1 are connected via the internet, moreover, a project being jointly earned on in Tokyo and California can be managed with a single desk top, which can be viewed in turn by a professor partioipatiaa in a conference in London. Hence project management that conventionally has been very difficult can be effected easily thanks to such management by project desktop and definite access management^ by user attribute.
Sea rches
Next, searches of contents and the like are described. In Fig. 21 i.-; diagr;rmed an example of the detailed configuration of. the search controller 160 indicated in Fig. 8. Referring once again to Fig. 13, the database 3 comprises the project user table 254 wherein are stored lists of the projects and of the contents included in those projects, a doci;ii>-n" ' able 260 .•:hsr~in are stored the locations where document files transmitted via the bookshelf section 38 of the project desktop are stored, etc., and a document folder table 262 wherein are stored virtual deployment positions in the bookshelf section 38 for the document files managed by the document table .- 6 : . The actual document files are converted to special file names for management purposes and stored in .-'i r:ard dis< or the like managed by the server 2. A" so. ss d i agr.vnmeci in Kig. 21, the search controller 160 o: l hvv :?•..• rve.:: '.'. r.iT.pr i.Xr-?3 a search unit 16.1 for

search-,1 s, in response to operations at the user
,• across .the various projects, of the contents in
:s and -[ document files managed by the document ,-;••-• i :y i :i ;i co:ite:ics titles or document titles as •. .:, .1 ' i •.'••' -.-roirK-t specifying unit ~\6?. that
references the project contents table 258 using the contents titles searched out by the search unit 161, and specifies the projects to which those contents belong, a second project soeciTying unit 163 that references the document table 260 and ,-)ie document fol ier i able 262 using the document titles searched out by the search unit 161, and specifies the projects to which those documents belong, and a list transmission controller 164 for transmitting a list of projects specified z/ the first and second project specifying units 162 and 163 tc user terminals, as the search results of the search unit, in 3 condition of being linked to the project desktop.
Fig. 22 is an explanatory diagram of one example of a search results page generated by the list transmission controller 164. As 3Lagra:nmed in Fig. 22, in this example, the search unit 161 prompts the user to specify a search target. As shown here, document contents 'full text search of document files registered in bookshelf section 38) are selected. "lower transmission cables" was entered as a key nh^ase and the search was executed. Let it be assumed that, as search results, there v;as a hit on "Company_A.doc" diagrammed in Fig. 15. The second project specifying unit 163 first references the document table 260 and specifies the ID of a virtual folder tc which that document belongs. The second project specifying unit 123 then references the document folder table 262 and specifies a project ID from the virtual folder ID. Thereupon, from the project table, the project title "Ana". .5:s :;f Surges During Crossbonded Section Ground O ;t ir. Under - - -u:i •; Power Transmission Cables" can be
specif i ed. -
,;-, t.he .ex.-vnplr- i i a'--: r.vr.mec ir. c'ig . 22, a single document Qee'i search e i •::..:, where'fore there is only one i-n'o ''. e.; . '. v- .s: transmission controller 16-i ;•_ ".e I o '..he user terminal as the
search results of the search unit 161 in a condition of being linked to the project desktop. In the search results page, the project, name is *n operation button, and a project
desktop like that di iqrammed in Fig. 15 will be displayed when that project na-r.e the link, for example) is operated.
For searching document files, it will be well to generate an index fo.-r document files ahead of time, during a time frame of lev; K--ve: load, and then search document files based on that index. it will also be well to make provision so that synopses of i certain length are automatically generated from document files and included in the search results.
Fig. 23 is a fVrjchart showing one example of a search processing routine 3 :.:c: iing to this example. The processing routine diagrammed i i Fig. 23 represents an example of the detailed operation o:: the search controller 160. First, the search target is specified (step CD . Following thereupon, the user is prompted to enter key words for the search (step C2'i . If this .is a :' f.l text search of document content (step CV] , a full text sea v:h engine is driven and a document ID is fetched (step C-.'i . .-oilowing that, the document table 260 is referenced, and the ID c: a virtual folder to which that document belongs is specified (step C5). Then the document folder table 262 is referenced, and a project ID and contents ID are fetched istep J3 . The processing routines in these steps C4, CL:, and CS constitute a first operation example for the second project specifying unit 163 indicated in Fig. 21.
'.•,";-.en th<- se j:\-r. •. .-i ;-t is a document title :file name of a doc-..T?>nt file' step "6} , the original file name is


•r.c.'.'. r.'-':r. t.-ible', and a virtual folder ID is -" • • >'-•": lev.'ing that, -the .document folder ..-so, ,I:T.-? the pro i.ect •_! [> and contents ID are
!':.e p;v;-ess ing routines in these steps C6,

C7, and C8 constitute a second operation example for the second project specifying unit 163 indicated in Fig. 21.
If the search target is a text section or a member list or the like (step C9), a contents content table (such as a text table (not shownj, lor example) is searched, and a project ID and contents ID are fetched (step CIO). The processing routines in these steps C9 and CIO constitute an operation example Cor the first project specifying unit 162 indicated in Fig. 21.
when a project is specified, the user attribute of the user iraking the search is determined [step Cll) . This step Cll determines the user attribute of the user making the search by the user attribute determination processing routine diagrammed in Fig. 1~, for example. This user attribute determination is done for each project specified. When access rights to a project exist, a link to the project desktop (PJ-DT) is displayed (step C13). If there are no access rights to the project, on the other hand, the link to that project is not included in the search results (step C14). 20 This processing routi.ie is executed for all projects speci fied.
: :i this manner, a project to which the content of contents searched belongs is specified, and a link to the project desktop of that project is provided as search results, wherefore it becomes; easier tc access peripheral information, and grasp the background against which and purpose for which those searched contents .'.'ere produced, etc. Even if a search is conducted -.-.'hen crib's remcry is vague, a user can be guided unconsciously to the search results aimed at. Furthermore, in casrs wherv a" us- • wishes U: reutilize resource materials used i:; A past pro ie ••'.., searches are possible by a -'variety of:.-apl1: o nci'.e-s , s .:ch a:-; .•: i th keywords used in_a document file, cr .--, tc•:•:'. in which a project sumir?.ry was included, etc.,
wherefore it is easy to retrieve the original resource
materials.
Saves
A description i ;-j given next of the relationship between saving project- desktops -ind bookshelf sections. In an embodiment aspect described earlier, in a case where the data structure diagrammed i.n rig. 13 was used, the server 2, as diagrammed in Klg. 1, includes the document management unit 140 that accommodates document files transmitted via the bookshelf section 38 in i document table 260, and also deploys those document files in a virtual directory in the bookshelf section 38. This document management unit 140, moreover, comprises a document operation control function 141 for copying and deleting document files in accordance with user attribute-oriented access rights set by the contents-oriented access controller 152 and for submitting those document files for downloading to a user terminal.
With this example, document files managed by this document management a.ir 140 can be saved in a single batch by the save controller :7Q indicated in Fig. 3. With this example, as diagrammed ^ .1 rig. 21, the save controller 170 comprises a save target setting unit 171 for setting one or a plurality of projects as save targets, an archive file archiving controller 172 for archiving the contents contained in the one or the plural i'..y of project desktops set by the save target setting unit 171, in one archive file, and an archive file transmission controller 173 for transmitting the archive i i.les archiv—i ry the archive Eile archiving controller ]'*?., in : ;j.-;p.M.-;e tc an operation at a user terminal, t,o rh-it '.,'e. :--^mnal
Che archi'/r: fi"1-- a -„:':: LV ir.g, controller 172, .in turn, comprises a piuiect d.-s';;pp paoe generator 174 for generating-proit-n desktop t;-'»-;: '; •-•.:.-.-re in :-o:ite:u s cotitent displays or Links to port i,-:i;-; ,•: 'C.Utnts are '.•.•ritten with a markup
language, for each project, in accordance with access rights set by the contents-oriented access controller 152, a file storage function 171 Tor storing image data used in that project desktop page and document files held in the document table in a associated folder, and an archive compression function I"/6 tor: storing a project desktop page and the content of a associated folder in one archive.
Fig. 24 ;A; is -j diagram of an example of a page for selecting a project, u:-; a r-;ave target. The save target setting unit 171, ar ji.^.-ammed in Fig. 24 (A) , generates a project desktop selection page, and prompts the user doing the save to select the project desktop that is to be the save target. At that tine, it will be well to display only projects that are aisplay enabled according to the user attribute of the user in the session doing the save.
With the archive ;'.! - e archiving controller 172, all data necessary to the project desktop display are extracted from the database and made an archive file. ~Lr\ a preferred example, moreover, that archive file will be compressed. More specifically, the project desktop page generator 174 generates a project desktop page wherein the display of the content of contents Wide display enabled or a link to a contents portion is '..'ritten with a markup language (ML) such as HTML or XML. Although this project desktop page does not greatly differ in acp-a -'ance from the project desktop diagrammed in rig. 3'3, nevertheless, in the first place, link information to docu;e it files or forum statement content and

•..':-. it project desktop is rewritten. .•::". 1 re well to delete the edit, - :---:' tc disable such- edit ing as
;?res image data used in -i:id docur.ent files accommodated in .;:-!:.;,• i .-i ted redder. In an example
where portrait photograph images of the members are displayed in the member list, for example, those portrait photograph images are read out from the user table and stored in an associated folder. In the case of a forum or the like where a tree form display is made, the content of each statement will become an individual ML page, wherefore an ML page wherein the content of those statements is written is also stored in an associated folder. Document files registered in a bookshelf section are also stored in an associated folder. The project desktop page generator 174 updates links from the project desktop to document files, statement content, and portrait photograph image files and the like using an associated folder name or the like.
The archive co i .press ion function 176 archives proj •.;•.;•_ desktop pages and associated folder content in a single archive and compresses them. In that way, all of the content in a project desktop is archived and compressed in a single file. By implementing compression, the communication time required when transmitting that archive file to a user terminal 1 can be shortened. The archive file transmission controller 173 generates a page for downloading an archive file (a project desktop rendered in HTML, for example) such -as diagrammed in Fig. 2-, (B} , for example. Provision may also be made so that the archive file transmission controller 173 adds that archive file to the bookshelf section 38 in the project desktop.
~ig, 2S is a flowchart representing one example of a project desktop save processing routine. The processing routine diagrammed 1:1 Fig. 25 constitutes an example of the oper.ii. ions of the ?-. v-- •.. .-irget setting unit 171 and the arrhive file archiving .-ontrol.ler 172. "first, the save ;.-, :,:ei projeo1. 13 s ?.-'•'c t e d i n response to" an operation .-v. : -i". ing a ;vi.:e s'..;-h =1.- th.-u diagrammed in Fig. 24 (A) istep 1)1) . i-'ol lowing thai. -i ii.^-'^y :'or:r.at is set for the save
according to the user attribute of the user that is to be making the save (step D2). Then a markup language (ML) page is generated in the same manner as in the project desktop page display process!.ig routine (step D3) . In parallel with thir- c"i ftp D3, an associated folder for storing associated files associated with the project desktop is made (step D4}, the document files and the like in the bookshelf section 38 are stored in that -i;;.v;oc lated folder, and a link to the ML page is also defines .step D5) .
Following thereupon, when there is a forum section i6, hierarchical data s.c'n. ar? forurr statements and the like are converted to :•":. pages and links are defined (step D6) . The ML pages and associated folders are stored in an archive (step D'?.1, arid that archive is compressed (step D8) .
--Personal De.v'r....op- -
Via. 26 is an explanatory diagram of one example of a personal desktop acccrda..^ to this example. Provision is made in this example so that, as diagrammed in Fig. 26, a list of the project.: .me belongs to can be displayed, and the prelect desktop can •:•'< 1 -mediately displayed. Referring once aqai'i i "~'ig- 3. t^= oerver ccxprises a personal desktop qene-ator 13? for generating an individual personal desktop for each user. This personal desktop generator 132 in turn comprises a list of p-ojects belonged to section generator 132A f'o reierenci:.. 'he project user table 254, when a personal desktop display request is received from a user, and generating a list c: prelects belonged to section that cisp'av.-, a list of 'he projects which that user belongs tc, anc; :) •,--.-;i f i-.--ii ion :' o1. i f i-rat icr. function 132B that, when j.|,_,.... ;--,.-: be-.i-; '' •?••'•"• i 'ition :vade to the contents o.f a ., t_., ;.[ tv.:- oro'r .;• '. :6t • qer.erated by the .list
be" ci-i.':-- '• to :'-ie>:i. ior .'.-.-nr
., ..... ... j,- .-i-H-ncc- ,v '. r.^i me d -. f i c a: :on to that project list
The list of projects belonged to section generator 132A, by referencinq the project user table 254, fetches the IDs of
all projects which that user belongs to. In the example diagrammed in Fig. 26, furthermore, the project table is referenced, a project, title is retched from a project ID, and that project title is drawn in the personal desktop as a link to a project desktop. Provision may also be made so that, in an example where a modification log is managed in each project desktop, when that project desktop is subjected to modification within a certain period of time from the present, a display will be appended to nc: ify of the fact that there has been a modification in a li,,-- displayed as a project name in .-I personal desktcp. In the example diagrammed in Fig. 26, for example, "New content update, date and time" is displayed. F.-•-..- :.- i.on may also be made for displaying updated contents section names or displaying the names of persons making modifications. In the personal desktop, it is possible to edit persona] information substituted in the project desktops, and to access the web ;r,aJl functions given to loa-in users.
• Project List Page
Referring yet again tc Fig. 8, the server 2 comprises a project list page generator 133 for generating a project list as a project list page. Moreover, that project list page generator 133 in turn comprises a user name adding function 13r- rcr referencing ;he project: user table 254 and adding the ivv.nes of users belonging to the projects to each of the proi-otr respectively on that project list page. Fig. 27 is an t:.xp~. anato: y diagram, of one example of a project list page ace-;: 1 i :v^ to '..his exarp^e. Ir. the example diagrammed in Fig. '?.'!, '..h-.-n "the expanc iiition has been operated, the names of men!; -e: .-.•• belonging to orojerls are added tc the' project ^i dio; • :. '..;}•' t ht- ,.ser n-i:re ado ing :o:noi. ion 133A. User i ot r :i.]-= -
Referring to Fig. 0, the server 2 comprises a user list page generator 134 for generating a list of users as a user list page. Moreover, that user list page generator 134 in turn comprises a project name adding function 134A for referencing the project user table 254 and adding the names of p'-r.j&cts to whir:I- the users belong to each of the users respectively in that user list page. Fig. 28 is an explanatory diagram of one example of a user list according to this example. wren the expand button indicated in Fig. 28 ha.; oi-'-n operated, ;:i the same manner as in the case diagrammed in Fig. 2'.', the names of projects to which a user belonqr-; are added to that _user .i;:;ne by the project name adding function 134A.
--Examples of U.se
.-'iq. r> 9 is an explanatory diagram representing the general course of processes up until a project desktop is completed according to this example. In terms of everything from the inception of a project, to the generation and verification of idess using the project desktop, the utilization of the croject desktop converted to HTML and saved at project ccipleticn, and the definite safekeeping of information after project completion, with the project management system according to this example, the project desktop grows as the project progresses, and, thereby, a tighter cognizance cf the way in which the project is progressing is fostered. In addition, because information relatjna to project activity and the activity history are recorded e}e.cl/onics-~-'.y .-.- a project desktop, everything from presr-:.t itions where::; that saved prefect desktop was used to uu> .'-.'. : ng of info: .,' [.\. -,:'id the like can be done easily and i :H. ..::•.: vely .-- •-1 G: .'••.' ;•;;.. ;\s,..- : :if ormat. ion< collectea •- and •_•,-:.; .-'.-.• prod;..'ed b;. ;;:c;r-.-- members are consolidated and inc.-. ..MMCjly perfect e-i ::: the project desktop, wherefore
information management that accords with the progress of the prcrject can be easily effected.
Fig. 30 is an explanatory diagram of access to a project desktop according to this example. In this example, access paths to a project desktop are provided for various users. For example, for the person himself or herself belonging to the project, a link to the project desktop is automatically displayed on his or her personal desktop, selection from a list of. projects oriented to users who know the project names in <-ra orqari i xnt i on i .c: -nad- possible, and, even when the project name is unknown ':,- has been forgotten, that project can be inferred fro-.n the member list when persons who have become members are known. Also, various searches by key wordsr, from full text searches of document files to searches of text sections, are rruvie possible to users or general visitors outside the organ! /.at: n who are interested in a specific field. In examples where links to project desktops are displayed as the search results of such searches, moreover, it becomes easy for the person making the search to access the information originally aimed at. Even in cases where the existence oC a project or member names or the like have ceen forgotten or are not known, full text searches by key word are possible, thus facilitating ready access to information pertaining to projects.
:-" i Q . 31 is a : ~. 0'/;chart. representing an example of using the project management system according to this example. The example dLaqrarmed in ?--;:. il is one example of putting the pro j i-."l :r.anci.;.;--T.ent .vy.it-'-. v •;• good use, but there are other ut i 1 i.-.-u ion r;x;i;r,plc; , c-.sic.r-p that diagrammed in Fig. 31, adapted to various .-•,.' u.v; i o:\s and organizations. The uti". i .'i'. ion rrxa.c.p! ;r ~ . .- i - . >1 is one that emphasizes the proet:L-.; oi p.--ie-ct ve.vk: -p .-.rcwth.
••: ;;( '':•;- pr.. •' -\. :-.iif :.itor is registered as the leader ;.--.; t.i -[•> •: I ) . ••,-.".". ow: .; i. .---IL. th.e content and so forth of the
project are registered by the leader (step E2). If the project involves research, the particulars of the research and the problems addressed and the like should be described. If the project involves the development of a new product, the technical presuppositions, market peculiarities, and so forth, should be described, us well as guidelines for project advancement. Follcv:ing that, members selected by the leader are sequentially registered to form a member list (step E3). In this example, the project leader registers the members. Members can register -..he'.nselves for a project wherein there are leg-in users in cases -.-/here the overall project desktop settings for the: me.rbers have been made such that writes are enab"ed.
Following that, contents sections that manage other _;ntents are define:; ,n the project desktop for each project having text contents and a member list (step E4). What kind of contents are to ce added to a project desktop will be determined by the l?aier or, when permitted by the leader, by members. Such contents should be such as document management contents for managir..: document files, and forum contents for recording the content of statements made by the leader and members. The acces? rights to the contents in each contents section are then set according to the user attributes of the leader, the members, .and other users !step E5) . This means thai roth forums t):-:t 3-= --,de secret '..c non - member users and open rorums can be r_: ;duced on the same desktop. It is also possible, while ope::", y disclosing the content of and stat.er.-nts :r.;-tue in : :; -j:r:.i, to prohibit reading out ;dov:n". oading or cof, ....ig/ document files in the bookshelf
; ':p , -. c i agrammed in rig. 3 1, a proj.e.ct
i:i response to a request ta display a desktop cor. i .1 ; n ; a-".1 contents sections, wherein the o!! and cpe: ;.'. ;o::.--. ;•-.-:rta i:i ing to the various contents

are limited by the specific attribute of the user making that display request, and contents input in response to that display are added to that project desktop (step E6). This step E6 is repeated until the project is completed. Then, upon completion of the project, a completion page is generated wherein text data, statement content, and document files related to that project are batched together and described with a markup language {step E8). When a completion page (i:. i.ue example described in the foregoing, a project desktop (MI. page) wherein are accommodated document files; is generated .-..i this way, he project desktop can be loaded into a computer such as a portable notebook computer, and a presentation given in a conference room or the like at another institution while referring to that project desktop Alternatively, if the project desktop is converted to HTML, it may be made public, without further modification, on a web server, making it possible to disclose information relating to a project to the outside. Thus the completion page is made public.

WE CLAIM :
1. project management system to manage projects of users by project desktops -and user attributes of the project including a server (2) connected by a network (5) to a plurality of user terminals (1) operated respectively by the users; a database (3) for storing contents contained in those projects for each of projects participated in by some or all of the users, and a communication controller (4) for transmitting prescribed pages to the user terminals (1), and receiving operation messages from the pages, characterized in that
wherein the database (3) includes:
a project user table (254) in which user attributes, for projects, of leader or members of the projects, set for each of those projects are recorded; and
a project contents table (258) in which the user attribute-oriented access rights are recorded for each set of contents belonging to projects, and
wherein the server includes:
a project desktop sheet generator (10) for reading contents data (40, 44, 46) from the database (3) in response to operation messages received by the communication controller (4) and generating, for each project, a page as a project desktop (30) for displaying or accessing all contents (40, 44, 46) belonging to the project;
the project desktop sheet generator (10, 131) comprises functions (50, 54, 56) for generating a project desktop (30) containing, as the contents (40, 44, 46), a text section (32) for displaying text, a forum section (36) for recording and displaying user statements, and a bookshelf section (38) for managing files transferred from user terminals (1);
a project-oriented user attribute controller (14) for determining the user attributes relating to projects which are objects of those communications via the communication controller (4) by using the project user table (254); and
a contents-oriented access controller (16) for controlling display and operation content pertaining to several contents (40, 44, 46) of t he project desktop (30), based on the user attributes determined for projects of accessing users (S11, S12) and on the user attribute-oriented access rights (S13) recorded in the project contents table (258),

wherein the contents-oriented access controller (16, 152) comprises function for permitting a write to the contents to the user having the write attribute, and for permitting a read to the contents to the user having the write attribute.
2. The system as claimed in claim 1, wherein the database (3) includes a project
table (252) in which are recorded the user attribute-oriented access rights for the
' project desktop (30) overall; and
wherein, the server (2) includes a project-oriented access setting unit (153) for setting access rights to the project desktop (30) based on user attributes determined by the project-oriented user attribute controller (14).
3. The system as claimed in claim 2, wherein the project contents table (258) has
contents order data wherein are recorded display order of contents belonging to that
project in the project desktop (30);
wherein, the project desktop sheet generator (10, 131) includes:
a contents section drawing function (131 A) for reading out contents (40, 44, 46) based on the contents order data and sequentially drawing a contents section (32, 36, 38) in accordance with access rights set by the contents-oriented access controller (16); and
a synthesis control function (131B) for effecting control to synthesize the contents sections (32, 36, 38) drawn by the contents section drawing function (131 A) in order according to the contents order data as a single-page project desktop (30).
4. The system as claimed in claim 1, wherein the database (3) includes a document
table (260) in which are stored the locations where document files transmitted via the
bookshelf section (38) of the project desktop (30) are stored, and
a document folder table (262) in which are stored virtual deployment positions in the bookshelf section (38) for the document files managed by that document table (260);
wherein, the server includes a document manager (140) for storing the document files transmitted via the bookshelf section (38) in the document table (260) and deploying those document files in a virtual directory in the bookshelf section (38); and

wherein, the document manager includes a document operation control function (141) for copying and deleting document files in accordance with user attribute-orienfed access rights set by the contents-oriented access controller (16) and for "submitting those document files for downloading to the user terminals (1).
5. The system as claimed in claim 4, wherein the server includes:
a save target setting unit (171) for setting one or a plurality of the plurality of projects as save targets;
an archive file archiving controller (172) for archiving contents contained in the one or the plurality of project desktops (30) set by the save target setting unit (171), in one archive file; and
an archive file transmission controller (173) for transmitting archive files archived by the archive file archiving controller, in response to operations at the user terminals, to those user terminals; and
wherein the archive file archiving controller includes:
a project desktop page generator (174) for generating project desktop pages (30) wherein contents content displays or links to portions of contents (40, 44, 46) are written with a prescribed markup language, for each of the projects, in accordance with access rights set by the contents-oriented access controller (152);
a file storage function (175) for storing image data used in that project desktop page (30) and document files stored in the document table (260) in an associated folder; and
an archive compression function (176) for storing the project desktop page (30) and content of the associated folder in one archive.
6. The system as claimed in claim 1, wherein the database (3) includes:
a project contents table (258) in which are stored lists of the projects and contents contained in those projects;
a document table (260) in which are stored locations where document files transmitted via the bookshelf section (38) of the project desktop (30) are stored; and

a document folder table (262) in which are stored virtual deployment positions in the bookshelf section (38) for document files managed by that document table 1260); and
wherein the server includes:
a search unit (161) for implementing searches, in response to operations at the user terminals (1), across the various projects, of contents (40, 44, 46) in those projects and of document files managed by the document table (260), and specifying contents titles or document titles as search results;
a first project specifying unit (162) that references the project contents table (258) using contents titles searched out by that search unit (161), and specifies projects to which those contents belong;
a second project specifying unit (163) that references the document table (260) and the document folder table using document titles searched out by the search unit (161), and specifies projects to which those documents belong; and
a list transmission controller (164) for transmitting a list of projects specified by the first and second project specifying units (162, 163) to the user terminals, as search results of the search unit (161), in a condition of being linked to the project desktop (30).
7. The system as claimed in claim 6, wherein the list transmission controller
includes functions for determining (C11) user attributes of users who performed the
search operations for the specified projects, and for removing projects (C12, C14)
which cannot be displayed to those users from the specification results.
8. The system as claimed in claim 1, wherein the database (3) includes a project
user table (254), for each of the projects, wherein is stored a list of users belonging to
that project;
wherein the server includes a personal desktop generator (132) for generating an individual personal desktop for each of the users; and the personal desktop generator (132) includes:

a list of projects belonged to section generator (132A) for referencing the project user table (254), when personal desktop display requests are received from users, and generating a list of projects belonged to section that displays a list of the projects which those users belong to; and
a modification notification function (132B) that, when there has been a modification made to the contents of a project in the project list, adds and indication of the presence or absence of that modification to that project list section.
9. The system as claimed in claim 8, wherein the server (2) includes a project list
page generator (133) for generating the project list as a project list page; and that
project list page generator (133) includes a user name adding function (133A) that
references the project user table and adds names of users belonging to projects to
each of several projects respectively on that project list page.
10. The system as claimed in claim 9, wherein the server (2) includes a user list
page generator (134) for generating a list of the users as a user list page; and that user
list page generator (134) includes a project name adding function (134A) for
referencing the project user table and adding names of projects to which users belong
to each of various users respectively in that user list page.
11. A project management system to manage projects of users by project desktops
and user attributes of the project substantially as herein described with reference to the
foregoing description and the accompanying drawings.