JP2014241113A - Content management device, content management system, content management method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To properly share information among a plurality of services without requiring a complicated operation of a user.SOLUTION: A content management device includes: deletion request transmission means that transmits a deletion request of posting information related to a content, which is posted to a posting management service, to the posting management service; response information reception means that receives response information indicating that the deletion of the posting information according to the deletion request has succeeded, from the posting management service; and content deletion means that, if the response information reception means receives the response information, deletes the content which is stored in storage means.

Description

  The present invention relates to a content management apparatus, a content management system, a content management method, and a program.

In recent years, with the development of network infrastructure, network lines have become faster and grid computing technology has improved. Along with this, cloud computing systems have begun to spread as a form of document management service for managing document files and form data and various processes on the server computer side.
In a cloud computing system, a user can access a web page of a cloud service from the browser of a client computer via the Internet. As a result, the user can upload information such as document files and form data to the server and download the information. Further, the user can display or share the information by accessing the Web page.

Some cloud services include a microblogging function. The microblogging function is one of communication services. In the microblog function, a user who has an account in the service can post a short message to the microblog service as a Web service. Each post by a user is assigned a unique identifier.
Further, on a user-specific web page called “timeline”, the user's own post, the post of the “followed” user, and the post to the group to which the user belongs are displayed. As a result, the user can communicate through follow-up and groups. Here, “follow” refers to registering a user so that other users' posts can be displayed on his / her web page. The “group” is a user group classified by users having common properties such as an affiliated organization and a project in charge. Posts to the group are displayed only on the Web page of the user belonging to the group. Examples of the microblog service as described above include Salesforce. com Chatter.

Also in the document management service described above, cooperation with other services has become important. Among document management services, there is also known one that notifies other users of the existence of a document by posting access URL information and shared information to the document to a microblog service as a Web service.
Conventional web services manage content within a single security domain. In such a Web service, contents can be registered, displayed, updated, and the like according to user operations. Furthermore, in the Web service, the content update result can be shared with other users within the Web service in accordance with the content update. Similarly, in the Web service, the content deletion and editing results can be shared with other users in the Web service in accordance with the content deletion and editing.

However, in the cooperation between a plurality of services such as the cooperation between the document management service and the microblog service described above, there is a problem that the security domain is different for each service. That is, since the security domain is different for each service, there arises a problem that content update information cannot be shared among a plurality of services.
In response to this problem, there is a technique for collectively managing information such as web pages and contents of a plurality of services. For example, Patent Document 1 discloses a website management system that collectively manages information on a plurality of different websites and contents using the web API of each service.

JP 2010-224700 A

In the Web site management system disclosed in Patent Document 1, information can be managed collectively, but when shared content is updated, the user logs in to the Web site management system and updates the shared information of the content. It must be cumbersome.
In addition, in the above-described cooperation between the document management service and the microblog service, even when the content on the document management service is deleted, the access URL information and shared information of the content on the microblog service remain without being deleted. Will remain. Therefore, even if the user browses the microblog and accesses the document management service based on the access URL information remaining on the microblog, there is an inconsistency that the desired document does not exist on the document management service. Can happen.
This access URL information for content that does not exist is called a dead link. The increase in dead links is a detrimental effect on information sharing among users, and is a serious problem that leads to inefficiency in business, especially in enterprise use. Even in the technique of Patent Document 1, this problem cannot be solved.

  The present invention has been made in view of such problems, and an object of the present invention is to provide a mechanism capable of appropriately sharing information among a plurality of services without requiring a complicated operation by a user. .

  Therefore, the present invention is a content management apparatus, a deletion request transmission means for transmitting a deletion request for posting information related to content posted to a posting management service to the posting management service, and the posting management service. , Response information receiving means for receiving response information indicating successful deletion of the posted information in response to the deletion request, and stored in the storage means when the response information receiving means receives the response information Content deletion means for deleting content is provided.

  According to the present invention, it is possible to appropriately share information among a plurality of services without requiring a complicated operation by a user.

It is a figure which shows a content management system. It is a figure which shows the hardware constitutions of a client apparatus, a microblog service, and a document management service. It is a figure which shows the software module which operate | moves on a microblog service. It is a figure which shows an example of a login screen and an authorization screen. It is a figure which shows an example of user information, group information, client information, and token information. It is a figure which shows an example of message information and comment information. It is a figure which shows an example of a timeline screen. It is a figure which shows the software module structure of a document management service. It is a figure which shows an example of document information, message information, user information, and authentication token information. It is a figure which shows an example of a login screen. It is a figure which shows an example of a preview screen. It is a figure which shows an example of a document registration screen. It is a sequence diagram of a document registration process. It is a sequence diagram of a document deletion process It is a flowchart which shows the document deletion process by a document management service. It is a flowchart which shows the document deletion process concerning 2nd Embodiment. It is a figure which shows an example of a message deletion confirmation screen.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

(First embodiment)
FIG. 1 is a diagram showing a configuration of a content management system. The content management system includes a client device 101, a microblog service providing server device 102, and a document management service providing server device 103.
The client apparatus 101, the microblog service providing server apparatus 102, and the document management service providing server apparatus 103 are connected to each other via a network 100 so as to be communicable with each other.

Examples of the network include a LAN such as the Internet, a WAN, a telephone line, a dedicated digital line, an ATM (Asynchronous Transfer Mode), a frame relay line, a cable TV line, and a data broadcasting wireless line.
The network may be a so-called communication network realized by a combination of these. The network only needs to be able to transmit and receive data. The communication means between the services may be different. For example, the communication means from the client apparatus 101 to the microblog service providing server apparatus 102 and the communication means to the document management service providing server apparatus 103 may be different.

The client device 101 issues a request to the microblog service providing server device 102 and the document management service providing server device 103. In response to a request from the client device 101 or the document management service providing server device 103, the microblog service providing server device 102 writes or reads a message as posted information and provides user information.
The microblog service providing server apparatus 102 manages information such as messages and comments posted by users. The microblog service providing server apparatus 102 is an example of an apparatus that executes a post management service.

The document management service providing server device 103 manages a document as content. In response to a request from the client apparatus 101, the document management service providing server apparatus 103 performs document management (content management) such as document registration, deletion, browsing, and update.
The document to be processed by the document management service providing server apparatus 103 is an electronic data document. The document management service providing server apparatus 103 stores the document in association with a URL that uniquely identifies the document. The document stored in the document management service providing server apparatus 103 is shared between users managed by the document management service providing server apparatus 103. The document management service providing server device 103 is an example of a content management device.

In the content management system, information related to a document managed by the document management service provided by the document management service providing server apparatus 103 is posted to the microblog service provided by the microblog service providing server apparatus 102. This provides a mechanism for sharing documents among registered users of the microblog service.
In the present embodiment, the document management service and the microblog service will be described as being executed by different apparatuses. However, these services may be realized in any device included in the content management system. As another example, the microblog service and the document management service may be provided in the same device. However, even if they are provided in the same device, the microblog service and the document management service are provided as different services, so that the security domains are different.

FIG. 2 is a diagram illustrating a hardware configuration of the client apparatus 101, the microblog service providing server apparatus 102, and the document management service providing server apparatus 103 in FIG. The CPU 201 directly or indirectly controls each device (ROM, RAM, etc. described later) connected by an internal bus, and executes programs for realizing various functions described later. The ROM 202 stores a BIOS program and the like. A RAM (direct storage device) 203 is used as a work area of the CPU 201 or used as temporary storage for loading software module programs for realizing various functions described below.
The HDD 204 stores an OS (Operating System), which is basic software, and software module programs. The input device 205 is a keyboard or a pointing device (not shown). The output device 206 is a display device such as a display. The I / F 207 is an interface for connecting to the network 100.
In these hardware, after starting the apparatus, the CPU 201 executes a BIOS program, and the OS program is loaded from the HDD 204 to the RAM 203 so as to be executable. The CPU 201 loads various software module programs, which will be described later, from the HDD 204 to the RAM 203 in an executable manner according to the OS program. Programs of various software modules are executed and operated by the CPU 201 in cooperation with the above devices. The I / F 207 is connected to the network 100 and is controlled by the CPU 201 in accordance with the OS program to realize communication by the communication means described above.

<Software Module Configuration of Microblog Service Providing Server Device 102>
FIG. 3 is a diagram illustrating a configuration of a software module (microblog service 300) that operates on the microblog service providing server apparatus 102. Each software module is realized by the CPU 201 loading a program stored in the HDD 204 shown in FIG. The microblog service 300 includes a transmission / reception unit 301, a control unit 302, a page generation unit 303, an authentication unit 304, a message management unit 305, and a DB 306.
The transmission / reception unit 301 processes communication with the Web browser 104 and the document management service 800 of the client apparatus 101. The control unit 302 executes processing according to the request received by the transmission / reception unit 301. The page generation unit 303 generates a web page for returning a response to the web browser 104.

The authentication unit 304 authenticates a user who has requested login, and further manages access rights such as user information, group information, client information, and token information. Authentication data that is referred to when the authentication unit 304 manages the access right is stored in the DB 306.
The message management unit 305 stores the message data in the DB 306, acquires the message data stored in the DB 306, and updates the message data in response to a request. The DB 306 stores message data of the microblog service 300 and information related to the access right described above. The message data and access right information stored in the DB 306 are set and updated at an arbitrary timing by a user such as an administrator via the Web browser 104.

<Authentication / authorization of microblog service 300>
FIG. 4 is a diagram illustrating an example of the login screen 400 and the authorization screen 410. The login screen 400 and the authorization screen 410 are generated by the page generation unit 303 of the microblog service 300 and displayed by the Web browser 104 of the client device 101.
When a request is made from the Web browser 104 to the microblog service 300, the transmission / reception unit 301 receives the request. Subsequently, processing is assigned to the authentication unit 304 by the control unit 302.

When the request is allocated, the authentication unit 304 determines whether the authentication session is valid. Then, the authentication unit 304 notifies the control unit 302 of the result of whether the authentication session is valid or invalid.
When the authentication session is invalid, the control unit 302 causes the page generation unit 303 to generate the login screen 400 and responds to the request with the login screen 400. When the authentication session is valid, the control unit 302 causes the page generation unit 303 to generate an authorization screen 410 and a timeline screen (FIG. 7) described later in response to the request. The control unit 302 responds to the generated authorization screen 410 and timeline screen in response to the request.

The authentication unit 304 manages an authentication session using an authentication token. The authentication unit 304 returns a session ID to the Web browser 104 when the authentication is successful. The Web browser 104 can continue authentication by adding an authentication token to the request. All requests to the microblog service 300 are session-managed by the authentication unit 304.
When the microblog service 300 receives a request, the authentication unit 304 always confirms the authentication session. However, in the following description, for simplification of description, description regarding authentication session confirmation processing in each request is omitted.

As illustrated in FIG. 4, the login screen 400 includes a user name 401, a password 402, and a login button 403. A user name 401 and a password 402 are input fields for a user name and a password necessary for authentication to the microblog service 300. When the login button 403 is pressed, the Web browser 104 transmits a login request including the input user name 401 and password 402 as parameters to the microblog service 300.
The authorization screen 410 has an authorization message 411, a permission button 412 and a rejection button 413. The authorization screen 410 is a screen for confirming to the user whether or not the document management service 800 may be granted access permission (authorization) to information managed by the microblog service 300. The OAuth protocol is generally used as an authorization method, and the authorization screen 410 is an example of an authorization screen defined by the OAuth protocol.

When the information of the microblog service 300 is generated, acquired, updated, or deleted, the document management service 800 transmits an authorization request to the microblog service 300 via the web browser 104 as a scope as a parameter.
The scope indicates a range where authorization is permitted. The document management service 800 according to the present embodiment designates the scope of the information acquisition and message posting of the microblog service 300 as the scope of authorization.
When the transmission / reception unit 301 of the microblog service 300 receives the authorization request, the control unit 302 instructs the page generation unit 303 to generate the authorization screen 410. Then, the control unit 302 responds an authorization screen 410 to the authorization request from the web browser 104.

The authorization message 411 is a message that presents information related to authorization to the user. In the example illustrated in FIG. 4, a message requesting the document management service 800 to obtain information on the microblog service 300 specified by the scope and to authorize message posting is displayed as the authorization message 411.
When the permission button 412 is pressed, the Web browser 104 transmits an authorization permission request to the microblog service 300. When the reject button 413 is pressed, the Web browser 104 transmits an authorization reject request to the microblog service 300.
When the transmission / reception unit 301 of the microblog service 300 receives an authorization permission request, the authentication unit 304 issues an authorization code. The authorization code is transmitted to the document management service 800 via the web browser 104.

The document management service 800 transmits a token acquisition request to the microblog service 300 using the received authorization code and client information as parameters. When receiving the token acquisition request, the microblog service 300 confirms a match between the requested client information and client information 520 (FIG. 5) described later, and issues token information 530.
The microblog service 300 returns an access token 532 and a refresh token 533 to the document management service 800 as a response to the token acquisition request. The document management service 800 adds an access token 532 to the request to the microblog service 300. Thereby, the document management service 800 can make a request for the scope of the microblog service 300.

The refresh token 533 is a token for updating the access token 532. When the microblog service 300 receives the refresh token and the client information in the token update request, the microblog service 300 confirms the match between the refresh token 533 and the client information 520 stored therein.
When the match of the client information 520 is confirmed, the microblog service 300 updates the access token 532 and the refresh token 533. The microblog service 300 returns the updated new access token 532 and refresh token 533 as a response to the token update request.
The access token 532 and the refresh token 533 are provided with expiration dates for use. The access token 532 is updated using the refresh token 533 at the timing when the use expiration date of the access token 532 expires.

FIG. 5 is a diagram illustrating an example of user information 500, group information 510, client information 520, and token information 530 managed by the authentication unit 304 of the microblog service 300 and stored in the DB 306.
The user information 500 is information related to registered users registered in the microblog service 300. The user information 500 includes a user ID 501, a user name 502, a password 503, an icon file path 504, a following user ID 505, a following user ID 506 and a belonging group ID 507.
The user ID 501 is an identifier that uniquely identifies the user information 500. A user name 502 and a password 503 are a user name and a password necessary for authentication. The icon file path 504 is a storage file path of an icon image indicating the user.

The following user ID 505 is the user ID of the user that the user is following, and can store a plurality of user IDs. The followed user ID 506 is a user ID of a user that the user is following, and can store a plurality of user IDs. The follow will be described later.
The group ID 507 is a group ID of a group to which the user belongs, and can store a plurality of group IDs.

The group information 510 is information regarding a group to which a registered user of the microblog service 300 belongs. The group information 510 includes a group ID 511, a group name 512, a belonging user ID 513, and public information 514. The user can create a group and belong to the created group.
The group ID 511 is an identifier that uniquely identifies the group information 510. The group name 512 is a name given to the group. The belonging user ID 513 is a user ID belonging to a group, and can store a plurality of user IDs. The public information 514 is a flag for determining whether a user other than the users belonging to the group can access, and is set to public or private.

The client information 520 includes a client ID 521 and a secret 522. The client ID 521 is an identifier for uniquely identifying client information 520 of a client connected to the microblog service 300. The secret 522 is a password for the client.
The client ID 521 and the secret 522 are issued by the microblog service 300. The client apparatus 101 can make an authorization permission request to the microblog service 300 using the client ID 521 and the secret 522.

The token information 530 includes a user ID 531, an access token 532, a refresh token 533, and a scope 534. The token information 530 is information for managing tokens issued by authorization by the microblog service 300. The user ID 531 is the user ID that issued the token.
The access token 532 is a token used when the client apparatus 101 makes a request. The refresh token 533 is a token for updating the access token 532. The scope 534 is information for designating a range to be authorized.

<Microblog function of microblog service 300>
The microblog service 300 provides a microblog function. The microblog function is a function for sharing a message posted by the user to the microblog service 300 among other users or a specific group. A user can post a message, post a message to a group, view a shared message, and the like. The microblog service 300 also provides a function for commenting on posted messages.
FIG. 6 is a diagram illustrating an example of message information 700 and comment information 710. The message information 700 is information regarding a message posted to the microblog service 300. The comment information 710 is information regarding comments posted to the microblog service 300.

The message information 700 includes a message ID 701, a message 702, a link 703, a user ID 704, a posting destination 705, and a time 706. The message information 700 is generated by the message management unit 305 when the microblog service 300 receives a message posting request that is a message posting request, and is stored in the DB 306.
The message ID 701 is a posting identifier that uniquely identifies the message information 700. A message 702 is a posted message character string. A link 703 is a posted URL. The user ID 704 is the user ID of the posted user.

A posting destination 705 is a posting destination. The posting destination 705 is information indicating a message sharing user indicating a user who a message posting user shares a message which is a posting content. More specifically, the posting destination 705 stores a user ID and a group ID. The posting destination 705 may store a plurality of user IDs and group IDs. Although not registered in the posting destination 705, the posting user naturally also shares the posting content and is included in the message sharing user. If the message destination is not specified, nothing is stored in the posting destination 705. Time 706 is the date and time when the message is posted.
Thus, in the message information 700 of the microblog service 300, the message ID is associated with the user ID and group ID of the posting destination. The message ID is an example of a posting identifier.

The comment information 710 includes a comment ID 711, a comment 712, a message ID 713, a user ID 714, and a time 715. The comment information 710 is generated by the message management unit 305 when the microblog service 300 receives a comment posting request and is stored in the DB 306.
The comment ID 711 is an identifier that uniquely identifies the comment information 710. A comment 712 is a posted comment character string. The message ID 713 is the message ID of the commented message information 700. The user ID 714 is the commented user ID. Time 715 is the date and time of comment.

FIG. 7 is a diagram illustrating an example of a timeline screen. The timeline screen 610 is a timeline screen of the user “userA”. The timeline screen 620 is a timeline screen of the user “userB”. The timeline screen 630 is a timeline screen of the “Group 2” group. When the microblog service 300 succeeds in user authentication, the microblog service 300 generates a timeline screen of the authenticated user and returns it to the Web browser 104.
The user timeline screens 610 and 620 include user information display areas (611 and 621), message posting areas (612 and 622), and comment posting areas (613 to 615, 623 and 624).

The user information display area (611, 621) includes a user icon and a user name. As a user icon, an image stored in an area specified by the icon file path 504 is displayed. In the user name, information on the user name 502 is displayed.
The message posting area (612, 622) includes a message input field, a link input field, and a posting button. When the posting button is pressed, the Web browser 104 transmits a message posting request including information input in the message input field and the link input field as parameters to the microblog service 300. When the microblog service 300 receives a message posting request, the microblog service 300 generates message information 700. The microblog service 300 then regenerates the timeline screen and returns it to the web browser 104.

The comment posting area (613-615, 623, 624) includes a message display area, a comment display area, a comment input field, and a comment button. The message display area includes a user icon, a user name, a posting destination, a message, and a link of the user who posted the message.
The user icon is an image stored in the icon file path 504 associated with the user ID 704. The posting destination is a user name 502 and a group name 512 associated with the user ID or group ID stored in the posting destination 705.

In the comment display area, comment information having a message ID 713 that matches the message ID 701 of the message displayed in the message display area is displayed in order from the newest time 715. The comment display area includes a user icon of the user who posted the comment, a user name 502 and a comment 712.
The user icon is an image stored in the icon file path 504 associated with the user ID 714. When the comment button is pressed, the Web browser 104 transmits a comment posting request including the input data in the comment input field as a parameter to the microblog service 300. When receiving the comment posting request, the microblog service 300 generates the comment information 710, regenerates the timeline screen, and returns it to the Web browser 104.

The comment posting area 613 is an example in which comments of userC and userD are displayed for a message posted by userB to Group1. The comment posting area 614 is an example in which a message and a link posted by userD to Group 2 are displayed.
The comment posting area 615 is an example in which a message and a link posted by userD to userA are displayed. The comment posting area 623 is the same as the comment posting area 613. The comment posting area 624 is an example in which messages and links posted by userC to userB are displayed.

It is assumed that the message information 700 displayed on the user's timeline screen satisfies the following three conditions. The first condition is that the user ID 704 matches the user ID 501 or the following user ID 505. The second condition is that the user ID of the posting destination 705 matches the user ID 501 of the own user. The third condition is that the group ID of the posting destination 705 matches the belonging group ID 507.
The user's timeline screen can also refer to other users' timeline screens. The timeline screen of another user is linked to the user name in the timeline screen, and is displayed when the link is pressed.

The message information 700 displayed on the timeline of another user is assumed to satisfy the following three conditions. The first condition is that the user ID 704 matches the user ID 501 of the own user or the display user. The second condition is that the user ID 704 matches the user ID 505 followed by the display user. The third condition is that the group ID of the posting destination 705 matches the group ID 507 of the display user, and the public information 514 is set to public.
Message information 700 that satisfies the above conditions and comment information 710 associated with the message are displayed on the user's timeline screen.
The display order of the comment display area is the latest time of the time 706 of the message information 700 and the time 715 of the comment information 710 displayed in the comment display area, and is the newest time.

A timeline screen 630 in FIG. 7 is a timeline screen of “Group 2”. The group timeline screen 630 is linked to the group name in the timeline screen, and is displayed when the link is pressed.
The group timeline screen includes a group information display area 631, a message posting area 632, and a comment posting area 633. In the group information display area 631, information on the group name 512 is displayed. The message posting area 632 is similar to the message posting area (612, 622) on the user timeline screen, but is posted with a group as a posting destination. The comment posting area 633 is the same as the message posting area (613-615, 623, 624) on the user timeline screen.

The message information 700 displayed on the group timeline screen 630 satisfies the following conditions. The first condition is that the group ID of the posting destination 705 matches the group ID 511 of the display group. The second condition is that the group ID 511 of the display group matches the group ID 507 of the own user. The third condition is that the display group public information 514 is set to public.
Message information 700 that satisfies the above conditions and comment information 710 associated with the message are displayed on the timeline screen of the group. The display order of the comment display area is the newest order of the time at the latest time among the time 706 of the message information 700 and the time 715 of the comment information 710 displayed in the comment display area.

<Software module configuration of document management service providing server device>
FIG. 8 is a diagram showing a configuration of a software module (document management service 800) of the document management service providing server apparatus 103. The document management service 800 includes a document sharing service 801 and an authentication service 811. The document sharing service 801 includes a transmission / reception unit 802, a control unit 803, a page generation unit 804, a document management unit 805, a message information management unit 806, and a DB 807. The authentication service 811 includes a transmission / reception unit 812, a control unit 813, a user management unit 814, a token management unit 815, and a DB 816.
The software module programs are stored in the HDD 204 shown in FIG. 2, and are loaded into the RAM 203 by the CPU 201 and executed as described above to implement the software modules.

The transmission / reception unit 802 processes communication with the Web browser 104 of the client apparatus 101, the microblog service 300, and the authentication service 811. The control unit 803 executes processing according to the request received by the transmission / reception unit 802. The page generation unit 804 generates a web page for returning a response to the web browser 104.
A document management unit 805 manages documents stored in the DB 807 and document information 1400 described later. For example, the document management unit 805 registers, acquires, updates, and deletes a document and document information 1400 in response to a request from the control unit 803.

The message information management unit 806 manages the message information 1410 on the DB 807. For example, the message information management unit 806 registers, acquires, updates, and deletes the message information 1410 in response to a request. Here, the message information 1410 is information that associates a document and document information 1400 with a message on the microblog service 300.
The DB 807 stores user setting information of the document sharing service 801 in addition to the document, document information 1400, and message information 1410. Information stored in the DB 807 is registered or updated at an arbitrary timing by a user such as an administrator via the Web browser 104.

The transmission / reception unit 812 of the authentication service 811 processes communication with the document sharing service 801. The control unit 813 executes processing according to the request received by the transmission / reception unit 812. The user management unit 814 manages user information 1420 described later stored in the DB 816. The user management unit 814 registers, acquires, updates, and deletes the user information 1420 in response to a request from the control unit 813, for example.
The token management unit 815 manages later-described authentication token information 1430 and microblog access token information 1440 stored in the DB 816 as well as the user information 1420. The token management unit 815 registers, acquires, updates, and deletes the authentication token information 1430 and the microblog access token information 1440 in response to a request from the control unit 813, for example.

<Management Information in Document Management Service 800>
FIG. 9 is a diagram showing document information 1400, message information 1410, user information 1420, authentication token information 1430, and microblog access token information 1440. Document information 1400 and message information 1410 are information stored in the DB 807 of the document sharing service 801.
The document information 1400 is information relating to a document as content, that is, content information. Document information 1400 is additional information related to a document. The document information 1400 includes a document ID 1401, a document storage location 1402, a user ID 1403, a document name 1404, a shared message ID 1405, a sharing permitted user ID and a group ID 1406.

The document ID 1401 is an identifier that uniquely identifies a document. The document storage destination 1402 is information indicating a file path, URL, and the like necessary for accessing the document. Note that the document is stored in the HDD 204 of the document management service providing server apparatus 103. As another example, the document may be stored in another device. In this case, information necessary for accessing the storage device is stored in the document storage location 1402.
The user ID 1403 is an identifier representing a user who created and registered a document in the document management service 800, that is, a creation user. The document name 1404 is the title of the document and is a character string that can be arbitrarily determined by the user.

The shared message ID 1405 is a posting identifier issued when the document information 1400 is posted to the microblog service 300. That is, the shared message ID 1405 is information corresponding to the message ID 701 of the microblog service 300.
The user ID and group ID 1406 permitted to share are the user ID and group ID that the document creation user permitted to share the document. Here, the user ID and group ID 1406 permitted to share are examples of a document sharing user (content sharing user) indicating a user who should share the document (content).
In addition, the document information 1400 may include arbitrary information regarding the document such as the document size and the number of pages.

The message information 1410 includes information about a message posted to the microblog service 300 for a document stored in the document management service providing server device 103. The message information 1410 includes a message ID 1411, a microblog URL 1412, a message posting user ID 1413, a posting destination 1414, and a document ID 1415.
The message ID 1411 is an identifier for uniquely identifying a message on the microblog service 300. The message ID 1411 is a posting identifier issued by the microblog service 300 when a message is posted.

The microblog URL 1412 is a URL for accessing the microblog service 300. In the microblog URL 1412, for example, the endpoint URL of the web service of the microblog service 300 is stored. The message posting user ID 1413 is the user ID of the user who posted the message on the microblog service 300. The posting destination 1414 is information indicating a message posting destination user ID or a posting destination group ID on the microblog service 300. The document ID 1415 is an identifier for associating the document information 1400 with the message information 1410.
Note that the shared message ID 1405, the document information 1400 that associates the user ID and group ID 1406 permitted to be shared with the document ID, and the message information 1410 are stored in the DB 807.

User information 1420, authentication token information 1430, and microblog access token information 1440 are information stored in the DB 816 of the authentication service 811. User information 1420 is information of a user registered as a user of the document management service 800. The user information 1420 includes a user ID 1421 and a password 1422.
The user ID 1421 is an identifier that uniquely identifies a user in the document management service 800. The password 1422 is a password used for authentication together with the user ID 1421 when the user logs in to the document management service 800 via the Web browser 104. In addition, the user information 1420 may include arbitrary information regarding the user such as a name and an e-mail address.

The authentication token information 1430 is authentication information of a user who has logged into the document management service 800. The authentication token information 1430 includes an authentication token 1431, a user ID 1432, and a time 1433. The authentication token 1431 is a character string unique within at least the document management service 800 for proving that it has been authenticated. The user ID 1432 is information indicating the user ID of an authenticated user. The time 1433 stores a date and time for determining the expiration date of the authentication token 1431.
The microblog access token information 1440 is user authorization information necessary for the document management service 800 to access the microblog service 300. The microblog access token information 1440 includes a user ID 1441, a microblog URL 1442, an access token 1443, and a refresh token 1444.

The user ID 1441 is an identifier for identifying a user on the document management service 800. The user ID 1441 corresponds to the user ID 1421 of the user information 1420. The microblog URL 1442 is a URL of a microblog to which the microblog access token information 1440 is to be used, and corresponds to the microblog URL 1412 of the message information 1410.
The access token 1443 is a character string including authorization information necessary for accessing the microblog URL 1442 with the user ID 1441. The refresh token 1444 is a token required for updating the access token 1443 issued by the microblog service 300.

<Authentication of document management service 800>
FIG. 10 is a diagram illustrating an example of a document management service login screen 900 displayed by the Web browser 104 of the client apparatus 101. The document management service login screen 900 is generated by the page generation unit 804 of the document management service 800.
When a request is made from the Web browser 104 to the document management service 800, the transmission / reception unit 802 receives the request. Subsequently, the transmission / reception unit 802 transmits an authentication check request to the authentication service 811 under the control of the control unit 803. At this time, the control unit 803 confirms whether the authentication token 1431 is included in the request, and if included, passes the authentication token to the authentication service 811.

The authentication service 811 receives a request at the transmission / reception unit 812. Subsequently, the control unit 813 requests the token management unit 815 to check the validity of the authentication token information 1430. The control unit 813 receives the result of whether or not the authentication token 1431 is valid from the token management unit 815. The control unit 813 transmits the result of whether or not it is valid to the document sharing service 801 via the transmission / reception unit 812.
When checking the validity of the authentication token 1431, the authentication token information 1430 is referred to, and it is checked whether the target authentication token 1431 is stored, whether the validity period has expired from the time 1433, or the like. The control unit 803 of the document sharing service 801 instructs the page generation unit 804 to generate the document management service login screen 900 when the authentication token 1431 is invalid.

Then, the control unit 803 responds to the generated document management service login screen 900 in response to the request. If the authentication token 1431 is valid, the control unit 803 generates a preview screen 1000 or the like, which will be described later, and responds in response to the request.
The document management service login screen 900 includes a user name 901, a password 902, and a login button 903. A user name 901 and a password 902 are input fields for a user ID and password necessary for authentication to the document management service 800. When the login button 903 is pressed, the Web browser 104 transmits a login request including information input to the user name 901 and the password 902 as parameters to the document management service 800.

When the login request is made, the control unit 813 of the authentication service 811 checks the validity. The control unit 813 confirms whether the combination of the user name 901 and the password 902 included in the login request is associated with each other in the user information 1420.
When the combination included in the login request exists in the user information 1420, the control unit 813 issues authentication token information 1430. Then, the control unit 813 stores the authentication token information 1430 in the DB 816 and returns the authentication token 1431 to the Web browser 104.
The Web browser 104 can continue authentication by adding the acquired authentication token 1431 to the request. All requests to the document management service 800 are authenticated and managed by the authentication service 811. When the document management service 800 receives the request, the authentication information is always checked. However, for the sake of simplicity, the description of the authentication information will be omitted hereinafter.

<Document Preview of Document Sharing Service 801>
FIG. 11 is a diagram illustrating an example of a document preview screen 1000 displayed by the Web browser 104 of the client apparatus 101. The preview screen 1000 is generated by the page generation unit 804 of the document sharing service 801.
In the generation process of the preview screen 1000, first, a document preview request including information for identifying a document is transmitted from the Web browser 104 to the document sharing service 801. When the transmission / reception unit 802 receives the request, the control unit 803 acquires the document information 1400 from the document management unit 805.

Here, the information for identifying a document transmitted from the Web browser 104 may be, for example, a URL including a document ID 1401. The control unit 803 can acquire document information 1400 that meets the request from the document management unit 805 by referring to the document ID 1401 included in the URL. The control unit 803 refers to the acquired document information 1400 and instructs the page generation unit 804 to generate a preview screen 1000 that can be displayed by the Web browser 104. Further, the control unit 803 returns the generated preview screen 1000 to the Web browser 104 through the transmission / reception unit 802.
The preview screen 1000 displays a document image 1010 acquired by referring to the document storage destination 1402 of the document information 1400, and also displays a document name 1002, a user name 1001, and the like. Also, in the area 1020 where the preview operation is performed, a button 1021 for performing page turning and an input area 1022 for designating a display page are displayed.

<Document Registration to Document Management Service 800>
Next, a document registration process to the document management service 800 by the content sharing system will be described with reference to FIGS. FIG. 12 is a diagram illustrating an example of a document registration screen displayed on the Web browser 104 of the client apparatus 101. A document registration screen 1100 shown in FIG. 12 is displayed when the Web browser 104 accesses the document management service 800 and makes a document registration screen display request.
The document registration screen 1100 includes a file name 1101 for specifying a document to be registered and a document registration button 1102. When the document registration button 1102 is pressed, the client apparatus 101 issues a document registration request for transmitting the document specified by the file name 1101 to the document management service 800.

FIG. 13 is a sequence diagram of document registration processing. Assume that the user logs in to the document management service 800 on the login screen 400 and the document registration screen 1100 (FIG. 12) is displayed on the Web browser 104. In this state, assume that the user presses the document registration button 1102 on the document registration screen 1100 displayed on the Web browser 104 of the client apparatus 101. In response to this, the Web browser 104 accepts a registration instruction corresponding to the document registration button 1102. In step S1201, the Web browser 104 transmits a document registration request to the document management service 800 together with the document.
The transmission / reception unit 802 of the document management service 800 receives a document registration request and a document (content reception process). In step S1202, the document management unit 805 stores the document received together with the document registration request and the document information 1400 corresponding to the document in the DB 807.
Further, the control unit 803 generates a document URL for the Web browser 104 to access the document based on the document. Further, the document management unit 805 stores the message information 1410 in the DB 807 using the document URL as a message. The document information 1400 and message information 1410 registered in S1202 are associated with each other by a message ID. That is, the process of S1202 is an example of a content registration process in which the message ID as the posting identifier and the document as the content are associated with each other and stored in the storage unit.

In step S <b> 1203, the transmission / reception unit 802 redirects the access token acquisition request to the web browser 104 under the control of the control unit 803. Here, the access token acquisition request is information requesting acquisition of an access token for posting a message from the document management service 800 to the microblog service 300.
In steps S1204 to S1210, the document management service 800 acquires an access token from the microblog service 300. The process for acquiring the access token has been described in <Authentication / authorization of microblog service 300>, and will not be described. The token management unit 815 of the document management service 800 stores the acquired access token in the DB 816 as the access token 1443.

In step S1211, the message information management unit 806 of the document management service 800 transmits a message posting request to the microblog service 300 together with the access token 1443 acquired in step S1208. The message posting request is request information for writing the document URL generated in S1202 as a message, and includes a message. S1211 is an example of posted information transmission processing.
The microblog service 300 receives a message registration request. Subsequently, the control unit 302 of the microblog service 300 confirms that the access token 1443 is an access token permitted to write a message through the authentication unit 304. When the control unit 302 confirms the access token, in step S <b> 1212, the message management unit 305 writes message information 700 having the document URL as a message in the DB 306. This completes the document registration process. A user can access a document by connecting to the microblog service 300 via the Web browser 104 and specifying a document URL as a message.

<Delete Document from Document Management Service 800>
FIG. 14 is a sequence diagram of document deletion processing. Assume that the user logs in to the document management service 800 on the login screen 400 and the preview screen 1000 (FIG. 11) is displayed on the Web browser 104. In this state, when the delete button 1040 on the preview screen 1000 is pressed by the user, the Web browser 104 receives an instruction to delete the document corresponding to the delete button 1040. When the Web browser 104 accepts the content deletion instruction, the Web browser 104 transmits a document deletion request together with the document ID to the document management service 800 in S1401. Here, the document deletion request is an example of a content deletion instruction. Further, S1401 is an example of a deletion instruction reception process.
The transmission / reception unit 802 of the document management service 800 receives the document deletion request and the document ID. In step S1402, the message information management unit 806 of the document management service 800 specifies message information 1410 related to the document to be deleted using the document ID as a key, and specifies the document ID 1415 included in the message information 1410. That is, S1402 is an example of a posting identifier specifying process.

In step S1403, the control unit 803 of the document management service 800 inquires the authentication service 811 about the microblog access token information 1440 that matches the message information 1410 specified in step S1402. In the authentication service 811, the transmission / reception unit 812 receives an inquiry. Then, the token management unit 815 acquires the microblog access token information 1440 under the control of the control unit 813, using the microblog URL 1412 and the message posting user ID 1413 as keys. Then, the transmission / reception unit 812 returns the microblog access token information 1440 to the document sharing service 801 under the control of the control unit 813.
Upon acquiring the microblog access token information 1440 from the authentication service 811, the document sharing service 801 transmits a message deletion request (message deletion request) including the document URL to the microblog service 300 in S1404. More specifically, the document sharing service 801 transmits the message deletion request with the microblog URL 1412 of the microblog access token information 1440 as the transmission destination of the message deletion request. The message deletion request is a deletion request including the access token 1443 of the microblog access token information 1440 and using the message ID 1411 of the message information 1410 acquired in S1402 as a key. Note that S1404 is an example of a deletion request transmission process.

In the microblog service 300, the transmission / reception unit 301 receives a message deletion request. Then, the control unit 302 inquires of the authentication unit 304 about the validity of the access token 1443 included in the message deletion request.
When the validity of the access token 1443 is confirmed, in step S1405, the message management unit 305 deletes the message using the message ID 1411 included in the message deletion request as a key under the control of the control unit 302.

Next, the transmission / reception unit 301 transmits the message deletion result to the document management service 800 as response information under the control of the control unit 302. Here, when the message deletion is successful, the transmission / reception unit 301 transmits response information indicating that the message deletion is successful. When the message deletion is not successful, the transmission / reception unit 301 indicates that the message deletion is not successful. Send response information.
The transmission / reception unit 802 of the document management service 800 receives response information indicating the result of message deletion (response information reception process). Then, the control unit 803 of the document management service 800 confirms the result of message deletion indicated in the response information. In step S <b> 1406, the document management unit 805 deletes the document and the document information 1400 stored in the DB 807 when the deletion is successful under the control of the control unit 803. Here, S1406 is an example of content deletion processing. The document management service 800 further transmits a document deletion result to the Web browser 104 of the client apparatus 101.

FIG. 15 is a flowchart showing detailed processing of the document management service 800 in document deletion processing. Note that description of the processing described with reference to FIG. 14 is omitted. In the document management service 800, first, in S1501, the transmission / reception unit 802 receives a document deletion request. In step S1502, the message information management unit 806 searches for message information 1410 related to the document to be deleted.
If the message information 1410 is not detected in S1502, the message information management unit 806 determines in S1503 that there is no message posting to the microblog service 300. In this case, the control unit 803 advances the process to S1507. In step S <b> 1507, the document management unit 805 deletes the document stored in the DB 807 and the document information 1400.

On the other hand, if the message information 1410 is detected in S1502, the message information management unit 806 determines in S1503 that there is a message post to the microblog service 300. Then, the control unit 803 advances the process to S1504. In step S <b> 1504, the transmission / reception unit 802 acquires a microblog access token 1443 from the authentication service 811 under the control of the control unit 803.
In step S <b> 1505, the transmission / reception unit 802 transmits a message deletion request to the microblog service 300 using the message ID 1411 as a key. Subsequently, the transmission / reception unit 802 receives response information indicating the result of message deletion from the microblog service 300. Upon receiving the response information, the control unit 803 confirms the result of message deletion based on the response information.

If the message is successfully deleted in S1506, the control unit 803 advances the process to S1507. In step S1507, the document management unit 805 deletes the document and the document information 1400. If the deletion of the message is not successful in S1506, the control unit 803 advances the process to S1508. In step S <b> 1508, the transmission / reception unit 802 returns the result of the document deletion request to the web browser 104 of the client apparatus 101 under the control of the control unit 803. That is, when the message deletion is not successful, the control unit 803 does not delete the document.
As described above, in the content management system according to the present embodiment, when deleting a document, the deletion of a message posted regarding the document is requested, and the document is deleted only when the deletion is successful. For this reason, in the content management system, it is possible to prevent the occurrence of dead links. Further, in the content management system, when a document deletion instruction is received from the user, the document and the message related to the document are automatically deleted, so that a complicated operation by the user can be eliminated.

(Second Embodiment)
Next, a content management system according to the second embodiment will be described. In the content management system according to the second embodiment, when a comment regarding a message exists, the message is appropriately left and only the document is deleted.
More specifically, in the content management system according to the second embodiment, when a comment exists, it is determined whether or not to delete the message according to an instruction from the user.

FIG. 16 is a flowchart showing document deletion processing by the document management service 800 according to the second embodiment. In step S1601, the transmission / reception unit 802 of the document management service 800 receives a document deletion request. In step S1602, the message information management unit 806 searches for message information 1410 related to the document to be deleted. If the message information 1410 is not detected, in S1603, the message information management unit 806 determines that there is no message posted to the microblog service 300. In this case, the control unit 803 advances the process to S1610. In step S <b> 1610, the document management unit 805 deletes the document and document information 1400 stored in the DB 807.
On the other hand, if the message information 1410 is detected in S1602, the message information management unit 806 determines in S1603 that a message has been posted to the microblog service 300. Then, the control unit 803 advances the process to S1604. In step S <b> 1604, the transmission / reception unit 802 acquires the access token 1443 from the authentication service 811 under the control of the control unit 803.

In step S <b> 1605, the control unit 803 of the document sharing service 801 generates an acquisition request for comment information 710 using the message ID 1411 including the access token 1443 acquired in step S <b> 1604 as a key. Then, the transmission / reception unit 802 transmits a request for obtaining the comment information 710 to the microblog service 300 having the microblog URL 1412.
In the microblog service 300, the message management unit 305 searches the comment information 710 for the message identified by the message ID 1411 using the message ID 1411 as a key. Then, when the comment information 710 is detected, the transmitting / receiving unit 301 of the microblog service 300 transmits the detected comment information 710 to the document management service 800.

The transmission / reception unit 802 of the document management service 800 receives the comment information 710 as a request result for the acquisition request (comment information reception process). When the document sharing service 801 acquires the comment information 710 as the request result of S1605, the page generation unit 804 generates a message deletion confirmation screen and returns it to the Web browser 104 in S1606. The message deletion confirmation screen is an example of selection screen information. S1606 is an example of a selection screen information generation process.
FIG. 17 is a diagram illustrating an example of a message deletion confirmation screen. A message deletion confirmation screen 1700 shown in FIG. 17 includes a document information display area 1701, a comment information display area 1702, and a selection button 1703. In the document information display area 1701, a part of the content of the document information 1400 to be deleted is displayed. In the comment information display area 1702, a part or all of the comment information 710 acquired in S1605 is displayed. A selection button 1703 is a button for the user to make a selection after confirming the screen.

The user confirms the comment information 710 on the message deletion confirmation screen 1700 displayed on the Web browser 104 and presses the selection button 1703. When the selection button 1703 is pressed by the user, the transmission / reception unit 802 of the document management service 800 receives a message deletion selection result corresponding to the pressing of the selection button 1703 from the Web browser 104 (selection reception process). In step S1607, the control unit 803 confirms the selection result.
In S1607, when an option not to delete a message is selected, the control unit 803 advances the process to S1610. If an option for deleting a message is selected in S1607, the control unit 803 advances the process to S1608. In step S1608, the transmission / reception unit 802 transmits a message deletion request to the microblog service 300 using the message ID 1411 as a key together with the access token 1443 under the control of the control unit 803.

Subsequently, the transmission / reception unit 802 receives response information indicating the result of message deletion from the microblog service 300. Upon receiving the response information, the control unit 803 confirms the result of message deletion based on the response information. If the message is successfully deleted in S1609, the control unit 803 advances the process to S1610.
If the deletion of the message is not successful in S1609, the control unit 803 advances the process to S1611. That is, in this case, the control unit 803 does not delete the document. In step S <b> 1611, the transmission / reception unit 802 returns the result of the document deletion request to the web browser 104 of the client apparatus 101 under the control of the control unit 803.

As described above, in the content management system according to the second embodiment, when there is a comment for a message regarding a document, it is possible to delete only the document and leave a message in accordance with an instruction from the user. Thereby, the convenience of the content management system can be improved.
The remaining configuration and processing of the content management system according to the second embodiment are the same as the configuration and processing of the content management system according to the first embodiment.

  As a modification example of the content management system according to the second embodiment, the content management system may determine whether to leave a message about a document according to an instruction from the user even when there is no comment on the message. Good. In this case, the document information and the selection button may be displayed on the message deletion confirmation screen.

<Other embodiments>
The present invention can also be realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media. Then, the computer (or CPU, MPU, etc.) of the system or apparatus reads and executes the program.

  As described above, according to each embodiment described above, it is possible to provide a mechanism capable of appropriately sharing information among a plurality of services without requiring a complicated operation by a user.

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.

Claims (10)

A deletion request transmission means for transmitting a deletion request for posting information related to content posted to the posting management service to the posting management service;
Response information receiving means for receiving response information indicating successful deletion of the posted information in response to the deletion request from the posting management service;
A content management apparatus comprising: a content deletion unit that deletes the content stored in a storage unit when the response information reception unit receives the response information. The storage means stores the content in association with a post identifier for identifying the post information related to the content;
The deletion request transmission means transmits the deletion request including the post identifier to the post management service,
The response information receiving means receives the response information including the posting identifier,
The content management apparatus according to claim 1, wherein the content deletion unit deletes the content associated with the posting identifier included in the response information in the storage unit. A deletion instruction receiving means for receiving a content deletion instruction input by a user;
When the deletion instruction is accepted, the storage unit further includes a specifying unit that specifies the posting identifier associated with the content that is the target of the content deletion instruction,
3. The content management apparatus according to claim 2, wherein the deletion request transmission unit transmits the deletion request including the posting identifier specified by the specifying unit to the posting management service. Content receiving means for receiving the content;
Post information sending means for sending the post information related to the content to the post management service when the content receiving means receives the content;
4. The content registration unit according to claim 2, further comprising: a content registration unit that associates the post identifier of the post information transmitted by the post information transmission unit with the content and stores the content in the storage unit. 5. Content management device. Further comprising selection accepting means for accepting selection by the user as to whether or not to delete the posted information;
The said deletion request transmission means transmits the said deletion request | requirement to the said post | mailbox management service, when the said selection reception means receives selection which performs deletion, The said posting request | requirement service is characterized by the above-mentioned. Content management device. Comment information receiving means for receiving, from the post management service, comment information for the post information subject to the deletion request;
When the comment information receiving means receives the comment information, the comment information receiving means further includes generation means for generating selection screen information for accepting selection of whether or not to delete the posted information,
The content management apparatus according to claim 5, wherein the deletion request transmission unit transmits the deletion request when a selection for deletion is input by a user on the selection screen. A deletion request transmission means for transmitting a deletion request for posting information related to content posted to the posting management service to the posting management service;
Response information receiving means for receiving response information indicating successful deletion of the posted information in response to the deletion request from the posting management service;
A content management system comprising: content deletion means for deleting the content stored in the storage means when the response information receiving means receives the response information. A content management method executed by a content management device,
A deletion request transmission step of transmitting a deletion request for posting information related to content posted to the posting management service to the posting management service;
A response information receiving step for receiving response information indicating that the deletion of the posted information in response to the deletion request has been successful, from the posting management service;
A content management method comprising: a content deletion step of deleting the content stored in the storage means when the response information is received in the response information reception step. A content management method executed by a content management system,
A deletion request transmission step of transmitting a deletion request for posting information related to content posted to the posting management service to the posting management service;
A response information receiving step for receiving response information indicating that the deletion of the posted information in response to the deletion request has been successful, from the posting management service;
A content management method comprising: a content deletion step of deleting the content stored in the storage means when the response information is received in the response information reception step. Computer
A deletion request transmission means for transmitting a deletion request for posting information related to content posted to the posting management service to the posting management service;
Response information receiving means for receiving response information indicating successful deletion of the posted information in response to the deletion request from the posting management service;
The program for functioning as a content deletion means for deleting the content stored in the storage means when the response information receiving means receives the response information.

Images