hi, it was a link on https://github.com/collectiveaccess/providence/releases/tag/1.6.2 but now everything is ok
thanks
Hi, Some feedback on 1.7 develop (all of which could be due to my inexperience) (1)I updated my system using git pull etc. git status says I am up to date. (2) after update I was unable to access my Object Description Editor Screen, this turned out to be corrupted metadata elements (mine) which I had dragged onto the screen in my previous version. (3) This corruption was that hierarchical lists which I had assigned to specific object types had got mixed up i.e wrong list assigned to wrong object type. (4) I corrected this by deleting the whole editor screen, fixing the metadata elements then rebuilding the screen. (5) Could then access my Object Description Editor Screen but there is now a blank space where the Hierarchical List Display should be. The search box is still there and works ok..(6) I deleted my jpeg and pdf files I had uploaded with add media representation and then reloaded them. Prefrences set to "Use Browser PDF plug in or fall back to document viewer. (7) Can view the jpeg full screen in the viewer but pdf does not open in browser pdf plugin opens in CA viewer and I can only see the thumbnails at the bottom of the screen in bookviewer. . In scroll view I can get three pages in the main screen but no scrolling. (8) In high resolution screen it is impossible to read the little drop down menu at the bottom right hand corner of the screen. Hope this info is of some use to you.
We'll do it later today if time allows
If those are indeed meant to be objects, you need to only map them to ca_objects (not ca_objects.name). Then, in your parameters, you must include both a relationship type and an object type. There's no need to expressly map the name (that will be handled automatically by the splitter). For example, {
"relationshipType": "related",
"objectType": "your_type",
"delimiter": ";",
}
"relationshipType": "related",
"objectType": "your_type",
"delimiter": ";",
}
I just updated to git 1.7 master as well, didn't change anything
Hi @juliaweist , those two names are actually the values of metadata elements for an object, not objects or entities themselves. I'm hoping to write the mapping for the object "Reel 1" for example, which has two names associated with it, "S.W. Hason" and "R.T. Fuller" (as examples). I'm hoping to have both of those imported as separate instances of the "Name" metadata element, if that makes sense
Hi,
I have an issue in setting value for ‘Remember last search or browse’ field in preferences. I want to set value of this field to "Clear previous search terms when performing a new search or browse". It displays save successful message when i update the value of this field, but still shows the old value i.e. "Retain previous search terms and results when performing a search or browse".
I am using Collective Access version 1.6.
Any clue how to solve this issue?
Thanks.
I have an issue in setting value for ‘Remember last search or browse’ field in preferences. I want to set value of this field to "Clear previous search terms when performing a new search or browse". It displays save successful message when i update the value of this field, but still shows the old value i.e. "Retain previous search terms and results when performing a search or browse".
I am using Collective Access version 1.6.
Any clue how to solve this issue?
Thanks.
@naeemmuhammad I am able to set the preference find on my 1.6 test system. Is the issue happening with all users or only certain logins?
please refer to these 2 pictures:
http://imgur.com/DJTJbZN
http://imgur.com/ELKRgN0
as you can see from the 1st pic, the location info below "Edit Art" (top left) is stuck to the previous location and not the current location. How do I fix this? We're using movement location tracking if that makes a difference. Thanks a lot! :)
Good Day, Some help please. I have created 22 metadata elements each restricted to a particular hierarchical list so depending on the New Object type selected only that list will appear on the Object Editor screen. They all work except for one where the hierarchical list does not appear. The list is imported and appears in the Manage Lists. The settings for the metadata element are the same as for the ones that work. The bind attribute is set correctly and the correct Display bundle is selected. If I use the search box at the bottom of where the hierarchical list should be I can access the list. This used to work ok so something is broken and I have been unable to figure out what. I include a screen shots which I hope clarifies my query. Apologies for the double upload.
@eriwm Try setting an explicit height for the hierarchy browser in the metadata element config
@naeemmuhammad Hmm, and you're running 1.6? Or 1.6.1 or 1.6.2?
@collectiveaccess Something weird going on - I have just dumped my database and reloaded the backup and I am getting the same fault with another metadat aelement - no display . Also the lists associated with a given element seem to get out of sync i.e the furniture list is now appearing in the "clothing" metadata element and the clothing list is appearing in a different metadata element.
We are facing some trouble with adding/deleting relationships to records, in Providence version: 1.6.1. After adding a relationship successfully it disappears when that record is opened in editor next time.
Example scenario:
Search an object in basic search, open that object in object editor, add a relationship to an entity. Go back to basic search open the same object again in object editor, newly added relationship is not visible. A refresh (ctrl+f5) shows the correct information.
It looks like a caching issue (as suggested by Seth on forum to our earlier question), however we have disabled caching as we are using cache_timeout = 0 (in brows.conf) and cache_timeout = 0 (in search.conf).
I also tried memcached, but it made no difference.
Any suggestion on how to solve this issue?
Thanks.
Example scenario:
Search an object in basic search, open that object in object editor, add a relationship to an entity. Go back to basic search open the same object again in object editor, newly added relationship is not visible. A refresh (ctrl+f5) shows the correct information.
It looks like a caching issue (as suggested by Seth on forum to our earlier question), however we have disabled caching as we are using cache_timeout = 0 (in brows.conf) and cache_timeout = 0 (in search.conf).
I also tried memcached, but it made no difference.
Any suggestion on how to solve this issue?
Thanks.
Make sure type restrictions on the editor bundle are set properly
Did you do it on the user interface editor by pressing the (i) icon?
@collectiveaccess when i store a collection description with 8217 characters the simple api shows the description when i add on more character the description isn't shown. also happening on the built-in service api. i don't need descriptions that long but in my simple api i need to get all related works of an collection plus their geolocation which results in the same problem after a certain amount of objects. i just tested it with the descripition to find out if it depends on the number of objects related or on some kind of character limit.
strange
File a JIRA for it and we'll look into it
Hi - Is the Place Authority that appears in the hierarchal display when you select 'New Place" the same as the Place Authority that appears when you select Manage Lists and Vocabularies -Place hierarchies or are they two different lists? e.g If I add a new country using either method should that country appear in the other list under Place Authority -?
@eriwm "New Place" creates a new place record (in the ca_places table). This defaults to a hierarchical interface since these records lend themselves to hierarchical nesting (ie California is part of the USA). The Lists & Vocabularies interface allows you to create new place types ie country, state, city etc which you can select when creating a new place record. Any other vocabularies you create will be created as "list items" (in the ca_list_items table) and are used as tags or subject headings