Week 1
Week 2
Week 3
Week 4
Week 5
Week 6
Eval 1
Week 7
Week 8
Week 9
Week 10
Week 11
Week 12
Week 13
Final Evaluation
Week 18
Week 19
Week 20
Week 21
Week 22
Eval 3
This project is targeted at updating how digital assets’ license, ownership and credits are stored, while considering how they can be displayed in a more detailed way. The system should be able to manage one or multiple owners, should they be individuals or institutions; manage credits, to one or more individual or institutions and the type of credit.
–> Completed Tasks
–> Ongoing Tasks
# | Status | Objectives | Associated Deliverables | issue(s) |
---|---|---|---|---|
1 | ![]() |
Design tables with their relationships with schema to handle the new data using cakePHP table and migration conventions | Perfect database schema for credit system implementation | !318 |
2 | ![]() |
Extending the API to accomodate new data for machines to access the data for the credit system | Write a rest API using cakephp for machines to access the additional information regarding digital assets for search results, and single artifacts | !318 |
3 | ![]() |
Extend the interface to display the information regarding the credits system where appropriate ( all the places where a digital asset can be displayed) | –Work on the views/template for the places where a digital asset can be displayed – Make adjustments so that the credit information displayed will align properly with the figma design and adjustments will not distort the interface aesthetics. | !318 |
4 | ![]() |
Collaborate with design challenge I person to feed the cite button for digital assets | –Accurate Citation button etc as well as other provision of good user experience for the credit system. | !318 |
5 | ![]() |
Create appropriate edition forms and bulk upload functionality for the addition/edition of credit data for digital assets | –Edit form and bulk upload functionality Implemented | !318 |
# | Status | Objectives | Associated Deliverables | issue(s) |
---|---|---|---|---|
1 | ![]() |
Address a related issue alreading existing which involves assigning proper roles (Author, Reviewer, Creator)for the authors contribution table. | List the respective roles (Reviewer, Author, Creator ) for event updates for artifacts while removing non essential columns | !630 |
2 | ![]() |
images management | The objectives of this issue are to put in place the infrastructure so displaying the web images and checking access will be done through the images table. This will also require minimal add / edit / delete functionality. A bonus objective is preparing a page that will harvest information about orphan web images so the admin can add them to the images table. | #885 |
–> Completed Tasks
–> Ongoing Tasks
–> Work Demonstration
Week | Objectives | Deliverables |
---|---|---|
1 |
![]() |
Perfect database schema for credit system implementation |
2 |
![]() |
–Preparing the models and other business logic for my project idea. – Start writing the logic in the controller for passing the right data to the views/template/in terface for displaying |
3 |
![]() |
–Rough UI Mockup for the interface. – Updating exisitng stated model to reflect the feedback from mentor |
4 |
![]() |
– Iterating and getting feedback from mentor |
5 |
![]() |
– Iterating and getting feedback from mentor feedback from mentor |
6 |
![]() |
–Evaluation |
7 |
![]() |
–Base on feedback, have Add and Edit credit feature for image credits for existing Images |
8 |
![]() |
Frontend File and logic coded |
9 |
![]() |
A functional controller files data-credits features |
10 |
![]() |
Delete and Edit Feature for data implemented |
11 |
![]() |
Granular information for 3d models for credit systems. |
12 |
![]() |
–Final submission of report, code and blog post |
Week 1
Week 2
Week 3
Week 4
Week 5
Week 6
Eval 1
Week 7
Week 8
Week 9
Week 10
Week 11
Week 12
Week 13
Final Evaluation
Week 18
Week 19
Week 20
Week 21
Week 22
Eval 3