# Epic SSI-7 - Composition of file identifiers that satisfy existing file management plans

Project: Stream Storage Integrations
Status: in specification
URL: https://community.openproject.org/work_packages/SSI-7

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

Automatically naming attached or linked digital files (work package attachments or linked files within a file storage platform such as SharePoint).

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Votes |  |
| List |  |
| Target versions | Wish List |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Work packages, Administration, Administration / Custom fields |
| Enterprise plan | Enterprise / Premium (PRE) |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Wieland Lindenthal |
| Accountable | Wieland Lindenthal |
| Product manager |  |
| Designer | Marc Alcobé |
| Developers | OP Dev Titan Team |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

Large organizations usually have an established **file management plan** to organize their (physical) files. "Files" in the original sense are groups of documents. A **file identifier** is a label for such a group. A **file management plan** set clear rules on how file identifiers are composed. It shall unequivocally identify a group of documents and give clear indications where it belongs within the organization and/or where it is stored.

Usually a file identifier is composed of multiple segments that are concatenated to one character string. Each segment represents an organizational unit. An organizational unit could be a department, an industry, a business process, a category and other organizational concepts.

Organizations that use OpenProject often need to reference such (physical) files in order to allow tracking for real business processes ("This project or this work package belongs to...").

This EPIC allows OpenProject administrators to define a **file management plan** for an entire OpenProject instance and automatically assign a **file identifier** to a work package.

The **file identifier** of a work package can be composed by attributes of the project and of the work package itself.