WO2013055371A1 - Automatic and semi-automatic tagging feature of work items in a shared workspace for metadata tracking in a cloud-based content management system with selective or optional user contribution - Google Patents
Automatic and semi-automatic tagging feature of work items in a shared workspace for metadata tracking in a cloud-based content management system with selective or optional user contribution Download PDFInfo
- Publication number
- WO2013055371A1 WO2013055371A1 PCT/US2011/056472 US2011056472W WO2013055371A1 WO 2013055371 A1 WO2013055371 A1 WO 2013055371A1 US 2011056472 W US2011056472 W US 2011056472W WO 2013055371 A1 WO2013055371 A1 WO 2013055371A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- metadata
- folder
- workspace
- attributes
- user
- Prior art date
Links
- 238000000034 method Methods 0.000 claims abstract description 57
- 238000013507 mapping Methods 0.000 claims description 4
- 230000008569 process Effects 0.000 description 23
- 238000010586 diagram Methods 0.000 description 16
- 238000004891 communication Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 4
- 230000001413 cellular effect Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000012552 review Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 101100162169 Xenopus laevis adrm1-a gene Proteins 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000007717 exclusion Effects 0.000 description 1
- RGNPBRKPHBKNKX-UHFFFAOYSA-N hexaflumuron Chemical compound C1=C(Cl)C(OC(F)(F)C(F)F)=C(Cl)C=C1NC(=O)NC(=O)C1=C(F)C=CC=C1F RGNPBRKPHBKNKX-UHFFFAOYSA-N 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/38—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
Definitions
- FIG. 1 illustrates an example diagram of a system where a host server supports file metadata in an online collaboration environment.
- FIG. 2 depicts an example diagram of a web-based or online collaboration platform deployed in an enterprise or other organizational setting for organizing work items and workspaces.
- FIG. 3 depicts a block diagram illustrating an example of components in the host server of a web-based collaboration environment that supports file metadata.
- FIG. 4 depicts a screenshot of an example user interface that shows attributes managed and maintained for an account by the account administrator.
- FIG. 5 depicts a screenshot of an example user interface that shows attribute setup during creation of a new folder.
- FIG. 6 depicts a screenshot of an example user interface for entering missing attributes for a work item.
- FIG. 7 depicts a screenshot of an example user interface that shows tags and attributes of a work item.
- FIG. 8 depicts a flow diagram illustrating an example process of creating metadata attributes by an administrator.
- FIG. 9 depicts a flow diagram illustrating an example process of creating metadata attribute sets by an administrator.
- FIG. 10 depicts a flow diagram illustrating an example process of creating a new folder.
- FIG. 11 depicts a flow diagram illustrating an example process of uploading a file.
- FIG. 12 depicts a flow diagram illustrating an example process of a collaborator entering a workspace.
- FIG. 3 shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
- a system for supporting metadata for work items stored in a workspace in a web-based content management system with a collaboration environment.
- the creator of the workspace specifies metadata attributes for all work items stored in the workspace.
- a user uploading a work item to the workspace is not required to provide metadata for the specified attributes before being permitted to upload the work item to the workspace.
- Collaborators of the workspace can provide metadata for any work item stored within the folder.
- FIG. 1 illustrates an example diagram of a system where a host server 100 supports collaborative metadata for work items in a content management system with an online collaboration environment for users 108 of the work items.
- the content management system can generally be a cloud-based service.
- the client devices 102 can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection, including wired, wireless, cellular connections with another device, a server and/or other systems such as host server 100.
- Client devices 102 will typically include a display and/or other output functionalities to present information and data exchanged between or among the devices 102 and/or the host server 100.
- the client devices 102 can include mobile, hand held or portable devices or non-portable devices and can be any of, but not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices including, a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a smart phone, a PDA, a Blackberry device, a Treo, a handheld tablet (e.g. an iPad, a Galaxy, Xoom Tablet, etc.), a tablet PC, a thin-client, a hand held console, a hand held gaming device or console, an iPhone, and/or any other portable, mobile, hand held devices, etc.
- the client devices 102 and host server 100 are coupled via a network 106.
- the devices 102 and host server 100 may be directly connected to one another.
- the input mechanism on client devices 102 can include touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1- axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination of the above.
- touch screen keypad including single touch, multi-touch, gesture sensing in 2D or 3D, etc.
- a physical keypad e.g., a mouse, a pointer, a track pad
- motion detector e.g., including 1- axis, 2-axis, 3-axis accelerometer, etc.
- a light sensor e.g., including 1- axis, 2-axis, 3-axis acceler
- Signals received or detected indicating user activity at client devices 102 through one or more of the above input mechanism, or others, can be used in the disclosed technology by various users or collaborators (e.g., collaborators 108) for accessing, through network 106, a web-based content management system with a collaboration environment or online collaboration platform (e.g., hosted by the host server 100).
- a web-based content management system with a collaboration environment or online collaboration platform (e.g., hosted by the host server 100).
- the collaboration platform or environment hosts workspaces with work items stored in the data repository 130 that one or more users can access (e.g., view, edit, update, revise, comment, add to discussions, download, preview, tag, or otherwise manipulate, etc.).
- a work item can generally include any type of digital or electronic content that can be viewed or accessed via an electronic device (e.g., device 102).
- the digital content can include .pdf files, .doc, slides (e.g., Powerpoint slides), images, audio files, multimedia content, web pages, blogs, etc.
- the data repository 130 is a database that can be managed by a database management system (DBMS), for example but not limited to, Oracle, DB2, Microsoft Access, Microsoft SQL Server, PostgreSQL, MySQL, FileMaker, etc.
- DBMS database management system
- the data repository 130 can be implemented via object-oriented technology and/or via text files, and can be managed by a distributed database management system, an object- oriented database management system (OODBMS) (e.g., ConceptBase, FastDB Main Memory Database Management System, JDOInstruments, ObjectDB, etc.), an object- relational database management system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS, etc.), a file system, and/or any other convenient or known database management package.
- OODBMS object- oriented database management system
- ORDBMS object- relational database management system
- a workspace can generally refer to any grouping of a set of digital content in the collaboration platform.
- the content management system permits a user to group stored files in a hierarchical manner, such that a workspace made up of a group of files can be contained within another workspace, such as a folder.
- the grouping can be created, identified, or specified by a user or through other means. This user may be a creator user or administrative user, for example.
- the workspace can also include an online discussion area for collaborators to engage in an online discussion.
- a workspace can be associated with a set of users or collaborators (e.g., collaborators 108) who have access to the content included therein.
- the levels of access (e.g., based on permissions or rules) of each user or collaborator to access the content in a given workspace may be the same or may vary among the users.
- Each user may have their own set of access rights to every piece of content in the workspace, or each user may have different access rights to different pieces of content.
- Access rights may be specified by a user associated with a work space and/or a user who created/uploaded a particular piece of content to the workspace, or any other designated user or collaborator.
- access rights can include permission to view and/or edit metadata or attributes associated with a work item.
- the collaboration platform allows multiple users or collaborators to access or collaborate efforts on work items such that each user can see, remotely, edits, revisions, comments, or annotations being made to specific work items through their own user devices.
- a user can upload a document to a work space for other users to access (e.g., for viewing, editing, commenting, discussing, signing-off, or otherwise manipulating).
- the user can log in to the online platform and upload the document (or any other type of work item) to an existing work space or to a new work space.
- the document can be shared with existing users or collaborators in a work space.
- FIG. 2 A diagrammatic illustration of the online collaboration environment and the relationships between workspaces and users/collaborators are illustrated with further reference to the example of FIG. 2.
- discussions among collaborators of a workspace or folder can be linked to the particular workspace or folder, and collaborators can create topics for discussion and comment on those topics.
- client devices 102 communicate with the host server 100 over network 106.
- network 106 over which the client devices 102 and the host server 100 communicate, may be a cellular network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination thereof.
- the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-232, SDH, SONET, etc.
- OSI Open System Interconnections
- the network 106 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices 102 and the host server 100 and may appear as one or more networks to the serviced systems and devices.
- communications to and from the client devices 102 can be achieved by, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet.
- communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS).
- SSL secure sockets layer
- TLS transport layer security
- communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMax, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WWAN), enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Digital Advanced Mobile Phone Service (D-Amps), Bluetooth, Wi-Fi, Fixed Wireless Data, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, 3G LTE, 3GPP LTE, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, 1 xRTT, EV-
- GSM Global System
- FIG. 2 depicts an example diagram of a web-based or online collaboration platform deployed in an enterprise or other organizational setting 250 for organizing workspaces 205, 225, 245 which include work items 215, 235, 255 and for providing a discussion workspace area 217, 237, 257 linked to the respective workspaces 205, 225, 245.
- the web-based platform for collaborating on projects or jointly working on documents can be used by individual users and shared among collaborators.
- the collaboration platform can be deployed in an organized setting including but not limited to, a company (e.g., an enterprise setting), a department in a company, an academic institution, a department in an academic institution, a class or course setting, or any other types of organizations or organized setting.
- multiple workspaces can be created to support different projects or a variety of work flows.
- Each workspace can have its own associated work items.
- work space A 205 and discussion workspace 217 can be associated with work items 215, work space B 225 and discussion workspace 237 can be associated with work items 235, and work space N 245 and discussion workspace 257 can be associated with work items 255.
- the work items 215, 235, and 255 may be unique to each work space but need not be.
- a particular document can be associated with only one work space (e.g., work space A 205) or it may be associated with multiple work spaces (e.g., work space A 205 and work space B 225, etc.).
- each work space has a set of users or collaborators associated with it.
- work space A 205 is associated with multiple users or collaborators 206.
- work spaces deployed in an enterprise may be department specific.
- work space B may be associated with department 210 and some users shown as example user A 208
- workspace N 245 can be associated with departments 212 and 216 and users shown as example user B 214.
- Each user associated with a work space can generally access the work items associated with the work space.
- the level of access will depend on permissions associated with the specific work space, and/or with a specific work item. Permissions can be set for the work space or set individually on a per work item basis.
- the creator of a work space e.g., one of user A 208 who creates work space B
- Creator user A 208 may also set different permission settings for each work item, which may be the same for different users, or varying for different users.
- a first type of permission level e.g. an editor
- a second type of permission level e.g. a viewer
- a third type of permission level e.g. an uploader
- the ability of a user associated with a workspace to contribute to a discussion workspace linked to that workspace or to invite others to join the workspace can be tied to the permission level of the user. For instance, an editor may be permitted to participate in the discussion workspace and invite other collaborators, while a viewer may only be allowed to participate in the discussion workspace, and an uploader may not be permitted to perform either action.
- separate discussion permission and/or invitation permission can be assigned by a creator or administrator of a workspace to individuals associated with the workspace.
- discussion permission and/or invitation permission can be associated with the workspace or the items in the workspace or can be based upon any other criteria.
- FIG. 3 shows a block diagram of an example host server 100 of a web- based collaboration environment that supports collaborative metadata for work items in the collaboration environment.
- Collaborative metadata refers to when one or more collaborators of a workspace or folder are given the ability to review metadata assigned to a work item in the folder and to add or edit metadata associated with the work item. In some embodiments, all collaborators are permitted to review and/or edit metadata associated with a work item, while in other embodiments, collaborators must be given metadata access rights before being permitted to do so. Because collaborators can add and/or edit metadata of a work item, a user is not required to provide any metadata before uploading the work item to the online content management system.
- the host server 100 of the web-based or online content management system with a collaboration environment can include, for example, a network interface 302, an attribute creation engine 310, an attribute database 320, a metadata request module 330, a metadata tracker module 340, a search engine 350, a metadata recommendation engine 360, and a metadata mapping engine 370.
- the attribute creation engine 310 can include an account tracking module 315.
- the network interface 302 can be a networking module that enables the host server 100 to mediate data in a network with an entity that is external to the host server 100, through any known and/or convenient communications protocol supported by the host and the external entity.
- the network interface 302 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1 G, 2G, 3G, 3.5G, 4G, LTE, etc.,), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.
- a network adaptor card e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1 G, 2G, 3G, 3.5G, 4G, LTE, etc.
- Bluetooth e.g., Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater
- a "module,” “a manager,” a “handler,” a “detector,” an “interface,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, handler, or engine can be centralized or its functionality distributed. The module, manager, handler, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all media that are statutory (e.g., in the United States, under 35 U.S.C.
- Known statutory computer-readable media include hardware (e.g., registers, random access memory (RAM), nonvolatile (NV) storage, to name a few), but may or may not be limited to hardware.
- One embodiment of the host server 100 includes an attribute creation engine 310 that allows an administrator of a workspace or a user authorized by the administrator to create and manage a list of metadata attributes that is accessible enterprise-wide to the administrator's managed user accounts. By restricting the creation and maintenance of enterprise-wide metadata to the administrator, metadata terms can be made consistent across the account.
- the attribute creation engine 310 prompts the administrator to provide an attribute name and to select a type for the attribute.
- the attribute type gives a user an indication of the format to include when providing metadata information for a particular work item or file.
- a type can include, for example, a free form text field, a pick list, date, or time. Additional information such as the settings for an attribute can also be requested.
- the settings can include a minimum and a maximum date range.
- the additional information can also include a description for the attribute to help the end user understand what is being requested.
- An example user interface for creating an attribute is shown in FIG. 4.
- attributes can be arranged into sets by the administrator through the attribute creation engine 310.
- An attribute set is a grouping of attributes that can be easily applied to a work item to ensure that the attributes requested for work items or files across an account is consistent.
- an attribute set for legal contracts can be created with the name 'legal contract attribute set'.
- the legal contract set can include attributes such as drafting attorney name, contract start date, and parties to the contract. Then the legal contract attribute set can be applied to a workspace or folder intended to organize legal contracts so that any work items placed in the folder will automatically request metadata for the attributes in the legal contract attribute set from the person who uploads the file to the folder or from a collaborator of the folder who accesses the folder after the work item has been uploaded.
- the database 320 stores the metadata for each work item stored in the web-based content management system that corresponds to the attributes and/or attribute sets corresponding to the work item.
- the database 320 can be made up of several separate databases.
- the database 320 can be external to the host server 100.
- the attribute creation engine 310 can include an account tracking module 315 that applies certain attributes and/or attribute sets created by an administrator only to the administrator's accounts.
- Each administrator can set up his own list of attributes and attribute sets to be used within the administrator's own account(s) that are separate from one or more accounts that the administrator manages for a group of users.
- the account tracking module 315 can also maintain a list of the users authorized by the administrator of an account to create and manage the attribute and attribute sets for the managed account(s).
- the metadata request module 330 prompts the creator of each folder for attributes and/or attribute sets to be requested for all work items that are stored in that folder.
- the metadata request module 330 also requests default values for the attributes and/or attribute sets that the creator selects.
- FIG. 5 shows an example user interface used by the metadata request module 330 to request attributes for a new folder. Child folders that are created in a parent folder that has already been assigned attributes and/or attribute sets inherit the same attributes and/or attribute sets upon creation. Similarly, the default values for the attributes are also inherited from the parent folder. However, the owner or creator of the child folder can modify the attributes and/or attributes sets associated with the child folder.
- the metadata request module 330 prompts a user who uploads a file to a particular folder to provide corresponding metadata for the attributes and/or attribute sets that have been assigned to that folder by the creator of the folder.
- the user can provide all, some, or none of the requested metadata information. Additionally or alternatively, the user can provide metadata for any attribute, even if it hasn't been designated by the folder creator as long as that attribute has been created by the administrator so that it exists in the attribute database 320.
- the user can provide incomplete metadata information or no metadata information at all for a file. If incomplete or no metadata information is provided by the user uploading the file, the user is still permitted to upload the file.
- FIG. 6 shows an example user interface used by the metadata tracker module 340 to request metadata.
- An example user interface for searching using metadata is shown in FIG. 7. A user can enter, edit, and/or add metadata search terms, and the search engine 350 can search for work items within the account that have been appropriately tagged.
- One embodiment of the host server 100 includes a metadata recommendation engine 360 that can recommend metadata to a user uploading a file to the online content management system.
- the metadata recommendation engine 360 can base the recommendations on other metadata terms in the folder to which the document is uploaded. Alternatively, or additionally, the metadata recommendation engine 360 can base the recommendations on previous metadata terms that have been entered by the uploading user.
- the metadata recommendation engine 360 can analyze the document for the use of substantive words or phrases having a minimum density, index and rank the content of the document based upon semantic analysis, or use any other metadata determination algorithm to determine the metadata terms to recommend to the user.
- the host server 100 performs cloud-based enterprise content management services (ECM).
- ECM enterprise content management services
- the host server 00 can connect with other client on-premise ECMs with traditional content platforms, for example, SharePoint or Documentum, to synchronize or transfer data to and from the host server 100 or when migrating content between the on-premise ECM and the host server 100.
- One embodiment of the host server 100 includes a metadata mapping engine 370 that maps metadata fields between files stored on the host server 100 and the on-premise ECM.
- data synchronized between the host server 100 and a client's other ECM, for example, SharePoint can contain the same or similar metadata.
- FIG. 8 depicts a flow diagram illustrating an example process of creating metadata attributes by an administrator.
- FIG. 4 shows an example user interface that shows some created attribute sets, attributes, attribute types, and attribute settings.
- the system requests and receives a name for the metadata attribute from the administrator of one or more accounts on the web-based content management system. Then at block 815, the system requests and receives a type for the attribute. Examples of metadata attribute types include, but are not limited to, free form text field, time, date, and list with a box that allows for multiple selections.
- the system requests and receives additional settings for the metadata attribute.
- the settings could indicate a minimum and a maximum data range.
- the settings can also include a description to explain to the end user the type of metadata information that is being requested by the system.
- FIG. 9 depicts a flow diagram illustrating an example process of creating metadata attribute sets by an administrator.
- the system requests and receives a name for the metadata attribute set from the administrator of one or more accounts on the content management system.
- the system requests and receives the metadata attributes for the set from the administrator.
- the system determines if there are more metadata attributes to be included in the set. If the administrator indicates that there are more attributes (block 920 - Yes) the process returns to block 915. If the administrator indicates that there are no more attributes to be included (block 920 - No), the process ends at block 999.
- FIG. 10 depicts a flow diagram illustrating an example process of creating a new folder in the web-based content management system.
- the system determines if there is a request to create a new folder. If there is no request (block 1005 - No), the process remains at decision block 1005 until there is a request. If there is a request (block 1005 - Yes), at block 1010, the system requests and receives from the creator of the folder metadata attribute names to be requested for work items uploaded to the folder.
- the system requests and receives default values, if any, for the attributes from the folder creator.
- one metadata attribute that can be assigned to a legal folder is 'client name'
- a default value for 'client name' can be Company ABC if all of the work items in the legal folder pertain to Company ABC.
- the system requests and receives from the folder creator information about whether the given default metadata are editable. If the folder creator indicates that the default metadata for an attribute is not editable, neither collaborators of the folder nor the user who uploads a work item to the folder is permitted to change the metadata for the attribute for the work item from the default value.
- FIG. 5 shows an example user interface for establishing metadata attribute information for a new folder in the online content management system.
- FIG. 11 depicts a flow diagram illustrating an example process of uploading a file to the online content management system.
- the system determines if a file upload request has been received from a user.
- An upload request can be made by using a user interface to the online content management system, using email, or through an application programming interface (API), for example. If no file upload request has been received (block 1105 - No), the process remains at decision block 1105 until there is a request. If a file upload request has been received (block 1105 - Yes), at block 1 107, the system requests metadata from the user for the attributes associated with the folder that were selected by the folder creator.
- API application programming interface
- the system receives metadata, if any, from the user for the selected file attributes.
- the user is not required to provide metadata for the file before uploading a file to the online content management system.
- the system uploads the file, even if the user has not provided any metadata for the required file attributes.
- the system analyzes the file to determine metadata recommendations.
- the system recommends the determined metadata for the file to the user.
- the system receives the user's acceptance of any of the recommended metadata selections. The user does not have to accept any of the recommended metadata.
- FIG. 12 depicts a flow diagram illustrating an example process of a collaborator entering a workspace or folder in the online content management system.
- the system determines if a collaborator is accessing a workspace. If no collaborator is accessing a workspace (block 1205 - No), the process remains at decision block 1205 until a collaborator accesses a workspace.
- a collaborator access a workspace (block 1205 - Yes)
- the system determines if any files or work items are missing metadata for the attributes selected by the workspace creator for the work items uploaded to the workspace. If there are no files missing metadata (block 1210 - No), the process ends at block 1299.
- the system displays a notice that metadata is needed, the files that need metadata, and the attributes for which metadata is missing for those files.
- the system can also permit the collaborator to add metadata for optional attributes not selected by the folder creator, as long as the optional attribute has been created by the administrator.
- the system determines if a file has been selected by the collaborator to add metadata. If the collaborator does not select a file for adding metadata (block 1225 - No), the process ends at block 1299.
- the system receives the metadata for the file. Then at block 1235, the system updates the metadata database with the new metadata.
- FIG. 13 shows a diagrammatic representation of a machine 1300 in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed
- the machine operates as a standalone device or may be connected (e.g., networked) to other machines.
- the machine may operate in the capacity of a server or a client machine in a client- server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.
- the machine may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
- PC personal computer
- PDA personal digital assistant
- machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine- readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions.
- the term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.
- routines executed to implement the embodiments of the disclosure may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as "computer programs.”
- the computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.
- machine-readable storage media machine-readable media, or computer-readable (storage) media
- recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.
- CD ROMS Compact Disk Read-Only Memory
- DVDs Digital Versatile Disks
- transmission type media such as digital and analog communication links.
- the network interface device enables the machine 1300 to mediate data in a network with an entity that is external to the host server, through any known and/or convenient communications protocol supported by the host and the external entity.
- the network interface device can include one or more of a network adaptor card, a wireless network interface card, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.
- the network interface device can include a firewall which can, in some embodiments, govern and/or manage permission to access/proxy data in a computer network, and track varying levels of trust between different machines and/or applications, he firewall can be any number of modules having any combination of hardware and/or software components able to enforce a predetermined set of access rights between a particular set of machines and applications, machines and machines, and/or applications and applications, for example, to regulate the flow of traffic and resource sharing between these varying entities.
- the firewall may additionally manage and/or have access to an access control list which details permissions including for example, the access and operation rights of an object by an individual, a machine, and/or an application, and the circumstances under which the permission rights stand.
- firewalls can be, for example, but are not limited to, intrusion-prevention, intrusion detection, next-generation firewall, personal firewall, etc. without deviating from the novel art of this disclosure.
- the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense (i.e., to say, in the sense of “including, but not limited to”), as opposed to an exclusive or exhaustive sense.
- the terms “connected,” “coupled,” or any variant thereof means any connection or coupling, either direct or indirect, between two or more elements. Such a coupling or connection between the elements can be physical, logical, or a combination thereof.
- the words “herein,” “above,” “below,” and words of similar import when used in this application, refer to this application as a whole and not to any particular portions of this application.
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/US2011/056472 WO2013055371A1 (en) | 2011-10-14 | 2011-10-14 | Automatic and semi-automatic tagging feature of work items in a shared workspace for metadata tracking in a cloud-based content management system with selective or optional user contribution |
GB1311417.8A GB2499767A (en) | 2011-10-14 | 2011-10-14 | Automatic and semi-automatic tagging feature of work items in a shared workspace for metadata tracking in a cloud-based content management system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/US2011/056472 WO2013055371A1 (en) | 2011-10-14 | 2011-10-14 | Automatic and semi-automatic tagging feature of work items in a shared workspace for metadata tracking in a cloud-based content management system with selective or optional user contribution |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013055371A1 true WO2013055371A1 (en) | 2013-04-18 |
Family
ID=44908113
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2011/056472 WO2013055371A1 (en) | 2011-10-14 | 2011-10-14 | Automatic and semi-automatic tagging feature of work items in a shared workspace for metadata tracking in a cloud-based content management system with selective or optional user contribution |
Country Status (2)
Country | Link |
---|---|
GB (1) | GB2499767A (en) |
WO (1) | WO2013055371A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015130399A1 (en) * | 2014-02-27 | 2015-09-03 | Dropbox, Inc. | Systems and methods for ephemeral eventing |
US9462054B2 (en) | 2014-02-27 | 2016-10-04 | Dropbox, Inc. | Systems and methods for providing a user with a set of interactivity features locally on a user device |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6732331B1 (en) * | 2000-02-15 | 2004-05-04 | Vlad Alexander | System and process for managing content organized in a tag-delimited template using metadata |
US20090235167A1 (en) * | 2008-03-12 | 2009-09-17 | International Business Machines Corporation | Method and system for context aware collaborative tagging |
-
2011
- 2011-10-14 WO PCT/US2011/056472 patent/WO2013055371A1/en active Application Filing
- 2011-10-14 GB GB1311417.8A patent/GB2499767A/en not_active Withdrawn
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6732331B1 (en) * | 2000-02-15 | 2004-05-04 | Vlad Alexander | System and process for managing content organized in a tag-delimited template using metadata |
US20090235167A1 (en) * | 2008-03-12 | 2009-09-17 | International Business Machines Corporation | Method and system for context aware collaborative tagging |
Non-Patent Citations (2)
Title |
---|
BRIGITTE KERHERVÉ: "Models for Metadata or Metamodels for Data?", 2ND IEEE METADATA CONFERENCE, 1 September 1997 (1997-09-01), Silver Spring, Ma, pages 1 - 12, XP055017749 * |
LANGFELD L ET AL: "Microsoft Sharepoint 2003 Unleashed", part Chapters 11 and 15 June 2004, SAMS, ISBN: 0-672-32616-7, XP002677597 * |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015130399A1 (en) * | 2014-02-27 | 2015-09-03 | Dropbox, Inc. | Systems and methods for ephemeral eventing |
US9462054B2 (en) | 2014-02-27 | 2016-10-04 | Dropbox, Inc. | Systems and methods for providing a user with a set of interactivity features locally on a user device |
US9942121B2 (en) | 2014-02-27 | 2018-04-10 | Dropbox, Inc. | Systems and methods for ephemeral eventing |
US10235444B2 (en) | 2014-02-27 | 2019-03-19 | Dropbox, Inc. | Systems and methods for providing a user with a set of interactivity features locally on a user device |
Also Published As
Publication number | Publication date |
---|---|
GB201311417D0 (en) | 2013-08-14 |
GB2499767A (en) | 2013-08-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8990151B2 (en) | Automatic and semi-automatic tagging features of work items in a shared workspace for metadata tracking in a cloud-based content management system with selective or optional user contribution | |
US11435865B2 (en) | System and methods for configuring event-based automation in cloud-based collaboration platforms | |
US9978040B2 (en) | Collaboration sessions in a workspace on a cloud-based content management system | |
US11144509B2 (en) | Method and apparatus for synchronization of items in a cloud-based environment | |
US8868574B2 (en) | System and method for advanced search and filtering mechanisms for enterprise administrators in a cloud-based environment | |
US8990307B2 (en) | Resource effective incremental updating of a remote client with events which occurred via a cloud-enabled platform | |
US9792320B2 (en) | System and method for performing shard migration to support functions of a cloud-based service | |
US9959420B2 (en) | System and method for enhanced security and management mechanisms for enterprise administrators in a cloud-based environment | |
US9575981B2 (en) | Cloud service enabled to handle a set of files depicted to a user as a single file in a native operating system | |
US20130080919A1 (en) | Central management and control of user-contributed content in a web-based collaboration environment and management console thereof | |
US20130013560A1 (en) | Desktop application for access and interaction with workspaces in a cloud-based content management system and synchronization mechanisms thereof | |
US20140282938A1 (en) | Method and system for integrated cloud storage management | |
US20130268480A1 (en) | Method and apparatus for selective subfolder synchronization in a cloud-based environment | |
US20130179799A1 (en) | System and method for actionable event generation for task delegation and management via a discussion forum in a web-based collaboration environment | |
US20130238969A1 (en) | Universal file type preview for mobile devices | |
US10452667B2 (en) | Identification of people as search results from key-word based searches of content in a cloud-based environment | |
US9495364B2 (en) | Enhanced quick search features, low-barrier commenting/interactive features in a collaboration platform | |
WO2013055371A1 (en) | Automatic and semi-automatic tagging feature of work items in a shared workspace for metadata tracking in a cloud-based content management system with selective or optional user contribution | |
GB2507650A (en) | Automatic and semi-automatic tagging feature of work items in a shared workspace for metadata tracking in a cloud-based content management system | |
GB2504617A (en) | Searching a Content Repository of a Cloud-Based Environment Across Multiple Users Associated with an Enterprise |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11779285 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 1311417 Country of ref document: GB Kind code of ref document: A Free format text: PCT FILING DATE = 20111014 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1311417.8 Country of ref document: GB |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 11779285 Country of ref document: EP Kind code of ref document: A1 |