mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #247] Architecture: Support organizing archived links with folders or tags #171
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#171
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 @rayrrr on GitHub (Jun 22, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/247
I am migrating from another software that allowed me to create persistent folders and subfolders of my archived links in the UI for organizational purposes. I would like that same functionality in ArchiveBox.
Ideally, I would like the UI to have a feature allowing folder creation and drag-and-drop placement of archived links into folders.
It would also be wonderful if ArchiveBox could preserve the folder structure of imported/synced browser bookmarks.
I know this project already uses timestamp-based folders for archiving during import; this new feature does not have to conflict with that. Rather, the "folders" for this feature can be "logical" organization using tags or the like, which ArchiveBox understands well enough to display the links in an organized manner. This way, the timestamp-based filesystem folder architecture could stay the same.
@MAX10541 commented on GitHub (Jun 15, 2020):
Any updates on this?
As far as I see, ArchiveBox does support adding tags from some sources (but not all).
However, it seems like it stops right there: editing/adding/removing tags is almost impossible, and there is no real use for tags other than displaying them next to the titles.
For now, I've written a small bash function that writes my new links with tags to a temp file using a specific format (that ArchiveBox understands), and then use that file as an input to ArchiveBox.
I'd love to contribute to this in any possible way, but I need to know if there are any current or future plans regarding this first :)
@pirate commented on GitHub (Jun 15, 2020):
You're right that they're not exactly easy to use ;) They were initially added as an afterthought because the Pocket export format I was parsing included them (even though I personally didn't use them).
Luckily tags become a first-class-citizen in archivebox >v0.4, with their own database field that can be queried, filtered, edited, etc.
If you want to check out the model you can look on the
djangobranch at thearchivebox/core/models.pyfile. Currently, it's just a CSV field, but it's easy to query with.filter(tags__icontains='sometag'). They are editable in the UI as well in the new Django admin interface for links, but I don't yet have a nice UI to display them or filter them on the homepage.One part that would be useful is an integration with DataTable's built-in filtering mechanism. If someone could connect the backend tags to DataTable's filter system in the frontend that would be very helpful (as a PR on the
djangobranch, but discuss your potential approach here first before writing any code). Keep in mind pagination is still WIP, so we will have to move the filtering to the backend once pagination is implemented, see #312.@cdvv7788 commented on GitHub (Oct 12, 2020):
We are refactoring this to use a proper
Tagmodel. It should be available soon.@mcrosson commented on GitHub (Jan 11, 2021):
Any updates on this?
@pirate commented on GitHub (Jan 11, 2021):
As of 0.4.24 we have Tags stored in a separate model with filter options based on tags in the Admin UI.
I'm leaving this issue open to track future additions to the tagging feature like nested tags / better filter options / etc.
@mcrosson commented on GitHub (Jan 11, 2021):
@pirate commented on GitHub (Jan 11, 2021):
@pirate commented on GitHub (Apr 6, 2021):
Tags have been around for a few versions at this point so I'm going to close this out. If there are any more feature requests related to tagging please open new issues for them :)
I don't think we'll natively support hierarchical tags anytime soon, but you can use slashes or dashes to indicate categories in your tag names
somecategory/somesubcategory/sometag(similar to how gmail tagging works).