The values of the work assignment parameter describing assignment of users to units of work may be determined based on one or more interactions by one or more users with a collaboration environment. In some implementations, one or more users may create and/or assign one or more unit of work to themselves and/or another user. In some implementations, a user may be assigned a unit of work and the user may effectuate a reassignment of the unit of work from the user or one or more other users.

In some implementations, values of the work completion parameter may indicate that a completion status of a unit of work has changed from “incomplete” to “marked complete” and/or “complete”. In some implementations, a status of complete for a unit of work may be associated with the passing of an end date associated with the unit of work. In some implementations, a status of “marked complete” may be associated with a user providing input via the collaboration environment at the point in time the user completes the unit of work (which may be before or after an end date).

In some implementations, managing the environment state component 108 may include maintaining queues of the units of work assigned to the users. The queues may be presented to the users in a user interface of the collaboration environment to facilitate access to the units of work via work unit pages. Individual queues may represent the units of work assigned to individual users organized in an order based on the individual end dates and/or other dates (e.g., start dates) and/or other ordering. Individual queues may be presented in a user interface based on one or more of a list view, a calendar view, and/or other views. The calendar view may be a calendar view by week, by more than one week (e.g., 1^stthrough 15^th), by month, by more than one month (e.g., May through July), and/or other calendar views. Units of work may be represented in a calendar view by user interface elements (e.g., icons, calendar entries, etc.).

Project information in project records may define values of project parameters for projects managed within the collaboration environment. The project parameters may characterize one or more projects created, assigned, and/or managed within the collaboration environment and/or via the collaboration environment, and/or the metadata associated with the one or more projects. Individual ones of the projects may be associated with individual ones of the project records. The project information may define values of the project parameters associated with a given project managed within the collaboration environment and/or via the collaboration environment. A given project may have one or more owners and/or one or more collaborators working on the given project. The given project may include one or more units of work assigned to one or more users under the given project heading. In some implementations, projects may include one or more units of work that may directly facilitate progress toward fulfillment of the projects. Accordingly, completion of units of work may directly contribute to progress toward fulfillment of the project. By way of non-limiting illustration, an individual project may be associated with a client and the units of work under the individual project heading may be work directly contributing to the fulfillment of a business relationship with the client.

In some implementations, activities that impact the progress toward completion of the individual projects may be reflected by changes in the values of one or more of the work unit parameters and/or the values of one or more of the project parameters.

The values of the project parameters may, by way of non-limiting example, include one or more of: one or more units of work within individual ones of the projects (which may include values of work unit parameters defined by one or more work unit records), status information, user role information, one or more user comment parameters (e.g., a creator, a recipient, one or more followers, one or more other interested parties, content, one or more times, upvotes, other hard-coded responses, etc.), a project name, a project description, one or more project dates (e.g., a start date, a due date, a completion date, and/or other project dates), one or more project collaborators (e.g., an owner, one or more other project collaborators, collaborator access information, and/or other project collaborators, and/or collaborator information), one or more attachments, notification settings, privacy, an associated URL, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), updates, ordering of units of work within the given project, state of a workspace for a given task within the given project, and/or other information.

In some implementations, projects created by, assigned to, and/or completed by the users may refer generally to a linking of the projects with the individual users in the collaboration environment. A project may be linked with a user in a manner that defines one or more relationships between the user and the project. Such a relationship may connote and/or be a result of an action (past, present, and/or future) of the user with respect to the project. Such actions may include one or more of creating a project record for a project, being assigned to participate in a project, participating in a project, being granted access to a project record of a project, adjusting a value of a project parameter of a project record of a project, being assigned a project-level role, and/or other actions.

User role information may specify individual roles of the individual users. A role may represent a position of an individual user. The position may be specified based on a description of one or more of a job title, level, stage, and/or other descriptions of position. The role may be specified with respect to a business organization as a whole and/or other specifications. By way of non-limiting illustration, a role may include one or more of chief executive officer (or other officer), owner, manager, supervisor, accountant, associate, employee, intern, entry-level, midlevel, senior, administrator, director, foreman, engineer, product developer, human resource officer, artist, art director, and/or other descriptions.

In some implementations, user role information may specify roles of the users within the units of work and/or the projects. The roles may convey expected contribution of the users in completing and/or supporting the units of work and/or the projects. The individual roles of individual users within the units of work may be specified separately from the individual roles of the individual users within the projects. The individual roles of individual users within the units of work and/or projects may be specified separately from the individual roles of the individual users within a business organization as a whole.

The objective information in objective records may include values of one or more objective parameters. The values of the objective parameters may be organized in objective records corresponding to business objectives managed, created, and/or owned within the collaboration environment. A given business objective may have one or more collaborators, and/or team members working on the given business objective. Business objectives may include one or more associated units of work and/or projects one or more users should accomplish and/or plan on accomplishing. Business objectives may be created by a given user for the given user and/or created by the given user and assigned to be owned to one or more other users. Individual business objectives may include one or more of an individual goal, an individual sub-goal, and/or other business objectives assigned to be owned by a user and/or associated with one or more users.

The business objectives may be associated with a set of units of work and/or projects that may indirectly facilitate progress toward fulfillment of the business objectives. The set of units of work and/or projects may not directly contribute to the progress. By way of non-limiting illustration, a connection between the set of units of work and/or projects and a corresponding business objective may be indirect in that completion of at least one of the units of work and/or projects may have no direct impact on progress toward fulfillment of the business objective. The concept of “no direct impact” may mean that completion of the at least one unit of work and/or project may not cause progress toward fulfillment of the business objective without independent action outside of the at least one unit of work and/or project. Instead, the fulfillment of the at least one unit of work and/or project may make such independent action more likely (e.g., through coercion, assistance, education, incentivization, reminder, etc.). However, in some implementations, business objectives may be associated with a set of units of work and/or projects that may directly facilitate progress toward fulfillment of the business objectives. Accordingly, completion of the set of units of work and/or projects may directly contribute to the progress toward fulfillment. Business objectives may be associated with an objectives and key result (OKR) goal-setting framework. Business objectives may be specified on one or more of a team basis, organization basis, and/or other specifications. In some implementations, business objectives may be characterized as user objectives. The user objectives may be associated with a set of units of work and/or projects that may indirectly (and/or directly) facilitate progress toward fulfillment of the user objectives. User objectives may be specified on an individual user basis.

Individual objective records may describe individual business objectives and/or identify sets of work unit records and/or project records that support the individual business objectives.

Individual sets of objective records may be defined by an objective record hierarchy. An objective record hierarchy may convey individual positions of objective records (and their corresponding business objectives) in the objective record hierarchy. By way of non-limiting illustration, a position may specify one or more of an objective record being superior to one or more other objective records, an objective record being subordinate to one or more other objective records, and/or other information. As a result, individual objective records may be subordinate and/or superior to other individual objective records. For example, the objective records may further include a second objective record. The first objective record and the second objective record may be organized by a first objective record hierarchy specifying that the second objective record is subordinate to the first objective record.

An objective record may define a business objective comprising a progress towards fulfillment, and a subordinate objective record may define a business objective comprising a subordinate progress towards fulfillment to the subordinate business objective. An objective record hierarchy may define a relationship between objective records.

Individual objective records may include hierarchical information defining an objective record hierarchy of the individual objective records. The hierarchical information of an objective record may include one or more of information identifying other objective records associated in an objective record hierarchy the objective record belongs to, a specification of the position of the objective record in the hierarchy, other relationships placed on the objective record by virtue of its position, and/or other information.

In some implementations, as a consequence of the objective record hierarchies, the individual business objectives described in the individual objective records that are subordinate to the other individual objective records may be subordinate to the individual business objectives in the other individual objective records.

In some implementations, the one or more objective parameters may include one or more of an objective definition parameter, an objective owner parameter, an objective management parameter, an objective creation parameter, an objective progress parameter, and/or other parameters. The value of the objective definition parameter may describe the particular business objective. The values of the objective owner parameter may describe business objectives assigned to be owned by an individual user. The values of the objective management parameter may describe business objectives managed as collaborators by the individual users. The values of the objective creation parameter may describe business objectives created by the individual users.

In some implementations, the business objectives may be described based on one or more of a business objective name, a business objective description, one or more business objective dates (e.g., a start date, a due date, and/or dates), one or more members associated with a business objective (e.g., an owner, one or more other project/task members, member access information, and/or other business objective members and/or member information), progress information (e.g., an update, a hardcoded status update, a measured status, a progress indicator, quantity value remaining for a given business objective, completed work units in a given project, and/or other progress information), one or more interaction parameters, notification settings, privacy, an associated URL, one or more custom fields (e.g., priority, cost, stage, and/or other custom fields), and/or other information.

The values of the objective owner parameter describing business objectives owned by the individual users may be determined based on one or more interactions by one or more users with a collaboration environment. In some implementations, one or more users may create and/or assign ownership of one or more business objectives to themselves and/or another user. In some implementations, a user may be assigned to own a business objective and the user may effectuate a reassignment of ownership of the business objective from the user or one or more other users.

Progress information for the individual business objectives may convey progress toward fulfillment of the individual business objectives. The progress information for the individual business objectives may convey progress toward fulfillment of the individual business objectives. In some implementations, the progress toward fulfillment of the business objectives may be specified as one or more of a quantitative value, a qualitative value, and/or other information. In some implementations, the quantitative value may be a percentage of completion, an integer value, a dollar amount, and/or other values. In some implementations, progress toward fulfillment of the individual business objectives may be determined independently from incremental completion of the units of work in the individual sets of units of work associated with the individual business objectives. Meaning, the completion of the units of work associated with a given business objective may not directly progress the given business objective toward fulfillment, but completing the units of work may make accomplishing the business objective more likely (e.g., through coercion, assistance, education, incentivization, reminder, etc.). However, in some implementations, progress toward fulfillment of the individual business objectives may be directly determined based on incremental completion of the units of work in the individual sets of units of work associated with the individual business objectives.

It is noted that any metadata and/or values of parameters related to any users, projects, business objectives, and/or units of work may be considered values of user parameters, project parameters, objective parameters, and/or work unit parameters.

In some implementations, environment state component 108 may be configured to manage information defining work unit pages corresponding to the individual units of work. Individual work unit pages may provide access to individual units of work. Managing information defining work unit pages may include determining, obtaining, and/or modifying information used to generate work unit pages. Managing information defining individual work unit pages may include providing information to the user interface component 110 to effectuate presentation of the work unit pages, and/or other information. In some implementations, individual work unit pages may include individual sets of interface elements displaying the values of one or more of the work unit parameters of the individual units of work.

In some implementations, environment state component 108 may be configured to manage information defining project pages corresponding to the individual projects. Individual project pages may provide access to individual projects. Managing information defining project pages may include determining, obtaining, and/or modifying information used to generate project pages. Managing information defining individual project pages may include providing information to the user interface component 110 to effectuate presentation of the project pages, and/or other information. In some implementations, individual project pages may include individual sets of interface elements displaying the values of one or more of the project parameters of the individual projects.

In some implementations, environment state component 108 may be configured to manage information defining business objective pages corresponding to the individual business objectives. Individual business objective pages may provide access to individual business objectives. Managing information defining business objective pages may include determining, obtaining, and/or modifying information used to generate business objective pages. Managing information defining individual business objective pages may include providing information to the user interface component 110 to effectuate presentation of the business objective pages, and/or other information. In some implementations, individual business objective pages may include individual sets of interface elements displaying the values of one or more of the objective parameters of the individual business objectives.

The user interface component 110 may be configured to effectuate presentation of a user interface of the collaboration environment on client computing platform(s) 104. The user interface component 110 may facilitate server information from server(s) 102 to client computing platform(s) 104 so that client computing platform(s) 104 may present the user interface. The user interface may provide one or more views of the collaboration environment and/or provide other features and/or functionality. The one or more views may include one or more pages of the collaboration environment. In some implementations, an individual view of the collaboration environment may textually and/or graphically display information from one or more of a user record, a project record, an objective record, and/or other records. By way of non-limiting illustration, a view may display one or more of a work unit page, a project page, a business objective page, a queue of units of work, and/or other information.

The user interface component 110 may be configured to effectuate presentation of a user interface through which users input and/or upload digital assets representing sets of content. The sets of content represented in the digital assets may generally be unstructured content. “Unstructured” may mean that the content represented in the digital assets may be unusable by the collaboration environment unless and/or until it is structured in one form or another. The user interface may include one or more portions. A portion may include an input portion configured to receive user input of the digital assets. In some implementations, the input portion may be configured to receive user input through drag-and-drop input, file selection through a search and/or drop down menu, and/or other input.

The user interface component 110 may obtain input information conveying user input into a user interface. In some implementations, the input information may define individual ones of the digital assets input by the users via the user interface. By way of non-limiting illustration, the input information may include the data included in uploaded files. By way of non-limiting illustration, the input information may define a first digital asset input into the user interface via the input portion by a first user and/or other users. The first digital asset may represent a first set of content.

In some implementations, digital assets that users may input may include one or more of document files, image files, video files, audio files, and/or other digital assets representing sets of content.

In some implementations, content of document files may include one or more of text, figures, formulas, and/or other content. Text may comprise one or more of words, phrases, glyphs, and/or other content.

In some implementations, content of image files may include visual content. In some implementations, the visual content may include one or more of a photograph, a screenshot, and/or other visual content. The photographs may be of physical documents including typed and/or handwritten text, drawings, figures, people, and/or other content.

In some implementations, content of audio files may include audio content and/or other content. The audio content may include one or more of user utterances (e.g., speech, emotes, and/or other utterances), environment sounds, and/or other audio content.

In some implementations, content of video files may include one or more of visual content, audio content, and/or other content.

Content component 112 may be configured to generate content information characterizing the sets of content represented in the digital assets. In some implementations, content component 112 may be configured to generate content information characterizing the sets of content represented in the digital assets in response to obtaining the input information. In some implementations, content component 112 may be configured to generate content information characterizing the sets of content represented in the digital assets in response to specific user input requesting the generation of the content information following the input of the digital assets. By way of non-limiting illustration, responsive to obtaining the input information defining the first digital asset, content component 112 may be configured to generate first content information characterizing the first set of content.

In some implementations, generating the content information for document files may include performing natural language processing on text and/or other content in the document files.

In some implementations, generating the content information for image files may include performing feature detection on visual content. The feature detection may characterize features in the visual content. By way of non-limiting illustration, techniques for feature detection may include one or more of computer vision, Speeded Up Robust Features (SURF), Scale-invariant Feature Transform (SIFT), Oriented FAST and rotated BRIEF (ORB), Optical Character Recognition (OCR), facial recognition, and/or other techniques.

In some implementations, generating the content information for audio files may include performing speech processing on audio content and/or other processing. In some implementations, the speech processing may identify users, characterize user utterances in the audio content, and/or produce other output. By way of non-limiting illustration, the speech processing may determine user utterances (e.g., words and/or phrases spoken), identify users who are speaking, and/or other provide other information.

In some implementations, generating the content information for video files may include performing one or more of feature detection on the visual content to characterize features in the visual content, speech processing on audio content to characterize user utterances in the audio content, and/or other processing techniques.

The work creation component 114 may be configured to generate individual work unit records and/or other records based on content information and/or other information. The individual work unit record may be generated by determining work information describing the individual work unit records as part of the environment state information. Determining work information may include specifying values for one or more parameters. In some implementations, certain content may trigger generation of individual work unit records. By way of non-limiting illustration, in some implementations, certain content may trigger specification of one or more values of one or more parameters. Individual work unit records may be generated based on identifying one or more of the trigger included in sets of content of the digital assets.

It is noted that creation of work unit records based on content information is for illustrative purposes only and not to be considered limiting. In some implementations, work creation component 114 may be configured to generate other records based on content information and/or other information. By way of non-limiting illustration, work creation component 114 may be configured to generate one or more of project records, user records, objective records, and/or other records based on content information and/or other information. In some implementations, work creation component 114 may be configured to determine what type of record should be created based on the content information and/or other information. By way of non-limiting illustration, work creation component 114 may be configured to determine an intent of work from the content information and/or other information. Intent may be characterized as one or more of completing one or more to-do items and/or action items, organizing one or more to-do items and/or action items, high-level goal setting, user onboarding/user introductions, and/or other characteristics. In some implementations, completing one or more to-do items may be associated with work unit records and/or other records. In some implementations, organizing one or more to-do items may be associated with project records and/or other records. In some implementations, goal setting may be associated with objective records and/or other records. In some implementations, user onboarding may be associated with user records and/or other records. A project record may be generated by determining project information describing the project record as part of the environment state information. Determining project information may include specifying values for one or more parameters. An objective record may be generated by determining objective information describing the objective record as part of the environment state information. Determining objective information may include specifying values for one or more parameters. Accordingly, while one or more implementations described herein may be directed toward work unit records, those skilled in the art may appreciate that the features and/or functionally may be extended to creating other records.

The work creation component 114 may be configured to store trigger information. The trigger information may include triggers to generate work unit records and/or other records. In some implementations, triggers may be user-specific and/or system-wide. In some implementations, the triggers may be set by users and stored within the user records for the users. In some implementations, the work creation component 114 may be configured to determine triggers through one or more machine learning techniques.

In some implementations, triggers in text and/or user utterances may include trigger words and/or phrases. By way of non-limiting illustration, the trigger phrases and/or words may include words and/or phrases conveying one or more of action items or tasks to be completed, desires or wants, and/or other information. In some implementations, the trigger phrases and/or words may include words accompanied by one or more of will you, can you, could you, please, by a given date, before the given date, we need, I need, I want, would be grateful if, you could, and/or other phrases and/or words. By way of non-limiting illustration, text may include “The background research to be completed should help us determine the next course of action.” An action item determined from this text may include “doing background research.” Another action item determined from this text may include “determine next course of action.” By way of non-limiting illustration, a user utterance may include “When Tom completes the background research, we will know the next course of action.” A desire from this text may include “have Tom do the background research.” In some implementations, the trigger phrases and/or words may be directly correlated to other existing records. By way of non-limiting illustration, a user utterance may specifically identify an existing record.

In some implementations, triggers in visual content of video files may include one or more trigger gestures and/or emotes. The trigger gestures and/or emotes may indicate a user's request, desire, inquiry, and/or need. By way of non-limiting illustration, a trigger gesture to generate a work unit record may include a thumbs-up gesture and/or other gestures conveying a desire to do something they are talking about. By way of non-limiting illustration, a trigger gesture and/or emote to generate a work unit record with low priority may include a shaking of the head and/or other gestures conveying a desire to do something but having little importance.

In some implementations, triggers in visual content in image files may include one or more trigger features. The trigger features may indicate a user's request, desire, inquiry, and/or need. By way of non-limiting illustration, a trigger feature in a photograph of a physical document may include words written on the physical document. Natural language processing may be performed on the words to determine the content of the words.

In some implementations, the content information characterizing the content of digital assets may include context information specifying context of the digital assets. The context may include one or more of an uploader of a digital asset (e.g., user who input the digital asset), a creator of a digital asset, a page of the collaboration environment from which the user accessed the user interface to input of the digital assets, a time and/or date associated with the input of a digital asset, and/or other information. In some implementations, the individual work unit records may be further generated based on the context information. By way of non-limiting illustration, the context information may be used to set individual values of one or more parameters.

The work creation component 114 may be configured to identify one or more of the users linked to a digital asset. The one or more users linked to the digital asset may include one or more of the creator of the digital asset, the uploader of the digital asset, and/or other users. The work creation component 114 may be configured to obtain the user records for the users linked to the digital asset.

In some implementations, an uploader of a digital asset may be identified. The user record of the uploader may be accessed and/or obtained to gather further information about the uploader. A generated work unit record may include values determined based on the identity of the uploaded. By way of non-limiting illustration, the uploader may be specified as one or more of an assignee of the work unit record, an assignor of the work unit record, a collaborator of the work unit record, a reviewer of the work unit record, and/or used to specify other values. In some implementations, a user linked to, and/or associated with, the uploader may be used to specify one or more values. By way of non-limiting illustration, a user having a subordinate role with respect to the uploader may be an assignee of the work unit record, a user having a superior role with respect to the uploader may be a reviewer of the work unit record, and/or other values may be specified.

In some implementations, a creator of a digital asset may be identified. The creator may be identified based on identifying information included in the content of the digital asset and/or metadata associated with the digital asset. The user record of the creator may be accessed and/or obtained to gather further information about the creator. A generated work unit record may include values determined based on the identity of the creator. By way of non-limiting illustration, the creator may be specified as one or more of an assignee of the work unit record, an assignor of the work unit record, a collaborator of the work unit record, a reviewer of the work unit record, and/or used to specify other values. In some implementations, a user linked to, and/or associated with, the creator may be used to specify one or more values. By way of non-limiting illustration, a user having a subordinate role with respect to the creator may be an assignee of the work unit record, a user having a superior role with respect to the creator may be a reviewer of the work unit record, and/or other values may be specified.

In some implementations, a user may access the user interface to input a digital asset by navigating to the user interface from a page of the collaboration environment. The page may be associated with a record, referred to as a “source record” for the page. The source record may include one or more of a user record, a work unit record, a project record, an objective record, and/or other records. In some implementations, a generated work unit record may be included in the source record. In some implementations, a generated work unit record may be specified as being subordinate to the source record. In some implementations, a generated work unit record may be specified as being superior to the source record. In some implementations, a generated work unit record may be specified as being dependent on, or depending from, to the source record. In some implementations, a generated work unit record may have one or more dates (e.g., due date, review date, and/or other dates) that are specified relative to one or more dates of the source record. By way of non-limiting illustration, the generated work unit record may have a due date that is specified as occurring a specified amount of days before and/or after a due date of the source record.

In some implementations, a time and/or date a digital asset is uploaded may be determined. A generated work unit record may include values determined based on the time and/or date. By way of non-limiting illustration, a due date of the work unit record may be determined relative the time and/or date of the upload. By way of non-limiting illustration, a due date may be specified as being given period of time following the time and/or date of upload.

By way of non-limiting illustration, work creation component 114 may be configured to generate a first work unit record based on the first content information and/or other information. Generating the first work unit record based on the first content information may include generating a first set of values for the work unit parameters. The first set of values may be determined from the characterization of the first set of content of the first digital asset. The first set of values may include a first value of a first work unit parameter. The first work unit parameter may include a title parameter and the first value may include a title extracted from a document file. In some implementations, a title of the first unit of work may be the first text and/or a portion of the first text. The first set of values may include a second value of a second work unit parameter. The second work unit parameter may include an assignee parameter. The second value may include a user who uploaded the first digital asset.

In some implementations, the environment state component 108 may be configured to, in response to the generating records, generate and/or store resource information in individual records. The resource information may include the digital assets and/or resource identifiers that facilitate access to the digital assets. A resource identifier may include one or more of a pointer, a hyperlink, and/or other identifier configured to provide access to an individual record (e.g., a source record and/or other record).

Storing the resource information in the individual records may cause individual resource identifiers to be presented in individual pages of the individual records.

In some implementations, environment state information may be updated as users continue to interact with the collaboration environment via the user interfaces over time. The environment state component 108 may store and/or archive the environment state information periodically and/or based on user request to archive. In some implementations, the environment state component 108 may store historical environment state information specifying historical user information, historical work information, historical project information, historical objective information, user interaction history, and/or other information.

Although one or more implementations herein describe the user interface component 110 in connection with effectuating presentation of a user interface on client computing platform(s) 104, this is for illustrative purposes only and is not to be considered limiting. In some implementations, one or more features and/or functionally of system 100 may be extended to external resource(s) (e.g., other application(s)) through an application programming interface (API). By way of non-limiting illustration, external resource(s) may be tasked with defining and/or presenting a user interface to receive user input. Accordingly, the user interface may be considered external to system 100 (e.g., not managed or provided by system 100). Automatically generating records may be effectuated by performing one or more API interactions with an external resource. An API interaction to achieve the extensibility between features and/or functionally of system 100 and external resource(s) may include one or more of Remote Procedure Call, Representational State Transfer, GraphQL, and/or other interactions. Through this type of arrangement, the features and/or functionality of system 100 may be provided as a service that other developers can incorporate into their applications.

FIG. 3 illustrates a user interface 300 of a collaboration environment, in accordance with one or more implementations. The user interface 300 may include a view of a collaboration environment. In particular, the user interface 300 may comprise a project page 302 for a project 301. The user interface 300 may display different values of one or more project parameters of the project, and/or other information. By way of non-limiting illustration, a user interface element 301 may display a title of the project 301 (e.g., Project Q). A user interface element 303 may display a due date of the project 301. A user interface element 304 may display a description of the project 301. A user interface element 306 may display a sets of units of work that support the project 301 (represented as Task X and Task Y). The project page 302 may include a user interface element 308 to initiate user uploads of digital assets to generate one or more work unit records.

FIG. 4 illustrates a user interface 400, in accordance with one or more implementations. The user interface 400 may be user interface through which users upload digital assets to generate work unit records. The user interface 400 may include an input portion 402 configured to receive user input of individual digital assets. The user interface 400 may include a user interface element 401 that provides access to a page of the collaboration from which the user interface 400 was accessed. By way of non-limiting illustration, based on selection of element 308 in FIG. 3, user interface 400 may be presented. The project record for Project Q in FIG. 3 may act as a source record for the subsequent creation of one or more work unit records.

A user may input a digital asset into input portion 402, for example, an audio file of meeting or a dictation. Processing of the audio file may characterize content of the meeting or dictation. By way of non-limiting illustration, the content may be characterized as identifying the Project Q, identifying the subject of one of the tasks of Project Q (see Task X in FIG. 3), identifying needs and/or desires of a speaker, identifying a named person, and/or other characterizations. By way of non-limiting illustration, the meeting or dictation may include one or more users speaking about the subject matter of Task X (finalizing a product design), and the need for a follow up task for a user, Bob, to test the final design, and/or other content.

FIG. 5 shows the project page 302 in response to creation of one or more work unit records based on the uploaded digital asset. By way of non-limiting illustration, a work unit record for a unit of work 502 (“Task A”) may be created. One or more values of one or more parameters may be specified. By way of non-limiting illustration, an assignee may be “Bob”; a description may be “Test final design”; a due date may be set; and/or other information may be specified. In some implementations, the due date may be specified relative to one or more other records linked to the source record. By way of non-limiting illustration, the due date for unit of work 502 may be set for two weeks following the due date of Task X. Further, the project page 302 may include a link 504 to the digital asset, which may be stored in the new work unit record and/or other record following upload.

Referring back to FIG. 1, in some implementations, server(s) 102, client computing platform(s) 104, and/or external resources 126 may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via a network 116 such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which server(s) 102, client computing platform(s) 104, and/or external resource(s) 126 may be operatively linked via some other communication media.

A given client computing platform may include one or more processors configured to execute computer program components. The computer program components may be configured to enable an expert or user associated with the given client computing platform to interface with system 100 and/or external resource(s) 126, and/or provide other functionality attributed herein to client computing platform(s) 104. By way of non-limiting example, the given client computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms.

External resource(s) 126 may include sources of information outside of system 100, external entities participating with system 100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resource(s) 126 may be provided by resources included in system 100.

Server(s) 102 may include electronic storage 128, one or more processors 130, and/or other components. Server(s) 102 may include communication lines, or ports to enable the exchange of information with a network 116 and/or other computing platforms. Illustration of server(s) 102 in FIG. 1 is not intended to be limiting. Server(s) 102 may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to server(s) 102. For example, server(s) 102 may be implemented by a cloud of computing platforms operating together as server(s) 102.

Electronic storage 128 may comprise non-transitory storage media that electronically stores information. The electronic storage media of electronic storage 128 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with server(s) 102 and/or removable storage that is removably connectable to server(s) 102 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 128 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. Electronic storage 128 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage 128 may store software algorithms, information determined by processor(s) 130, information received from server(s) 102, information received from client computing platform(s) 104, and/or other information that enables server(s) 102 to function as described herein.

Processor(s) 130 may be configured to provide information processing capabilities in server(s) 102. As such, processor(s) 130 may include one or more of a digital processor, a physical processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 130 is shown in FIG. 1 as a single entity, this is for illustrative purposes only. In some implementations, processor(s)