8000 Importing same web page twice should give error or warning · Issue #607 · LuteOrg/lute-v3 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Importing same web page twice should give error or warning #607

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.

Sign up for GitHub

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

Jump to bottom
Open
tbm opened this issue Apr 10, 2025 · A186 1 comment
Open

Importing same web page twice should give error or warning #607

tbm opened this issue Apr 10, 2025 · 1 comment

Comments

@tbm
Copy link
tbm commented Apr 10, 2025

Is your feature request related to a problem? Please describe.

  • I import news articles from BBC Swahili
  • I might forgot what I imported already
  • I might import an article that I already imported before

Describe the solution you'd like

If a book already exists with the same Source URI you're trying to add, the import web page should give an error or at least a warning and show information about the book you already have in your collection.
@jzohrab
Copy link
Collaborator
jzohrab commented Apr 11, 2025

Is this really an issue? You'd just have the same article twice, and maybe you want to re-read it :-)

But sure, if the source URI already exists, it could show a message. The check could be done when the page is initially imported into the book form, and the message shown then, as you've mentioned, e.g., "You've already imported the article from : - you can still re-import it if you wish." or something like that.

Cheers @tbm, thanks!

@jzohrab jzohrab added this to Lute-v3 Apr 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Lute-v3
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tbm @jzohrab
0