Right now, in order to create a tag with the API, I create a temporary topic with the new tag, then delete the temporary topic. Is there a cleaner way?

I don’t know, but a slightly less painful solution would be to create a post in the staff category (where Assets for site design is) and just add the new tags there. The reason is that you want to create a bunch of tags so that users can use them in the future, but your community doesn’t yet have p…

Thanks @pfaffman . [Bild] pfaffman: I don’t know, but a slightly less painful solution would be to create a post in the staff category (where Assets for site design is) and just add the new tags there. You mean manually adding the new tag? Or is it possible to use the “Update a single topic” …

[Bild] jack2: I guess this would be a legit use case. But mine is less legit: I use tags to store metadata (object ids from an external app). Yeah, that’s not a good idea, especially if each tag is only used once. You should either have a separate database mapping the external IDs to Discour…

Since there is a legit use case, I believe adding a “new tag” API in the future would be a plus. I can feel the danger of using tags the way I do. But as I need to display, in Discourse, a list of the topics that relate to a specific external object, the “tags.show” route seems the only way…

Well, what are the external objects? How many topics will one get? will a topic relate to multiple of these things? You may be able to get away with using search.

The external objects are document subsections. One topic relates to one and only one subsection. A minimum guess is: 100 documents x 100 subsections per document = 10,000 subsections = 10,000 tags in a single Discourse instance. I know this is dangerous, but since I’m in the prototype phase, tags ar…

Consider not pre-creating that many topics - there’s often not much to discuss about the Bibliography. You can have a small service that takes a document & subsection ID and redirects you to either the existing topic or opens the composer pre-filled with the document link, subsection ID, etc. title…

Yes, I already have something like this. I don’t create the subsection tags beforehand when a document is created. I’ve changed the “tag not found” page of a subsection so that it looks like an empty topic list with a “New Topic” button at the top. When user clicks the button, I create the tag on th…

[Bild] jack2: Right now, in order to create a tag with the API, I create a temporary topic with the new tag, then delete the temporary topic. Is there a cleaner way? Yes there is: create a tag group populated with the tag you want to create (see the API here ).

The above method to create a tag with the API (by creating a tag group) has one drawback: it works only if you’re an admin.

[API] Cleaner way to create a tag?

Entwickler

syl 24. August 2020 um 18:52 12

Und noch eine weitere Möglichkeit, Tags mit der API zu erstellen (aber immer noch nur für Administratoren): die undokumentierte API /tags/upload.json, die vom Menü „Tags hochladen

Create dynamic Tag Group at topic level?

Thema		Antworten	Aufrufe
Discourse-tagging plugin customization Feature	1	947	8. April 2016
Moving from sub-categories to tags? Support	13	1516	10. Juni 2020
How do I add tags to a post created with the API? Support	4	2536	28. Februar 2020
How find tags id to add tags when create topic via API Support	5	1263	10. Juni 2020
How to add machine-generated tags to a post? Feature	2	873	28. Juni 2020

[API] Cleaner way to create a tag?

Verwandte Themen