Endeca N value update to more human readable
up vote
0
down vote
favorite
currently we are using endeca for url and that contains N value . wanted to update that N value to something which is more human readable
Currently we have something like this
abc.com/clothing-mens/_/N-256Z1z141ur
but looking for something
abc.com/clothing-mens/shirt/
How can we do this in edneca to update this ?
atg endeca
asked Nov 12 at 20:29
Abhi
1
add a comment |
up vote
0
down vote
favorite
currently we are using endeca for url and that contains N value . wanted to update that N value to something which is more human readable
Currently we have something like this
abc.com/clothing-mens/_/N-256Z1z141ur
but looking for something
abc.com/clothing-mens/shirt/
How can we do this in edneca to update this ?
atg endeca
asked Nov 12 at 20:29
Abhi
1
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
currently we are using endeca for url and that contains N value . wanted to update that N value to something which is more human readable
Currently we have something like this
abc.com/clothing-mens/_/N-256Z1z141ur
but looking for something
abc.com/clothing-mens/shirt/
How can we do this in edneca to update this ?
atg endeca
asked Nov 12 at 20:29
Abhi
1
currently we are using endeca for url and that contains N value . wanted to update that N value to something which is more human readable
Currently we have something like this
abc.com/clothing-mens/_/N-256Z1z141ur
but looking for something
abc.com/clothing-mens/shirt/
How can we do this in edneca to update this ?
atg endeca
atg endeca
asked Nov 12 at 20:29
Abhi
1
asked Nov 12 at 20:29
Abhi
1
asked Nov 12 at 20:29
Abhi
1
asked Nov 12 at 20:29
Abhi
1
asked Nov 12 at 20:29
Abhi
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
The short answer is that you can't do anything in Endeca to solve this. Everything in Endeca is identified by a dimension value. So in the example you have here, the part in front of the /_/ has no literal meaning to the backend but rather gives you a view of what it should be from an SEO point of view. In fact the Base36 encoded value after the /_/ is the only part that really provides meaning to Endeca.
That said, there is something you can do to try and attempt to close the gap. Assuming you are using Endeca 11.2+ and CAS you can export the Dimension Value Id Mapping from CAS. You can then implement a dataloader to attach the dimension value for each category/product into the product catalog. The final step would be to then implement pipeline servlet to take the URL, find the dimension value from the database through a query and then do an internal lookup to Endeca for the actual page. If it isn't in the lookup table, simply pass to the servlet pipeline to resolve to any other page. One caveat to this approach is that it is extremely difficult to implement multiple facets (for example category and brand).
This is really a high level approach, that I have seen working but ultimately you have to ask yourself whether customers will really be trying to find products on the site using vanity URLs. If you use Endeca as a site search and navigation tool, chances are your products are already easy to find. Your vanity URLs only start to add value from an SEO point of view. Perhaps spend attention there.
answered Nov 19 at 16:02
radimpe
2,73412140
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53269632%2fendeca-n-value-update-to-more-human-readable%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
The short answer is that you can't do anything in Endeca to solve this. Everything in Endeca is identified by a dimension value. So in the example you have here, the part in front of the /_/ has no literal meaning to the backend but rather gives you a view of what it should be from an SEO point of view. In fact the Base36 encoded value after the /_/ is the only part that really provides meaning to Endeca.
That said, there is something you can do to try and attempt to close the gap. Assuming you are using Endeca 11.2+ and CAS you can export the Dimension Value Id Mapping from CAS. You can then implement a dataloader to attach the dimension value for each category/product into the product catalog. The final step would be to then implement pipeline servlet to take the URL, find the dimension value from the database through a query and then do an internal lookup to Endeca for the actual page. If it isn't in the lookup table, simply pass to the servlet pipeline to resolve to any other page. One caveat to this approach is that it is extremely difficult to implement multiple facets (for example category and brand).
This is really a high level approach, that I have seen working but ultimately you have to ask yourself whether customers will really be trying to find products on the site using vanity URLs. If you use Endeca as a site search and navigation tool, chances are your products are already easy to find. Your vanity URLs only start to add value from an SEO point of view. Perhaps spend attention there.
answered Nov 19 at 16:02
radimpe
2,73412140
add a comment |
up vote
1
down vote
The short answer is that you can't do anything in Endeca to solve this. Everything in Endeca is identified by a dimension value. So in the example you have here, the part in front of the /_/ has no literal meaning to the backend but rather gives you a view of what it should be from an SEO point of view. In fact the Base36 encoded value after the /_/ is the only part that really provides meaning to Endeca.
That said, there is something you can do to try and attempt to close the gap. Assuming you are using Endeca 11.2+ and CAS you can export the Dimension Value Id Mapping from CAS. You can then implement a dataloader to attach the dimension value for each category/product into the product catalog. The final step would be to then implement pipeline servlet to take the URL, find the dimension value from the database through a query and then do an internal lookup to Endeca for the actual page. If it isn't in the lookup table, simply pass to the servlet pipeline to resolve to any other page. One caveat to this approach is that it is extremely difficult to implement multiple facets (for example category and brand).
This is really a high level approach, that I have seen working but ultimately you have to ask yourself whether customers will really be trying to find products on the site using vanity URLs. If you use Endeca as a site search and navigation tool, chances are your products are already easy to find. Your vanity URLs only start to add value from an SEO point of view. Perhaps spend attention there.
answered Nov 19 at 16:02
radimpe
2,73412140
add a comment |
up vote
1
down vote
up vote
1
down vote
The short answer is that you can't do anything in Endeca to solve this. Everything in Endeca is identified by a dimension value. So in the example you have here, the part in front of the /_/ has no literal meaning to the backend but rather gives you a view of what it should be from an SEO point of view. In fact the Base36 encoded value after the /_/ is the only part that really provides meaning to Endeca.
That said, there is something you can do to try and attempt to close the gap. Assuming you are using Endeca 11.2+ and CAS you can export the Dimension Value Id Mapping from CAS. You can then implement a dataloader to attach the dimension value for each category/product into the product catalog. The final step would be to then implement pipeline servlet to take the URL, find the dimension value from the database through a query and then do an internal lookup to Endeca for the actual page. If it isn't in the lookup table, simply pass to the servlet pipeline to resolve to any other page. One caveat to this approach is that it is extremely difficult to implement multiple facets (for example category and brand).
This is really a high level approach, that I have seen working but ultimately you have to ask yourself whether customers will really be trying to find products on the site using vanity URLs. If you use Endeca as a site search and navigation tool, chances are your products are already easy to find. Your vanity URLs only start to add value from an SEO point of view. Perhaps spend attention there.
answered Nov 19 at 16:02
radimpe
2,73412140
The short answer is that you can't do anything in Endeca to solve this. Everything in Endeca is identified by a dimension value. So in the example you have here, the part in front of the /_/ has no literal meaning to the backend but rather gives you a view of what it should be from an SEO point of view. In fact the Base36 encoded value after the /_/ is the only part that really provides meaning to Endeca.
That said, there is something you can do to try and attempt to close the gap. Assuming you are using Endeca 11.2+ and CAS you can export the Dimension Value Id Mapping from CAS. You can then implement a dataloader to attach the dimension value for each category/product into the product catalog. The final step would be to then implement pipeline servlet to take the URL, find the dimension value from the database through a query and then do an internal lookup to Endeca for the actual page. If it isn't in the lookup table, simply pass to the servlet pipeline to resolve to any other page. One caveat to this approach is that it is extremely difficult to implement multiple facets (for example category and brand).
This is really a high level approach, that I have seen working but ultimately you have to ask yourself whether customers will really be trying to find products on the site using vanity URLs. If you use Endeca as a site search and navigation tool, chances are your products are already easy to find. Your vanity URLs only start to add value from an SEO point of view. Perhaps spend attention there.
answered Nov 19 at 16:02
radimpe
2,73412140
answered Nov 19 at 16:02
radimpe
2,73412140
answered Nov 19 at 16:02
radimpe
2,73412140
answered Nov 19 at 16:02
radimpe
2,73412140
2,73412140
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53269632%2fendeca-n-value-update-to-more-human-readable%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
