In the adequates view, a great help in data collection is the retrieval of additional information from the content behind a link, immediately after the link address has been entered in the Url text field and the user has made that text field unfocused by clicking elsewhere in the same modal window or by using the tab key to move to the next visual element. The title of the page behind the link is then automatically retrieved and the corresponding text field in the form is filled. At the same time, a sort of short description of the textual content of the page is generated, but not stored anywhere. The "sort of" here refers to the fact that this summary text and the mentioned page title have been retrieved using a third-party API, and it can not be given much more parameters than the desired length of the resulting summary text. This API is only free of charge up to a certain limit (per month). As this API tries to load the page it was given to load, it may happen that time passes and nothing special seems to happen, but this would be because the server behind the link does not respond in tens of seconds, but is not completely inaccessible either. When the information about the link is finally received, the processing of the rest of the links will continue.

In the text editing view, a great help in data collection is the retrieval of additional information from the content behind the link/id. This information is retrieved using an additional service, e.g. the service provided by the YouTube that outputs information in oEmbed format. A query returns structured (i.e. machine-readable) information, e.g. on the length, author and height in pixels of a video (in the case of an online video). Some of this information is not visible to the user at any point, but is used in other ways.