Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation attributes to add - to make this the "master list" #53

Open
raprasad opened this issue Oct 13, 2016 · 1 comment
Open

Installation attributes to add - to make this the "master list" #53

raprasad opened this issue Oct 13, 2016 · 1 comment
Assignees

Comments

@raprasad
Copy link
Contributor

raprasad commented Oct 13, 2016

Attributes

  • fork - optional. Url indicating the fork the installation is running
  • contact_name - optional
  • contact_email - optional
  • related_tickets - optional. 0 to M url links

Functionality

  • Export to Excel
  • Map; don't escape installation descriptions
@raprasad raprasad self-assigned this Oct 13, 2016
@pdurbin
Copy link
Member

pdurbin commented Oct 14, 2016

The master list ("source of truth") of known installations is currently a private Google Spreadsheet at https://docs.google.com/spreadsheets/d/1EWDwsj6eptQ7nEr-loLvdU7I6Tm2ljAplfNSVWR42i0/edit?usp=sharing and @djbrooke and I recently reaffirmed this. If this is changing, that's fine, but let's all make sure we're on the same page.

At https://groups.google.com/d/msg/dataverse-community/fqyVxWZSDRA/6cfNvCEYBgAJ I mentioned that I think we should expose the data as JSON and add an optional field called oia_pmh_url (or harvesting_url). For privacy reasons, perhaps we shouldn't even store contact_name and contact_email in the database. I'm glad these have been flagged above as optional, at least. Maybe we don't need related_tickets either. I do think we should be tracking forks so I'm very much in favor of adding a fork field.

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

No branches or pull requests

2 participants