[{"_1":2,"_154":-5,"_155":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_133":134},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_124":-5,"_125":11,"_126":17,"_127":11,"_128":-5,"_129":11,"_130":-5,"_131":132},"canonicalUrl","https://hub.docker.com/r/smtx/portia/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","smtx","reponame","portia","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":-5,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":17,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2015-07-22T14:01:29.842644Z","description","","is_private","last_updated","2015-07-22T14:55:54.805345Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.distribution.manifest.v1+prettyjws","name","pull_count",281,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","Portia\n======\n\nPortia is a tool that allows you to visually scrape websites without any programming knowledge required. With Portia you can annotate a web page to identify the data you wish to extract, and Portia will understand based on these annotations how to scrape data from similar pages.\n\nAnatomy of a Portia Project\n---------------------------\n\nA project in Portia generally consists of one or more spiders.\n\n### Spider\n\nA spider is a crawler for a particular website. The configuration of a spider is split into three sections:\n\n* **Initialization**\n* **Crawling**\n* **Extraction**\n\nThe **Initialization** section is used to set up the spider when it's first launched. Here you can define the start URLs and login credentials.\n\nThe **Crawling** section is used to configure how the spider will behave when it encounters URLs. You can choose how links are followed and whether to respect [nofollow](http://en.wikipedia.org/wiki/nofollow). You can visualise the effects of the crawling rules using the **Overlay blocked links** option; this will highlight links that will be followed in green, and links that won't be followed in red.\n\nThe **Extraction** section lists the templates for this spider.\n\n### Templates\n\nWhen the crawler visits a page, the page is matched against each template and templates with more annotations take precedence over those with less. If the page matches a template, data will be extracted using the template's annotations to yield an item (assuming all required fields are filled). Templates exist within the context of a spider and are made up of annotations which define the elements you wish to extract from a page. Within the template you define the item you want to extract as well as mark any fields that are required for that item.\n\n![Field extractors](docs/_static/portia-extractors.png)\n\nYou can also add extractors to item fields. Extractors allow you to further refine information extracted from a page using either regexes or a predefined type. For example, let's say there's an element on the page that contains a phone number, but it also contains some other text that you don't need. You could use a regular expression that matches phone numbers and add it as an extractor to the relevant field; upon extracting that field only the phone number would be stored.\n\nYou may need to use more than one template even if you're only extracting a single item type. For example, an e-commerce site may have a different layout for books than it does for audio CDs, so you would need to create a template for each layout. See [Tips for Working with Multiple Templates](#tips-for-working-with-multiple-templates) for more info.\n\n### Annotations\n\n![Creating an annotation](docs/_static/portia-annotation-creation.png)\n\nAn annotation defines the location of a piece of data on the web page and how it should be used by the spider. Typically an annotation maps some element on the page to a particular field of an item, but there is also the option to mark the data as being required without storing the data in an item. It's possible to map attributes of a particular element instead of the content if this is required, for example you can map the ``href`` attribute of an anchor link rather than the text.\n\n### Items\n\nAn item refers to a single item of data scraped from the target website. A common example of an item would be a product for sale on an e-commerce website. It's important to differentiate **item** and **item definition**; in Portia an item definition or item type refers to the schema of an item rather than the item itself. For example, ``book`` would be an item definition, and a specific book scraped from the website would be an item. An item definition consists of multiple fields, so using the example of a product you might have fields named ``name``, ``price``, ``manufacturer`` and so on. Annotations are used to extract data from the page into each of these fields.\n\nIf you want to ensure that certain fields are extracted for an item, you can set the **Required** flag on a field which will discard an item if the field is missing. Duplicate items are removed by default. In some cases you may have fields where the value can vary despite being the same item, in which case you can mark them as **Vary** which will ignore the field when checking for duplicates. It’s important to only use **Vary** when necessary, as misuse could easily lead to duplicate items being stored. The ``url`` field is a good example of where **Vary** is useful, as the same item may have multiple URLs. If the ``url`` field wasn’t marked as **Vary** each duplicate item would be seen as unique because its URL would be different.\n\n### Field Types\n\nSetting a field's type will ensure the field will only match certain types of data. The following field types are available:\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n

text	Plain text. Any markup is stripped and text within nested elements is also extracted.
number	A numeric value e.g. 7, 9.59
image	An image URL. In most cases you will want to map an ``img`` element's ``src`` attribute.
price	The same as ``number``, a numeric value.
raw html	Non-sanitized HTML.
safe html	Sanitized HTML. See below for more details.
geopoint	The same as ``text``.
url	A URL.
date	A date value parsed by [dateparser](https://github.com/scrapinghub/dateparser). This won't work if the annotated element includes non-date text, in which case you should use partial annotations.

\n\nThe ``safe html`` field type keeps the following elements: ``br``, ``p``, ``big``, ``em``, ``small``, ``strong``, ``sub``, ``sup``, ``ins``, ``del``, ``code``, ``kbd``, ``samp``, ``tt``, ``var``, ``pre``, ``listing``, ``plaintext``, ``abbr``, ``acronym``, ``address``, ``bdo``, ``blockquote``, ``q``, ``cite``, ``dfn``, ``table``, ``tr``, ``th``, ``td``, ``tbody``, ``ul``, ``ol``, ``li``, ``dl``, ``dd``, ``dt``.\n\nAll other elements are discarded, with the exception of header tags (`h1`, `h2` ... `h6`) and `b` which are replaced with `strong`, and `i` which is replaced with `em`. Whitelisted elements contained within non-whitelisted elements will still be retained, with the exception of elements contained within a `script`, `img` or `input` element. For example,``

example

`` would extract to ``example``, whereas ```` would be discarded completely.\n\nCreating a Portia Project\n-------------------------\n\nTo create a new project, begin by entering the site's URL in the navigation bar at the top of the page and clicking ``Start``. Portia can be used as a web browser, and you can navigate to pages you want to extract data from and create templates for them. Clicking ``Start`` should create a new project along with a spider for the website, and you should see the loaded web page:\n\n![Newly created project](docs/_static/portia-new-project.png)\n\nThe spider can be configured on the right. The start pages are the URLs the spider will visit when beginning a new crawl. Portia can be used as a web browser, and you can navigate to the pages you want to extract data from and create new templates. To define the data you wish to extract from the page, click the ``Annotate this page`` button, which will create a new template and allow you to annotate the page.\n\n![Annotating the page](docs/_static/portia-annotation.png)\n\nYou will now be able to define annotations by highlighting or clicking elements on the page. When annotating, a context menu will appear allowing you to map an element's attribute or content to a particular item field. Should you want to add a new item field without having to go into the item editor, you can use the ``-create new-`` option in the field drop down to create a new field. If you want to mark an element as having to exist on the page without storing its data, you can select ``-just required-`` instead of a field. It's important to note when using ``-just required-``, only the existence of the element will be checked rather than its content.\n\n![Items editor](docs/_static/portia-item-editor.png)\n\nOnce you are finished annotating, you can then mark any fields that are required by going into the item editor under ``Extracted item``. As mentioned earlier, if the item appears in several locations and some fields differ despite being the same item, you can also tick ``Vary`` on any relevant fields to exclude them from being used to detect duplicate items.\n\n![Extracted items will be shown on the page](docs/_static/portia-extracted-items.png)\n\nYou can now confirm that your template works by clicking ``Continue browsing``. The page should reload and a pop-up should appear showing you the items extracted from the page. When visiting a page in Portia, the whole extraction process is performed with the spider with the set of currently defined templates. This allows you to check that data will be extracted from the page before running the spider against the whole website.\n\nIf you have created a template around one page where the data extracts successfully, but you visit a similar page and no item is extracted, then it's likely that particular page has a different layout or some fields missing. In this case you would simply click ``Annotate this page`` again to create a new template for the page, and then annotate it the same way you had done with the other page. See [Tips for Working with Multiple Templates](#tips-for-working-with-multiple-templates) for more details on how multiple templates are used within a single spider.\n\nOnce you've confirmed that your spider works and extracts data properly, your project is now ready to [run](#running-portia) or [deploy](#deploying-a-project).\n\nAdvanced Use of Annotations\n---------------------------\n\n### Multiple Fields\n\nIt's possible to extract multiple fields using a single annotation if there are several properties you want to extract from an element. For example, if there was an anchor link on the page, you could map the ``href`` attribute containing the URL to one field, and you could map the text to another. You can view a particular annotation's settings by either clicking the cog in the annotation pop-up window or by clicking the cog beside the annotation in the ``Annotations`` section of the template configuration. Within this context there is an ``Attribute mappings`` section where you can define additional mappings for the selected annotation should you want to map other attributes.\n\n### Variants\n\nIt’s common for there to be a single item with a number of variations e.g. different sizes such as small, medium and large. It’s likely that each variation will have its own annotation for one or more fields and you want to keep each variation’s value. In situations like this you can use variants to make sure each value is stored. Each annotation you define has a variant selected, the default being ``Base`` referring to the base item. To assign an annotation to a variant, you simply select the variant you want the annotation to use in its options or under the ``Annotations`` section in the template settings.\n\nConsider the following scenario where variants would be useful:\n\nYou are wanting to scrape an e-commerce website that sells beds, and some beds come in multiple sizes e.g. ``Single``, ``Double``, ``Queen``, ``King``. The product page for each bed has a table of prices for each size, like so:\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n

Single	$300
Double	$500
Queen	$650
King	$800

\n\nThe rest of the data you want to extract (product name, description etc.) is common across all sizes. In this case, you would annotate the common data to the base item and create the fields ``size`` and ``price``. You would then annotate the ``Single`` cell as variant 1 of ``size``, and the ``$300`` cell as variant 1 of ``price``, followed by annotating ``Double`` as variant 2 of ``size``, ``$500`` as variant 2 of ``price`` and so on. It's worth noting that in this case, it wouldn't be necessary to create a variant for each row; usually it is enough to annotate only the first and last row of the table as Portia will automatically create variants for rows in between.\n\n### Partial Annotations\n\nPartial annotations can be used to extract some part of text which exists as part of a common pattern. For example, if an element contained the text ``Price: $5.00``, you could highlight the ``5.00`` part and map it to a field. The ``Price: $`` part would be matched but removed before extracting the field. In order to create a partial annotation, all you need to do is highlight the text the way you would normally, by clicking and dragging the mouse. The annotation window will pop up and you will be able to map it to a field the same way you would with a normal annotation.\n\nThere are some limitations to partial annotations. As mentioned in the previous paragraph, the text must be part of a pattern. For example, let's say an element contains the following text:\n\n Veris in temporibus sub Aprilis idibus habuit concilium Romarici montium\n\nOne of the pages visited by the crawler contains the following text in the same element:\n\n Cui dono lepidum novum libellum arido modo pumice expolitum?\n\nIf you had annotated ``Aprilis`` in the template, nothing would have matched because the surrounding text differs from the content being matched against. However, if the following text had instead appeared in the same element:\n\n Veris in temporibus sub Januarii idibus habuit concilium Romarici montium\n\nThe word ``Januarii`` would have been extracted, because its surrounding text matches the text surrounding the text that was annotated in the template.\n\nTips for Working with Multiple Templates\n----------------------------------------\n\nIt's often necessary to use multiple templates within one spider, even if you're only extracting one item type. Some pages containing the same item type may have a different layout or fields missing, and you will need to accommodate those pages by creating a template for each layout variation.\n\nThe more annotations a template has, the more specific the data being extracted and therefore less chance of a false positive. For this reason, templates with more annotations take precedence over those with less annotations. If a subset of templates contains equal number of annotations per template, then within that subset templates will be tried in the order they were created from first to last. In other words, templates are tried sequentially in order of number of annotations first, and age second.\n\nIf you are working with a large number of templates, it may be difficult to ensure the correct template is applied to the right page. It's best to keep templates as strict as possible to avoid any false matches. It's useful to take advantage of the ``-just required-`` option and annotate elements that will always appear on matching pages to reduce the number of false positives.\n\nConsider the following example:\n\nWe have an item type with the fields ``name``, ``price``, ``description`` and ``manufacturer``, where ``name`` and ``price`` are required fields. We have create a template with annotations for each of those fields. Upon running the spider, many items are correctly scraped; however, there are a large number of items where the manufacturer field contains the description, and the description field is empty. This has been caused by some pages having a different layout:\n\nLayout A:\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n

name	price
manufacturer
description

\n\nLayout B:\n\n\n \n \n \n \n \n \n \n \n \n

name	price
description

\n\nAs you can see, the problem lies with the fact that in layout B the description is where manufacturer would be, and with ``description`` not being a required field it means that the template created for layout A will match layout B. Creating a new template for layout B won't be enough to fix the problem, as layout A's template would contain more annotation and be matched against first.\n\nInstead we need to modify layout A's template, and mark the ``description`` annotation as **Required**. With this added constraint, items displayed with layout B will not be matched against with layout A's template due to the missing ``description`` field, so the spider will proceed onto layout B's template which will extract the data successfully.\n\nRunning Portia\n--------------\n\n### Running Portia with Vagrant (Recommended)\n\nCheckout the repository:\n\n git clone https://github.com/scrapinghub/portia\n\nYou will need both [Vagrant](http://www.vagrantup.com/downloads.html) and [VirtualBox](https://www.virtualbox.org/wiki/Downloads) installed.\n\nRun the following in Portia's directory:\n\n vagrant up\n\nThis will launch a Ubuntu virtual machine, build Portia and start the ``slyd`` server. You'll then be able to access Portia at ``http://localhost:8000/static/index.html``. You can stop the ``slyd`` server using ``vagrant suspend`` or ``vagrant halt``. To run ``portiacrawl`` you will need to SSH into the virtual machine by running ``vagrant ssh``.\n\n### Running Portia Locally\n\nIf you would like to run Portia locally you should create an environment with virtualenv:\n\n virtualenv YOUR_ENV_NAME --no-site-packages\n source YOUR_ENV_NAME/bin/activate\n cd ENV_NAME\n\nNow clone this repository into that env:\n\n git clone https://github.com/scrapinghub/portia.git\n\nand inside this env install the required packages:\n\n cd portia\n pip install -r requirements.txt\n pip install -e ./slybot\n\nTo run Portia start slyd:\n\n cd slyd\n twistd -n slyd\n\nPortia should now be running on port 9001 and you can access it at: ``http://localhost:9001/static/index.html``\n\n###### Missing Dependencies on Linux\n\nWhen running Portia on Ubuntu or Debian systems you may need to install the following dependencies:\n\n sudo apt-get install libxml2-dev libxslt-dev python-dev zlib1g-dev libffi-dev libssl-dev\n\n### Running Portia with Docker\n\nCheckout the repository:\n\n git clone https://github.com/scrapinghub/portia\n\nIf you are on a Linux machine you will need [Docker](https://docs.docker.com/installation/) installed or if you are using a [Windows](https://docs.docker.com/installation/windows/) or [Mac OS X](https://docs.docker.com/installation/mac/) machine you will need [boot2docker](http://boot2docker.io/).\n\nAfter following the appropriate instructions above the Portia image can be built using the command below:\n\n docker build -t portia .\n\nPortia can be run using the command below:\n\n docker run -i -t --rm\n -v /data:/app/slyd/data:rw \\\n -p 9001:9001 \\\n --name portia \\\n portia\n\nPortia will now be running on port 9001 and you can access it at: ``http://localhost:9001/static/index.html``\nProjects will be stored in the project folder that you mount to docker.\n\nTo run `portiacrawl` add `/app/slybot/bin/portiacrawl [SPIDER] [OPTIONS]` to the command above.\n\n:warning: `For Windows the path must be of the form /`\n\n### Running a Portia Spider\n\nProjects you have created in Portia will reside in ``slyd/data/projects``. You can use ``portiacrawl`` to run a spider from one of your projects:\n\n portiacrawl PROJECT_PATH SPIDER_NAME\n\nwhere ``PROJECT_PATH`` is the path of the project and ``SPIDER_NAME`` is a spider that exists within that project. You can list the spiders for a project with the following:\n\n portiacrawl PROJECT_PATH\n\nPortia spiders are ultimately [Scrapy](http://scrapy.org/) spiders. You can pass Scrapy arguments when running with ``portiacrawl`` using the ``-a`` option. You can also specify a custom settings module using the ``--settings`` option. The [Scrapy documentation](http://doc.scrapy.org/en/latest) contains full details on available options and settings.\n\nDeploying a Project\n-------------------\n\nPortia projects can be deployed using [Scrapyd](http://scrapyd.readthedocs.org/en/latest). You can deploy a Portia project by going into ``slyd/data/projects/PROJECT_NAME`` and adding your target to ``scrapy.cfg``. You can then run ``scrapyd-deploy`` to deploy your project using the default deploy target, or specify a target and project using the following:\n\n scrapyd-deploy your_scrapyd_target -p project_name\n\nand then schedule your spider with:\n\n curl http://your_scrapyd_host:6800/schedule.json -d project=your_project_name -d spider=your_spider_name\n\n:warning: `Running scrapyd from your project directory will cause deployment to fail`\n\nAdditional Features\n-------------------\n\n### Git backend for projects\n\nVersioning for projects can be enabled by creating a `local_settings.py` file in `slyd/slyd` with the contents below:\n\n import os\n SPEC_FACTORY = {\n 'PROJECT_SPEC': 'slyd.gitstorage.projectspec.ProjectSpec',\n 'PROJECT_MANAGER': 'slyd.gitstorage.projects.ProjectsManager',\n 'PARAMS': {\n 'storage_backend': 'dulwich.fsrepo.FsRepo',\n 'location': os.environ.get('PORTIA_DATA_DIR', SPEC_DATA_DIR)\n },\n 'CAPABILITIES': {\n 'version_control': True,\n 'create_projects': True,\n 'delete_projects': True,\n 'rename_projects': True\n }\n }\n\n### MySQL backend for projects\n\nA MySQL backend can be used by adding a `local_settings.py` file in `slyd/slyd` with the contents below:\n\n import os\n SPEC_FACTORY = {\n 'PROJECT_SPEC': 'slyd.gitstorage.projectspec.ProjectSpec',\n 'PROJECT_MANAGER': 'slyd.gitstorage.projects.ProjectsManager',\n 'PARAMS': {\n 'storage_backend': 'dulwich.mysqlrepo.MysqlRepo',\n 'location': os.environ.get('DB_URL'),\n },\n 'CAPABILITIES': {\n 'version_control': True,\n 'create_projects': True,\n 'delete_projects': True,\n 'rename_projects': True\n }\n }\n\nThis will store versioned projects as blobs within the MySQL database that you specify by setting the environment variable below:\n\n DB_URL = mysql://:@:/\n\nWhen this env variable is set the database can be initialized by running the `bin/init_mysqldb` script.\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",442208605,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},"content_type","creator",17647,"digest","sha256:d9171000f6bbe132d13f4092a098bd4e8687350ebf4d43ab4ce46a9f6f6230d2","full_size",245824103,"id",603601,"images",[99],{"_100":101,"_91":92,"_102":44,"_103":104,"_105":106,"_107":44,"_108":44,"_109":-5,"_110":111,"_59":62,"_112":-5},"architecture","amd64","features","last_pulled","2026-09-18T20:15:23.599260854Z","last_pushed","2015-07-22T14:41:31Z","os","os_features","os_version","size",245824391,"variant","2015-07-22T14:41:32Z","last_updater","last_updater_username","media_type","latest","repository",262924,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":135,"_142":143,"_131":152,"_153":11},{"_36":136,"_38":137,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":138,"_53":31,"_28":29,"_54":55,"_56":-5,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":139,"_75":17,"_76":141,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":140},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_144":60,"_145":-5,"_146":-5,"_147":148},"count","next","previous","results",[149],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_97":150,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},[151],{"_100":101,"_91":92,"_102":44,"_103":104,"_105":106,"_107":44,"_108":44,"_109":-5,"_110":111,"_59":62,"_112":-5},[],"canDeleteTags","actionData","errors"]

smtx/portia

Tags for smtx/portia