mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #660] Feature Request: description/notes per entry? #1925
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#1925
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @adamwolf on GitHub (Mar 5, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/660
Type
What is the problem that your feature request solves
I need to remember why I added something :)
Describe the ideal specific solution you'd want, and whether it fits into any broader scope of changes
What are your thoughts on adding a description or notes field? Is this something you are really opposed to? Is this something other people are asking for? If I were to add it, would it be reasonable to add now vs after some changes in-flight?
What hacks or alternative solutions have you tried to solve the problem?
How badly do you want this new feature?
@pirate commented on GitHub (Mar 5, 2021):
I would not be opposed to adding it but I don't know how it's going to fit, we don't have much new column space available in the list views.
In general you may prefer a different tool like Archivy if you want more notes-centric archiving.
@adamwolf commented on GitHub (Mar 5, 2021):
Yeah, I get the spacing thing. Hmm. I'd personally be OK if it was only in
the detail view.
I'm currently abusing tags for this (and probably could keep doing that
forever).
On Fri, Mar 5, 2021 at 12:44 PM Nick Sweeting notifications@github.com
wrote:
@pirate commented on GitHub (Mar 5, 2021):
If you want to add a field and make it visible in the detail view only to start that's fine by me. We can figure out a way to squeeze in in the list views / elsewhere later.
@karlicoss commented on GitHub (Mar 27, 2021):
Wanted something similar, but at the
archivebox addtime (I have different 'sources', so would like to tag with a source). Is there something like that? From a quick look at the code looks that tags aren't exposed to the CLI, only in the web interface and some specific link extractors?@pirate commented on GitHub (Mar 27, 2021):
Yeah an
archivebox add --tag=tag1,tag2,tag3option is a great idea. I just added it to v0.6, as well as a form to the add page to add tags with URLs:fea0b89(#655)f3a3d76(#655)