What non-data Portfolio information can I copy or clone?- I (v5)

The information below is derived from the International English Portfolio Network client v5.01 for Windows. Information noted as being stored in the Registry will most likely be stored in the Preferences folder on a Mac though this may not be as accessible to users as Windows Registry settings are via Regedit.

Notes:

1. This is data stored on the PC on which the client is installed and affects any catalogue opened on that computer.
2. This is the level at which the client will attempt to log on to any Catalogue opened. If the Catalogue cannot be opened at that level (only one user may access as admin and not while a Catalogue is served) the next highest access level will be suggested for log in.
3. These are all set via the Edit -> Preferences dialog.
4. This is the 'Scripts' subfolder within the installed Portfolio files (default location = C:\Program Files\Extensis\Portfolio 5.0\Scripts\). Most Windows scripts are single executable files which will require the v5 or v6 Visual Basic run-time files to be installed (depending on your OS version you may need to download these separately). Some scripts - such as FilFolio for reading EXIF data - are more complex and have their own installer, otherwise you can make a script accessible by simply dragging the executable (EXE) file into the Scripts folder. The scripts menu is only available when a Catalogue is open in the client. Note that Scripts are not supported in the desktop version of the client.
5. This is the 'Servers' subfolder created within the installed Portfolio files when you create information about Portfolio Servers you access (default location = C:\Program Files\Extensis\Portfolio 5.0\Servers\). These data files have no extension in Windows. The files may be simply copied from one client's folder to another (on PC or Mac) to make the same servers available in the 'connect to Servers' dialog.
6. These are the details and passwords for level-based and user-based types of access. It is not necessary to have any access passwords set but this is not advisable outside a single-user situation.
7. When you save a Gallery named 'Default' or default', the catalogue uses these as the template for any automatically generated 'Untitled' type Galleries.
8. General, Add, Update, Mappings, File Types, and Exclude Strings tabs. Although the latter 3 allow the adding, editing and deletion of new settings, these cannot be saved for import/export. The General, Add and Update tab options can be accessed and set via VB (and AppleScript?) automation.
9. Keywording, Passwords, Custom Fields, Startup and Previews tabs. Keyword lists, Startup settings, Splash Screens and Disk Previews are referenced separately below.
10. When importing data via text files you can save the field mappings you create as named items which can then be used as a time-saver when doing subsequent imports of a similar field set with new data. You can add, rename or delete these lists but not export them.
11. HTML templates whether exporting direct to HTML or for use with PortWeb can only be used when stored within a Catalogue. However by opening a saved template in the Edit HTML dialog you have access to Import and Export buttons. It is important to note that the export process does not save two important setting, one is the template's internal saved name (used with PortWeb queries) and the other is the number of data rows/columns set in the Edit HTML dialog. When exporting templates you are advised to add this information as comments in the HTML:
    • <!-- Template name = "mytemplate" -->
    • <!-- Rows = "4", Columns ="2" -->
    The data formatting in the comment doesn't really matter as the notes are only there to be read and used manually when importing the template. When you import a template the filename is not inserted in the name field, you must do this manually as well as set he row and column numbers in the Edit HTML dialog.
12. From the Administration -> Keywording tab you can export a text file listing (one keyword per line) of all the keyword (not just the Master Keywords List - MKL). There is no import method as such but you could import the list as an MKL - see note 15 below. Be aware: some versions of the client do not properly add a carriage return/line feed after keyword on the last line which causes that item not to be loaded on import - you are advised to check this and add a cr/lf (use 'Enter' key) if necessary.
13. Although you can't export this information, by going to the Administration -> Custom Fields dialog clicking a field from the list and then the edit button you can see - but not alter - the original settings. Where fields use pre-defined lists, you can import/export these as described in the next note below.
14. The MKL and pre-defined lists (as used by custom fields) can both be imported and/or exported. The text file has one keyword/entry per line. Note the comment above about checking for correct termination of exported files.
15. You can import but not export images to be used as splash screens via the Startup settings dialog. Compacting a Catalogue should (not tested) remove unwanted/unreferenced images recovering the file space used.
16. If you have set Disk Previews, this folder location should still be shown on the Administration -> Previews dialog.
17. These images can be imported but not exported via the Gallery Customisation dialog -> Thumbnail View tab. As with splash screen, unwanted images can most probably be deleted via compacting.
18. Though you can't export these, you can check out the settings by opening the Gallery of interest and then the Gallery Customisation dialog.
19. To check a Saved Find's arguments, open the Find dialog and then select the Saved find from the drop-down list, the Find dialog will updated to show the stored Find and you copy the settings manually.
20. These options apply globally to any slideshow run in the Catalogue.
21. This creates or reads in a '.PJD' file which lists the Catalogue's Categories and their hierarchy. The file can only be used to replicate Categories between folders but it holds no data about records and the Categories to which they are linked.
22. Although different clients accessing a shared/served Catalogue can have different on/off states for (each) automation this information appears to reside in the Catalogue rather than the client.

Question: What non-data Portfolio information can I copy or clone?- I (v5) [FAQ00186.htm]
Last Update:- 01 June 2006

This FAQ is created and maintained using

Friday - The Automatic FAQ Maker