Skip to content
This repository has been archived by the owner on Jan 25, 2018. It is now read-only.

do we need both uuid and dc_identifier_s fields? #53

Open
mejackreed opened this issue Apr 2, 2015 · 4 comments
Open

do we need both uuid and dc_identifier_s fields? #53

mejackreed opened this issue Apr 2, 2015 · 4 comments

Comments

@mejackreed
Copy link
Member

These seem redundant to me, unless I'm missing something?

@andrewbattista
Copy link
Contributor

I agree that these seem redundant. Mainly because I can't think of a scenario where we would want these two values to be different.

@drh-stanford
Copy link

dc_identifer_s is often the same as uuid but may be an alternate identifier. perhaps we don't need this flexibility since we already have layer_id_s and layer_slug_s which are alternate identifiers. in that case, i'd vote for dropping uuid in favor or dc_identifier_s to remain consistent with dublin core.

@andrewbattista
Copy link
Contributor

I second that vote!

@mejackreed
Copy link
Member Author

Shouldn't be too big a deal for GeoBlacklight https://github.com/geoblacklight/geoblacklight/search?utf8=%E2%9C%93&q=uuid

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

No branches or pull requests

3 participants