Replies: 2 comments
|
(There are about a dozen taxonomies under |
|
It's straight forward enough using Arc APIs, but will require a script to process all your content. There is no bulk way of doing this, you'll need to iterate over each article and update them. You would use draft API to update each ANS document - using the API
In draft API you will need to
You will need to regenerate a URL which in Arc will create the redirects for you. This allows old URLs pointing to the current URLs to work with the move of content to the new section {
"document_id": "123455",
"website_id": "${webiste_id}",
"website_url": "/springfield/article-url/",
"website_primary_section": {
"type": "reference",
"referent": {
"type": "section",
"id": "/springfield",
"website": "irishtimes"
}
},
"website_sections": [{
"type": "reference",
"referent": {
"type": "section",
"id": "/springfield",
"website": "irishtimes"
}
}]
} |
Uh oh!
There was an error while loading. Please reload this page.
There's an interest from our editorial team to move some of our taxonomies from a deeply-nested path to a top-level taxonomy. Essentially, the idea is:
Has anybody done that? Any problems we should look out for? We have years of content inside those taxonomies if that affects things.
All reactions