DAM Reclaimer
DAM Reclaimer
Author:
|
Steven Valenti
|
Creation Date:
|
06-15-2016
|
Last Revised:
|
06-27-2016
|
Version:
|
1.0
|
The Creative Services Department uses a digital assets management system, Extensis Portfolio, to store and retrieve images. Previous version of Portfolio allowed development using AppleScript as a programming language. An Applescript Objective C program was created for previous version that allowed a list of filenames to be collected into a gallery from the DAM rather than collecting each file one by one. With the new version of Portfolio 2016 there is no longer a desktop client and users must use their web browser to connect to the server. Application development now needs to use Java, C# or PHP. The Creative Services Department wants to rebuild an application to reclaim the time spent on collection images for projects.
Project purpose
The purpose of this project is to rebuild the DAM Reclaimer application using Extensis Portfolio API with Java or C#. The use of this application will save time collecting assets from the DAM for projects since assets are not stored with a project.
Project goal
The project goal is to provide artist with an application to retrieve project assets from the DAM quickly so time is spent on project design and layout rather than collection images. The Creative Services Department needs an application rebuilt to replace their previous application that no longer functions with new version of Portfoio.
Project objective
The project objective is to create an application that can rapidly collect images from a list of filenames.
-
The application will be built using Java or C#.
-
The application user interface will allow selection of a method to generate a list from open InDesign file or text file within job folder.
-
The application will auto select the path to project folder when a retrieve method is chosen.
-
The application will override version number to select the highest number.
-
The application will use contains find then evaluate version if more than one item is found.
-
The application will allow the writing of text file of links to a project folder.
-
The application will display results of missing files and multi files.
Business goal
The business goal for this project is to decrease time spent on gathering assets for projects. Another goal is to select the highest version automatically rather than user determining the highest version.
Scope and expectations
The scope of this project is to rebuild the DAM Reclaimer application that will function with the new version of Portfolio. We also want to include the objectives above to improve the system. Any additional ideas will be considered that don’t change the major structure or functionality of the system. It is expected that some development work may change minor details or at times need to go about implementing an objective in a way not seen beforehand. All effort will be made to follow this outline as close as possible.
Roles and responsibilities
Management will be responsible for supplying any information about needed feature the application should contain. They will also assume the role of reviewing posted notification and directing changes during the development. Steven Valenti will assume the role of application development and will hold the responsibility of implementation when application is completed. Steven will also keep everyone updated on the development using a website. Management will participate in the role of development and directing changes during the development by posting subjects and comments on the project’s website located at https://svalentiblog.wordpress.com/category/dam-reclaimer/
Project assumptions and risks
-
Any changes to the projects workflow during development may prolong development.
-
Work load for other critical tasks will delay implementing this project.
-
Development in not fluent programming language may prolong development.
-
This project will be implemented when objectives are finished and management is satisfied with results.
Project Approach
Phase I: Presentation of objectives.
Phase II: Research API and determine which programming language we will use.
Phase III: Design user interface.
Phase IV: Design and code program logic.
Phase V: Testing of application.
Phase VI: Documentation and distribution of application.
Phase VII: Maintenance.
Phase I: Project proposal and objectives
This phase will be to present why this project is being initiated. We will gather all the ideas we want to incorporate into the application and design how the system should function.
Phase II: Research API
This phase will consist of gathering information about Extensis Portfolio’s API and determining which programming language we will go with.
Phase III: Design user interface
This phase will be to design the user interface and how the user will interact with the application.
Phase IV: Design and code program logic
This phase will be to build the actual code that will perform the tasks when user interacts with interface.
Phase V: Testing of application
This phase will be to test the overall functionality of the application and correct any issues when identified.
Phase VI: Documentation & Distribution
This phase will document how to use the application as well as actually installing on users virtual machines. We will probably hold a short session with users to go over the documentation and give opportunity to ask any question.
Phase VII: Maintenance
This phase will be the ongoing support to keep the application functional and make any necessary changes to accommodate additional needs.
Previous Application Documentation
|
Page
Share with your friends: |