Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

66%
+2 −0
Q&A automatic linking to a specific category, by title

I like this idea (obviously, clearly it is partly inspired by my post https://judaism.codidact.com/questions/276421 ). A bit of confusion though about "category", "post", etc. A category is a group...

posted 4y ago by manassehkatz‭  ·  edited 4y ago by manassehkatz‭

Answer
#2: Post edited by user avatar manassehkatz‭ · 2020-06-30T23:49:46Z (almost 4 years ago)
  • I like this idea (obviously, clearly it is partly inspired by my post https://judaism.codidact.com/questions/276421 ). A bit of confusion though about "category", "post", etc. A category is a group of posts (e.g,., Q&A or Meta or Recipes or Divrei Torah). I think as initially stated this would be limited to one Category, so if there were 2 within a given community (e.g., a Biography category in Judaism as well as Glossary (not saying we *need* Biography, but just a hypothetical example)) then it would be good to be able to disambiguate (and, I'd argue OK to *always* require, else back to "self" as explained below).
  • End result would be something like:
  • `[[glossary:muktzah]]` to link to the *muktzah* named post in the *glossary* category
  • `[[biography:rambam]]` to link to the *Rambam* named post in the *biography* category
  • `[[can-i-zoom-on-shabbos]]` to link to the *Can I Zoom on Shabbos* named post in the same (e.g., Q&A in this example) category.
  • Now this gets to another interesting problem - IDs vs. names. A StackExchange full link includes **both** the ID and the name. But only the ID is really necessary and, more importantly, the name can change. There are a couple of different ways to solve the problem *and keep things simple for non-techie users*:
  • * Names applied to posts in a "won't change so frequently" way. Normally names of posts are based on titles. Titles can be changed (and often are, for a lot of reasons). If I make the glossary post **muktzah** and someone else decides it must be **muktzeh** we can't have 23 links break. If the original **muktzah** is saved then it will always work (barring later duplicates). However, that would also require users making these links to know where/how to get that *static keyword*.
  • * When you create a link of this type, the system searches for a match and tries to piece it all together for you. This can work in the opposite way too - paste in a full Codidact link and it will flip it back to this new shortcut category:post format, *with the ID included*. In other words, enter in any of the following:
  • * `[[glossary:muktzah]]` Exact match of category + post title
  • * `[[glossary:muktzah]]` Close match - system searches and says "How about..."
  • * `[[654321]]` ID, which system knows is currently Glossary -> Muktzah
  • * `[[https://judaism.codidact.com/questions/654321]]` Full link pasted in, which system can now shorten.
  • and even:
  • * `https://judaism.codidact.com/questions/654321` The link by itself - system (I think SE does something similar) should be smart enough to *figure it out*.
  • All (after verification if not an exact match) would shorten to something like:
  • `[[glossary:654321:muktzah]]`
  • and all would display *as if they were*:
  • `[Muktzah](https://judaism.codidact.com/questions/654321)`
  • displaying just **Muktzah** in a link style.
  • I like this idea (obviously, clearly it is partly inspired by my post https://judaism.codidact.com/questions/276421 ). A bit of confusion though about "category", "post", etc. A category is a group of posts (e.g,., Q&A or Meta or Recipes or Divrei Torah). I think as initially stated this would be limited to one Category, so if there were 2 within a given community (e.g., a Biography category in Judaism as well as Glossary (not saying we *need* Biography, but just a hypothetical example)) then it would be good to be able to disambiguate (and, I'd argue OK to *always* require, else back to "self" as explained below).
  • End result would be something like:
  • `[[glossary:muktzah]]` to link to the *muktzah* named post in the *glossary* category
  • `[[biography:rambam]]` to link to the *Rambam* named post in the *biography* category
  • `[[can-i-zoom-on-shabbos]]` to link to the *Can I Zoom on Shabbos* named post in the same (e.g., Q&A in this example) category.
  • Now this gets to another interesting problem - IDs vs. names. A StackExchange full link includes **both** the ID and the name. But only the ID is really necessary and, more importantly, the name can change. There are a couple of different ways to solve the problem *and keep things simple for non-techie users*:
  • * Names applied to posts in a "won't change so frequently" way. Normally names of posts are based on titles. Titles can be changed (and often are, for a lot of reasons). If I make the glossary post **muktzah** and someone else decides it must be **muktzeh** we can't have 23 links break. If the original **muktzah** is saved then it will always work (barring later duplicates). However, that would also require users making these links to know where/how to get that *static keyword*.
  • * When you create a link of this type, the system searches for a match and tries to piece it all together for you. This can work in the opposite way too - paste in a full Codidact link and it will flip it back to this new shortcut category:post format, *with the ID included*. In other words, enter in any of the following:
  • * `[[glossary:muktzah]]` Exact match of category + post title
  • * `[[glossary:muktzeh]]` Close match - system searches and says "How about..."
  • * `[[654321]]` ID, which system knows is currently Glossary -> Muktzah
  • * `[[https://judaism.codidact.com/questions/654321]]` Full link pasted in, which system can now shorten.
  • and even:
  • * `https://judaism.codidact.com/questions/654321` The link by itself - system (I think SE does something similar) should be smart enough to *figure it out*.
  • All (after verification if not an exact match) would shorten to something like:
  • `[[glossary:654321:muktzah]]`
  • and all would display *as if they were*:
  • `[Muktzah](https://judaism.codidact.com/questions/654321)`
  • displaying just **Muktzah** in a link style.
#1: Initial revision by user avatar manassehkatz‭ · 2020-06-30T22:53:06Z (almost 4 years ago)
I like this idea (obviously, clearly it is partly inspired by my post https://judaism.codidact.com/questions/276421 ). A bit of confusion though about "category", "post", etc. A category is a group of posts (e.g,., Q&A or Meta or Recipes or Divrei Torah). I think as initially stated this would be limited to one Category, so if there were 2 within a given community (e.g., a Biography category in Judaism as well as Glossary (not saying we *need* Biography, but just a hypothetical example)) then it would be good to be able to disambiguate (and, I'd argue OK to *always* require, else back to "self" as explained below).

End result would be something like:
`[[glossary:muktzah]]` to link to the *muktzah* named post in the *glossary* category
`[[biography:rambam]]` to link to the *Rambam* named post in the *biography* category
`[[can-i-zoom-on-shabbos]]` to link to the *Can I Zoom on Shabbos* named post in the same (e.g., Q&A in this example) category.

Now this gets to another interesting problem - IDs vs. names. A StackExchange full link includes **both** the ID and the name. But only the ID is really necessary and, more importantly, the name can change. There are a couple of different ways to solve the problem *and keep things simple for non-techie users*:

* Names applied to posts in a "won't change so frequently" way. Normally names of posts are based on titles. Titles can be changed (and often are, for a lot of reasons). If I make the glossary post **muktzah** and someone else decides it must be **muktzeh** we can't have 23 links break. If the original **muktzah** is saved then it will always work (barring later duplicates). However, that would also require users making these links to know where/how to get that *static keyword*.

* When you create a link of this type, the system searches for a match and tries to piece it all together for you. This can work in the opposite way too - paste in a full Codidact link and it will flip it back to this new shortcut category:post format, *with the ID included*. In other words, enter in any of the following:

* `[[glossary:muktzah]]` Exact match of category + post title
* `[[glossary:muktzah]]` Close match - system searches and says "How about..."
* `[[654321]]` ID, which system knows is currently Glossary -> Muktzah
* `[[https://judaism.codidact.com/questions/654321]]` Full link pasted in, which system can now shorten.

and even:

* `https://judaism.codidact.com/questions/654321` The link by itself - system (I think SE does something similar) should be smart enough to *figure it out*.

All (after verification if not an exact match) would shorten to something like:

`[[glossary:654321:muktzah]]`
and all would display *as if they were*:
`[Muktzah](https://judaism.codidact.com/questions/654321)`
displaying just **Muktzah** in a link style.