[
https://jira.duraspace.org/browse/DS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28299#comment-28299
]
Ivan Masár commented on DS-1572:
--------------------------------
The manual announce of the repository metainfo URL would actually happens at
step 4), step 5) is an activity initiated by dspace.org. But it's all open to
discussion at this point. In the scenario I proposed there would be no need to
announce changes periodically, because dspace.org would harvest them
periodically. If a repository can't be harvested for an extended period (say,
unreachable for 1 month if harvests are done weekly), it can be discarded from
public display until it can be reached again.
> provide option to report repository metadata to dspace.org
> ----------------------------------------------------------
>
> Key: DS-1572
> URL: https://jira.duraspace.org/browse/DS-1572
> Project: DSpace
> Issue Type: Task
> Reporter: Ivan Masár
>
> http://www.dspace.org/whos-using-dspace
> There is a "Who's using DSpace" page on dspace.org that registers those
> repositories who wish to be registered and provides some metainformation
> about them:
> Name, URL, version, web UI, Country, launch date, public/private,
> institution, database, OS, content description
> In light of the planned migration of dspace.org to a new CMS (Drupal), we may
> want to re-think how this metainformation database is kept:
> 1) make it easier to submit the information
> 2) make it effortless to maintain for the dspace.org webmaster
> Most of the information could be gathered automatically and (optionally, at
> the discretion of each repo admin) submitted automatically to dspace.org.
> This is an umbrella ticket for the tasks necessary to achieve this.
> =========================================================
> Here are some suggested steps to achieve this:
> 1) Define which information we want to collect
> 2) Determine which information can be automatically detected from a running
> DSpace instance
> 3) Expose this information via a REST endpoint, but independently of a
> particular web UI (or, alternatively, in all web UIs)
> 4) Announce the availability of this endpoint to dspace.org during DSpace
> installation
> 5) Have dspace.org harvest this information periodically (once a month?)
> 6) Expose the information on dspace.org's "Who's using DSpace" page
> See also tickets linked to this ticket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
