> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/package-and-tags-lookup.md).

# Package and Tags Lookup

## Description

The *Package and Tags Lookup* part allows you to retrieve a list of published packages in your application that are associated with selected tags. With project configuration and using the Package Installer you can associate tags to projects and published packages. Using this part, you can search for all packages with a particular tag. For example, this would allow you to give users the ability to answer questions that had tags associated with them. Your system could then display the packages the user should access based on related tags.

**Node Type:** This part is located in process nodes under the *Misc* dropdown menu.

**Used With:** This part can be used with all frameworks.

## Editor Fields

The *Package and Tags Lookup* part has the following fields.

| Field Name                                        | Description/Use                                                                                                                                                                                                                                                                                 | <p>Type/<br>Options</p> | <p>Optional/<br>Mandatory</p> |
| ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | ----------------------------- |
| Result                                            | This is the data object path in which the system stores the result.                                                                                                                                                                                                                             | Text                    | Mandatory                     |
| Data location                                     | <p>This is the location where the system finds the tags.<br>- <strong>Manual:</strong> You specify the search tag in the Tag Name field.<br>- <strong>Data-object:</strong> You load the search tags from a list in the context.</p>                                                            | Dropdown                | Mandatory                     |
| Tag prefix                                        | This is the search tag prefix. You can use this for searching for tags with the same prefix; for example, the tag *tissue.skin* has the prefix *tissue*.                                                                                                                                        | Text                    | Optional                      |
| Tag name                                          | If you select *Manual* in the *Data location* field the system displays this field. Enter the name of the search tag; for example, *tissue.skin*.                                                                                                                                               | Text                    | Mandatory                     |
| Tag Data-object                                   | If you select *Data-object* in the *Data location* field, the system displays this field. This data object allows you to enter one or more search tags; for example, (with prefix) “tissue.skin”, “tissue.bone”, “tissue.blood” or (without prefix) “skin”, “bone”, “blood”.                    | Text                    | Mandatory                     |
| <p>Filters<br>v8.1+</p>                           | <p>- <strong>Accessible for current user</strong>: when checked, the only packages returned by the lookup are those that the current user is authorized to use<br>- <strong>Has startcode</strong>: when checked, the only packages returned by the lookup are those possessing a startcode</p> | True \| False           | Optional                      |
| <p>Has parent package<br>v8.1+</p>                | Enter a parent package/framework name here to lookup only those packages that are based on the specified package/framework                                                                                                                                                                      | Text                    | Optional                      |
| <p>Merge settings of parent packages<br>v8.1+</p> | Return the package settings merged across all parent packages                                                                                                                                                                                                                                   | True \| False           | Optional                      |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/package-and-tags-lookup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.