Feed tags #145

Closed
opened 5 years ago by jking · 2 comments
jking commented 5 years ago
Owner

Most of the prospective protocols which could be implemented in The Arsse (e.g. Google Reader, Fever, Feedbin, and more) use one-to-many mapping between feeds and tags (a.k.a. categories, groups, labels, etc.) rather than one-to-one mapping between feeds and folders. Therefore, the database would need to be able to store and manipulate these mappings for any of those protocols could be properly implemented.

Requirements include:

  • Identify tags by numeric ID or by their string, and perform any operation using either as a reference
  • Add, remove, and rename tags
  • Assign a feed to one or more tags
  • List tags for a feed, or feeds for one or more tags
  • List all tags, optionally suppressing tags with no members

The existing article label facilities for Tiny Tiny RSS will provide a starting point. However, ideally The Arsse should reconcile tags with top-level folders so that e.g. if a feed is moved to a folder in NCN or TTRSS, it automatically acquires an equivalent label for other protocols as well, and vice versa.

Most of the prospective protocols which could be implemented in The Arsse (e.g. Google Reader, Fever, Feedbin, and more) use one-to-many mapping between feeds and tags (a.k.a. categories, groups, labels, etc.) rather than one-to-one mapping between feeds and folders. Therefore, the database would need to be able to store and manipulate these mappings for any of those protocols could be properly implemented. Requirements include: - Identify tags by numeric ID or by their string, and perform any operation using either as a reference - Add, remove, and rename tags - Assign a feed to one or more tags - List tags for a feed, or feeds for one or more tags - List all tags, optionally suppressing tags with no members The existing article label facilities for Tiny Tiny RSS will provide a starting point. However, ideally The Arsse should reconcile tags with top-level folders so that e.g. if a feed is moved to a folder in NCN or TTRSS, it automatically acquires an equivalent label for other protocols as well, and vice versa.
jking added this to the Future milestone 5 years ago
jking added the
internals
label 5 years ago
Poster
Owner

It has been decided that tags and folders should not interact, as they are conceptually dissimilar and could in fact co-exist as parallel organizational tools.

It has been decided that tags and folders should not interact, as they are conceptually dissimilar and could in fact co-exist as parallel organizational tools.
jking modified the milestone from Future to 0.8.0 5 years ago
Poster
Owner

Implemented in back-end

Implemented in back-end
jking closed this issue 5 years ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.