Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Source URL separate field #424

Closed
jt196 opened this issue Feb 19, 2021 · 7 comments
Closed

Source URL separate field #424

jt196 opened this issue Feb 19, 2021 · 7 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@jt196
Copy link

jt196 commented Feb 19, 2021

Is your feature request related to a problem? Please describe.
Paprika has a separate field for the source URL, it would be nice to have something like this. Current behaviour is to add the source URL to the instructions text.

Describe the solution you'd like
Add a separate source URL field that is populated when importing from a website.

Additional context
Further down the road, this separation of data could be quite helpful in creating lists populated by recipes from different sites.

In addition to the Source URL, Paprika has a 'source' field as well. I use this to add a more descriptive name to the source, or if the recipe has come from a book, I'll write the author name/title of the book here.

@jt196 jt196 added the enhancement New feature or request label Feb 19, 2021
@vabene1111
Copy link
Collaborator

interesting idea, i think many recipe managers do this. Should be easy to add

@vabene1111
Copy link
Collaborator

#668

@mhoenes
Copy link

mhoenes commented Nov 28, 2021

In addition to a source URL field, it would be nice to have 2 more dedicated source fields for:

  • the offline source (book/magazine/tv show etc.).
  • the author/chef (although this could probably also be achieved by creating a tag hierarchy).

Ideally, those fields would be searchable.

@vabene1111
Copy link
Collaborator

i think both of these use cases could very well be solved by tags dont you ? this would also make it super easy to search and its even a very logical approach. But i will look into it when adding the source field.

@mhoenes
Copy link

mhoenes commented Dec 1, 2021

The author/chef use case works pretty well for me with tags. I tried it.
For the offline source, I feel the possible values would be too numerous. Creating a tag for every single one might become tedious.

For both use cases, in the end, it comes down to how many different values one wants to manage. To a certain extent, tags are very well feasible.

@smilerz
Copy link
Collaborator

smilerz commented Dec 1, 2021

@mhoenes I'd consider using hierarchical tags for your offline sources.
TV
-TV Show 1
--Espisode 123
-TV Show 2

You can manage tags for the things you care about (some shows you want to keep track of, others can just get dropped into TV) Much depends on how much data you want to maintain and how you want to search/discover your recipes.

image

@vabene1111
Copy link
Collaborator

source field is imported with the new importer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

4 participants