With this option, we can choose which will be the way to fetch de data when the import is made. Then comes the importer options that configure its behaviour. The first thing you need to provide is a name and a description of the importer, data that is simply a way of being able to easily know the importer's use: data for humans that has no impact on the importer's execution. On this page we will be able to see the following: Imports are created under Structure > Feeds Types > Add Feed Type (/admin/structure/feeds/add). news type content) and other configurations. Here we can specify the origin of the data (if it is a URL, a file, etc), the content to which they are going to be imported (e.g. It is the general configuration of an import. This is creating a FeedType, in Feeds jargon. Create an import configuration (Feed Type) The Feeds are under the content section because after all, they are a potential content. To reflect this separation we can see where Feeds puts the Feed Types and Feeds: the Feed Types are under the structure section, next to the content types, taxonomies, views or types of comments. In the end, all the data would be imported into the same content (for example, a match content). We could reuse the same configuration in different imports, one for each folder with the data of each city. One person per city would create the CSV and save it in a different folder so that each person works on their own file without interfering. In the previous example of petanque, let's imagine that the petanque league extends to more cities. This scheme allows us to use the same configuration for different sources, so we configure it once and use it in several imports. Once we have our import configuration, we must create a Feed itself, which is what really makes the import, using the Feed Type that we have previously created. The idea of Feeds is this: first, we must create an import configuration, Feed Type, which is the general configuration of how to import data, from what type of source, and where to put it. You can do this using Composer: cd /path/to/project With Feeds we could configure the import of data from these different sources to our website, with the advantage that if you modify the data in the original websites those changes will be transferred to our website. It could also be useful if we need to import public data from several websites to a new website. Feeds would periodically process that CSV, adding to our website the new games that have occurred, but it could also update previous games that have been modified (by an initial transcription error, because a player claim has been addressed, etc). Let's say someone collects the result of the games and saves it in a CSV file. For example, petanque in all public parks in a city. All the content is ready to import without any additional processing.įor example, imagine that our website shows information about the results of a sports competition.Several imports can be made from different files, URLs, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |