JP2009230593A - Data sharing system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a data sharing system, allowing free and easy arrangement and association of information by a member. <P>SOLUTION: In the data sharing system, a database 2 accumulates a layout of a page HTML for displaying data, a structure of articles constituting the page, and documents (data) constituting the articles. A page display part 11 acquires, upon receipt of a display request from a member terminal 3, the layout of the page concerned, the structure (HTML) of articles related to the page, and documents contained in the articles. The documents are made into HTML format, the document HTML is marked up to the article HTML (structure), and the marked articles are further incorporated to the page HTML based on the layout. The page HTML to which the documents and articles are incorporated is displayed on the member terminal 3. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a data sharing system and program for sharing data between registered members through a network. In particular, the present invention relates to a data sharing system capable of managing the configuration information of personal pages on which data shared between members is displayed in a hierarchical manner and providing data in a flexible expression format, and a computer of the data sharing system. It relates to a program that functions as a server.

  Conventionally, a system for sharing data between predetermined members is known.

  In Patent Document 1, users in a user group share a document, and other user groups present only accessible documents set in advance so that comments and related information can be attached. An information management apparatus that supports exchanges between a plurality of user groups via shared information is disclosed.

  Patent Document 2 holds knowledge information including the reference relationship of data of the document group for each group of documents accessible via the network, and matches a search condition with respect to a client document search request. An information processing apparatus that returns knowledge information of a document and enables a client to access the document based on the knowledge information is disclosed.

  In Patent Document 3, attributes such as publication, personal use, and data are assigned to documents, the documents are managed by association information (e.g., grounds, references, and summary), and only documents with predetermined attributes are displayed at the time of display. A document search system for displaying is disclosed.

  Furthermore, in Patent Document 4, documents are stored in association with creators (knowledge workers) and their attributes at the time of knowledge collection, and documents and creator information can be accessed by multiple users (knowledge workers) during exchange. A knowledge management system that promotes knowledge exchange by registering at a place is disclosed.

  On the other hand, using the WWW service on the Internet to provide information to other members in the group is widely performed.

For example, when a document created by a member of a company, organization, or the like is disclosed to other members using a member-dedicated network, the document creator first has a Web site (Web page) described in HTML. Upload the document file to be published. Thereafter, the other members access the Web site and browse the contents of the document file of the Web page displayed by the Internet browser (Web page browser). Alternatively, the document file is downloaded by selecting the URL of the document file on the Web site.
JP 2002-140323 A JP 2003-263462 A JP 2004-326637 A JP 2007-34965 A

  In recent years, since WWW services have become widespread, there is a demand for a system in which data is shared among predetermined members by using Web pages and the data display mode is flexible and data can be easily updated. Yes. However, in the conventional data sharing system, members cannot edit the data display format.

  In particular, selecting, collecting, and associating data based on a certain viewpoint and purpose is necessary for organizing information, but data that each member freely collects and associates with is necessary. There was no mechanism to provide other members as a single data collection.

  In the organized data group, the data summarization itself becomes information, and the searchability of data can be improved.

  On the other hand, when using a Web page with a high degree of freedom of expression in the data sharing system, it is necessary to statically add / change the HTML description of the Web page each time document data is added / updated on the page. was there. Furthermore, the document file had to be replaced when the page was updated. In addition, when it is desired to display the same contents in a plurality of Web pages, it is necessary to duplicate the corresponding part (HTML) of the reference source page, which causes double management of HTML between the reference source and the reference destination. Therefore, it is necessary to detect a change in the reference page and reflect the change in all the copied Web pages, and problems such as omissions, mistakes, and time lag have occurred.

  The problem of the prior art will be described as an example of sharing data internally.

  The employee A of the company posts the sales document A created by A on the Web page of the sales department. The employee B of the technical department accesses the Web page of the sales department, downloads the document A, and uploads this (referred to as document A ′) to the Web page of the technical department. The document A of the sales department Web page (sales department page) and the document A 'of the technical department Web page (technical department page) have the same contents, but are stored and managed separately in the database. Therefore, when the employee revises the document A and reposts it on the sales department page, the content of the document A ′ on the engineering department page is different.

  In order to maintain the identity of the information posted on each page, it is necessary to monitor the change of the document A, manage the page on which the document A is posted, and change the page. In order to make the update of the document A known, an update notification (marks such as “New” and “Update”) is displayed on the page, and an update date is described. Also in this case, the HTML of all the corresponding pages must be changed, and the burden of the change work increases.

  In the data sharing system, if each member can freely associate and summarize data, various viewpoints on the use of data will be introduced, and the data sharing system will be actively used to improve the searchability of data. It is thought that it is done.

  The invention of the present application is a system in which registered members share data, allows free editing of each member's page and incorporation of data, allows data to be easily organized, and further organizes a data collection. The purpose is to provide a data sharing system and program that can be used by other members.

  In order to achieve the above object, according to the present invention, a page for displaying data shared by members is assigned to each member, and information on the elements of the page and their arrangement is constructed and managed.

  In other words, data to be incorporated in an article between an information layer (page layer) indicating a component of a page (referred to as an article) and its arrangement (page layer) and a layer (item layer) indicating individual data (referred to as a document) to be shared. And an information layer (article layer) indicating its arrangement.

  Then, the member can freely edit the layout of the article of the assigned page and the layout of the document to be included in the article, and the article selected by the document can be freely used by other members.

  Specifically, the system according to the present invention includes 1) identification information of the page, identification information of articles constituting the page, and layout of the page for a page assigned to the member for data display. A page information storage unit that stores page information; 2) an article information storage unit that stores article information including identification information of the article, identification information of a document constituting the article, and article content indicating the configuration of the article; 3) a document storage unit for storing document information composed of the document identification information and the document body serving as shared data; and 4) receiving a page display request from the member's terminal and receiving the page requested to be displayed. Page information from the page information storage unit The article information of the article recorded in the extracted page information is extracted from the article information storage unit, the document information of the document recorded in the extracted article information is extracted from the document storage unit, and 5) the extracted page Display page data is generated based on the layout of the information, 6) for each article, a document to be configured is incorporated in the article content, and the article content incorporating the document is incorporated in the display page data. 7) A page display processing unit for transmitting display page data in which the document and article content are incorporated to the member's terminal.

  When the data sharing system receives a page display request from the member's terminal, the page information of the page requested to be displayed is extracted from the page information storage unit, and the article information of the article recorded in the extracted page information is stored in the article information. The document information of the document extracted from the document and recorded in the extracted article information is extracted from the document storage unit. Display page data is generated based on the layout of the extracted page information, and for each article that constitutes the display page, the component document is incorporated into the article based on the article content. Generate embedded article content. Further, the article content incorporating the document is incorporated into the display page data. The display page data in which the document and article contents are incorporated is transmitted to the member terminal.

  For example, the layout of the page requested to be displayed is stored as XML data, the article content indicating the configuration of the article is stored as HTML data, and the document that is data included in the article is stored as binary data. Then, the page display unit generates HMTL data (page HTML) of the page based on the layout (XML). Further, the binary data of the document is converted into HTML data to generate a document HTML, and the document HTML is inserted into the corresponding position (markup position) of the article content (HTML). Then, the HTML data (article HTML) of the article including the document is incorporated into the page HTML to form a display page (Web page).

  In the member terminal, the HTML transmitted from the system is interpreted by an existing web page browsing application, and a web page composed of articles in which the document is incorporated is displayed on a display or the like.

  The document may be set in the article HTML so that information indicating the document, for example, a document title name (character string), a thumbnail or the like is generated and displayed instead of the main data indicating the content.

  According to the present invention, page configuration information for displaying data (documents) shared by members is constructed with a three-layer structure of page article items, and the association of information of each layer is managed. Each time a page display request is made, a display page is generated based on these pieces of information and displayed on the member's terminal.

  Therefore, even when the data is replaced, the member can browse the display page in which the latest data is incorporated. In addition, the member can browse the display pages having different contents for each member, and can use the shared data through various expression formats.

  Furthermore, when a system editing request is received from a member terminal, the system according to the present invention generates an editing page by a process similar to that for a display page. When a page component (article, document) and a change in its arrangement are detected on the editing page, the related page information, article information, and page information are updated based on the detected editing operation.

  As a result, members can freely add, move, and delete documents and articles on their editing pages, and can organize and present data based on individual viewpoints and meanings. Therefore, it is possible to enrich the viewpoint of providing information in the data sharing service.

  In addition, when a document download request is made, the present invention displays the document access log information including the requested document, the identification information of the page and article referenced at the time of the download request, the request date and time, and the requested member. It can be registered in the access log storage unit.

  Further, the present invention can detect a page display request, and register the page requested to be displayed, identification information of articles constituting the page, page access log information including a request date and time and a requested member in the access log storage unit. it can.

  As a result, it is possible to obtain analysis data indicating which page, article, and document are highly interested.

  According to the present invention, shared data stored in the system is displayed on a page assigned to each member. Then, the configuration information of the page on which the data is displayed is configured and managed in a three-layer hierarchy of pages, articles, and items (data).

  By establishing an article layer between the page layer of page configuration information linked to individual members and the item layer of information specifying individual data, and managing the association between pages and individual data, Each member can arbitrarily collect documents, generate articles and incorporate them into pages, and organize and associate various information (items) including documents based on their own viewpoints.

  Furthermore, articles can be freely incorporated into pages, and members can use articles created by other members as well as articles created by themselves.

  Since this variety of articles can be used, various viewpoints are provided to the shared data system, data searchability and access convenience are improved, and utilization of know-how through information sharing is promoted. .

  Further, according to the present invention, when the shared data is updated, the link to the updated data is set even when there is a display request for a page to link this data after the updated data is uploaded. Generate a display page.

  Therefore, the member linking the updated data does not need to correct the link setting of the page configuration information.

  In addition, when an article is updated, if the original article (original data) is updated, the updated article is displayed in the layout of all pages that refer to this article. In addition, since there is no need for double management of reference destinations, it is excellent in data maintainability, and it is advantageous in that sharing of information is promoted in that appropriate information is always provided.

  Furthermore, according to the present invention, history information on access and reference to pages, articles, and documents is stored as access log information. Therefore, by analyzing the access log information, it is possible to grasp the pages, articles, and documents that are of high interest, and to evaluate the degree of contribution to the data sharing system.

  In addition, members who contribute to data sharing by providing pages, articles and documents with high demand can be identified.

  FIG. 1 shows a configuration example in an embodiment of a data sharing system according to the present invention.

  The data sharing system shown in FIG. 1 is implemented as a data sharing system between company employees, and includes a data sharing server 1, a database 2, and a member terminal 3.

  The data sharing server 1 generates page data (HTML of the Web page) for displaying the document stored in the database 2 and transmits it to the member terminal 3 through the network 4.

  Documents are data shared by members, such as text data, spread seed data, and image data.

  The member terminal 3 includes a display unit 31 that displays the display page transmitted from the data sharing server 1 and allows editing by the editing page.

  Further, the data sharing server 1 is connected to the employee authentication server 5 via the network 4. The employee authentication server 5 includes a member authentication unit 51 that performs an authentication process for registered members who can use the data sharing server 1 with reference to the personnel table 53.

  The database 2 includes a page table 21, a page access log table 22, an article table 23, an article access log table 24, a document table 25, a document version table 26, a document access log table 27, and a member table 28.

  The page table 21 stores information (page information) indicating the configuration of the page displayed on the member terminal 3.

  As shown in FIG. 2A, the page table 21 includes a “page ID” indicating page identification information, a “page creator” indicating the member who created the page, a “layout” indicating the page layout, and an evaluation score. It is composed of data items such as “score”.

  The layout is XML data in which the components of the page, their arrangement and display mode are described.

  FIG. 3 shows an example of layout data. In the layout of FIG. 3, the page is composed of three columns as the layout of the page p111. For each column, articles a222 and a223 are assigned to column id = 0, articles a333 and a988 are assigned to column id = 1, and column id = 2 defines that articles a555 and a666 are included as components.

  The page access log table 22 stores access log information for each page.

  As shown in FIG. 2B, the page access log table 22 includes a “page ID” indicating page identification information, a “referencer” indicating a member who has accessed the page, a date, date and time when the page was accessed. It consists of data items such as “reference date and time”.

  The article table 23 stores information (article information) indicating the configuration of an article that is a component of a page.

  As shown in FIG. 4A, the article table 23 includes an “article ID” indicating article identification information, an “article creator” indicating the member who created the article, an “article content” indicating the configuration of the article, and an article. Data item such as “creation date and time” indicating the date and time when the article was created, “change date and time” indicating the date and time when the article was changed, and “score” indicating the evaluation score.

  The article content is HTML data in which the constituent elements of the article, their arrangement, display mode, and the like are described.

  FIG. 5 shows an example of article content data. The article content in FIG. 5 includes articles d5555 and d7777 as constituent elements in article id = a333, and the title of the article and the title of the document are set.

  The article access log table 24 stores access log information for each article referred to when a document is accessed.

  As shown in FIG. 4B, the article access log table 24 includes an “article ID” indicating the identification information of the article, a “document ID” indicating the identification information of the document accessed with reference to the article, and the accessing member. Data items such as “referencer” indicating “access”, “reference date” indicating the date and time of access.

  The document table 25 stores document information (document information) that is a component of the article.

  As shown in FIG. 6A, the document table 25 includes a “document ID” indicating document identification information, a “document creator” indicating the member who created the document, and a “file extension” indicating the data format of the document. , “Document body” that is the content of the document, “Update date” that indicates the date when the document information was updated, “Creation date” that indicates the date and time when the document information was created, and the document body was changed It consists of data items such as “change date and time” indicating the date and time and “score” indicating the evaluation score.

  The document body is binary data that is the content of the document.

  The document version table 26 stores version number information indicating a document update state when a document update process is performed.

  The document version table 26 shown in FIG. 6B includes a “document ID” indicating document identification information, a “document version number” for specifying update of the document, a “deletion flag” indicating whether the document body is deleted, a document It is composed of data items such as “document creator” indicating the member who created the document.

  The “delete flag” is set to a value = 1 when the document body of the corresponding version is deleted along with the update process, and set to a value = 0 when the document body is not deleted.

  The document access log table 27 stores access log information for each document.

  As shown in FIG. 7, the document access log table 27 includes a “document ID” indicating document identification information, a “referencer” indicating a member who has accessed the document, and a “reference date and time” indicating the date and time of access. Etc. are composed of data items.

  The member table 28 stores information on members who can use the data sharing server 1. As shown in FIG. 8A, the member table 28 includes data items such as “employee number” which is identification information of a member and “name” which indicates the name of the member. The member table 28 may further include member contact information (email address), comments, and the like.

  The member table 28 is generated by copying a part of the employee information in the personnel table 53 shown in FIG. The personnel table 53 is a known personnel master database or the like composed of data items such as “employee number” and “name”.

  The page that the data sharing server 1 displays on the member terminal 3 is defined by information whose configuration information is constructed by a three-layered structure of a page layer, an article layer, and an item layer.

  As shown in FIG. 9, in the page layer, the page table 21 defines the arrangement of the entire page and the article that is a component.

  In the article layer, the article table 23 defines a document that is a component in each article that constitutes a page and its arrangement.

  In the item layer, the document table 25 defines a document entity that is shared data.

  When a member accesses a document, not only the access information to the corresponding document but also the access information of the page and the article that was referred to when the access to the document is requested, the page access log table 22 of each hierarchy, the article access It is recorded in the log table 24 and the document access log table 26. This makes it possible to grasp the pages and articles involved in accessing the document.

  The data sharing server 1 includes a page display unit 11, a document management unit 13, an update unit 15, an access log recording unit 17, an evaluation unit 18, and a member registration unit 19.

  The page display unit 11 is a processing unit that receives a page display request from the member terminal 3 and generates page data (HTML) that can be displayed on the display unit 31 of the member terminal 3 based on the data in the database 2. is there.

  As shown in FIG. 10, the page display unit 11 includes a page HTML generation unit 111, an article HTML generation unit 113, an item markup processing unit 114, a document HTML generation unit 115, and a member HTML generation unit 116.

  The page HTML generation unit 111 accepts a page display request from the member terminal 3 and notifies the access log recording unit 17 of the page information. The page HTML generation unit 111 obtains corresponding page information from the page table 21 based on the identification information of the page requested to be displayed. Extract. Further, a page HTML serving as a display page is generated based on the page information layout (XML). Further, all defined article HTML is acquired and incorporated into the corresponding position of the page HTML.

  The article HTML is generated from the article content (HTML) of the article, and is converted from the binary data of the document body of the constituent element or predetermined data corresponding to the document body (for example, link information to the document title and the document body) ) Is incorporated.

  The article HTML generation unit 113 extracts the corresponding article information from the article table 23 based on the notified article identification information, and generates article HTML from the article content (HTML).

  The item markup processing unit 114 notifies the document HTML generation unit 115 of the document identification information. If the member identification information is notified, the item markup processing unit 114 notifies the member HTML generation unit 116 of the member identification information. Then, the document main body HTML and member information HTML are obtained and incorporated in a predetermined position of the article HTML.

  The document HTML generation unit 115 acquires the document body (binary data) of the corresponding document from the document table 25 based on the document identification information, converts the document body, and generates a document HTML.

  The member HTML generation unit 116 acquires corresponding member information (for example, name, email address, etc.) from the member table 28 based on the employee number of the member, and generates member HTML based on the acquired information.

  The document management unit 13 is a processing unit that receives a document download request from the member terminal 3, acquires a corresponding document from the database 2, and transmits the document.

  As shown in FIG. 11, the document management unit 13 includes a document request reception unit 131, a document input / output unit 133, and a document transmission unit 135.

  The document request receiving unit 131 receives a document download request from the member terminal 3, notifies the document input / output unit 133 of the document identification information, and the access log recording unit 17 sends the document identification information and the identification information of the referenced article. To notify.

  The document input / output unit 133 refers to the document version information from the document version table 26 based on the document identification information, and retrieves the document body corresponding to the version specified in the download request from the document table 25. Extract. If no version is specified in the download request, the latest version is assumed.

  Further, the document input / output unit 133 extracts the requested document body from the document table 25.

  If the document body of the document table 25 is stored as difference data generated by updating the document, the document body having contents corresponding to the version is extracted and merged.

  The document transmission unit 135 transmits the document body (binary data) acquired by the document input / output unit 133 to the member terminal 3 that requested the download.

  The updating unit 15 receives an editing request from the member terminal 3, generates an editing page, displays the page for editing on the display unit 31 of the member terminal 3, changes a page component (article, document, etc.), changes a layout, etc. Processing means for performing editing operations (for example, adding, deleting, moving, changing contents, etc.) and adding, deleting, and updating page information, article information, and document information based on these editing operations.

  As shown in FIG. 12, the update unit 15 includes a page layout editing unit 151, a page layout input / output unit 152, an article page linkage unit 153, an article input / output unit 154, an article list display unit 155, an article editing unit 156, a document version. A management unit 157 and a document input / output unit 158 are provided.

  The page layout editing unit 151 receives an editing request from the member terminal 3, generates an editing page (HTML) based on the page information, article information, and document information acquired from the member identification information, and sends it to the member terminal 3. To obtain the editing operation of the member terminal 3.

  The page layout input / output unit 152 acquires corresponding page information from the page table 21 based on the identification information of the member who requested editing. Further, the corresponding page information in the page table 21 is updated based on the editing operation performed on the editing page.

  The article page linkage unit 153 reflects the change state of the articles constituting the layout of the editing page (HTML) in the related article content (HTML).

  The article input / output unit 154 acquires article information related to the editing page from the article table 23. Further, based on the editing operation performed on the editing page, the corresponding article information in the article table 23 is updated, or the article information is added or deleted.

  The article list display unit 155 receives an article list display request during editing, generates a list of articles stored in the article table 23, and displays the list on the member terminal 3.

  The article editing unit 156 receives an article editing request during editing, and receives an editing result for the requested article.

  The document version management unit 157 updates the version information of the uploaded document in the document version table 26 when the editing operation is a document upload request.

  The document input / output unit 158 acquires document information related to the page requested to be edited from the document table 25. In addition, the document information of the uploaded document is added to the document table 25.

  When there is a page display request or a document download request, the access log recording unit 17 accesses the access log information to the page requested to be displayed, and the access log of the document requested to be downloaded and the related page and article. Information is generated and stored in the page access log table 22, article access log table 24, and document access log table 27.

  The evaluation unit 18 assigns a predetermined evaluation (score) to each document, article, and page based on information stored in the page access log table 22, article access log table 24, and document access log table 27. In addition, the evaluation (score) is totaled and an evaluation order list is generated using the access log information.

  FIG. 13A shows an example of an article evaluation rank list. The article evaluation rank list 340 includes a descending “rank”, an “article ID” which is identification information of the article, an “article content” indicating a document included in the article, a “creator” indicating the member who created the article, It consists of data items such as “score” assigned based on the access log information.

FIG. 13B shows an example of a document evaluation order list. The document evaluation rank list 350 includes a descending “rank”, a document identification information “document ID”, a “creator” indicating the member who created the document, and a “score” given based on the document access log information. The member registration unit 19 configured with data items such as the above uses the employee information registered in the personnel table 53 to register the member who receives the document sharing service, and stores the member information in the member table 28.

  FIG. 14 shows a display example of a page generated by the data sharing server 1 and the relationship with each data table of the database 2.

  A member (page editor) who wants to edit article a1 of page p111 assigned to him / her makes a page editing request.

  The update unit 15 of the data sharing server 1 generates HTML of the page p111 according to the layout (XML) of the page p111 based on the page information of the page p111, the article information of the articles a1 to a3, and the document information of the document d1. To do. Further, the binary data of the document body of the document d1 is converted to HTML (document HTML). Furthermore, the HTML document d1 is incorporated into the article content (HTML) of the article a1.

  Further, the HTML of the article a1 incorporating the document d1 as the contents of the column c0 of the page p111 is set as the contents of the articles a2. Each HTML of a3 is incorporated into the page HTML to be an editing page. The editing page p111 is displayed as a page editing screen 300.

  Thereafter, a member (browser) who wants to browse data makes a display request for page p111. The page display unit 11 of the data sharing server 1 refers to the database 2 and generates a display page (HTML). The display page p111 is displayed on the member terminal 3 as a page release screen 310 (p111).

  When the viewer makes a download request for the document d1 included in the article a1 on the page release screen 310, the document management unit 13 reads the document main body of the corresponding document “Proposal for Manufacturing” d1 from the document table 25. And is sent to the member terminal 3 of the viewer.

  The access log recording unit 17 generates access log information of the requested document d1, the related page p111, and the article a1, and adds them to the document access log table 27, the page access log table 22, and the article access log table 24, respectively. .

  Thereafter, the document d1 is created, and the updated member (updater) requests upload of the updated document “Proposal for Manufacturing (Revised)” d1 ′ of the document d1. The update unit 15 of the data sharing server 1 displays the document upload screen 320 on the member terminal 3 of the updater.

  When the updated document d1 ′ is designated as the upload target on the document upload screen 320, the document d1 has already been recorded in the document table 25. Therefore, the update unit 15 determines the version number (2), Version number information such as designation of deletion of the original document (0 = none) or the like is set in the document version table 26, and document information of the document d 1 ′ is generated and stored in the document table 25.

  After the update, when the viewer requests page display, the page release screen 310 of the page p111 in which the document d1 ′ is incorporated in the article a1 is displayed on the member terminal 3 of the viewer. Then, when a download request for the document d1 ′ is made, the document management unit 13 extracts the document body of the corresponding document “Proposal for manufacturing (revised)” d1 ′ from the document table 25, and sends it to the member terminal 3 of the viewer. Send.

  The access log recording unit 17 generates access log information of the requested document d1, the related page p111, and the article a1, and adds them to the document access log table 27, the page access log table 22, and the article access log table 24, respectively. .

  FIG. 15 shows a more detailed display example of the page release screen displayed on the member terminal 3.

  Here, the page assigned to each member is composed of three columns c0 to c2, and one or more articles are set in each column, and documents, link information, etc. are freely pasted in each article. Suppose you can.

  In the page disclosure screen 510 of the page (p111) created by the member whose membership number is 11113, the column c0 contains articles a222 and a223, the column c1 contains articles a333 and a988, the column c2 contains articles a555 and a666, respectively. Assuming that

  A photo and text are included as the main body of the article a222 in the column c0. Article a 223 is created by another member B.

  Documents d5555 and d7777 are incorporated in the article a333 of the column c1. Documents d5555 and d7777 are configured in such a manner that only the document title is displayed on article a333 and the document body is displayed in a separate frame. Article a 988 is configured to display the contents of the incorporated document d6666 within the article.

  An article a555 of the column c2 incorporates a calendar provided as a standard document. Article a666 is configured to be able to input history information of members who have viewed page p111.

  FIG. 16 shows a display example of a page release screen for another page p333.

  Articles a333 and a988 are incorporated in the column c1 of the page p333 in FIG. In addition, the article a333 incorporates documents d5555 and d7777.

  If the document d5555 has been updated before the page display request for the page p333 in FIG. 16 is requested, the latest version of the document d5555 is determined by the document information in the document table 25 and the version management information in the document version table 26. The second version of is automatically incorporated.

  FIG. 17 shows a relationship example between pages, articles, and documents.

  In page p111 shown in FIG. 15, page p111 and articles a333 and a988 are associated with each other. Further, the article a333 and the documents d5555 and d7777 are associated with the article a988 and the document d6666, respectively. Such association is set by the reference relationship of each data table.

  When article a333 is set as a component of another member's page (p333), page p333 and article a333 are associated with each other.

  Also, when there is a download request for the document d5555, it can be specified by the article information (identification information) used at the time of generating the page which of the articles a333 and a999 is referenced.

  FIG. 18 shows a display example of an article on the page release screen.

  By describing the article content, a document that is a component of the article can be displayed as a document body, a document title, or a thumbnail corresponding to the document. In the article display example 511 of FIG. 18, a document is displayed with a document title, and link information to the document body is set in the document title.

  In addition, by placing the cursor on the document title, the “extension”, “score”, “comment (text data)”, etc. of the document can be displayed.

  As the “extension”, setting information of “document extension” of the corresponding document information in the document table 25 is used. By displaying the extension, you can inform the data format of the document.

  As the “score”, the “score” value of the document information is used. This can inform the evaluation of the document.

  “Comment (text data)” is displayed using the text data set in the article content of the article information of the article table 23. This can provide simple introductory information about the document.

  FIG. 19 shows a login screen to the data sharing server 1. When the data sharing server 1 receives the login request, the data sharing server 1 displays the login screen 330 on the member terminal 3. The user ID and password input on the login screen 330 are used in the authentication process based on the personnel table 53 in the member authentication unit 51 of the employee authentication server 5.

  20 to 29 show processing flows of the data sharing server 1.

  20 and 21 are flowcharts of the page display process.

  The data sharing server 1 determines whether there is a login request (step S10). If there is a login request (YES in step S10), it determines whether the authentication is successful (step S11). If the authentication is successful with reference to the member table 28 (YES in step S11), a member individual page display process is performed (step S12).

  Thereafter, it is determined whether there is a document upload request (registration request) (step S13). If there is a document registration request (YES in step S13), the document registration process is performed, and the document table 25 and the document version table 26 are updated. (Step S14).

  Further, it is determined whether there is an article creation / editing request (step S15). If there is an article creation / editing request (YES in step S15), the article creation / editing process is performed, and the related page table 21 and article table are processed. 23, the document table 25 is updated (step S16).

  Further, it is determined whether there is a page layout creation / editing request (step S17). If there is a page layout creation / editing request (YES in step S17), page layout creation / editing processing is performed, and the related page table is created. 21, the article table 23 and the document table 25 are updated (step S18).

  Further, it is determined whether there is a document download request (step S19). If there is a document download request (YES in step S19), the document access log information is added to the document access log table 27 (step S20) and is referred to. Article access log information is added to the article access log table 24 (step S21), and the document body extracted from the document table 25 is transmitted to the member terminal 3 (step S22).

  The elapse of the predetermined period is determined (step S23), and when the predetermined period elapses (YES in step S23), it is registered for each article based on the article table 23 and the article access log table 24 as a download aggregation process. The number of document download requests is totaled, and an article list in which articles are arranged in descending order based on the total number of downloads is generated (step S24).

  FIG. 22 is a process flowchart of the page display process in step S12.

  When the page HTML generation unit 111 of the page display unit 11 receives a page display request from the display unit (browser) 31 of the member terminal 3 (step S100), the layout of the corresponding page information based on the page identification information ( XML) is acquired and a page HTML is generated (step S101).

  It is determined whether an unprocessed page still exists (step S102). If an unprocessed page exists (YES in step S102), a link setting (page link) for transitioning to the page is set in the page HTML. It adds (step S103).

  If there is no unprocessed page (NO in step S102), the layout (XML) under the selected page is acquired (step S104).

  Further, it is determined whether an unprocessed column still exists on the page to be processed (step S105). If an unprocessed column exists (YES in step S105), the column is added to the page HTML (step S106). . It is determined whether there is an unprocessed article in the column (step S107). If the article exists (YES in step S107), the article HTML generation unit 113 acquires the corresponding article HTML (step S108). Further, the acquired article HTML is inserted into the corresponding position of the page HTML (step S109).

  Until there are no unprocessed articles (NO in step S107), the processes in steps S108 and S109 are repeated for each article. If no unprocessed column exists (NO in step S105), the requested page HTML (page HTML in which the article HTML is incorporated) is output to the display unit (browser) 31 of the member terminal 3 (step S110). ).

  FIG. 23 is a processing flowchart of article HTML generation processing related to the processing in step S108.

  When the article HTML generation unit 113 receives a request from the page HTML generation unit 111 (step S150), the article HTML generation unit 113 acquires the corresponding article content (HTML) (step S151). The item markup processing unit 114 interprets the article content (HTML), generates an article HTML (step S152), and determines whether there is a markup in the article HTML (step S153).

  If there is a markup (YES in step S153), the markup element is determined (step S154).

  If it is a markup of a document (“document” in step S154), the document HTML generation unit 115 acquires the document body of the corresponding document (step S155), and generates a document HTML corresponding to the document body (binary data). (Step S156).

  The item markup processing unit 114 adds the document HTML to the corresponding position of the article HTML (step S157).

  If it is a member markup (“member” in step S154), the member HTML generation unit 116 acquires the member data of the corresponding person (step S161), and generates member HTML corresponding to the member information (step S162). .

  The item markup processing unit 114 adds the member HTML to the corresponding position of the article HTML (step S163), and adds the member ID of the corresponding person to the member list stored therein (step S164).

  If there is no unprocessed markup (NO in step S153), it is determined whether a plurality of documents are included in the article HTML (step S170).

  If a plurality of documents are included (YES in step S170), a link to the document body is inserted into the document title portion of the article HTML instead of incorporating the document HTML into the article HTML (step S171). Further, a “mailto link” for automatic e-mail generation processing is created from the member list generated in step S164 and inserted into a predetermined position of the article HTML (step S172).

  The processed article HTML is returned to the page HTML generation unit 111 (step S173), and the process ends.

  FIG. 24 is a process flow diagram of the new article creation process in the article creation / editing process of step S16.

  By an operation such as clicking on a “new article” button provided on the page editing screen 300, the article editing unit 156 receives an article creation request (step S210). The article input / output unit 154 acquires the layout of the corresponding page from the page table 21 via the article page link unit 153 and the page layout input / output unit 152 (step S211).

  The article input / output unit 154 generates empty article information and stores it in the article table 23 (step S212). The article page link unit 153 adds the generated empty article setting to the page layout (step S213). The page layout input / output unit 152 stores the updated layout in the page table 21 (step S214).

  FIG. 25 is a process flow diagram of article movement processing in the article creation / editing process of step S16.

  By an operation such as clicking a “move” button provided on the page editing screen 300, the article editing unit 156 receives an operation for moving an article (step S220). The article input / output unit 154 acquires the layout of the corresponding page from the page table 21 via the article page linkage unit 153 and the page layout input / output unit 152 (step S221).

  The article editing unit 156 copies the article setting description selected as the movement target to the movement destination column of the layout (step S222), and deletes the article setting description of the original column (step S223). The page layout input / output unit 152 stores the updated layout in the page table 21 (step S224).

  FIG. 26 is a process flow diagram of an article addition process by referring to an article of another member in the article creation / editing process of step S16.

  When the article list display unit 155 receives an article reference request by an operation such as clicking an “article reference” button provided on the page editing screen 300, a list of articles stored with reference to the article table 23 is stored. And an article reference screen including the article list is displayed on the member terminal 3 (step S230).

  The article editing unit 156 acquires the article to be added and the addition position specified on the article reference screen (step S231). The article input / output unit 154 acquires the layout of the corresponding page from the page table 21 via the article page link unit 153 and the page layout input / output unit 152 (step S232).

  The article page link unit 153 sets the specified article at the specified additional position in the page layout (step S233). The page layout input / output unit 152 stores the updated layout in the page table 21 (step S234).

  FIG. 27 is a process flowchart of article storage processing in the article creation / editing process of step S16.

  When the article input / output unit 154 receives an article storage request following article creation / editing (step S250), the article input / output unit 154 determines whether the article to be stored includes a plurality of document markups (step S251). Is marked up (YES in step S251), the document body (binary data) of each document is acquired, subjected to data compression processing, and stored in the document table 25 (step S252). Further, the requested article is stored in the article table 23 (step S253).

  FIG. 28 is a process flowchart of the document transmission process in step S22.

  When the document request receiving unit 131 receives a document download request from the member terminal 3 (step S270), the access log recording unit 17 stores the downloaded document and the access log of the article including the document in the article access log table 24. And the score is added (step S271). Further, the access log of the requested document is recorded in the document access log table 27 (step S272).

  The document input / output unit 133 refers to the document version table 26 and acquires the latest version of the document body (binary data) from the document table 25 (step S273). The document transmission unit 135 transmits the acquired document (binary data) to the requesting member terminal 3 using HTTP (step S274).

  FIG. 29 is a processing flowchart of member registration processing.

  The member registration unit 19 determines whether there is a member registration request (step S290). If there is a member registration request (YES in step S290), the member registration unit 19 checks whether the authentication is successful (step S291). When the authentication with reference to the personnel table 53 is successful in the employee authentication server 5 (YES in step S291), member registration is performed, member information is added to the member table 28 (step S292), and the process ends. If the authentication is not successful (NO in step S291), the process ends as it is.

  Although the present invention has been described above with reference to the embodiments, it is obvious that the present invention can be variously modified within the scope of the gist thereof.

It is a figure which shows the structural example in embodiment of a data sharing system. It is a figure which shows the data structural example of a page table and a page access log table. It is a figure which shows the XML example of the layout of page information. It is a figure which shows the example of a data structure of an article table and an article access log table. It is a figure which shows the HTML example of article content. It is a figure which shows the data structural example of a document table and a document version table. It is a figure which shows the data structural example of a document access log table. It is a figure which shows the data structural example of a member table and a personnel table. It is a figure which shows the relationship between a page layer, an article layer, an item layer, and a table. It is a figure which shows the structural example of a page display part. It is a figure which shows the structural example of a document management part. It is a figure which shows the structural example of an update part. It is a figure which shows the example of an article evaluation order list, and an example of a document evaluation order list. It is a figure which shows the relevance with each data table of the page display example and database which a data sharing server produces | generates. It is a figure which shows the example of a display of a page public screen (the 1). It is a figure which shows the example of a display of the page public screen (the 2). It is a figure which shows the example of a relationship between a page, an article, and a document. It is a figure which shows the example of a display of the article of a page public screen. It is a figure which shows the login screen to a data sharing server. It is an outline processing flow figure of a data sharing system. It is an outline processing flow figure of a data sharing system. It is a processing flow figure of page display processing. It is a process flow figure of the production | generation process of the article HTML relevant to the process of step S108. It is a process flow figure of new article creation processing in article creation and edit processing of Step S16. FIG. 10 is a process flow diagram of article movement processing in article creation / editing processing in step S16. FIG. 10 is a process flow diagram of article addition processing by referring to an article of another member in the article creation / editing process of step S16. FIG. 10 is a process flow diagram of article storage processing in article creation / editing processing in step S16. It is a processing flowchart of the document transmission process of step S22. It is a processing flowchart of member registration processing.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Data sharing server 11 Page display part 111 Page HTML production | generation part 113 Article HTML production | generation part 114 Item markup process part 115 Document HTML production | generation part 116 Member HTML production | generation part 13 Document management part 131 Document request reception part 133 Document input / output part 135 Document Transmission unit 15 Update unit 151 Page layout editing unit 152 Page layout input / output unit 153 Article page linkage unit 154 Article input / output unit 155 Article list display unit 156 Article editing unit 157 Document version management unit 158 Document input / output unit 17 Access log storage unit 18 Evaluation Department 19 Member Registration Department 2 Database 21 Page Table 22 Page Access Log Table 23 Tcl table 24 article access log table 25 document table 26 Document version table 27 document access log table 28 members table 3 the member terminal 31 display unit 4 network 5 employees authentication server 51 member authentication section 53 HR table

Claims (12)

In a data sharing system composed of registered member terminals and a data sharing server that stores and manages data that can be shared by the members,
A page information storage unit for storing page information including page identification information, identification information of articles constituting the page, and page information including the layout of the page for pages assigned to the member for data display;
An article information storage unit for storing article information including identification information of the article, identification information of a document constituting the article, and article content indicating the configuration of the article;
A document storage unit for storing document information composed of document identification information and a document body serving as shared data;
A page display request is received from the member terminal, page information of the page requested to be displayed is extracted from the page information storage unit, and article information of the article recorded in the extracted page information is extracted from the article information storage unit. Extracting the document information of the document recorded in the extracted article information from the document storage unit,
Generate display page data based on the extracted page information layout,
For each article, a document to be configured is incorporated into article content, and an article content incorporating the document is incorporated into the display page data.
A data sharing system comprising: a page display processing unit that transmits display page data in which the document and article content are incorporated to the terminal of the member. The data sharing system according to claim 1, wherein the page display processing unit converts a document body of a document to be incorporated into the article into the same data format as the article content, and incorporates the converted document body into the article content. The data sharing system according to claim 1, wherein the page display processing unit incorporates, as a document to be incorporated into the article, a data name of the document and link information to the corresponding document main body into the article content. A page editing request is received from the member terminal, and the page information storage unit, article information storage, the member page information, the article information of the article included in the page information, and the document information of the document included in the article. Each of the page and the document storage unit, and using the extracted page information, article information, and document information, generate an edit page for the member,
The editing operation detects an increase / decrease or arrangement change of the component including the document or article of the editing page, and relates to the editing page based on the detected increase / decrease or arrangement change of the component. The data sharing system according to any one of claims 1 to 3, further comprising an update unit that updates page information, article information, and document information. The update unit receives a registration request for the document, and includes a registration date and a version number for specifying the registration request in the document requested for registration when the document requested for registration is stored in the document storage unit. In addition to having a version number management section that gives version number information,
The data sharing system according to any one of claims 1 to 4, wherein document information and version number information of the document requested to be registered are registered in the document storage unit. The document management part which receives the download request of a document from the said member's terminal, extracts the document information of the document requested for download from the said document memory | storage part, and transmits to the said member's terminal is provided. The data sharing system according to any one of the above. The document management unit refers to the version number information when the version number information is given to the download requested document, and the document information corresponding to the latest version or the version number specified in the download request. The data sharing system according to claim 6, wherein the document body of the extracted document is transmitted to the terminal of the member. A document access log recording unit for registering in the access log storage unit the document requested to be downloaded, identification information of a page and an article referred to at the time of the download request, request date and time, and document access log information including the requested member; The data sharing system according to claim 6. A page access log recording unit that detects a display request for the page and registers in the access log storage unit the page access log information including the page requested to be displayed, identification information of articles constituting the page, request date and time, and requesting member The data sharing system according to any one of claims 1 to 6. An evaluation unit that calculates the number of downloads of each document and the number of references of each article from the document access log information stored in the access log storage unit, and assigns evaluation points to the document and the article based on the calculated values The data sharing system according to claim 8. An evaluation unit that calculates the number of accesses to each page and each article from page access log information accumulated in the access log storage unit, and assigns an evaluation score to the page and article based on the calculated value. 9. The data sharing system according to 9. To store and manage data that can be shared among registered members,
A page information storage unit for storing page information including page identification information, identification information of articles constituting the page, and page information including the layout of the page for pages assigned to the member for data display;
An article information storage unit for storing article information including identification information of the article, identification information of a document constituting the article, and article content indicating the configuration of the article;
A document storage unit for storing document information composed of document identification information and a document body serving as shared data;
A page display request is received from the member terminal, page information of the page requested to be displayed is extracted from the page information storage unit, and article information of the article recorded in the extracted page information is extracted from the article information storage unit. Extracting the document information of the document recorded in the extracted article information from the document storage unit,
Generate display page data based on the extracted page information layout,
For each article, a document to be configured is incorporated into article content, and an article content incorporating the document is incorporated into the display page data.
A data sharing program that functions as a data sharing server including a page display processing unit that transmits display page data including the document and article content to the member terminal.

Images