Bug #5068
Application error trying to link a digital object to a description where the institution has a long title
| Status: | Invalid | Start date: | 05/10/2013 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | José Raddaoui Marín | % Done: | 0% | |
| Category: | Digital Content Management | Estimated time: | 8.00 hours | |
| Target version: | Release 1.4.0 | |||
| Google Code Legacy ID: | Tested version: | |||
| Sponsored: | No | Requires documentation: |
Description
Our digital objects are stored in the filesystem organized by institutions. Each institution has its own directory and it's represented by its slug or permalink. The slug column in the db is a varchar(255) and AtoM started truncating the slugs to 235 characters in v1.3.
Steps to reproduce:- Create a new institution with the following authorized form of name: "university of british columbia library rare books specialcollections university of british columbia library rare books specialcollections university of british columbia library rare books specialcollections university of british columbia library rare books specialcollections"
- Create a new archival description and link to the institution above
- Link a digital object to the new archival description
Related issues
History
#1 Updated by José Raddaoui Marín almost 9 years ago
- File long_repository_title_with_dig_obj.png added
- Status changed from New to QA/Review
- Assignee changed from Jesús García Crespo to José Raddaoui Marín
I couldn't reproduce this issue. The slug and the folder name are truncated, but linking digital objects works as expected. I tried linking an upload file, an external url and importing multiple files (see screenshot).
#2 Updated by Dan Gillean almost 9 years ago
- Status changed from QA/Review to Invalid
Like Radda, I tried several different times to reproduce, and found that though the slug truncated, everything still worked. Marking invalid for now.