Overview

The ImageManager Module allows you to manage all your images, graphics and photos in one simple area online! With the ImageManager, you can easily upload, view and edit all your valuable photos in one place. Think of the ImageManager as a large central repository or "library" of images, which you may reference anytime, anywhere using a simple web browser. The ImageManager also manages your centralized Images database and contains information and paths to all your photos uploaded and stored inside ImageIsland. With the Image Manager, your photos are centralized and your complete library is always available via the web. Come here first whenever you need to manage your images.

In addition, because the ImageManager controls all images uploaded and managed in the web site, all other areas and modules in the site will use the ImageManager's database of images. This gives you the freedom to manage all your images in one area, while having the freedom to assign and distribute them in another. You can, for example, upload and manage as many images as you like in the ImageManager without having to worry about which images are displayed publicly to others (unless you allow public access to the ImageModule itself, as described above). As you use other modules in your web application, those module will be able to access the ImageManager's repository of images as stored in its database, and share them out in all kinds of creative ways, without affecting the ImageManager's ability to manage those images for you. So, any changes to any image in the ImageManager affects all images it shares with all other modules and web pages. Keep this in mind as you begin to grow your image repository and to add new modules and assign images to those modules, independent of your ImageManager photo library. Your ImageManager Module will allow you to keep track of your images and photos online as you add more over time and begin to use them in creative ways in the web application.

Viewing Images

When you first visit the ImageManager, you will see an "eye" icon and the word "images" in the upper left hand corner of the toolbar at the top. This is the main image viewer for the ImageManager Module. This tool bar icon allows you to quickly view your complete image library in the ImageManager. From this area, you can view all your images and photos using different views and sorts and filters. For example, you can access a thumbnail view of you images, where they are stacked as thumbnails in the display. Or you can view a vertical listing of all your images stored in the system. You can even see folders and groups of images in the system using the filter area. As you manage your images you will use this area more than any other. So, just remember the "eye" gives you access to views of all your images.

When you are in this default area, you have several different ways to organize and view your images. To begin with, you will see a dropdown "view" selection, which allows you to control how your images are listed in the web application. You may use the views dropdown to choose one of the available views. Each one has its advantages. The default is "thumbnail view", which shows tiled and paged sets of image thumbnails in the web page. This is the most visual and popular of the view types. The other views allow additional ways of viewing your images and may be helpful to you, including a vertical "thumblist view" with detailed tables of information about each image. And, there is a "textlist view", which shows simple listings of images by title. When you come to this view area and change views, the system will retain the preferred view for the life of your session. Returning to this area will always show your images in your last chosen view.

In addition to views, you will see a "sort" dropdown list. The sort allows you to sort your images in different ways so that you may access certain images more quickly using various criteria. The default is to always show the newest images first (sorted newest to oldest). Other sorts may be helpful to you in getting to specific types of images, sizes of images, names, etc. You may want to sort by file type, like gifs and jpegs, or oldest to newest, etc. Combining a "view" choice with a "sort" choice, allows you to get really detailed listings of your images, as they get larger over time and allow you to combine sorts with views to get access to specific types of images quickly. For example, try choosing the thumblist view and then sort by file size. You can see what the largest images are in a vertical thumbnail list format. These sorts and views may help you make decisions on certain groups of images and get to images in a fast and efficient way.

Folders and Groups

New! The newest addition to the ImageManager is the "filter" area, or filtering select list. Filtering refers to the ability to see smaller subsets or categories of images in the system. You you will find that filters are quite powerful in helping you and your users organize files and manage subgroups of images added over time. This is a major addition to the web application. For that reason, we will describe this new toolset below in more detail.

The default filter is "all" or all files displayed. This showcases all files in the system. When a Global Administrator logs in, he/she can see all files by all users in the display. Users will only see the files they have added to the system. The next choice is "folders". When you choose folders, the page changes and a new page layout appears. The new layout now includes a listing of physical storage folders on the left and your images displayed on the right. The new folder listing shows all physical folders shown on the server starting at the default, root "Storage" folder inside ImageIsland. This is the root storage folder for all files uploaded and added to ImageIsland. The system allows users to create subfolders underneath the Storage folder, upload images to them, and manage both in the system using a new hierarchical folder "tree" structure. (What certain users can see, as well as the "types" of folders in the system are all outlined in more detail later on in this Help page). Once folders are added under Storage, you can click those folders in the folder tree and see what imags are associated with the folder. Simply click a folder to see the images it contains displayed to the right in the image listing area. Each folder also has a name or title you can customize, and included the number or files or images it contained, next to the folder name. You can not only edit, delete, and add folders to your folder tree, but also move images from folder to folder. And you can even make a folder "private". These fatures are dependent on user security settings, of course. Global Administrators, in general, once logged in, have full access to manage the folder tree and can create and setup an organized structure of folders for use when uploading, moving and managing files on the server. You will find the folder filter system a powerful way of managing all your files and for organizing those files directly on the server. As already mentioned, all files and folders shown in the folder tree are the actual physical files and folders stored on your web server and site. In this way, the new folder filter system in ImageIsland works just like a typical folder tree on your PC and will help you stay organized much like any folder tree would. More detailed information on folders and folder security is listed farther down in this file.

The view of folders also has a small toolbar at the top of the folder tree. The icons shown in this toolbar allow you to manipulate and manage your folder tree as needed, and the files stored with them. The tools/icons shown include the following items:

• Edit/Add Selected Folder - This is the edit icon for editing a folder. You can now choose a folder in the tree and clicking this icon, edit the name of the folder, delete the folder and all its child folders and files, or add a new child folder. (Who can edit which folders is outlined in more detail farther down in this Help file.)
• Rebuild Folder Tree - Clicking this icon instantly refreshes and rebuilds the tree menu from the server. As the folder tree gets larger and more files are added, you may find you need to rebuild the folder tree. Clicking this tool allows you to do that instantly.
• Move File to Folder Mode - You can physically move any image or file in the system to a new folder or child folder. Using this tool, you will see dropdowns appear above all images displayed to the right. Simply choose a new location or folder name from the dropdown above the image you wish to move and it will appear in a new folder (and is removed from the original folder). This physically moves the image to a new folder, as well as its thumbnail, and updates the image files database entry, so its reference inside ImageWebPage Modules and others is not affected. At this time, you cannot copy images, but can only move them from folder to folder. You will find maintaining a single master copy of the original image is much easier to manage. (When we get to "Groups", you will be able to assign the same physical image to multiple groups or categories.)
• Edit/View File Mode - This tool icon allows you to return to the default view of your images displayed to the right. For example, you may be in "move" mode or edit folder mode. Clicking this allows you to return to the view mode, or folder view, that shows all images assigned to the folder you selected in the tree.
• Collapse All Folders - This handy tool allows you to collapse all folders in the system, allowing you the ability to see a smaller compresed view of your main subroot folders under Storage. This is helpful in situations where you may have allot of nested items and need to go back to the root folders quickly.
• Expand All Folders - This handy tool allows you to expand all folders in the system, allowing you the ability to see all the folder tree elements in the system complelety expanded. This may be helpful in situation where you have created many nested folders and need to view their depth quickly.

* Keep in mind, folders represent actual physical folders on the server and the files stored inside them under the Storage root folder. Any changes you make are permanent and changed on the server itself. Groups are different (see below). We provide more details about types of folders and their security setup below.

We also show Groups under "filters". Groups is a logical organization of images that is different than folders. Unlike folders, which is a physical representation of files and folders on the server, Groups are simply labels added to images in a hierarchical, tree-like structure. That means that, unlike folders, you can assign the same image to multiple groups and subgroups, expanding your use of a single image by assigning multiple categorization to it. This new filtering system allows you to store your master files in one physical folder, but then assign them to multiple custom categories or groups you create in the Group tree system. Like folders, groups are designed as trees, and you can create groups and subgroups under these. They also are organized around users, and like folders, who can see what groups is tied to user security, which is explained in more detail below. Groups have some of the same features and buttons as folders, but with a few variations, described below:

• Edit/Add Selected Group - Like folders, you can choose a group in the tree and clicking this icon, edit the name of the group, delete the group and all its child groups and files, or add a new child group. This is the edit icon for editing a group. Unlike folders, the delete group feature never deletes the physical child groups and images associated with the group. It just deletes the image-to-group associations in your group tree. This is why groups are a better choice for organizing categories of files. (Who can edit which groups is outlined in more detail farther down in this file below.)
• Rebuild Group Tree - Like folders, clicking this icon instantly refreshes and rebuilds the group tree system. As the group tree gets larger and more files are added, you may find you need to rebuild the group tree. Clicking this tool allows you to do that instantly. If you log in and dont see a refresh of accurate tree data, try clicking refresh as well to update your view based on your user security rights.
• Add File to Group Mode - Unlike folders, when you assign a file or image to a group, you are assigning a database entry to an abstract category...not a physical representation of file and group on the server. This is much better, as you can now assign the same image to multiple groups and child groups, using the same image in many different ways without affecting the original image stored in your folder on the server. As you use groups in the ImageWebPage Module, this will prove very helpful to you. For example, you could assign a picture of a family member to three different groups, and thus, use the same image in many different displays, web pages and galleries all organized around different groups you manage separate from both the folder it sits in and the ImageWebPages you build and add over time. This area also works like folders, in that a dropdown now appears above the image you wish to assign. Unlike the "move" feature in folders where you first choose a folder, then click to move it to another folder in the dropdown, clicking "add" in this area, takes you to the root group or "All Files" parent group, which houses a list of all files the user has access to. They can now assign images from their matser libarary to all groups in the dropdown that appears above the image.
• Remove File from Group Mode - This is the same as the "Add File to Group Mode" area above, but allows you to remove an image from a group that's been selected.
• Edit/View File Mode - This allows you to return to the default view of your images displayed to the right. For example, you may be in "add to group mode" or "edit group mode". Clicking this icon allows you to return to the group view that shows all images assigned to the group you selected in the tree.
• Collapse All Groups - This handy tool allows you to collapse all groups for all users in the tree, allowing you the ability to quickly reduce down the display of group trees in situations where you may have allot of nested items and need to go back to the root groups quickly.
• Expand All Groups - This handy tool allows you to expand all groups for all users, giving you the ability to see all the group tree elements in the system at a glance.

Note: Both Folders and Groups are designed around "tree-based" systems, so as you add and manage these items, you can continue to nest them and organize them as you would on your PC or Mac. All trees have a "state" as well, meaning that the web site will store the last state of the tree as you left it. To do this, a small cookie is stored in the browser, which records the last state of your view of the folder/group tree. That means, if you are managing files and folders, and leave and come back a week later, the system will maintain a state of where you were in the tree (granted, you have not cleared or block cookies in your browser). Please Note: JavaScript and cookies must be enabled to use the Folder and Group tree-based system.

Paging

Next, you will see a numerical paging toolbar. This gray toolbar allows you to quickly access "pages" of images. Because only a certain number of images are displayed per page, managing hundreds of images is much easier using this paging system. Click a number to go to that page of images, once you have several hundred images added. The paging bar will increase its numbers, with each number representing anywhere from 20-200 images in your system, depending on the type of page and view you are using.

Finally, you may notice the "refresh" button. This button may be clicked if you have lots of images, but feel one or more may be missing from the display. The system stores image references in memory after pulling them from the database, which allows the system to manage thousands of images quickly this way. Sometimes the built-in memory manager and indexer doesnt record the latest images added by others using the system, so pressing refresh makes a fresh call to the database, updating the memory manager that indexes your files in the display.

Viewing an Individual Image

Using the view inside the ImageManager, when you click a thumbnail of an image, or a text link to an image, you get to view that image full-size. When you go to view an individual image, a new toolbar will appear at the top with new icons. Because you upload all images as they are originally (not resized), what you see is what you get, as far as size. Some images may appear very large here. Others may appear very small. Check you image pixel dimension before uploading, remembering that on the World Wide Web, digital media display sizes are based on pixels and monitor resolution combined. To help with views of very large images, the ImageManager comes with a "rescale" and "resize" tool. Each is unique. The "rescale" icons (eyes) allow you to visually change the size of the image in the browser interface, without changing the original file physically. This is usually a percentage of the original size. For larger images, this is especially helpful in scaling them down to a smaller size so you can view them in your browser window. Each of the "eyes" allows you to get smaller and smaller. The "resize" tool (box with arrows) is different. It allows you to physically alter your original image and size your image down to a smaller, more manageable size. You may find that you have some very large images that you only need as small photos on the Web. Resizing them changes the pixel dimensions so they fit better in the browser to your viewers, are smaller in kilobytes (size), as well as faster in display. Changing the size speeds up the download and view speed of an image online. Remember, resizing is permanent. Rescale is not. Its often a better plan to rescale your images first before uploading to increase the upload speed. But you have the option to do that here from the web site, as well, if needed. Be sure you understand the difference, however, between rescale and resize.

Besides the size and scale tools, there is an edit button. Click the edit tool to take you to the edit area. This allows you to see a box to the left that displays more detailed information about the image, such as its size and dimensions, its url, id, etc. You may add a name and description to your image, which may display with the image in various parts of the product (i.e. some ImageWebPage templates). In this module, those names and descriptions are helpful in the "textlisting view" of images, so you can quickly identify images by name or description, if needed. As mentioned, the name and description may also appear in some ImageWebPage templates. So, adding those to your image is generally a very good practice, and helps you track and archive your images on the server as more are added.

Also at the top of the edit view area is a purple circular arrow. Clicking that will rotate your image 90 degrees to the left (or clockwise). Keep clicking to align you image as needed. Many digital cameras create horizontal image views which you have to turn your head to see. This handy tool was created for those people who may be uploading right off their digital camera into the product and need a quick way to quickly rotate their images. Clicking this tool permanently rotates the image. Like rescaling, it does affect the original image, and changes are permanent. Rotating also saves the original in its new rotation, adds the new dimensions to the database, and recreates its thumbnail in the new rotation.

Uploading Images

The ImageManager Module also allows you to upload new images into your web site. You may upload images from your computer to your web site and server using the file upload system under the "Upload" button and blue arrow icon. In the upload area, you will see ten upload file fields, and a submit button. Simply choose images you wish to upload by clicking "browse" buttons in the ten upload buttons found in the Uploads page, then clicking "upload images" to upload these images from your computer to the server. Please be patient while your images upload to your site. Note` the new Folder dropdown menu, as well in this area. This new dropdown feature allows you and your users the ability to choose a folder as a destination for your images. When uploading, its helpful to upload to known folders that you are managing on the server as a user. This helps organize your images faster on the server. If you do not choose a folder, whatever default is shown becomes the new folder for file upload. Note: Whatever folder you last clickied or updated should be shown by default in the folder dropdown.

*Bandwidth Note: Dialup users may have to wait some minutes when uploading very large files. To prevent this, please reduce the size of your image before uploading. The same applies for images several Megabytes in size over a faster connection. Its possible that large numbers of very large images may "time out" on the upload process, even on T1 and cable model connections. To prevent this, again, please resize your images when possible to a smaller size.

After the images are uploaded, the system will refresh and you may see a message at the top that describes which images were successful and which could not be uploaded. The system will refresh the page and will then generate thumbnails for all your images automatically. PLEASE DO NOT TOUCH OR CLICK THE INTERFACE TILL BOTH UPLOAD AND THUMBNAIL PROCESSES ARE COMPLETE! During this process the system needs to complete both the image upload process and the thumbnail creation process in order to successfully complete your upload. Otherwise, it may fail and you might get broken image displays in the Image Manager listing area. Interrupting this process will stop the thumbnail creation and/or database save processes, as well, on the server, and you may have to delete whatever images uploaded and reload them again.

Upon completion, the upload page will return you to your page and indicate that your upload is complete, displaying a green checkmark and message. After completion, your images can be seen by clicking the "eye" or view images button in the toolbar at the top. You may have to click the last paging numbers in the paging toolbar at the top to see the latest images you just added, if you changed your sort dropdown earlier. Simply click the sort dropdown and choose "newest to oldest" and submit. New images may be clicked in the display to view, or edited by clicking edit. The new images are now in the ImageManager Module and ready for viewing and sharing!

Because uploading files to a web server can be problematic, we have listed some additional support information below in order to assist you with any problems you may experience.

Troubleshooting Image Uploads

* You may read our section below if you are having any special issues with uploading your images or creating thumbnails:

• Supported File Formats: This version of the application is designed to support only those image formats that display in most current browsers, and without the support of third party plugins. These generally include JPEG, PNG, GIF, and BMP. Many other image formats are not supported by your browser for visual display, so have been excluded in this version. This includes file formats like TIFF, PSD (Photoshop), TARGA, PICT, Paint, RAW, many others. Keep in mind this is by design as the ImageManager is designed for web viewing, and these other image formats are not visually displayed by current web browsers. If you need to convert files before uploading, there are many great desktop software applications to assist you with that process.
• Original File Formats Retained: On uploading an image, the original image format, size, dimensions, and file name are retained exactly as you created them. The exception would be if you have "illegal characters" used in your image name (like quotes, etc.). Some characters may be stripped out so the file paths work in a users browser and display in the interface correctly. No conversion, compression, or manipulation of the original image is ever done, except to store the image on your web site and server exactly as you created it. For that reason, its important that you resize and rename your images as needed before uploading. After upload, certain tools in the interface will allow you to manipulate the image (i.e. rotate tool, etc.) But essentially what you upload is what you get!
• Image Thumbnails: In this version of the application, all thumbnails are created for you as new images based on the original image, when possible. Thumbnails are automatically created for you after the initial image upload is complete. The thumbnails are generally created as 80 x 80 pixel thumbnail images.
  *Note: Because a small ASP.NET web page performs this function, your web server must support ASP.NET as well as ASP, and have full read/write permissions assigned on the main ImageIsland folder for both the anonymous IUSR account and the ASP.NET worker process account. Without those permission applied to all files inside the ImageIsland folder, the web site and upload area may not function correctly. If, after uploading a file, you see a white box with missing thumbnail icon for your image in the ImageManager after upload, there may be a problem with the .NET permissions. Please contact your ISP or Web Host Provider and ask their support team to add these permission on yur web site's ImageIsland physical folder and all child folders, if you still see errors in the web site.
  These thumbnails, when created, are currently created and stored as JPEGS. Some image formats do not convert to the thumbnail format created in this web application. Conversion to the thumbnail format used in this application may cause issues with some types of 8-bit color JPEGS, certain GIF (including some animated formats), PNG files, some color indexed images, and other compressions. If you see thumbnails missing for some images you upload, this is expected for these formats. When the system can create a thumb from the image you upload, it will be shown in the image view area. If not, a placeholder image will be provided. You may still click that item to see the image full size. Note: The system uses a small JavaScript call to process the web page upon completing your inital image upload. If you have disabled JavaScript support or your agent does not support JavaScript, you will see a button you may still physically press to trigger the thumbnail creator script when upload is complete. In general, most browsers will skip this process and automaticfally create the thumbnails for you as well as upload you image, all in one easy process.
• Large Files May Not Upload: Large files take longer to upload and some very large images uploaded on dial-up may time out your connection to the server before the file is completely uploaded. Edit the size and dpi of your images before uploading to reduce their size whenever possible, especially if you are using a dial-up connection. Smaller photos are better in that scenario and on the web in general, when showing to others online. In all cases its always better to upload images 4 megabytes or less, or less than 1 megabyte when possible, so users who view your images online do not have to wait long periods of time waiting for their browsers to download images to them from your site. If you and your visitors have broadband connections, then larger file uploads and views will be possible. Even then, very large images will appear too big for the browser display. So, smaller images are better in all cases, when uploading to your web site. Keep that in mind when creating images on your desktop that will be uploaded into ImageIsland.
• Check your Host Provider for File Space Allowed: Because the practice of uploading and storing large amounts of images on a web server takes up space on your hosted web site, you may quickly exceed the allowed space on your host provider's server account you have with them, and your upload process may fail. Please check with your web site host provider first to see how much hard drive space in megabytes or gigabytes they allow for your web site as found under your hosting contract with them. Make sure you have plenty of hard drive space before uploading large volumes of images to your site. The same rule applies to gigabytes of downloaded files allowed. Most host providers also allow so much download bandwidth. Make sure you also have enough bandwidth to present your images. The web application cannot control those factors, especially if your host provider has systems in place that disallow you to upload additional items once you reach your maximum allowed.
• Check your Host Provider for Read/Write Permissions on your Web Site: If you have any problems uploading images to the server (errors listed at the bottom of this page), or they do not appear after uploading, check to make sure your web site has write permissions set on all folders inside this web application. Contact your ISP or the host provider for your web site and request that they give the ASP.NET (ASP_NET or NETWORK_SERVICES) and anonymous user accounts (IUSR) full write/read/delete/folder permissions on the server for all folders and files inside the ImageIsland web application. The same permission changes apply, in general, to all errors related to reading and writing to the module databases, as the web application uses MSXML to manage and write to the database, and will need those same anonymous and ASP worker process accounts given full permissions on the folder and file permission settings as well, to function correctly.
• When I upload my files or press submit, it says successful, but nothing has changed, or no images show up? The reason that nothing appears when you upload files is because your web site folder on the web server does not have the right "security permissions" setup. You Web Site Host Provider must go on the server and give the IUSR and ASP.NET accounts read and write permissions for the "ImageIsland" (or your product's folder name) physical folder, and all child folders under it. This will allow the web application and its processes on the web server the right to store image files, write xml data, create thumbnails, and rotate images. Without these permissions setup correctly on your web site server, your web site pages cannot perform these tasks. Because these permissions apply to a whole host of security processes controlled by the company that hosts your web site, we cannot affect these changes. They are a part of the security tied to your Host Provider and the Web in general. Please contact your ISP and request that these changes be made on your web site.
• When I upload my images, only images less than 200 kb are uploaded. This is a security restriction in Windows Server 2003. To fix this, make sure the IIS web server is not restricting the size of ASP uploads. IIS 6 (Windows Server 2003) has a limit of 200 KB for ASP requests in general and file uploads in particular. To remove this limitation in IIS 6, your ISP or Web Site Host Provider will need to edit the Metabase file on the web server itself, which can be found at c:\Windows\System32\Inetsrv\MetaBase.xml. Follow these steps: go to IIS and right click the server, select properties, and check the box "Allow changes to MetaBase configuration while IIS is running"; if after this step the metabase file is still locked, try turning off IIS or even restarting the machine in safe mode; open the file in an editor; the variable AspMaxRequestEntityAllowed limits the number of bytes in the page request (by default 200KB); change the value to 1073741824 (unlimited) or to a limit of your choice; check whether the same variable shows up in other places in the file. If your ISP will make this change, then files over 200kb will upload correctly.
• Final Note: If you have any additional problems or errors uploading images, it is mostly likely due to a setting on the web server. Make sure ASP and ASP.NET 1.1 are enabled on your web site first. Then, make sure the problem is not related to a permission setting on the physical ImageIsland folder stored on the web server where your web site is hosted. Please ask you ISP to add write permissions (or priveleges) for the "IUSR" and ASP.NET user identity accounts on your ImageIsland folder and all sub folders and files. Please read the "INSTRUCTIONS.txt" file in the root web folder for ImageIsland, or visit our FAQ and Support areas at http://www.giantisland.com/, for more information.
• Copyrights and Your Responsibility: It is the users responsibility to make sure that no copyright infringements occur with the images they choose to upload to this system. The creator of this software (GiantIsland LLC) is not liable for or responsible, in any way, for infringements of any kind or damages that occur to other groups or peoples, from the storing or uploading of files using this software, which may or may not involve copyrighted material or patent infringments related to files uploaded to this system. All images and files stored and used in this software by the user are the sole responsibility of the user(s) of the software. By using this software, the user agrees to these requirements and stipulations as defined in the license that comes with this software.

Folders and Groups

The new Folder and Group tree-based system is actually quite powerful. But it also has some built in features and security assignments you should be aware. These will impact how you and your users (who may login and create folders and groups) use the system and manage those items on your server. We have outlined more details about these areas for you, so you can plan and predict how large numbers of users and folders and files are organized and managed behind the scenes in ImageIsland. You will find, as your folder and group trees grow and expand, many new issues in terms of how you and your users are managing and storing files in the system. So, we hope the information below helps you plan for that growth and understand fully how it impacts file and folder storage, as well as tree security in the system, over time. We highly recommend you take the time and read the information provided below.

Understanding Folders

General Folder Structure - The root folder, or top parent folder of all files and folders stored in the system and on the server, is called the "Storage" folder. It is found inside the root folder of the "ImageIsland" folder itself, and is the central repository for all images uploaded and stored in the system. We designed this single centralized "storage" folder so you could manage all your files in one location on the server, and have some control over read/write permissions, as well as some ability to manage all your files using FTP and other server access mechanisms. WE DO NOT RECOMMEND YOU EDIT, CHANGE, DELETE, OR MOVE THIS FOLDER in your web application. Otherwise, you will lose files and all your users will lose their files and paths to files stored in the XML Native database built into the website!

When you first use your software ImageManager Module, you will see the Storage folder listed in the folder tree. The Storage root folder may be used, by default, as a storage folder (logged Global Administrators only), or main parent for child folders added under it. No user, including Global Administrators, may delete or edit this folder name. The Global Administrator is the only user allowed to add folders to the system, including any child folders, under Storage. The exception is logged in users who may add child folders under their prebuilt user folders (see below). If logged in users want to add folders under the Storage folder directly, they must do so using prebuilt "user" folders added under Storage when the user is created in the Security Module. In that case, only logged in users may add folders under their personal child "user" folder. For example, a logged in user called "user2" may only add files and folders to the "Storage/user2" folder, but may not add folders or files under "Storage" directly. Public users (not logged in) can only add files under public folders added under the Storage folder by the Global Administrator, and may never add any kind of folder in the system. This helps protect even public intranet systems where the ImageManager may be public, but where its dangerous to allow anyone to delete or change folders of files in the folder tree that may impact thousands of managed files and folders built by others. In cases where you need public users to have the ability to add folders and add files directly under the root Storage folder, we recommend you give those users access to the Global Administrator account, or a shared user account in a private (login) Module setup. So in summary, if you login as the Global Administrator, you can easily add new images and folders/child folders under Storage. All other users may not. They can only add child folders under their user folders, and only when logged in as users. Again, this helps protect the root Storage folder and public folders from being corrupted, deleted, or modified by others who are not logged into the system.

Keep in mind that the Folder system in ImageIsland is closely tied to the physical folders actually built and managed on the server itself. Any changes to any files or folder in the "Storage" folder on the server will cause image paths to break, so be careful what changes you make to this system outside the Folder management peiece built into the ImageManager Module.

WARNING! The upload or storage folder is always called "Storage" in our software, and we do NOT recommend you change this folder name. However, ImageIsland, is designed, so if you HAVE to change this folder name, you may do so. We recommend, if you decide to do this, you also change the Storage variable name found inside the "Systems/SystemSettings.asp" file first, then on the folder on the server. In addition, we recomend you do this BEFORE you start your website application on the server for the first time and BEFORE you upload any files to your system. The reason is, if you change that name later, you may be able to upload files to your system, but old files already in the database, will have paths that now no longer work. The only fix for lost files like this, is to delete the data in the database for the Manager Module and WebPage Modules (email us for isntructions), and run what we call the "Batcher" module, which will automatically add in these files again. ALL USER FILES WILL BE LOST, as well, if you do this, and the only fix, will be to zip up any "user" folder files in "user" folders on the server and send them to users so they can reupload these files again, after logging in! If needed, you can purchase this batcher module from our website (http://www.giantisland.com/).

When you first come to the Folder area of the ImageManager, you will most likely NOT be logged into the module. You are considered a "public" user at that point. Public users do not have the ability to add folders in the system, but may add files to child folders already created for them by a logged in Global Administrator. To setup a system for public access users (no login), we recommend you login as the Global Administrator, even though the Module may not be private (Security Module), and create some public folders for your visitors. When you do so, you will find you can now start creating folders under the Storage folder. These folders will appear as plain, vanilla folder icons in the folder tree. These are what we call "public folders" because they are viewable in the system by any user, logged in or not. Once created, these folders are accessible to public users in cases where you elect to leave the Manager Module public (not set to "private" in the Security Module). In those cases, any user can access the ImageManager Module without a logtin and start uploading files under these public folders. (This is the default setup for the ImageManager Module). As mentioned, only Global Administrators may upload directly under Storage (root). This is by design to keep unmanaged images from be stored by many users in the root folder area. In addition, logged in users may also see and use public folders created by the admin, as found in a "private" Module setup. In that case, users who log in will now see both their private "user" folder as well as these public folders. In this system, you might elect to have both of these folder types as central repositories for all your users to share as a group. Keep in mind, images uploaded by a user are only seen by that user, so though the folder is shared, the images are not. So, all images uploaded to this folder are really only seen by the Global Administrator. User images are only seen by the user. This is by design to prevent users from deleting user images owned by another user. Again, if you want a shared folder and file environment, consider setting up your software as a public system, create folders, and allow all your public or intranet users to access, upload, and view shared images in these public photos. This is the primary purpose and use for public photos, and why we do NOT recommend you create public folders in a private Module security setup. The only reason for using public folders in a private secure module setup would be for you to have users move images to a central repository, which only you as Global Administrator can access, and where images may be moved or deleted or modified by you.

In addition to public folders we have private folders. Private folders are of two types: User folders created by the system when a user is created in the Security Module and a public folder a Global Administrator has set as private. User folders have special user icons and their names contain the unique ID of the user they represent. These folders are only seen by the user who is logged in or the Global Administrator. User folders are the new "root" folder for the user. They may add and organize folders and files under these folders and create their own folder trees as needed. They again, are prepresented by physical folders on the actual server, so are a good way of isolating specific folders of files tied to a specific user, should you need to FTP off the server these files. These are private folders. Public folders set as private is a special feature that give Global Admins the ability to change a public folder to private, isolating the folder tree and its contents from all public and private users in the system. The Global Admin has their own private user folder, so this is really an extra feature you might never use. Keep in mind the Global Admin can log in and see ALL user folders, so they are not hidden from the Global Admins.

The following are more detailed security "rules" summarized for all folder types, which includes more detailed information about public and private folders in the system:

• Public folders are folders created by Global Administrators. They are not set as private, but may be set as private by them later. They are accessible to all users and admins, in general. This applies to seeing the folders and uploading and managing files inside them (not adding, editing or deleting folders). In the case of logged in users, they can still only see images they uploaded to these folders (not anyone else's images). The Global Administrator may see all user images and change them as needed. In a public Module system, all public users may add, edit or delete any file uploaded by the group. But, like logged in users, they may not change the folders themselves or create more folders for their own personal user.
• Private folders are either user folders, which are private to logged in users only in private system (viewable by public users in a public system), or public folders set to "private" by the Global Administrator. In both cases, the folders are private to the user only or hidden from all users but the Global Administrator. Public folders set to private are only viewable by the Global Administrator.
• If your ImageManager Module is set to "Public" in Security, then all folders are available for anyone on the Web who visits your Manager Module. They still cannot delete folders or add them, but can upload files and delete them without a login.
• If your ImageManager Module is set to "Private" in Security, then no one on the Web can access or see the Manager Module, nor your folders without a user login. This is what is referred to a private (user folder) system.
• Files uploaded to a public folder by Web users (no logins) can be seen by all users, and so edited and deleted by anyone. If you later make your ImageManager Module private from public, all Web user files can be viewed, edited and deleted by any login user or administrator in the system. Keep that in mind when switching the system from public to private.
• Files uploaded to a public folder by login users (logins) can be seen by public users (no login) if you later make your ImageManager Module public from private, in Security. So, those files are edited and deleted by anyone in a public Manager Module security setting. Keep that in mind when switching the system from private to public.
• In a private ImageManager security setup, all public folders are available to all users, but may not be added to, edited or deleted, except by the Global Administrator. However, files users upload to these folders, remain private to them, and are not seen by other users, escept admins.
• Even in a public system, all public folders may only be created, edited and deleted by Global Administrators who have logged into the system, if you elect to use a public Manager security setting. For this reason, we recommend you login as Global Administrator first, using the login panel located under the Module and Skin dropdown at the top of the web application, and create a folder system first, before allowing users to use your folder tree.
• The "root folder", or "Storage" folder, that is the parent to all folders and files, may not be deleted or renamed by any user, including Global Admins. It may only be changed by changing its physical name on the server, then using the "System/SystemsSettings.asp" variable setting, when changing its name. By doing that, you will lose ALL images and paths to images in folders will all be broken. If you elect to change this name, be sure to do it before uploading any files into the system, and testing it with a dummy folder and file upload.
• Only the Global Administrator may upload files to and from the root Storage folder. As such, any file uploaded into the root may only be done by Global admins, and so are seen only by Global Admins. Public users (no login) in a public Manager Module setup may view, move and delete files uploaded to the root folder, but may not upload files. Users in a private Manager Module system, after login, can not view, edit, delete or move any files under the root folder, but may do so under all child public folders of the root, including public files. For that reason, we do not recommend you use this root folder for storage of files as the Global Admin, unless you plan to have a very simple private ImageManager Module system where you are the only one allowed to upload and view images in the ImageManager Module.
• Moving Files - Files can be moved to other folders depending on who owns the file (user id assigned when uploaded), what folder its moved to (user private folder versus public folder), and the status of the user logged in. In general, all files moved from a public to a private user folder are assigned to the user id of the folder. This is a good way to "convert" public files to private files assigned to a specific user. Files moved from a private user folder to a public folder however retain their user id assigned, and remain private to that user. Of course if you assign a private ImageManager Module to a public status, all public users can then see the file in the public folder.
• Moving Files - Files moved to a public folder are still assigned to the user privately and available to them, even though they may not have permissions to upload more files to that folder. Files moved to a "user" folder inherits the user id of the parent user folder. So, if, for example, an admin moves a file from his private user folder to say, user2's folder, user2 can now login and see this new folder. In this way, the Global Administrator my move around images and allow users to see such files. Files the Global Administrator moves to public folder remain assigned to his id, so remain private and unseen by all other users, however. This is another difference between public and private folders.
• Creating Private Folders - The Global Administartor has a special feature in the "Edit Folders" icon area of the Folders section. When he/she goes to edit a public folder, a new "Make This Folder Private" feature appears under the edit name area of the folder edit section. By clicking the yes radio button, and submitting, the public folder can now be made "private". Such private folders are not assigned to a user but are special folders that only the Global Administrator has access to as far as veiwing the folder and its contents. In a public Module system, this is a powerful way to hide certain folders of files from even public users. Again, the Global Administrator must log in to affect this change and see the private folder. Such folders are also hidden from logged in users in a private system. In that case, there may be a need at times to hide folders lots of users are sharing. In that case, the Global Administrator has this special tool. Remember, he/she also has their own private "user" folder (user1) that is also held private in a private Module setup from all other users.
• Moving Files - Using the two special Global Administrator folders (private folders and admin user folder) it is possible for the admin to access another user's folder, and move files from the user to one of these two private Global Administrator folders. In this case you have two options based on the two types (private folders and admin "user1" folder): In the former case, moving a file there keeps the file assigned to the user id assigned, but its now housed in a hidden folder only the admin can access and see. Users cannot move files there nor see them. In the latter case, moving any file to the "user1" (global admin folder) changes the file to a private global admin file and sticks it in the private userid1 or admin folder as well. In that case, the file is reassigned to the admin as owner. This again allows you some creativity with how you move and manage files for all your users, depending on what your needs are.
• In a public ImageManager Module setup, no matter what userid is assigned to a file, all public users can see and move all files. In this case, because only public folders are accessible, the userid remains assigned to the file when moved from folder to folder. This allows you the flexibility to keep older private Manager settings where logged in users in the old system uploaded files, which were private to them. If you switch back to a private system, those folders remain hidden from all logged in users but the original user that uploaded it.
• Public users in a public system can never see Global Administrator files (files uploaded by a Global Administrator who are logged in as such) or private folders in the system, ever. This again allows Global Administrators, even in a public system, some ability to manage private folders and files as neededd.
• When you login as Global Administrator, you will see you also have your own private "user" folder called "user1". You are the first user created by default so this is your private "user" folder. You may NOT delete or alter this folder, as it contains private files you can control. If you elect to delete or alter this folder name on the server, you will lose access to all your files and the ability to store more files using this folder.
• When you login as global administrator, you will also see your private "user1" folder and those of other users you have created. Any folder that starts with "user" is given a special white folder with a user icon on it to identify it as a private user folder only you as admin or the user assigned, may see.
• User Folders - All users in the website, including global administrators, are assigned a special "private" folder where they can manage all their files and folders without others seeing them. Only global admins can see all folders and files, regardless of security. Anytime a new user is added in the Security Module, a new "user" folder is created and stored directly under "Storage" on the web server, with the id of the user after the word "user". This folder is only accessible to the user, when they login to the system. This folder is viewable to all users when the ImageManager Module is made public. Only the Global Administrator's "user1" folder remains private and hidden from view in a public Module setup. In a private login system, the user folder is private to the logged in user, and they may add folders and files under it as needed.
• Users can centrally manage and store all their files and folders under their personal "user" folder. Users can upload files under this folder, or create other child folders and manage and upload files there. This allows users to automatocally manage and secure their personal images under one centralized subfolder system on the web server. It also allows the Global Administrator the ability to also delete all user folders for users who have left the system, later. As new users are added, they in turn get their own users folders. Again, these are private folders, and cannot be made public later. We recommend you do not create "public folders" in a private Module setup, as described above, UNLESS you choose not to have logged in users, as these private user folders are the best place for your users to store their files.
• Keep in mind, deleting a user in the Security Module, where they are created, does NOT delete the user folder of files on the server. This prevents large numbers of important images from being deleted in the system. Keep this in mind as you manage users, as you may build up allot of redundant (user) images on the server over time.
• You can always tell what user a file is assigned to using the user folder "tooltip", or image rollover system. Simply rollover an image to the right while in the folder filter area of the web application. We have added this special tooltip rollover to all images in the system, which contains the name of the user/owner assigned to the file, so you, as Global Administrator, can login and see orphaned or misplaced images in the system from any folder. Simply move your mouse over the thumbnail of the image in the image listing when viewing folders of files.

Understanding Groups

Groups are another important organizational file assignment system, which allows you to quickly assign the same image to multiple categories, or groups you and your users create. Groups work much like folders, using a tree-like structure, where logged in users can create their own groups and assign images to them. They can in turn, create groups under these groups. Keep in mind, unlike folders, there are no special prebuilt user groups created when a user is added to the system. For this reason, all users logged into the system must create their own user groups in this area, and assign images from the system that are either public or ones they have uploaded. The power of groups again is the ability to assign multiple files to multiple groups, and do very flexible organization of image categorization. For your reference, we have provided a list of features specific to groups. Otherwise, the same general rules for folders apply to groups:

• Unlike public folders, where admins are are the only users who have the ability to edit and delete public folders, users and even public users can edit, add and remove public groups at any time. Users who are logged in, of course, cannot create public groups, but can create groups private to them (assigned to their user id). For this reason, its important to ONLY ADD PUBLIC GROUPS if all members and users (in either a public or private module settup) agree that such groups are shared and may be modified by anyone in the group. This allows you to bypass some of the rigid folder security found in the folder area and in groups, add the ability for multiple members to add/edit/delete groups and subgroups of files they share. Keep in mind this is not affected by files and folders assigned by logged in private users, who may create private subgroups under public groups and add private files to the public and private groups. In those cases, those files remain private, though the parent group is public and accessible to all users. Thats why its a bit "dangerous" to rely on parent public groups for managing user groups of assigned files. Therefore, we do NOT recommend you create public Groups in a private Module setup, unless necessary. If your ImageManager Module has been setup in Security for private access, its best to delete all public groups created from an older public setup. This will avoid problems later should you need to remove these groups, which could be shared by numerous logged in users.
• When users are logged in (regardless of a public or private ImageManager Module setup), any groups they create are private to them alone and not seen by other users in the system (except global administrators, of course, who can see everything). Admins can see all groups and add or remove groups, as needed. To know which groups are assigned to users, roll over the group name in the left hand listing or tree groups. That will tell you the user id that has rights to the group. You can also log in as that user to see "what they see" as far as groups and subgroups. Because users create private groups to start with, they can continue to add and organize subgroups under these and build very complex trees of organized groupings and galleries as needed. Just remember, if you log in as admin, you can delete these groups or change them, but that will or could impact hundreds of files controlled by that user. For this reason, we recommend, besides removing public groups created by public users in an earlier setup, you also tell all users what they can and cannot do as far as groups. But, the system is designed for flexibility, if you need that for your users. Also, remember, if you elect to add public groups, deleting or changing those will impact all users who have elected to associate files with them.
• Unlike the Folder system, in Groups, there is no need to convert groups to private status, so that feature does not exist in Groups. If you want a private folder for your Global Administrator account, simply login then create a group using your admin login. Its private to you and no other user, public or private, can see that group.
• Any group created by a non-public user is always visible to public users, when choosing to make the module public. So, for example, if you have been running a private ImageManager Module setup, where all your users are required to login to access the Manager Module, then all files and groups have been created with users id's mapped to those private users. When you turn off security for the module and allow public or all web visitors as public users to see the module groups created, then they will be able to see all public and private groups. All files, whether public or private, like folders, are also always seen by public users, regardless of userid status, or whether they were uploaded by logged in users. Again, this system allows you to convert what is a very private system quickly, to a public one where all public users can edit and view all groups and files associated with them.

ImageManager As Image Portal

Besides being a central repository for photos, the ImageManager may also be used as a quick image viewing tool, or even a portal area for sharing large volumes of photos with others. Even though the ImageManager is designed as a management tool only, and not a "viewer", you may decide the ImageManager is all you need for viewing and sharing images online. Any web visitor can access the ImageManager by default, if given "public" access (using the Security Module). All users who use the ImageManager as a public module and without a login can upload any image they want and see all images uploaded by all public users. This works well in a secure "Intranet" system, but is a bit dangerous on the World Wide Web. When used on the Web, we do recommend you secure the Manager Module. If you choose to secure the ImageManager Module by making it "private", you can then assign specific users to the ImageManager so that they can add, edit, and delete their own images managed inside your module. For this reason, the ImageManager is considered a "portal" for managing not just your own personal library, but that of others as well. To enable other users to use your site in this way, it is better to secure the ImageManager so that only you and your select users have access to the ImageManager. This way, you can manage all your images securely without the risk of others changing your images, or those of your users. However, if you are in an intranet environment, or feel secure with allowing others the ability to add their images publicly to your library without a login (public portal), then you may allow others to access the ImageManager and upload their own images to the application in that way. In that situation, the ImageManager becomes a true open portal for the upload and exchange of images. Keep in mind again, when the module is publicly accessible without a login, all users can upload and all users can delete and view all other user's images, including your own!

For more information about Securing ImageIsland, visit the Security Module and read about securing modules and assigning users to those modules.

New Modules!

The ImageManager works best when combined with other modules, which allow you to access images from the ImageManagerModule (i.e. ImageWebPages Module, etc.), secure them behind a login (i.e. Security Module), or extend their use into future modules you add to the product. Always keep in mind that each module in ImageIsland is designed to serve a small set of functions, but which combined with other modules, enhance the final web application and extend its feature set into new and more exciting areas. Together, modules make the site do what you need it to do! So, look for newer modules at our web site, as they may have newer features you have been looking for.

You may download new modules and skins, as well as get more information about this product and others we offer by visiting us online: http://www.giantisland.com/