You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
List of additional Regex's in configured websites to extract user-defined information, such as the author, publication date, etc.
Environment
When should this feature be enabled ? Which environments should support it ?
During importing a website. Supported for any configured website.
Motivation
Why do you want to see this feature ? What use cases does it support ? Approximately how big percent of user base do you think would use this feature ?
I often import information from the same websites, which is why I've set up some configured websites. However, these configs only let me extract the title and date, not any of the other relevant bits of context. Many people who use website configs would use this.
Documentation-type explanation
Open the configured website of choice
Click "Add context Regex (optional)"
Add a name
Define the Regex
Save
Import website, and see the new field in the context information (yay!)
Drawbacks
What potential issues should we consider ? Why should we not do this ?
I think this would fit quite naturally. Possible reasons would be overcomplication through too many features, and incompatibility with some parts expecting a fixed set of extracted context fields.
The text was updated successfully, but these errors were encountered:
Description
List of additional Regex's in configured websites to extract user-defined information, such as the author, publication date, etc.
Environment
When should this feature be enabled ? Which environments should support it ?
During importing a website. Supported for any configured website.
Motivation
Why do you want to see this feature ? What use cases does it support ? Approximately how big percent of user base do you think would use this feature ?
I often import information from the same websites, which is why I've set up some configured websites. However, these configs only let me extract the title and date, not any of the other relevant bits of context. Many people who use website configs would use this.
Documentation-type explanation
Drawbacks
What potential issues should we consider ? Why should we not do this ?
I think this would fit quite naturally. Possible reasons would be overcomplication through too many features, and incompatibility with some parts expecting a fixed set of extracted context fields.
The text was updated successfully, but these errors were encountered: