• State Suggested Answer
  • Replies 14 replies
  • Answers 2 answers
  • Subscribers 141 subscribers
  • Views 13545 views
  • Users 0 members are here
Options
Related

Need help extracting a large number (8-25k) of files from older SDL (11.1)

Susan Masters

Hi all from an SDL novice - my group needs to extract a large number of files (up to 25k) out of SDL (and older version, I believe 11.1?) so that it can be placed on an FTP server. We have a tight timeline and budget and don't know of a script or quick way to extract more than a small number at a time (maybe 20 files?) manually.

Does anyone have any experience with this or know of a script that can be used? Any help or input is appreciated. Thanks
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hey

    Not sure if you imply all versions/languages/resolutions of these objects, but what some clients have done is to create a temporary/dummy publication in which they insert the maps that reference the objects they need. Possibly by creating a temporary 'supermap'.

    Make sure you select the appropriate versions of the objects so that the baseline is up to date.

    Assuming you need clean DITA XML (not file system resolved), you could then use the publication report in the web client to export the data to the file system. In this publication report you can specify the language(s) that you want to export.

    Depending on the structure of your data, it may make sense to create a couple of such dummy publications.

    If you use variables/conref, you have to make sure they are part of your publication obviously.

    Best regards
    Kurt
  • 0 in reply to Kurt Van Deun
    Hi ,
    With regard to your comment about clean DITA XML. As per my understanding (please comment/correct as needed) there are two ways to export the content:

    1) As resolved DITA XML, in which case the exported source would not contain any ishcondition or conref attributes, to mention two examples. In this export, elements with ishcondition attributes are kept/dropped based on the publishing context. Content references are populated (and so there is no content reference in the resulting XML). Variable placeholders are populated. And so on. (The result is valid DITA XML).

    2) As SDL custom DITA, that is, the exported content directly reflects that in the database. To use this content in another system would require some reverse engineering, e.g. implementing ditaval instead of ishcondition. And implementing keyrefs instead of variables.

    Or, then again, another system may introduce some spices of its own that in some way or other extend the core DITA feature set, as laid out in the OASIS specification(s).

    , using either alternative there is some rework to be done.

    Thanks
    Joakim
Reply
  • 0 in reply to Kurt Van Deun
    Hi ,
    With regard to your comment about clean DITA XML. As per my understanding (please comment/correct as needed) there are two ways to export the content:

    1) As resolved DITA XML, in which case the exported source would not contain any ishcondition or conref attributes, to mention two examples. In this export, elements with ishcondition attributes are kept/dropped based on the publishing context. Content references are populated (and so there is no content reference in the resulting XML). Variable placeholders are populated. And so on. (The result is valid DITA XML).

    2) As SDL custom DITA, that is, the exported content directly reflects that in the database. To use this content in another system would require some reverse engineering, e.g. implementing ditaval instead of ishcondition. And implementing keyrefs instead of variables.

    Or, then again, another system may introduce some spices of its own that in some way or other extend the core DITA feature set, as laid out in the OASIS specification(s).

    , using either alternative there is some rework to be done.

    Thanks
    Joakim
Children
No Data