Timeline for Using Core service to copy items to different publications
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10, 2013 at 7:49 | vote | accept | Ibrar Hussain | ||
| Apr 10, 2013 at 7:02 | comment | added | Bart Koopman | a lot of functionality you have to build, but nothing that can't be done with the Core Service, you just need to follow the API guide and all examples out there (there have been quite a lot of questions about it here and on StackOverflow already) | |
| Apr 9, 2013 at 19:06 | comment | added | Ibrar Hussain | Furthermore, whilst looping through each page whilst retaining each CP, I need to check if each component against every CP has been created at the correct publication, if not I will want to re-create this. | |
| Apr 9, 2013 at 19:03 | comment | added | Ibrar Hussain | Well, let's take a page for example, we'll have page metadata to handle and CPs. CPs will include both components and CTs. So is it possible to retain all this information when creating a new page at a different location? | |
| Apr 9, 2013 at 18:56 | comment | added | Nuno Linhares♦ | As long as you can fulfill all of the dependencies of the page, sure, why not? | |
| Apr 9, 2013 at 18:53 | comment | added | Ibrar Hussain | Thanks Bart. So does this apply for any item type? For e.g. Can I create a new SG/Page in PublicationB and populate it with the contents of an existing SG/Page in PublicationA? | |
| Apr 9, 2013 at 16:06 | history | edited | Bart Koopman | CC BY-SA 3.0 |
added 64 characters in body
|
| Apr 9, 2013 at 15:31 | history | answered | Bart Koopman | CC BY-SA 3.0 |