Skip to content

Conversation

@tomdonaldson
Copy link
Contributor

An updated attribute of 2020-05-11 in the RofR is misleading since the resource was just updated for VOTable 1.5 and is likely preventing some downstream propagation of that update.

Copy link
Contributor

@msdemlei msdemlei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, you're right; the propagation to the harvesting registries should not be triggered by that date (for reasons discussed in sect. 5 of 2014A&C.....7..101D; not sure about the RofR implementation, but if it used the updated attribute, that'd certainly be a problem), but it's still wrong in principle.

Time for amending the submission checklist, I think.

@tomdonaldson tomdonaldson merged commit f84405e into master Jan 31, 2025
1 check passed
@tsdower
Copy link
Contributor

tsdower commented Jan 31, 2025

Confirmed the RofR was not announcing the VOTable resource using a recent from (http://rofr.ivoa.net/oai?verb=ListRecords&metadataPrefix=ivo_vor&from=2024-11-01), so the MAST overnight delta ingest hadn't pulled it. Once it's in the RofR with the new date, let me know. I'll test it again and pull it to our registry by hand if needed.

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

Successfully merging this pull request may close these issues.

4 participants