Abstract: Provided are TCRs (e.g., TCRs that bind to NY-ESO-1), cells and pharmaceutical compositions comprising these TCRs, nucleic acids encoding these TCRs, expression vectors and host cells for making these TCRs, and methods of treating a subject using these TCRs.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing project tasks using content items. A user can create tasks within a content item. The tasks can be assigned to users and/or be assigned due dates. The content item can be shared with other users such that updates to the content item (e.g., updates to the tasks) can cause sending notifications to users associated with the content item. When a task in the content item is updated, all members of the project can be notified of the updated status of the task. A task list for a project can be created that aggregates tasks from multiple content items associated with the project. Tasks can be organized in the task list according to the content item the task was created in. Updates to tasks in the task list can cause corresponding updates to the tasks in the content items.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing project tasks using content items. A user can create tasks within a content item. The tasks can be assigned to users and/or be assigned due dates. The content item can be shared with other users such that updates to the content item (e.g., updates to the tasks) can cause sending notifications to users associated with the content item. When a task in the content item is updated, all members of the project can be notified of the updated status of the task. A task list for a project can be created that aggregates tasks from multiple content items associated with the project. Tasks can be organized in the task list according to the content item the task was created in. Updates to tasks in the task list can cause corresponding updates to the tasks in the content items.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing content item collections. For example, in embodiment, a client device may receive first user input selecting a content item collection. The client device may generate a graphical user interface for presenting the content item collection. The content item collection may include one or more tiles. Each tile may correspond to a content item embedded into the content item collection and stored by a content management system. The client device may present the content item collection including the one or more tiles. The client device may present, within each of the one or more tiles, an image representing the corresponding content item.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing content item collections. For example, in embodiment, a client device may receive first user input selecting a content item collection. The client device may generate a graphical user interface for presenting the content item collection. The content item collection may include one or more tiles. Each tile may correspond to a content item embedded into the content item collection and stored by a content management system. The client device may present the content item collection including the one or more tiles. The client device may present, within each of the one or more tiles, an image representing the corresponding content item.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects in a content management system. In some embodiments, a content management system can generate a graphical user interface that presents a centralized view of a project. For example, the project can include project members, content items, tasks assigned to project members, communications between project members and activity history for the project. The graphical user interface can present this project data (e.g., project members, content items, tasks, communications, activity, etc.) so that a project member can easily and quickly view multiple aspects of the project.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing content item collections. For example, in embodiment, a client device may receive first user input selecting a content item collection. The client device may generate a graphical user interface for presenting the content item collection. The content item collection may include one or more tiles. Each tile may correspond to a content item embedded into the content item collection and stored by a content management system. The client device may present the content item collection including the one or more tiles. The client device may present, within each of the one or more tiles, an image representing the corresponding content item.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects in a content management system. In some embodiments, a content management system can generate a graphical user interface that presents a centralized view of a project. For example, the project can include project members, content items, tasks assigned to project members, communications between project members and activity history for the project. The graphical user interface can present this project data (e.g., project members, content items, tasks, communications, activity, etc.) so that a project member can easily and quickly view multiple aspects of the project.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing content item collections. For example, in embodiment, a client device may receive first user input selecting a content item collection. The client device may generate a graphical user interface for presenting the content item collection. The content item collection may include one or more tiles. Each tile may correspond to a content item embedded into the content item collection and stored by a content management system. The client device may present the content item collection including the one or more tiles. The client device may present, within each of the one or more tiles, an image representing the corresponding content item.

Abstract: A collaborative content management system allows users to access collaborative content items. When a client device accesses a shared collaborative content item, the client device displays a portion of the collaborative content item that falls within a viewport. The client application generates a notification count of notification events associated with content that is contained in the collaborative content item and positioned below the viewport, and the client device displays the notification count in a graphical element adjacent to a bottom viewport edge. A similar process generates a second notification count of the notification events associated with content positioned above the viewport and displays a graphical element with the second notification count adjacent to the top viewport edge. The user can iteratively select one of the graphical elements to move the content of the collaborative content item to a portion corresponding to the next notification event above or below the viewport.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing project tasks using content items. A user can create tasks within a content item. The tasks can be assigned to users and/or be assigned due dates. The content item can be shared with other users such that updates to the content item (e.g., updates to the tasks) can cause sending notifications to users associated with the content item. When a task in the content item is updated, all members of the project can be notified of the updated status of the task. A task list for a project can be created that aggregates tasks from multiple content items associated with the project. Tasks can be organized in the task list according to the content item the task was created in. Updates to tasks in the task list can cause corresponding updates to the tasks in the content items.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing project tasks using content items. A user can create tasks within a content item. The tasks can be assigned to users and/or be assigned due dates. The content item can be shared with other users such that updates to the content item (e.g., updates to the tasks) can cause sending notifications to users associated with the content item. When a task in the content item is updated, all members of the project can be notified of the updated status of the task. A task list for a project can be created that aggregates tasks from multiple content items associated with the project. Tasks can be organized in the task list according to the content item the task was created in. Updates to tasks in the task list can cause corresponding updates to the tasks in the content items.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for copying content from a rendered document into another document. The disclosed technology addresses the need in the art to maintain a version of a collection of content items that includes changes and/or comments from a first group of users, and provide a second version of the collection of content items to an external user that does not include internal comments and/or visible changes. The solution may provide a work product that appears complete and/or professional to the second group of users, while the first group of users continue to update and/or collaborate on the first version of the collection of content items.

Abstract: A collaborative content management system allows users to access collaborative content items. When a client device accesses a shared collaborative content item, the client device displays a portion of the collaborative content item that falls within a viewport. The client application generates a notification count of notification events associated with content that is contained in the collaborative content item and positioned below the viewport, and the client device displays the notification count in a graphical element adjacent to a bottom viewport edge. A similar process generates a second notification count of the notification events associated with content positioned above the viewport and displays a graphical element with the second notification count adjacent to the top viewport edge. The user can iteratively select one of the graphical elements to move the content of the collaborative content item to a portion corresponding to the next notification event above or below the viewport.