With meta-data, we identify all data that surrounds a slide, but that is not graphical. The actual pixels (or viewport representation) of a slide are not meta-data. Annotations can be considered meta-data in the semantic sense, but they're link to graphical activities as well. So annotations are discussed elsewhere in this manual.
There is a blog article that serves as a complementary tutorial to this blog entry. In the article, we consider 3 types of meta-data in PMA.core:
| Meta-data | Location | Storage |
|---|---|---|
| Intrinsic meta-data | Embedded in the slide's file format | File system or cloud FS |
| User-captured meta-data | Stored in PMA.core | PMA.core RDBMS (SQLServer) |
| External meta-data | Stored in own (customer) database | SQLServer or Oracle |
This type of data can be consulted via the Image Management's left panel, or more directly via the API.
In the forms management section, data input forms can be designed that are subsequently assigned to virtual slides. These forms can then be filled in by the system's users while viewing slides. The data that users submit for each form are also available within this section.
No matter how powerful we make our own form management, we realize that there will always be external data silos that for any number of reasons are inconvenient to bring to PMA.core in their entirety.
That's why we provide the option to establish links to external databases systems in a two-step fashion:
* first, you define the link to the resource (via a connectionstring). In PMA.core 2 this can be a SQLServer or Oracle RDBMS. * second, you define a query that retrieves the data from the RDBMS, and identify a way so that individual records can be mapped back to specific filenames.