The ability of handling side-results, which are typically generated in any experiment or simulation, is an important aspect to maximize knowledge gain from each individual activity. Our approach on this is to record a comprehensive number of parameters not only focusing on the data of primary interest. A strong interconnection between the various data, corresponding metadata, requests, and reports is crucial to allow for versatile entry points of data access. Unique identifiers corresponding each part of the data and timestamps showed to be very important for tracking the origin and sequence of results. Data lineage takes the collection of metadata one step further. This is not yet included in the current implementation of our MAP, as the full data lineage in the MAP cannot be provided by a central service. Full data lineage tracking requires each agent to provide the data lineage for its workflow and to report it to FINALES. In our framework, AiiDA, HELAO and Pipeline Pilot offer data lineage tracking functionalities. In the future, FINALES needs to keep track of data lineage during the overall workflow and needs to collect all the data lineage from the connected agents.