Search based content inventory comparison
Summary by NHIP
Release Environment Package Comparison
The method filters product content data using selected environment filters to display package comparisons across development, testing, and production environments. Upon detecting release completion, the system promotes packages from the first filtered environment to the second filtered environment within the release management system.
Claim Score by NHIP
Abstract
The subject matter of this specification can be implemented in, among other things, a method that includes receiving a selection of content filters for content data that identifies products, packages, and repositories, and receiving a selection of environment filters. The method includes filtering the content data to identify content items in view of the content filters and the environment filters. The content items include one or more of the repositories, the products, or the packages. The method includes causing presentation of a list of the content items, which organizes the content items in view of release environments that are within the content items and repositories that are within the content items. The method includes receiving a selection of repository-environment combinations from the subset of the release environments and the subset of the repositories and causing presentation of a comparison of ones of the packages for each of the repository-environment combinations.

Term
Projected expiry 19 February 2034.
- Priority and filed
- Granted
- Today
- Projected expiry
19 claims: 3 independent, 16 dependent
- 1Broadest claimClaim Score 31, narrow(NHIP)A method comprising:receiving, using a processing device of a release management system, a selection of content data identifying a plurality of products, each of the plurality of products comprising a plurality of packages, wherein the release management system comprises a plurality of release environments comprising a development environment, a testing environment, and a production environment with each release environment representing an installation area in which a portion of the packages associated with the content data is to be released;receiving a selection of first and second environment filters from a plurality of environment filters, the plurality of environment filters comprise one or more of a development environment filter, a testing environment filter, and a production environment filter that correspond to at least one of the plurality of release environments;responsive to receiving the selection of first and second environment filters, providing for display of a comparison between of a corresponding package from each of the release environments associated with the first and second environment filters;and responsive to detecting completion of a level in the releasing of the content data, causing packages to be promoted from one release environment corresponding to the first environment filter of the plurality of environment filters to another release environment corresponding to the second environment filter of the plurality of environment filters.
- 8A non-transitory computer-readable medium having instructions that, when executed by a processing device, cause the processing device to:receive, using the processing device, a selection of content data identifying a plurality of products, each of the plurality of products comprising a plurality of packages, wherein the release management system comprises a plurality of release environments comprising a development environment, a testing environment, and a production environment with each release environment representing an installation area in which a portion of the packages associated with the content data is to be released;receive a selection of first and second environment filters from a plurality of environment filters, the plurality of environment filters comprise one or more of a development environment filter, a testing environment filter, and a production environment filter that correspond to at least one of the plurality of release environments;responsive to receiving the selection of first and second environment filters, provide, using the processing device, for display of a comparison between a corresponding package from each of the release environments associated with the first and second environment filters;and responsive to detecting completion of a level in the releasing of the content data, cause packages to be promoted from one release environment corresponding to the first environment filter of the plurality of environment filters to another release environment corresponding to the second environment filter of the plurality of environment filters.
- 14A system comprising:an interface of a release management system to: receive a selection of content data that identifies a plurality of products, each of the plurality of products comprising a plurality of packages, wherein the release management system comprises a plurality of release environments comprising a development environment, a testing environment, and a production environment with each release environment representing an installation area in which a portion of the packages associated with the content data is to be released;receive a selection of first and second environment filters from a plurality of environment filters, the plurality of environment filters comprise a development environment filter, a testing environment filter, and a production environment filter that correspond to at least one of the plurality of release environments;and a processing device operatively coupled to the interface to: responsive to receiving the selection of first and second environment filters, provide for display of a comparison between a corresponding package from each of the release environments associated with the first and second environment filters;and responsive to detecting completion of a level in the releasing of the content data, cause packages to be promoted from one release environment corresponding to the first environment filter of the plurality of environment filters to another release environment corresponding to the second environment filter of the plurality of environment filters.
Independent claims3
64 paragraphs in 4 sections, as filed
TECHNICAL FIELD
0001This instant specification relates to a user interface for search based content inventory comparison.
BACKGROUND
0002In software, a package management system, sometimes called a package manager, includes software tools that automate the installation, upgrade, configuration, and removal of software packages for software programs on client computer systems. Package management systems provide remote administration and software distribution that takes the place of manual installations and updates. Packages are distributions of software, applications, and data. Packages may also contain metadata, such as the software's name, a description of the purpose of the software, a version number of the software, a vendor name for the software, a checksum for the software, and a list of dependencies for the software to run properly. Upon installation, the metadata may be stored in a package database. The package management system may use the list of software dependencies and version information to prevent software mismatches and missing prerequisites.
DESCRIPTION OF DRAWINGS
0003<figref idref="DRAWINGS">FIG. 1</figref> is a schematic diagram that shows an example of a system for search based content inventory comparison.
0004<figref idref="DRAWINGS">FIGS. 2A-B</figref> show examples of user interfaces for search based content inventory comparison.
0005<figref idref="DRAWINGS">FIG. 3</figref> is flow chart that shows an example of a process for search based content inventory comparison.
0006<figref idref="DRAWINGS">FIG. 4</figref> is a schematic diagram that shows an example of a computer system.
DETAILED DESCRIPTION
0007This specification describes systems, processes, and user interfaces for search based content inventory comparison. Release management systems often manage a large number of products. Those products may each be made up of one or more packages. Each package for each product may have one or more instances corresponding to different versions of the package. Each version of a package may be hosted by one or more repositories. A group of versions of packages may be bundled together as a changeset or system template and used by the release management system as a release to be distributed to client computer systems. The changeset and/or system template may represent a particular stage of a development cycle for a product that includes those packages.
0008The stages of the development cycle may be associated with a particular installation environment, such as a development, testing, or production environment. Sometimes a set of versions of packages may be promoted from one environment to another or another release management operation may be performed, such as adding and/or removing a package to or from a changeset or modifying a version of a package in a changeset. In performing release management operations, a user of the release management system may want to search for and identify particular versions of packages for particular products, repositories, and/or environments. In addition, the user may want to compare the identified items to aid in making a decision related to the release management operation to be performed.
0009The systems, processes, and user interfaces described below provide tools for quickly searching for and identifying particular products, repositories, and packages within the release management system. The systems, processes, and user interfaces described below also provide tools for comparing packages across repositories and environments. In addition, as a result of the identification and comparison, the systems, processes, and user interfaces described below further provide for performing release management operations, such as modifying packages and/or versions of packages within changesets and/or system templates.
0010<figref idref="DRAWINGS">FIG. 1</figref> is a schematic diagram that shows an example of a system <b>100</b> for search based content inventory comparison. The system <b>100</b> includes a release management system <b>102</b>, multiple repository systems <b>104</b><i>a</i>-<i>c</i>, and multiple computer systems <b>106</b><i>a</i>-<i>c </i>in communication with a network <b>108</b>.
0011The network <b>108</b> may include wired and/or wireless communication devices. The network <b>108</b> may include a local network, a wide network, and/or one or more of the computer devices that make up the Internet.
0012The repository systems <b>104</b><i>a</i>-<i>c </i>store software packages for software products in multiple data storages <b>110</b><i>a</i>-<i>c</i>, respectively. The repository systems <b>104</b><i>a</i>-<i>c </i>provide the packages to the computer systems <b>106</b><i>a</i>-<i>c </i>for installation at the computer systems <b>106</b><i>a</i>-<i>c </i>within multiple data storages <b>112</b><i>a</i>-<i>c</i>, respectively.
0013In addition, one or more of the computer systems <b>106</b><i>a</i>-<i>c </i>may include a virtual computer system <b>114</b>. The virtual computer system <b>114</b> is a virtual machine that emulates a physical computer device using software. The virtual computer system <b>114</b> may include a virtual data storage <b>116</b> in which the virtual computer system <b>114</b> may install one or more of the packages from the repository systems <b>104</b><i>a</i>-<i>c. </i>
0014The computer systems <b>106</b><i>a</i>-<i>c </i>may install new versions of the packages as sets of packages are promoted from one environment to another, e.g., from a development environment to a testing environment or from a testing environment to a production environment. The release management system <b>102</b> provides a user interface for managing the distribution and installation of the packages at the computer systems <b>106</b><i>a</i>-<i>c </i>as well as promotion of the packages.
0015The release management system <b>102</b> stores content data in a data storage <b>118</b>. The release management system <b>102</b> may retrieve the content data from the repository systems <b>104</b><i>a</i>-<i>c </i>and/or the computer systems <b>106</b><i>a</i>-<i>c</i>. The content data identifies the products and versions of packages within the products that are available at each of the repository systems <b>104</b><i>a</i>-<i>c</i>. The content data also identifies the environments to which each of the versions of the packages belong. In some implementations, the release management system <b>102</b> may store data describing ones of the computer systems <b>106</b><i>a</i>-<i>c </i>to which each of the versions of the packages have been distributed and/or installed. In addition, the release management system <b>102</b> may store data describing dependencies between versions of the products and/or packages.
0016The release management system <b>102</b> provides a user interface for searching or filtering the content data and comparing the results of the search. In some implementations, the user interface is provided at the release management system <b>102</b>. In some implementations, the release management system may provide the user interface to a computer device that is separate or remote from the release management system <b>102</b>. The user interface may be a standalone application, such as a desktop application or a mobile device app. The release management system <b>102</b> may provide data to the standalone application for presentation to a user, such as the results of the search or filtering and the comparison.
0017Alternatively, a server application at the release management system <b>102</b> may provide instructions to an interpreter application, such as a browser application, at the release management system <b>102</b> or at a remote computer device. The interpreter application processes the instructions to present the results of the search or filtering and the comparison to the user. In the case of the browser application, the instructions may include markup, such as Hypertext Markup Language (HTML) and/or Extensible Markup Language (XML). The instructions may also include scripting instructions, such as JavaScript. The browser application processes the markup and scripting to present the results of the search or filtering and the comparison to the user.
0018<figref idref="DRAWINGS">FIG. 2A</figref> shows an example of a user interface <b>200</b> for search based content inventory comparison. The user interface <b>200</b> may be presented to a user on a display device, for example, at the release management system <b>102</b> or another computer system. The user interface <b>200</b> includes a filter area <b>202</b> and a results area <b>204</b>. A user may make inputs in the filter area <b>202</b> to select filters that filter content data, such as the content data stored in the data storage <b>118</b> of the release management system <b>102</b>.
0019The filter area <b>202</b> includes a content type filter <b>206</b>. The content type filter <b>206</b> allows a user to make an input to select the type of content to be presented in the results area <b>204</b>. The content type filter <b>206</b> may be, for example, a pull-down list with options that include packages, products, and repositories. In some implementations, the results presented in the results area <b>204</b> are hierarchical and the content type filter <b>206</b> selects the lowest level of the hierarchy to be presented in the results area <b>204</b>. For example, the user has selected “Repositories” in the content type filter <b>206</b>. Accordingly, the results area <b>204</b> presents a hierarchy that includes multiple products <b>208</b><i>a</i>-<i>b </i>and multiple repositories <b>210</b><i>a</i>-<i>e </i>as the lowest level below each of the products <b>208</b><i>a</i>-<i>b</i>. In particular, the Repositories A1, A2, A3, and A4 all store packages for Product A and, accordingly, are listed below the first product <b>208</b><i>a </i>in the results area <b>204</b>. The Repository A1 also stores packages for Product B and, accordingly, is listed below the second product <b>208</b><i>b </i>in the results area <b>204</b>. In another example, a user may select “Packages” in the content type filter <b>206</b>. The results area <b>204</b> may then present one or more packages below each of the repositories <b>210</b><i>a</i>-<i>e </i>representing the packages stored at the repository.
0020The filter area <b>202</b> also includes multiple content filters <b>212</b><i>a</i>-<i>b</i>. The first content filter <b>212</b><i>a </i>is a products content filter that is applied to products in the content data. The second content filter <b>212</b><i>b </i>is a repositories content filter that is applied to repositories in the content data. The content filters <b>212</b><i>a</i>-<i>b </i>may include multiple keyword filters <b>214</b><i>a</i>-<i>b </i>and multiple individual filters <b>216</b><i>a</i>-<i>b</i>. A user may make an input in the first keyword filter <b>214</b><i>a </i>to request that the products be filtered based on a keyword appearing in data for the products, such as in names or identifiers of the products. A user may make an input in the second keyword filter <b>214</b><i>b </i>to request that the repositories be filtered based on a keyword appearing in data for the repositories, such as in names or identifiers of the repositories. The second keyword filter <b>214</b><i>b </i>includes the keyword “Repository A.” Accordingly, the user interface <b>200</b> only includes repositories in the results area <b>204</b> that have “Repository A” in the name of the repository, e.g., “Repository A1,” “Repository A2,” “Repository A3,” and “Repository A4.”
0021The individual filters <b>216</b><i>a</i>-<i>b </i>allow a user to input a name or portion of a name of a content item of the corresponding content type. For example, a user may input a name or portion of a name of a specific product in the first individual filter <b>216</b><i>a </i>or a specific repository in the second individual filter <b>216</b><i>b</i>. The user may then select an “Add” button to request that the specific content item be added as a filter. The user interface <b>200</b> may then present a list of the specific individual content filters below the corresponding one of the individual filters <b>216</b><i>a</i>-<i>b. </i>
0022In some implementations, the user interface <b>200</b> may disable a keyword filter for a content type if the individual filter for the content type is being used and vice versa. Alternatively, the user interface <b>200</b> may allow both the keyword filter and the individual filter for the content type to be used concurrently. For example, the separate results from the keyword filter and the individual filter for the content type may be combined in the results area <b>204</b>.
0023In some implementations, the user interface <b>200</b> may disable and/or cease presentation of ones of the content filters <b>212</b><i>a</i>-<i>b </i>that are below the content type that has been selected in the content type filter <b>206</b> in the hierarchy of content types. For example, in response to selection of “Repositories” in the content type filter <b>206</b>, the user interface <b>200</b> may disable and/or cease presenting a content filter for packages because packages are below repositories in the hierarchy of content types. If “Packages” had been selected in the content type filter <b>206</b>, then the user interface <b>200</b> would present a content filter for packages, which may have corresponding keyword and individual filters. The packages presented in the results area <b>204</b> below each of the repositories <b>210</b><i>a</i>-<i>e </i>would then be the result of any filters specified in the package content filter.
0024The results area <b>204</b> includes an environment filter <b>218</b>. In response to a user selecting the environment filter <b>218</b>, the user interface <b>200</b> presents a list of environments from which the user may make selections. The environments represent levels in a release process for one or more products and/or packages within the products. The environments may include, for example, a development environment where software is initially written or developed. The environments may include a testing environment where software is installed for testing. The environments may include a production environment where software is installed for use in production. While described here as three levels, the environments may include more or fewer levels. In addition, the three types of environments described may include multiple levels.
0025As a set of versions of packages for one or more products completes a level of the release process it is promoted to the next level. The set of versions of packages may be referred to as a changeset. For example, once packages in a changeset have been written by developers, the changeset may be promoted from a development environment to a testing environment. Once testing has been completed, the changeset may be promoted from the testing environment to the production environment.
0026The computer systems <b>106</b><i>a</i>-<i>b </i>and/or the virtual computer systems <b>114</b> may request the current packages for a particular environment. For example, the first computer system <b>106</b><i>a </i>may be a developer console that loads packages of one or more products for a development environment. The second computer system <b>106</b><i>b </i>may be a testing station that loads packages of one or more products for a testing environment. The third computer system <b>106</b><i>c </i>may be a production server that loads packages of one or more products for a production environment.
0027The user interface <b>200</b> presents the list of environments in response to user selection of the environment filter <b>218</b>. The user may select individual environments from the list, or in some implementations, the user may select a set or progression of environments (e.g., corresponding development, testing, and production environments). In response to selection of a development environment filter and a testing environment filter in the list of environment filters, the user interface <b>200</b> presents content data for multiple environments <b>220</b><i>a</i>-<i>b</i>. In particular, the user interface <b>200</b> presents content items in the results area <b>204</b> that satisfy both the content filters <b>212</b><i>a</i>-<i>b </i>(e.g., repositories that include “Repository A” in their names) and the environment filters (e.g., the “Dev” and “Test” environments). In some implementations, the results area <b>204</b> also presents a default environment referred to as “Library.” The Library default environment may include, for example, a list of versions (e.g., the latest versions and/or all versions) of each package for each product at each repository.
0028Each cell in the grid shown in the results area <b>204</b> represents a combination of a particular content item and an environment in which the content item exists. Each cell may present information about the combination. For example, the cell for the first product <b>208</b><i>a </i>and the first environment <b>220</b><i>a </i>indicates that there are two repositories within the first product <b>208</b><i>a </i>that satisfy the second content filter <b>212</b><i>b </i>(e.g., the first repository <b>210</b><i>a </i>and the second repository <b>210</b><i>b</i>). In response to selection of a cell (e.g., hovering a pointer over the cell or clicking on the cell), the user interface <b>200</b> may present additional information, such as numbers of content items, if any, within the selected content item and/or a link to a user interface that lists the content items that are within the selected content item.
0029The results area <b>204</b> may include a keyword filter <b>222</b>. A user may input one or more keywords into the keyword filter <b>222</b>. In response, the user interface <b>200</b> filters the list of content items in the results area <b>204</b> in view of the keywords in the keyword filter <b>222</b>. The user interface <b>200</b> may include only those content items that include the keywords from the keyword filter <b>222</b>, regardless of the type of the content item. For example, a user may input “A” in the keyword filter <b>222</b>. The user interface <b>200</b> may then continue to present the first product <b>208</b><i>a </i>and the repositories <b>210</b><i>a</i>-<i>e </i>because their names all include “A.” The user interface <b>200</b> may stop presenting the second product <b>208</b><i>b </i>as its name does not include “A.”
0030The results area <b>204</b> may also include a uniqueness filter <b>224</b>. In response to selection of the uniqueness filter <b>224</b>, the user interface <b>200</b> may present a list of options including “All,” “Unique Content,” and “Shared Content.” In response to selection of the “All” option, the user interface <b>200</b> may present all of the content items that satisfy the other filters, such as one or more of the content type filter <b>206</b>, the content filters <b>212</b><i>a</i>-<i>b</i>, the environment filter <b>218</b>, or the keyword filter <b>222</b>.
0031In response to selection of the “Unique Content” option, the user interface <b>200</b> may present the content items that are unique across the environments <b>220</b><i>a</i>-<i>b</i>, such as the fourth repository <b>210</b><i>d </i>within the first product <b>208</b><i>a </i>and the fifth repository <b>210</b><i>e </i>within the second product <b>208</b><i>b</i>. The fourth repository <b>210</b><i>d </i>has unique content because the first environment <b>220</b><i>a </i>does not include any packages from the fourth repository <b>210</b><i>d </i>as indicated by the dash in the results area <b>204</b> for that cell, while the second environment <b>220</b><i>b </i>does include one or more packages from the fourth repository <b>210</b><i>d </i>as indicated by the checkbox in the results area <b>204</b> for that cell. The fifth repository <b>210</b><i>e </i>has unique content because the first environment <b>220</b><i>a </i>does not include any packages from the fifth repository <b>210</b><i>e </i>as indicated by the dash in the results area <b>204</b> for that cell, while the second environment <b>220</b><i>b </i>does include one or more packages from the fifth repository <b>210</b><i>e </i>as indicated by the checkbox in the results area <b>204</b> for that cell. While described here as “the fifth repository <b>210</b><i>e</i>,” this repository may be the same repository as one or more other repositories in the results area <b>204</b>, such as the first repository <b>210</b><i>a </i>(e.g., both are “Repository A1”).
0032In response to selection of the “Shared Content” option, the user interface <b>200</b> may present the content items that are shared across the environments <b>220</b><i>a</i>-<i>b</i>, such as the first repository <b>210</b><i>a </i>and the second repository <b>210</b><i>b </i>within the first product <b>208</b><i>a</i>. The first repository <b>210</b><i>a </i>has shared content because the first environment <b>220</b><i>a </i>includes one or more packages from the first repository <b>210</b><i>a </i>as indicated by the checkbox in the results area <b>204</b> for that cell, and the second environment <b>220</b><i>b </i>also includes one or more packages from the first repository <b>210</b><i>a </i>as indicated by the checkbox in the results area <b>204</b> for that cell. The second repository <b>210</b><i>b </i>has shared content because the first environment <b>220</b><i>a </i>includes one or more packages from the second repository <b>210</b><i>b </i>as indicated by the checkbox in the results area <b>204</b> for that cell, and the second environment <b>220</b><i>b </i>also includes one or more packages from the second repository <b>210</b><i>b </i>as indicated by the checkbox in the results area <b>204</b> for that cell.
0033The user interface <b>200</b> may apply the uniqueness filter <b>224</b> to the type of content in the results area <b>204</b> that was selected in the content type filter <b>206</b>. For example, because “Repositories” is selected in the content type filter <b>206</b>, the user interface <b>200</b> may apply the uniqueness filter <b>224</b> to the repositories <b>210</b><i>a</i>-<i>e </i>in the results area <b>204</b>. If “Packages” is selected in the content type filter <b>206</b>, then the user interface <b>200</b> may apply the uniqueness filter <b>224</b> to packages in the results area <b>204</b>. In addition, if “Products” is selected in the content type filter <b>206</b>, then the user interface <b>200</b> may apply the uniqueness filter <b>224</b> to products in the results area <b>204</b>.
0034The filter area <b>202</b> may include a favorites control <b>226</b>. In response to selection of a first portion of the favorites control <b>226</b>, the user interface <b>200</b> may store the entries from one or more of the content type filter <b>206</b>, the content filters <b>212</b><i>a</i>-<i>b</i>, the keyword filter <b>222</b>, the environment filter <b>218</b>, or the uniqueness filter <b>224</b>. The user interface <b>200</b> may present an input dialog to the user in which the user may input a name for the set of filters, such as “Repository A.” Subsequently, the user may select a second portion of the favorites control <b>226</b>. In response, the user interface <b>200</b> presents a list of the saved sets of filters, including the “Repository A” set of filters. In response to selection of a set of filters from the list, the user interface <b>200</b> populates one or more of the content type filter <b>206</b>, the content filters <b>212</b><i>a</i>-<i>b</i>, the keyword filter <b>222</b>, the environment filter <b>218</b>, or the uniqueness filter <b>224</b> with the stored values for the corresponding filter and presents the results of the filters in the results area <b>204</b>.
0035One or more of the cells in the grid of the results area <b>204</b> may include multi-select controls, such as checkboxes. Each cell may represent a combination of a particular content item, such as a repository, and a particular environment. Selecting a multi-select control, selects the corresponding combination of content item and environment. Once a set of combinations is selected, the user may request that an operation be performed on the set of combinations. For example, in response to a user selection of a compare control <b>228</b>, the user interface <b>200</b> may present a comparison of content items between each of the selected repository-environment combinations.
0036<figref idref="DRAWINGS">FIG. 2B</figref> shows an example of a user interface <b>250</b> for search based content inventory comparison. The user interface <b>250</b> presents a comparison of multiple packages <b>252</b><i>a</i>-<i>h </i>across multiple repository-environment combinations <b>254</b><i>a</i>-<i>d </i>in a comparison area <b>256</b>. For example, the packages <b>252</b><i>a</i>-<i>h </i>may be presented along a vertical axis of a grid and the repository-environment combinations <b>254</b><i>a</i>-<i>d </i>may be presented along a horizontal axis of the grid, or vice versa. The user interface <b>250</b> may present the comparison in response to selection of the compare control <b>228</b>.
0037Each of the cells in the grid may present information about the package-repository-environment combination, such as a version of the package within the repository-environment combination. For example, the cells for the first package <b>252</b><i>a </i>show that Package A has a version of four for the first repository-environment combination <b>254</b><i>a </i>(Repository A2 and the Library environment), a version of two for the second repository-environment combination <b>254</b><i>b </i>(Repository A2 and the Dev environment), a version of one for the third repository-environment combination <b>254</b><i>c </i>(Repository A2 and the Test environment), and that the Package A is not present within the fourth repository-environment combination <b>254</b><i>d </i>(Repository A3 and the Library environment).
0038As with the cells in the results area <b>204</b>, the user interface <b>250</b> may present additional information for each of the cells in the comparison area <b>256</b> in response to a selection, such as a hover or click operation of a pointer device, from the user. In the case of packages, the additional information may include, for example, an identifier of a person that committed or finalized the version of the package represented by the cell. The additional information may also include the time and/or date that the version was committed or finalized.
0039Also similar to the results area <b>204</b>, each of the cells may include a multi-select control, such as a check-box, that allows the user to select multiple packages within the comparison area <b>256</b>. The user may then request that the user interface <b>250</b> perform an operation on the selected packages. For example, in response to a user selection of a changeset control <b>258</b>, the user interface <b>250</b> may present a list of changesets to which the selected packages may be added and/or a control for creating a new changeset that includes the selected packages. The user may then select a changeset from the list or the changeset creation control to request the operation. Alternatively, the user may select a system template control <b>260</b>. In response, the user interface <b>250</b> may present a list of system templates to which the selected packages may be added and/or a control for creating a new system template that includes the selected packages. The user may then select a system template from the list or the system template creation control to request the operation.
0040In some implementations, the results area <b>204</b> and/or the comparison area <b>256</b> disable the compare control <b>228</b> unless content items from two different environments and/or repository-environment combinations are selected. In addition, the results area <b>204</b> and/or the comparison area <b>256</b> may disable the changeset control <b>258</b> and/or the system template control <b>260</b> unless content items from the same environment and/or the same repository-environment combination are selected.
0041<figref idref="DRAWINGS">FIG. 3</figref> is a flow chart that shows an example of a process <b>300</b> for search based content inventory comparison. The process <b>300</b> may be performed, for example, by a system such as the system <b>100</b>. For clarity of presentation, the description that follows uses the system <b>100</b> as an example for describing the process <b>300</b>. However, another system, or combination of systems, may be used to perform the process <b>300</b>.
0042At box <b>302</b>, the process <b>300</b> begins with receiving a selection of one or more content filters from a plurality of content filters including a products content filter, a repositories content filter, and a packages content filter. A release management system stores content data that identifies a plurality of products that each have a plurality of packages. The content data identifies each of the plurality of packages as a particular version of at least a component of a corresponding one of the plurality of products. The content data also identifies a plurality of repositories that each store a subset of the plurality of packages for one or more of the plurality of products. For example, the release management system <b>102</b> may receive the selections in the content filters <b>212</b><i>a</i>-<i>b </i>from the user interface <b>200</b>. The user interface <b>200</b> may be in operation at the release management system <b>102</b> or at a computer device that is separate from the release management system <b>102</b> and in communication with the release management system <b>102</b>, such as over the network <b>108</b>.
0043At box <b>304</b>, the process <b>300</b> includes receiving a selection of one or more environment filters from a plurality of environment filters. The release management system has a plurality of release environments including one or more of a development environment, a testing environment, or a production environment. The plurality of environment filters comprise one or more of a development environment filter, a testing environment filter, or a production environment filter that correspond to the plurality of release environments. Each of the plurality of release environments has a corresponding one of a plurality of changesets that includes at least one package from the plurality of packages for one or more of the plurality of products. For example, the release management system <b>102</b> may receive the selections of environments using the environment filter <b>218</b> of the user interface <b>200</b>.
0044At box <b>306</b>, the process <b>300</b> includes filtering the content data to identify a first plurality of content items in view of the one or more content filters and the one or more environment filters. The first plurality of content items includes one or more of the plurality of repositories, the plurality of products, or the plurality of packages. For example, the release management system <b>102</b> may use the values from the content filters <b>212</b><i>a</i>-<i>b </i>to filter the content data from the data storage <b>118</b> and identify one or more content items.
0045At box <b>308</b>, the process <b>300</b> includes causing presentation of a list of the first plurality of content items. The presentation organizes the first plurality of content items in view of a subset of the plurality of release environments that are within the first plurality of content items and a subset of the plurality of repositories that are within the first plurality of content items. For example, the release management system <b>102</b> may cause the user interface <b>200</b> to present the identified content items in the results area <b>204</b>.
0046At box <b>310</b>, the process <b>300</b> includes receiving a selection of a plurality of repository-environment combinations from the subset of the release environments and the subset of the plurality of repositories. For example, the release management system <b>102</b> may receive the selections of the repository-environment combinations from the user interface <b>200</b> using the multi-select controls in the results area <b>204</b>.
0047At box <b>312</b>, the process <b>300</b> includes causing presentation of a comparison of ones of the plurality of packages for each of the plurality of repository-environment combinations. For example, the release management system <b>102</b> may cause the user interface <b>250</b> to present the comparison of the packages for the repository-environment combinations in the comparison area <b>256</b>. The user interface <b>250</b> may be in operation at the release management system <b>102</b> or at a computer device that is separate from the release management system <b>102</b> and in communication with the release management system <b>102</b>, such as over the network <b>108</b>.
0048In some implementations, the process <b>300</b> may include receiving a selection of a content type from a plurality of content types comprising a products content type, a repositories content type, and a packages content type. The presentation of the list of the first plurality of content items may then be organized further in view of the content type.
0049In some implementations, the process <b>300</b> may include receiving a selection of a uniqueness filter from a plurality of uniqueness filters comprising a unique filter that filters for unique ones of the content type across the subset of the release environments, a shared filter that filters for shared ones of the content type across the subset of the release environments, and an all filter that filters for all of the content type across the subset of the release environments. Filtering the content data to identify the first plurality of content items may then be further in view of the uniqueness filter.
0050In some implementations, the process <b>300</b> may include receiving a selection of a content item from the first plurality of content items in the list. The process <b>300</b> may then include causing presentation of a list of a second plurality of content items that are within the content item in response to receiving the selection of the content item.
0051In some implementations, the process <b>300</b> may include receiving a selection of a keyword search term. Filtering the content data to identify the first plurality of content items may then be further in view of the keyword search term.
0052In some implementations, the process <b>300</b> may include receiving a selection of one or more packages from the comparison of the ones of the plurality of packages for each of the plurality of repository-environment combinations. The process <b>300</b> may then include adding the one or more packages to a changeset in the plurality of changesets.
0053<figref idref="DRAWINGS">FIG. 4</figref> is a schematic diagram that shows an example of a machine in the form of a computer system <b>400</b>. The computer system <b>400</b> executes one or more sets of instructions <b>426</b> that cause the machine to perform any one or more of the methodologies discussed herein. The machine may operate in the capacity of a server or a client machine in client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a web appliance, a server, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute the sets of instructions <b>426</b> to perform any one or more of the methodologies discussed herein.
0054The computer system <b>400</b> includes a processor <b>402</b>, a main memory <b>404</b> (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), a static memory <b>406</b> (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage device <b>416</b>, which communicate with each other via a bus <b>408</b>.
0055The processor <b>402</b> represents one or more general-purpose processing devices such as a microprocessor, central processing unit, or the like. More particularly, the processor <b>402</b> may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets or processors implementing a combination of instruction sets. The processor <b>402</b> may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. The processor <b>402</b> is configured to execute instructions of the release management system <b>102</b>, the repository systems <b>104</b><i>a</i>-<i>c</i>, and/or the computer systems <b>106</b><i>a</i>-<i>c </i>for performing the operations and steps discussed herein.
0056The computer system <b>400</b> may further include a network interface device <b>422</b> that provides communication with other machines over a network <b>418</b>, such as a local area network (LAN), an intranet, an extranet, or the Internet. The computer system <b>400</b> also may include a display device <b>410</b> (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device <b>412</b> (e.g., a keyboard), a cursor control device <b>414</b> (e.g., a mouse), and a signal generation device <b>420</b> (e.g., a speaker).
0057The data storage device <b>416</b> may include a computer-readable storage medium <b>424</b> on which is stored the sets of instructions <b>426</b> of the release management system <b>102</b>, the repository systems <b>104</b><i>a</i>-<i>c</i>, and/or the computer systems <b>106</b><i>a</i>-<i>c </i>embodying any one or more of the methodologies or functions described herein. The sets of instructions <b>426</b> of the release management system <b>102</b>, the repository systems <b>104</b><i>a</i>-<i>c</i>, and/or the computer systems <b>106</b><i>a</i>-<i>c </i>may also reside, completely or at least partially, within the main memory <b>404</b> and/or within the processor <b>402</b> during execution thereof by the computer system <b>400</b>, the main memory <b>404</b> and the processor <b>402</b> also constituting computer-readable storage media. The sets of instructions <b>426</b> may further be transmitted or received over the network <b>418</b> via the network interface device <b>422</b>.
0058While the example of the computer-readable storage medium <b>424</b> is shown as a single medium, the term “computer-readable storage medium” can include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the sets of instructions <b>426</b>. The term “computer-readable storage medium” can 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 present disclosure. The term “computer-readable storage medium” can include, but not be limited to, solid-state memories, optical media, and magnetic media.
0059In the foregoing description, numerous details are set forth. It will be apparent, however, to one of ordinary skill in the art having the benefit of this disclosure, that the present disclosure may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the present disclosure.
0060Some portions of the detailed description have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
0061It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise, it is appreciated that throughout the description, discussions utilizing terms such as “identifying”, “providing”, “enabling”, “finding”, “selecting” or the like, refer to the actions and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (e.g., electronic) quantities within the computer system memories or registers into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
0062The present disclosure also relates to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but not limited to, any type of disk including a floppy disk, an optical disk, a compact disc read-only memory (CD-ROM), a magnetic-optical disk, a read-only memory (ROM), a random access memory (RAM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic or optical card, or any type of media suitable for storing electronic instructions.
0063The words “example” or “exemplary” are used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “example” or “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the words “example” or “exemplary” is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from context, “X includes A or B” is intended to mean any of the natural inclusive permutations. That is, if X includes A; X includes B; or X includes both A and B, then “X includes A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Moreover, use of the term “an embodiment” or “one embodiment” or “an implementation” or “one implementation” throughout is not intended to mean the same embodiment or implementation unless described as such. The terms “first,” “second,” “third,” “fourth,” etc. as used herein are meant as labels to distinguish among different elements and may not necessarily have an ordinal meaning according to their numerical designation.
0064It is to be understood that the above description is intended to be illustrative, and not restrictive. Other implementations will be apparent to those of skill in the art upon reading and understanding the above description. The scope of the disclosure should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
Contents4
9 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US11841956B2 | Cited by | United States of America | Applicant |
| US12248564B2 | Cited by | United States of America | Applicant |
| US11875180B2 | Cited by | United States of America | Applicant |
| US12530220B2 | Cited by | United States of America | Applicant |
| US11748457B2 | Cited by | United States of America | Applicant |
| US12253944B2 | Cited by | United States of America | Applicant |
| US12124576B2 | Cited by | United States of America | Applicant |
| US10725778B2 | Cited by | United States of America | Applicant |
| US12524394B2 | Cited by | United States of America | Applicant |
| US12373314B2 | Cited by | United States of America | Applicant |
| US12124566B2 | Cited by | United States of America | Applicant |
| US12393677B2 | Cited by | United States of America | Applicant |
| US12079197B2 | Cited by | United States of America | Applicant |
| US12242575B2 | Cited by | United States of America | Applicant |
| US11977613B2 | Cited by | United States of America | Applicant |
| US11797398B2 | Cited by | United States of America | Applicant |
| US2002057290A1 | Cites | United States of America | Search report |
| US2005091642A1 | Cites | United States of America | Search report |
| US2006282480A1 | Cites | United States of America | Search report |
| US2006288054A1 | Cites | United States of America | Search report |
| US2006288055A1 | Cites | United States of America | Search report |
| US2007101197A1 | Cites | United States of America | Search report |
| US2007168956A1 | Cites | United States of America | Search report |
| US2009132645A1 | Cites | United States of America | Applicant |
| US2009199047A1 | Cites | United States of America | Search report |
| US2009199160A1 | Cites | United States of America | Search report |
| US2009281857A1 | Cites | United States of America | Search report |
| US2009319544A1 | Cites | United States of America | Search report |
| US2010042603A1 | Cites | United States of America | Applicant |
| US2010114642A1 | Cites | United States of America | Search report |
| US2010205266A1 | Cites | United States of America | Search report |
| US2010250511A1 | Cites | United States of America | Search report |
| US2011055544A1 | Cites | United States of America | Search report |
| US2011055826A1 | Cites | United States of America | Search report |
| US2011107300A1 | Cites | United States of America | Search report |
| US2012137138A1 | Cites | United States of America | Search report |
| US2012240236A1 | Cites | United States of America | Search report |
| US2012284111A1 | Cites | United States of America | Applicant |
| US2012330937A1 | Cites | United States of America | Applicant |
| US2013014006A1 | Cites | United States of America | Search report |
| US2013159867A1 | Cites | United States of America | Search report |
| US2013339932A1 | Cites | United States of America | Search report |
| US5920873A | Cites | United States of America | Search report |
| US6397212B1 | Cites | United States of America | Applicant |
| US7469409B2 | Cites | United States of America | Search report |
| US8065307B2 | Cites | United States of America | Applicant |
| US8180868B2 | Cites | United States of America | Search report |
| US8225292B2 | Cites | United States of America | Search report |
| US8255362B2 | Cites | United States of America | Search report |
| US8370803B1 | Cites | United States of America | Search report |
| US8418147B1 | Cites | United States of America | Search report |
| US8533844B2 | Cites | United States of America | Search report |
| US8561012B1 | Cites | United States of America | Search report |
| US8635204B1 | Cites | United States of America | Search report |
| US8701078B1 | Cites | United States of America | Search report |
| US8739047B1 | Cites | United States of America | Search report |
| US8739112B1 | Cites | United States of America | Search report |
| US8799044B2 | Cites | United States of America | Search report |
| US8819617B1 | Cites | United States of America | Search report |
| US8984628B2 | Cites | United States of America | Search report |
| US9159039B2 | Cites | United States of America | Search report |
| US9177269B2 | Cites | United States of America | Search report |
| US20020057290A1 | Cites | United States of America | Search report |
| US20050091642A1 | Cites | United States of America | Search report |
| US20060282480A1 | Cites | United States of America | Search report |
| US20060288054A1 | Cites | United States of America | Search report |
| US20060288055A1 | Cites | United States of America | Search report |
| US20070101197A1 | Cites | United States of America | Search report |
| US20070168956A1 | Cites | United States of America | Search report |
| US20090132645A1 | Cites | United States of America | Applicant |
| US20090199047A1 | Cites | United States of America | Search report |
| US20090199160A1 | Cites | United States of America | Search report |
| US20090281857A1 | Cites | United States of America | Search report |
| US20090319544A1 | Cites | United States of America | Search report |
| US20100042603A1 | Cites | United States of America | Applicant |
| US20100114642A1 | Cites | United States of America | Search report |
| US20100205266A1 | Cites | United States of America | Search report |
| US20100250511A1 | Cites | United States of America | Search report |
| US20110055544A1 | Cites | United States of America | Search report |
| US20110055826A1 | Cites | United States of America | Search report |
| US20110107300A1 | Cites | United States of America | Search report |
| US20120137138A1 | Cites | United States of America | Search report |
| US20120240236A1 | Cites | United States of America | Search report |
| US20120284111A1 | Cites | United States of America | Applicant |
| US20120330937A1 | Cites | United States of America | Applicant |
| US20130014006A1 | Cites | United States of America | Search report |
| US20130159867A1 | Cites | United States of America | Search report |
| US20130339932A1 | Cites | United States of America | Search report |
| NPL—Beginning Ubuntu Linux, Fifth Edition, The Complete Introduction to Ubuntu—Apress—Emilio Raggi, Keir Thomas, Trevor Parsons, Andy Channelle, Sander van Vugt, 2010—Chapter 20, pp. 415-442. | Non-patent | – | Search report |
| NPL—Beginning Ubuntu Linux From Novice to Professional, Kei Thomas; 2006—Chapter: 29, pp. 413-434. | Non-patent | – | Search report |
| The Waterfall Model in Large-Scale Development—Kai Petersen, Claes Wohlin, and Dejan Baca; Blekinge Institute of Technology, Ronneby, Sweden; Ericsson AB, Karlskrona, Sweden—F. Bomarius et al. (Eds.): PROFES 2009, LNBIP 32, pp. 386-400, 2009—Springer-Verlag Berlin Heidelberg 2009. | Non-patent | – | Search report |
| Integrating agile software development into stage-gate managed product development—Daniel Karlstro<?img id="CUSTOM-CHARACTER-00001" he="2.79mm" wi="2.12mm" file="US09507589-20161129-P00001.TIF" alt="custom character" img-content="character" img-format="tif" ?>m & Per Runeson—Empir Software Eng (2006)—Department of Communication Systems, Lund University, Box 118, SE-221 00 Lund, Sweden—Springer Science, Business Media, Inc. 2006. | Non-patent | – | Search report |
| Toward a distributed package management system—Fabien Dagnat, Gwendal Simon, Xu Zhang; Institut Telecom Telecom Bretagne, France—Lococo 2011: workshop on logics for component con<sub>—</sub>guration, Sep. 2011, Perugia, Italy. | Non-patent | – | Search report |
| Zhang et al., “Evaluation and Evolution of a Browse and Search Interface: Relation Browser ++”, In: Proceedings of the 2005 national conference on Digital government research, 2005, pp. 179-188. | Non-patent | – | Applicant |
| NPL-Beginning Ubuntu Linux, Fifth Edition, The Complete Introduction to Ubuntu-Apress-Emilio Raggi, Keir Thomas, Trevor Parsons, Andy Channelle, Sander van Vugt, 2010-Chapter 20, pp. 415-442. | Non-patent | – | Search report |
| NPL-Beginning Ubuntu Linux From Novice to Professional, Kei Thomas; 2006-Chapter: 29, pp. 413-434. | Non-patent | – | Search report |
| The Waterfall Model in Large-Scale Development-Kai Petersen, Claes Wohlin, and Dejan Baca; Blekinge Institute of Technology, Ronneby, Sweden; Ericsson AB, Karlskrona, Sweden-F. Bomarius et al. (Eds.): PROFES 2009, LNBIP 32, pp. 386-400, 2009-Springer-Verlag Berlin Heidelberg 2009. | Non-patent | – | Search report |
| Integrating agile software development into stage-gate managed product development-Daniel Karlstrom & Per Runeson-Empir Software Eng (2006)-Department of Communication Systems, Lund University, Box 118, SE-221 00 Lund, Sweden-Springer Science, Business Media, Inc. 2006. | Non-patent | – | Search report |
| Toward a distributed package management system-Fabien Dagnat, Gwendal Simon, Xu Zhang; Institut Telecom Telecom Bretagne, France-Lococo 2011: workshop on logics for component con-guration, Sep. 2011, Perugia, Italy. | Non-patent | – | Search report |
| Zhang et al., "Evaluation and Evolution of a Browse and Search Interface: Relation Browser ++", In: Proceedings of the 2005 national conference on Digital government research, 2005, pp. 179-188. | Non-patent | – | Applicant |
2 members in 1 office; this record represents the family
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 201314074263 | United States of America | A | |
| US201314074263 | – | – | – |
Members2
| Document | Office | Kind | |
|---|---|---|---|
| US2015127497A1 | United States of America | A1 | |
| US9507589B2This record | United States of America | B2 |
59 transactions on the USPTO file
Allowed after 2 non-final rejections, 1 final rejection and 1 RCE.
- Non-final rejections
- 2
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Post Issue Communication - Certificate of CorrectionN423 | N423 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Interview Summary - Applicant Initiated - TelephonicMEXAT | MEXAT | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| After Final Consideration Program Amendment too ExtensiveAFNE | AFNE | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| PILOT- Request for After Final Consideration ProgramRAFC | RAFC | |
| Response after Final ActionA.NE | A.NE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Close TICLTI | CLTI | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| FITF set to YES - revise initial settingFTFS | FTFS | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Application Is Now CompleteCOMP | COMP | |
| Sent to Classification ContractorPGPC | PGPC | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Cleared by OIPE CSRL194 | L194 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Patent Term Adjustment - Ready for ExaminationPTA.RFE | PTA.RFE | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Entity status set to undiscounted (initial default setting or status change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX |
10 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Maintenance fee paymentMAFP | MAFP | |
| Certificate of correctionCC | CC | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Notice of allowance and fees dueORIGINAL CODE: NOAZAAA | ZAAA | |
| Notice of allowance mailedORIGINAL CODE: MN/=.ZAAB | ZAAB | |
| AssignmentAS | AS |
Numbers
- Publication
- 09507589
- Publication, DOCDB
- 9507589
- Publication, EPODOC
- US9507589
- Application
- 14074263
- Application, DOCDB
- 201314074263
- Application, EPODOC
- US201314074263
Titles
- English
- Search based content inventory comparison
Patent term adjustment
- A delay
- +104 daysthe office missed an examination deadline
- Net adjustment
- 104 days
Classification
- CPC, 3
- G06F8/71
- G06F8/60
- G06Q10/087
- IPC, 2
- G06F9 44
- G06Q10 08
- USPC, 1
- 001001000