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

director's view time/date for archival work is confusing #3021

Closed
lbestock opened this issue Dec 28, 2024 · 5 comments
Closed

director's view time/date for archival work is confusing #3021

lbestock opened this issue Dec 28, 2024 · 5 comments
Assignees
Labels
new-issue issue needs to be reviewed and labels and projects need to be added. Remove afterwards. request

Comments

@lbestock
Copy link
Collaborator

Using Director's View when looking at a team that is inputting archival data turns out to be a bit confusing because the dates displayed are invariably the creation dates of the records. Fine when you're in the field, and that matches the date of the thing itself, but confusing with archival stuff which then looks in DV as though it were from today when it is in fact from long ago. For OPs and loci, I would rather see opening dates.

@lbestock lbestock added request new-issue issue needs to be reviewed and labels and projects need to be added. Remove afterwards. labels Dec 28, 2024
@lbestock
Copy link
Collaborator Author

(Amusingly the CM for BUAP all comes in with less confusing dates because that is being automatically imported and it knows the record was actually created in 2012. But I guess even for CM it is the displayed date chosen by the archaeologist, the date of finding, not the date of record creation, that makes more sense.)

@urapadmin
Copy link
Collaborator

I do kinda get the point, but not all record type have a manual date. Sure, we could use the opening (or closing?) date of the locus, the "date of creation" (which appears to be too ambiguous a term in this context) for a unit and the "date collected" for the cm record.

But to me this also feels like you are using the director's view for something it isn't designed for -> looking at the particular data in detail. It is designed to see what your team was doing on that day or the day before.

However, I could make these changes for those record types. I don't see any harm for real time field work coming from it.

@lbestock
Copy link
Collaborator Author

In terms of getting a quick overview of what people had done, it kept making me think they had not entered the dates properly, which would be a real problem for the data. And is easy to do, since inputting the current date is the click of a button. It was a real use case, checking on the work of the BUAP team!

@urapadmin
Copy link
Collaborator

Kiosk 1.6.14

  • unit information has the unit_creation_date now as "creation"
  • locus information has the date_defined date as "creation"
  • collected material has the field "date" as "creation", which is the manually added date collected in the recording app.

@luizaogs
Copy link
Collaborator

luizaogs commented Jan 5, 2025

The dates are all from 2012 now (I'm looking at 27 XII 2024) so this looks fine I think.

@luizaogs luizaogs closed this as completed Jan 5, 2025
@github-project-automation github-project-automation bot moved this from Needs triage to Closed in testing Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-issue issue needs to be reviewed and labels and projects need to be added. Remove afterwards. request
Projects
Status: Closed
Development

No branches or pull requests

3 participants