Home | About

• Home
• Technical Solutions
• Data Management
• Licence Management
• Security
• Service Level Agreements
• Portals
• VO Management
• Technical Publications
• Grid Business
• Announcements
• Grid Middleware
• Existing Grids
• Grid Links
• Feedback

 

The File Management Pattern consists of the following components:

• Repository Location Selection: allows the user to choose the Grid repository location he / she is going to work with. This can be done by means of a direct URL, or by displaying a list of available locations. The history of previous user locations can be used, or a call-out to an external resource list or resource discovery service can be made, in order for the list of available locations to be prepared.
• File Repository: allows the user to view the directory structure of a given file repository and to choose files and directories to change their properties (like access rights or owner) or to delete them.

• View: presents on the portal files of different types from the Grid repository.

Two additional well-known operations have to be mentioned here:

• Download: allows the user to store given files in his / her local machine.
• Upload: allows the user to store files from his / her local machine in the given Grid repository location.

The entry point of the File Management Pattern is always the Repository Location Selection. After the user successfully points to an existing Grid Repository, it is opened in the File Repository component. The user can navigate through the directory structure of the Grid Repository and choose files or directories on which to perform operations (like change access rights, delete, download or upload files to repository). The view operation is carried out by another component of the File Management Pattern, the View Component. This component also works in the context of the chosen file and is used for displaying the content of files in the appropriate form. For example, the View component can present in the user’s browser only the needed –at that point in time- part of a given file or a scaled down view of large visualizations, in order to avoid downloading whole files. After finishing each operation or component usage, the control goes always back to the nearest component from which that operation initially started.