Skip to content
This repository has been archived by the owner on May 14, 2022. It is now read-only.

If a FileSet has a dc:title value, use it as the label instead of ebucore:filename #183

Closed
escowles opened this issue Nov 24, 2015 · 6 comments
Assignees

Comments

@escowles
Copy link
Member

The FileSet renaming updates the dc:title value. That should be used in the ScannedResource list of FileSets, if it's available.

@jpstroop
Copy link
Member

I wonder if rdfs:label might be more appropriate?

@escowles
Copy link
Member Author

👍 to putting the user-supplied page number in rdfs:label instead of dc:title.

@escowles
Copy link
Member Author

escowles commented Dec 7, 2015

On closer inspection, FileSet is just using dc:title because that's what CurationConcerns::RequiredMetadata does. So #230 just updates the views, but doesn't change the predicate being used.

Should we open a CurationConcerns ticket to change the predicate? I agree rdfs:label is a better fit, but on the other hand I see the attractiveness of saying every object has a dc:title value.

@jpstroop
Copy link
Member

jpstroop commented Dec 7, 2015

Ugh. I buy the "every object has a dc:title" argument. One could also argue that page numbers (regardless of the predicate) are contextual, and really belong on the Proxy. I'm not sure I'm ready to go there...

@escowles
Copy link
Member Author

escowles commented Dec 7, 2015

Yes, putting the page numbers on the proxies would make sense, but I agree it's an unnecessary complication right now. I would prefer using rdfs:label for the page numbers, but I could live with dc:title for now.

@jpstroop
Copy link
Member

jpstroop commented Dec 7, 2015

I think we should stick w/ title for the sake of interop., but it does make me a little uncomfortable.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants