Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Problem: can't arrange a SIP from backlog with long names #53
My transfer looks as the one below. To reproduce, re-create a similar structure. Start the transfer, move it to backlog and then try to arrange a new SIP from it.
The SIP never appears in the user interface. SS returns a 500 error but the Dashboard doesn't let the user know about the situation. SS throws an error (rsync can't locate files).
The problem seems to be in that the values that we're storing in
This is the schema of
CREATE TABLE `main_siparrange` ( `id` int(11) NOT NULL AUTO_INCREMENT, `original_path` varchar(255) DEFAULT NULL, `arrange_path` varchar(255) NOT NULL, `file_uuid` varchar(36) DEFAULT NULL, `transfer_uuid` varchar(36) DEFAULT NULL, `sip_created` tinyint(1) NOT NULL, `aip_created` tinyint(1) NOT NULL, `level_of_description` varchar(2014) NOT NULL, `sip_id` varchar(36) DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `original_path` (`original_path`), KEY `main_siparrange_2664b5aa` (`sip_id`), CONSTRAINT `main_siparrange_sip_id_601574f35f1ea7ec_fk_SIPs_sipUUID` FOREIGN KEY (`sip_id`) REFERENCES `SIPs` (`sipUUID`) ) ENGINE=InnoDB AUTO_INCREMENT=8 DEFAULT CHARSET=latin1
I recreated the same directory structure and placed it in a transfer called "long-dir-test-1":
I moved the transfer to backlog but when I try to arrange a SIP from it, the directory doesn't open to lower levels like it does for other backlog directories, i.e. it stays uncollapsed when clicking the arrow icon (note: this happens in both Chrome & Firefox)