XBRLmapper: Difference between revisions

From XBRLWiki
Jump to navigationJump to search
Line 12: Line 12:
# Automatic extraction of data from XBRL reports and data loading into different repositories
# Automatic extraction of data from XBRL reports and data loading into different repositories


Both products share a similar archtecture. Both are based on a common definition of data events connected with the XBRL side and specific drivers that attend the data events. This architecture has multiple advantages:
Both products share a similar architecture. Both are based on a common definition of data events connected with the XBRL side and specific drivers that attend the data events. This architecture has multiple advantages:


# Isolates the complexity of the XBRL Technology in one part (the data events). If the taxonomy changes the user may need to change just the connection between the events and the taxonomy or instance templates
# Isolates the complexity of the XBRL Technology in one part (the data events). If the taxonomy changes the user may need to change just the connection between the events and the taxonomy or instance templates

Revision as of 17:18, 28 June 2009

XBRLmapper WIKI

Product page

[XBRL Mapper product page]

Descripcion

XBRLmapper is a sofisticated tool that transfers data from information systems to XBRL reports and from XBRL reports to other systems. It supports then two different purposes:

  1. Automatic generation of XBRL reports from different data sources
  2. Automatic extraction of data from XBRL reports and data loading into different repositories

Both products share a similar architecture. Both are based on a common definition of data events connected with the XBRL side and specific drivers that attend the data events. This architecture has multiple advantages:

  1. Isolates the complexity of the XBRL Technology in one part (the data events). If the taxonomy changes the user may need to change just the connection between the events and the taxonomy or instance templates
  2. Isolates the complexity of the internal data repositories each one of the repositories may be accessed by an intantiation of a specific driver
  3. Each driver has his own configuration file that is specific for the data repository it is specialized
  4. The generation of an XBRL report may involve several drivers looking at data in different repositores simultaneously
  5. The same event could be potentially attended by more than one driver
  6. Multiple drivers of the same repository type can be used concurrently

The XBRL mapper is a software component that can be launched from a GUI or can be integrated in a workflow. The integration requires development of code (in Java or .NET)

Generating XBRL (Mapper)

The instance document template

Drivers

Moving XBRL data (Loader)

The definition of the loading events

Drivers

Navigate

Main Page