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

Support attachment categorization / tags? #31

Closed
Rad0van opened this issue Oct 20, 2020 · 11 comments
Closed

Support attachment categorization / tags? #31

Rad0van opened this issue Oct 20, 2020 · 11 comments
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@Rad0van
Copy link
Sponsor

Rad0van commented Oct 20, 2020

I would like to be able to categorize and/or tag attachments (primarily on products but more general approach is fine). The reason is there are many kinds of documents for products we sell like user manuals, technical manuals, schemas, guarantee certificates, other certificates... We'd need a flexible way to group/filter these to be able to quickly find what is needed. I'd also use it for filtering documents that should be displayed on website - some in shop, some in customer portal, ...

Currently reviewed PR #9 integrates ir.attachments into DMS which provides both categories and tags. However looking at the code the integration goes in opposite direction - DMS document points to ir.attachment not the opposite way around. The ideal outcome would be changed view on attachments, where one would at least see (edit optionally - but that could be done in DMS as it is currently) category and tags. So these would be available as attributes of the ir.attachment so they could be used elsewhere as well.

Is this feasible or stupid idea?

@etobella
Copy link
Member

Filtering there obviously needs to modify the widget in order to allow filters.

Another option would be to allow filtering of tags and so-on on #12

@pedrobaeza
Copy link
Member

First of all, if you decide to go to the attachment part, this should go to OCA/knowledge, not here. Second, I think you should improve the bidirectional way of the attachment integration instead of handling the attachment part that is harder.

@Rad0van
Copy link
Sponsor Author

Rad0van commented Oct 20, 2020

Filtering there obviously needs to modify the widget in order to allow filters.

Another option would be to allow filtering of tags and so-on on #12

Will have a look at that but it seems highly interesting.

@Rad0van
Copy link
Sponsor Author

Rad0van commented Oct 20, 2020

First of all, if you decide to go to the attachment part, this should go to OCA/knowledge, not here. Second, I think you should improve the bidirectional way of the attachment integration instead of handling the attachment part that is harder.

You mean to expose DMS attributes like category and tags as attributes of linked attachment? That would certainly be the first step.

@pedrobaeza
Copy link
Member

Well, I think all that work should go on DMS, and you only need to add a link from each product to DMS to show "related documents".

@Rad0van
Copy link
Sponsor Author

Rad0van commented Oct 20, 2020

Well, I think all that work should go on DMS, and you only need to add a link from each product to DMS to show "related documents".

Well I thought more in a way like to add many2one relation from ir.attachment to dms.file and thus in fact forming 1:1 relation and through that publish related category_id and tag_ids on ir.attachment. That way I could create a list view for attchmanets where I could filter, ... This would also work for attachments attached to any kind of object I guess.

@pedrobaeza
Copy link
Member

But why listing attachments? List documents...

@Rad0van
Copy link
Sponsor Author

Rad0van commented Oct 21, 2020

But why listing attachments? List documents...

Well you're probably right. I view from the point of view of current users who only know attachments now as a way to have some files related to objects. But I guess if DMS was used (esp. with #12 ) we could change their behavior to look at documents instead. Is that what you have in mind?

@pedrobaeza
Copy link
Member

Only with #24 and a link from chatter to related documents is enough IMO.

@Rad0van
Copy link
Sponsor Author

Rad0van commented Oct 21, 2020

Only with #24 and a link from chatter to related documents is enough IMO.

I'll add that to my queue of things to investigate and possibly work on. It's getting longer and longer. Thanx for hints.

@github-actions
Copy link

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Oct 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

4 participants
@pedrobaeza @Rad0van @etobella and others