PHPackages                             visualmedia/data\_extract\_bundle - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. visualmedia/data\_extract\_bundle

ActiveLibrary[Utility & Helpers](/categories/utility)

visualmedia/data\_extract\_bundle
=================================

Symfony2 bundle that helps extending Bundles

1.0.2(10y ago)11.2kGPL-2.0PHPPHP >=5.4.0

Since Sep 17Pushed 10y ago1 watchersCompare

[ Source](https://github.com/visualmedianl/VisualMDataExtractBundle)[ Packagist](https://packagist.org/packages/visualmedia/data_extract_bundle)[ RSS](/packages/visualmedia-data-extract-bundle/feed)WikiDiscussions master Synced 1w ago

READMEChangelog (3)Dependencies (2)Versions (4)Used By (0)

Data Extract Bundle
===================

[](#data-extract-bundle)

Symfony2 Bundle to assist with (meta)data extraction from entities. Data can be extracted from Doctrine entities using annotations, data from other objects can be extracted using tagged services. When parsing entities and tagged services a dictionary is build that can be used to inform the user which data is available.

Author
------

[](#author)

This Symfony2 bundle is provided for free by [VisualMedia](http://www.visualmedia.nl) a dutch web development, web design and internet marketing company.

Feature overview
----------------

[](#feature-overview)

- Available data is configured using annotations
- Tagged service interface for extra (not annotated) data
- Dictionary with available data

Requirements
------------

[](#requirements)

- PHP 5.4+
- Symfony v2.4+
- Doctrine ORM v1.2+
- Doctrine Bundle v2.4+

Use Case
--------

[](#use-case)

The content in every application contains valuable information that can be used in (meta)tags, search indexers, etc. This information can be link within program code, but this prevents marketeers to use the information without stepping to a developer. Within our application we use an easy to use expression language that has access to the extracted data, enabling marketeers to create new and dynamic tags based on information contained in the application. The dictionary shows them which information is available.

Design considirations
---------------------

[](#design-considirations)

### No MetaData inheritance

[](#no-metadata-inheritance)

When scanning for available (meta)data only the entity classes are considered, this is by design and prevents unintentional inheritance for non relevant data. In the future a new annotation could be added that indicates how deep the system should scan for annotations

### Only annotations based

[](#only-annotations-based)

At the moment only annotations are used for providing meta(data) configuration, this is done becouse VisualMedia works with annotations for configuring columns, etc. XML and/or YAML configuration files could be implemented.

### No global (meta)data

[](#no-global-metadata)

The bundle only extracts (meta)data from objects and has no way to provide global (meta)data like an analytics code eg. This is by design as this is a whole new use case.

Installation
------------

[](#installation)

Add the following dependencies to your projects composer.json file:

```
"require": {
    # ..
    "visualmedia/data_extract_bundle": "~1.0"
    # ..
}

```

Enable VisualMDataExtractBundle in your AppKernel:

```