The url content parser allows you to set a precedence score, so you can grab just one set of URLs if there are competing URL sets of varying quality.
I propose this be expanded to other types of content parsers, specifically the tags parser, although other content parsers could also potentially benefit from this.
To give an example of the intended use case: let's say you're writing a parser for a site in the style of Tumblr, X (Twitter), or similar where users can repost content posted by other users. You'd like your parser to be able to automatically grab the author of a post and add it as a creator tag, but you only want to tag the original poster, not the account which reposted it.
If the site doesn't offer a simple way to always grab the original poster (e.g. their API only returns an original_poster key/value pair on reposts, meaning you can't check for that pair on a link to an original post), it should still be possible to make it work through some complex setup with zipper formulas and string conversion or something, but it would make for simpler parser writing if you could have multiple tag parsers that can override each other like so:
| name |
produces |
| creator tag ("author") |
creator tag (priority 50) |
| creator tag ("original_poster", gets OP for reposts) |
creator tag (priority 75) |
The url content parser allows you to set a precedence score, so you can grab just one set of URLs if there are competing URL sets of varying quality.
I propose this be expanded to other types of content parsers, specifically the tags parser, although other content parsers could also potentially benefit from this.
To give an example of the intended use case: let's say you're writing a parser for a site in the style of Tumblr, X (Twitter), or similar where users can repost content posted by other users. You'd like your parser to be able to automatically grab the author of a post and add it as a
creatortag, but you only want to tag the original poster, not the account which reposted it.If the site doesn't offer a simple way to always grab the original poster (e.g. their API only returns an
original_posterkey/value pair on reposts, meaning you can't check for that pair on a link to an original post), it should still be possible to make it work through some complex setup with zipper formulas and string conversion or something, but it would make for simpler parser writing if you could have multiple tag parsers that can override each other like so: