![]() Click “Save and Import.” If successful, you should see a message like “Successfully created 8 nodes” or similar. To import new content, simply Edit the appropriate XML feed, click “Remove” to change the target file, and then “Browse” to your volume’s corpus file (in your local RC-TEI repo). It does so according to the XPath mapping set in each feed type’s configuration, as described in the previous section. The XML feed simply parses the corpus file you created in the XML to HTML and Corpus Transformations documentation above. Instead, Edit each feed to change its import behavior for each volume.įollow the instructions below to execute the XML feeds import, then the HTML import. Note that if you click on the name of a feed, Drupal will take you to the feed page, which will only give you the option to re-run the same import or delete previously imported items. Though the order in which you execute the importers probably doesn’t matter, it seems like a best practice to begin with the XML import, which brings in many of the metadata fields for each node (identified by title), and then follow with the HTML import, which brings in the content fields (abstract, body, notes, etc.). Note that, from the main Feeds content page, two importers already exist for Praxis and Editions content, one “XML” and one “HTML.”īy using both the XML and HTML importers for a volume, we can import all its content and metadata into the Drupal database with only a few simple steps. Most of the time you’ll be (re)running a feed that already exists and pointing its fetcher to a different file or directory. To “run” a feeds importer, navigate to the “Feeds” tab of the admin “Content” menu. ![]() Once all production files are in the sFTP, you’re ready to (1) import the volume’s main content and then (2) clean it up. If you need to create a new importer or modify the behavior of an existing one, head over to the Feeds Importer page in the technical documentation. ![]() The present guide is concerned only with the importation of content in the production process using existing feeds importers. Unfortunately, this process is not perfect, as you’ll see below, but it does a pretty good job of getting content into the site. The importers allow this process to happen in a matter of seconds. The resulting importers allow the bulk importation of metadata and HTML content into the site this is important since manually producing, to take one example, each of the thousands of Southey letters for web presentation would take countless hours. These three modules work seamlessly together in Drupal’s backend to enable you to create/configure and then run an importer. RC’s Drupal site uses three separate contributed modules to facilitate the importation of fields into the Drupal database: Feeds, Feeds Extensible Parsers, and Feeds Tamper.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |