Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Welcome to the CollectiveAccess support forum! Here the developers and community answer questions related to use of the software. Please include the following information in every new issue posted here:

  1. Version of the software that is used, along with browser and version

  2. If the issue pertains to Providence, Pawtucket or both

  3. What steps you’ve taken to try to resolve the issue

  4. Screenshots demonstrating the issue

  5. The relevant sections of your installation profile or configuration including the codes and settings defined for your local elements.


If your question pertains to data import or export, please also include:

  1. Data sample

  2. Your mapping


Answers may be delayed for posts that do not include sufficient information.

Storage Location Tracking and Related objects

edited March 13 in Troubleshooting

I am fairly new to collective access and trying to look into an issue reported with our CA implementation.

We are hoping to display the 'Related objects' and 'Related Objects table' within the Storage Location Contents screen based on the current objects present in the selected location.

Step 1. Using the Object Editor --> Location Tracking screen(UI configuration screen shot below), we update the location of the object and save the object.
Step 2. Go to the Storage Location Editor screen for the above location, and we have 'Contents' screen (UI configuration screen shot below) and it has a list of the current contents of this location but we would like to display the current contents(objects) under the 'Related objects' element.

Is it possible to achieve this? Would the system update(delete when moved out from a location) the object relationship automatically when the object's storage location is updated?

This is our app.conf file - location tracking configuration.

app.conf configuration:

object_storage_location_tracking_relationship_type = storage_loc
movement_storage_location_tracking_relationship_type = moved_to
movement_object_tracking_relationship_type = part
record_movement_information_when_moving_storage_location = 1
movement_storage_location_date_element = removal_date

current_location_criteria = {
ca_movements = {
movement = {
date = removal_date,
template = ^ca_storage_locations.hierarchy.preferred_labels%delimiter=
}
}
}

Any help or advise on this is much appreciated...

Thanks,
Manu



Comments

  • The issue with "Related Objects" is there's no valid relationship type defined or a relationship type restriction preventing the objects from showing. Notice the blank drop-down menu.

  • edited March 13

    @Julia
    Can you explain where would this be configured? - there's no valid relationship type defined or a relationship type restriction preventing the objects from showing

    Regarding 'Notice the blank drop-down menu', are you referring the below screen? If yes, then my question is about this screen and how can we automatically display the objects under the 'Related Objects' section when an object is moved to the corresponding Storage Location. If I add the object manually by selecting it from 'Related Objects' drop down box then it will display there but doesn't get removed when the object is moved out from this location.

    Can this be achievable?

  • @Julia

    This is how the Relationship Type is configured - see below. Am missing something here? Please help.

  • The location tracking method you've chosen relies on movements to effect the location of objects in storage locations. From what you describe it sounds like the direct object-location workflow is a better choice for you: https://docs.collectiveaccess.org/wiki/Location_tracking#Direct_object-location_reference

    For the blank drop-down I was referring to here, which shows that there's no relationship type defined for this object x storage location bundle:

  • Digging a little deeper in this object-location relationship and its display, the related objects listing that one gets at one location only contains the objects specifically at that location.

    Is there a "natural" way to leverage the hierarchical nature of the location stack ( room 2 > aisle 23 > shelf 7 > container 18 ) to list the objects located at or below a location ( for instance, all the objects in shelf 7, that is all the objects that sit directly in shelf 7 and also all the objects in all containers located in shelf 7)? Is there a way to instruct a search by location idno to have that behavior?

    Searching for objects by location name after having configured a hierarchical indexing for locations sort of works, at least if the location names are carefully chosen to avoid ambiguities, but is there a way to exclude previous locations from the search? That is if object A was previously in shelf 7 but has now moved to shelf 9 but the relation still exists, with an end date (for traceability), we wouldn't want it to show up in a search meant to look for objects present in shelf 7, but by default it does.

    In short, what would the most expedient way be to list all objects (currently) present at or below a given location?

  • @Julia

    Thanks for your response. I tried using the object-location workflow but it appears that the 'Related Objects' relationship still exists when an object is moved from the Storage Location - see screenshot below. How can we get the object - storage location relationship to be removed when the object is moved out from the location?

  • That's correct behavior. The relationships aren't deleted and form a location history.

  • @seth
    Thanks for confirming this.
    Is there a way to 'download/export' the 'Current contents of a location' - Similar to the download option available in the 'related objects table' section?

  • Not currently.

Sign In or Register to comment.