Skip to content
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.

Add items/timeline browse view #2

Open
jeremyboggs opened this issue Jul 25, 2011 · 2 comments
Open

Add items/timeline browse view #2

jeremyboggs opened this issue Jul 25, 2011 · 2 comments
Labels
feature

Comments

@jeremyboggs
Copy link
Member

Add a items/timeline view, to be able to see any query of items on a timeline from the items/browse view.
@waynegraham waynegraham mentioned this issue Oct 13, 2011
Closed
jeremyboggs pushed a commit that referenced this issue May 14, 2012
Adds view for all timeline items.
5a3e662 
Adds an 'items' view to the timelines controller, with a neatlinetime-json
context. This now means the JSON for a timeline's items is
/neatline-time/timelines/items/1?output=neatlinetime-json.

Removes neatlinetime-json context from ItemsController, since it is not
currently possible to retrieve all the items at once at items/browse. This
will likely make issue #2 a wontfix.
@jeremyboggs
Copy link
Member Author

would be nice to also include a way to create a new timeline from this view. In other words, search for items in Omeka's items/browse view, see the timeline, then click a "Save Timeline" button which would create a new Neatline Time record where users could fill out a title and description.

@erochest erochest added this to the NeatlineTime 2.1.0 milestone Oct 1, 2014
@erochest
Copy link
Contributor

This seems really interesting for changing the way omeka operates.

Might need to hook into:

And on the backend, it would be handled by:

  • after_save_ (hopefully the POST data isn't cleared out automatically); or
  • a new endpoint for the items_browse hook

@erochest erochest removed this from the NeatlineTime 2.1.0 milestone Feb 29, 2016
@cwsstkates cwsstkates mentioned this issue Apr 25, 2018
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@erochest @jeremyboggs