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

As a User I should be aware when data source records were updated last #30

Open
dimus opened this issue Nov 28, 2013 · 2 comments
Open
Assignees
Labels

Comments

@dimus
Copy link
Member

dimus commented Nov 28, 2013

Currently resolver does not give information when a particular source was updated. There are two ways of adding this information -- when someone queries data source itself, or as a part of each record. I think the best way would be to return it once for each data source mentioned in the output.

data sources
    data_source
        id 1
        title NCBI
        last_updated 2012-12-1
@ghost ghost assigned dimus Nov 28, 2013
@dshorthouse
Copy link
Member

By "updated", do you mean when the provider last updated their resource or do you mean when the resource was last harvested and incorporated into GNI? There should be both a last_updated and last_harvested entry to make it a little clearer to everyone involved.

@dimus
Copy link
Member Author

dimus commented Nov 29, 2013

I am not sure how can we know when a data source itself was updated as there is no any system at this time which would allow us to know that. So my idea was to add information from eml.xml about the date of dwca creation, and if it does not exist -- the date when actual upload did happen. It does sound like two separate categories though, so It does make sense to make 2 fields in a record. May be 'last upated' and 'last uploaded' ?

@dimus dimus closed this as completed Nov 29, 2013
@dimus dimus reopened this Dec 3, 2013
@dimus dimus added the ready label Aug 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants